autonomy doctor

Run operator-runtime health checks (docker, port 7777, WAL writability, etc.)

Synopsis

Run operator-runtime health checks and print a PASS / FAIL / SKIP
table with remediation pointers on FAIL.

Doctor is intentionally narrower than the demo preflight surface:
it covers the substrate operators need when running autonomy
outside the demo (production runtime, orchestrator deployment,
single-binary install), NOT the demo-specific surface (uv,
docker-compose v2 plugin, Python 3.12, demo binary build, demo
ports 5000/4318/4319/16686, etc.). The two coexist; the table
closes with a pointer to the demo preflight target for operators
who need demo-stack readiness too.

Exit code:
  0   every required check passed (SKIP allowed for unconfigured
      optionals — they don't count as failures).
  1   any required check FAILed, OR any required check SKIPed
      (defensive: a required check that silently skipped is a
      configuration bug, not a green light), OR any optional check
      FAILed (the operator opted in by setting the env var, so a
      failure on that path is a real problem).

Flags:
  --output text|json
      'text' (default): operator-readable table, one row per check,
      with a multi-line remediation block under each FAIL row.
      'json': stable schema for CI consumption — array of
      {check, status, detail, hint_id}.

Usage

autonomy doctor [flags]

Options

  -o, --output string   output format: text|json (default "text")

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)