autonomy preflight verify

POST a PreflightRequest to the runtime and render the decision

Synopsis

Submits a PreflightRequest to the runtime's POST /v1/preflight
endpoint and prints the resulting PreflightDecision.

The request file is JSON-encoded; pass "-" to read from stdin. See
docs/api/preflight.md for the schema.

Exit codes:
  0  outcome=pass
  1  outcome=repair_required
  2  outcome=deny
  >2 transport or schema error

Output:
  --output text (default)  human-readable summary + per-contract table
  --output json            indented JSON of the full PreflightDecision

Flags:
  --dry-run  Sends the request with the ?dry_run=true query parameter:
             the runtime evaluates the request and returns the same
             decision shape, but writes NO autonomy.preflight WAL
             frame. The preflight_id and audit_id come back empty
             — the verdict is for plan-validation only and cannot be
             used as an X-Autonomy-Preflight-Id binding on /v1/tool.
             Useful for planner agents iterating on candidate plans
             without polluting the audit trail.

Usage

autonomy preflight verify <request-file> [flags]

Options

      --dry-run              evaluate the request without writing a WAL frame; preflight_id + audit_id come back empty
      --output string        output format: "text" (default) or "json" (default "text")
      --runtime-url string   runtime URL (default: $AUTONOMY_RUNTIME_URL or http://127.0.0.1:7777)

Options inherited from parent commands

      --require-signed-manifest   Refuse to start if the SHA256SUMS release manifest or its cosign signature is missing/invalid (Tier 2 binary-integrity check; default: build-time compile-in via -ldflags -X, build-hardened artifacts=true, all others=false)

See also