project_tool_review

Purpose and availability

Build-only candidate-scoped project tool lifecycle; bounded isolated execution, no host/network access or engineering approval.

Before invocation

Inspect the current definition and exact version/project binding before invoking. Required fields, enums, bounds and consent fields below are authoritative. Omit no required input and do not invent unavailable values.

Exact input schema

{
  "additionalProperties": false,
  "properties": {
    "payload": {
      "additionalProperties": false,
      "properties": {
        "fixtures": {
          "items": {
            "additionalProperties": false,
            "properties": {
              "expected_sha256": {
                "pattern": "^[0-9a-f]{64}$",
                "type": "string"
              },
              "input": {
                "type": "object"
              }
            },
            "required": [
              "input"
            ],
            "type": "object"
          },
          "maxItems": 8,
          "minItems": 1,
          "type": "array"
        },
        "tool_id": {
          "pattern": "^[0-9a-f]{32}$",
          "type": "string"
        },
        "version_id": {
          "pattern": "^[0-9a-f]{64}$",
          "type": "string"
        }
      },
      "required": [
        "tool_id",
        "version_id",
        "fixtures"
      ],
      "type": "object"
    },
    "request_id": {
      "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
      "type": "string"
    }
  },
  "required": [
    "request_id",
    "payload"
  ],
  "type": "object"
}

Results, errors and safety

Inspect the structured result and retained IDs/artifacts. Errors, unsupported profiles, missing data and cancellation remain explicit. A successful call grants no human engineering approval. Do not retry inference automatically. See Workflows, History and Project tools.