{
  "checker": {
    "claims": [
      {
        "claim": "Start the local proxy and open the dashboard.",
        "command": "<guest-path>",
        "evidence": "Probe did not finish within the existing 120 second claim window.",
        "expected": "healthy status",
        "input": "GET /health",
        "kind": "claim",
        "outcome": "Probe did not finish within the existing 120 second claim window.",
        "source": "mcc-server`, then <http://127.0.0.1:8082/admin> (the desktop app does both for you).",
        "source_checked": true,
        "source_file": "README.md",
        "verdict": "blocked"
      }
    ],
    "cycle_checks": [
      {
        "claim": "Scheduled or looping main behavior",
        "command": "",
        "evidence": "README and entry points describe a continuously running proxy; no scheduled cycle trigger is documented.",
        "expected": "identify the product trigger",
        "input": "source inspection",
        "kind": "cycle",
        "outcome": "README and entry points describe a continuously running proxy; no scheduled cycle trigger is documented.",
        "source": "repository entry points",
        "verdict": "yes"
      }
    ],
    "details": {
      "argv": [
        "<guest-path>"
      ],
      "blocker": "HTTP health response verifies startup only; a full probe must exercise a useful product operation. Keep this as check=start for a partial result.",
      "bytes": 457197,
      "kind": "http",
      "response_checked": true,
      "response_excerpt": "healthy &mdash; unreachable,\n              refused for intercepting TLS, or cooling down after a refusal.\n              Either way, if every entry is paused, every address has been\n              removed or the chain file cannot be read, requests to that\n              provider are refused with a 503 that names the setting and move\n              on to your model fallback chain, and its card says so in red;\n              switch the chain off to send them from this computer on purpose.\n              MCC never rewrites a chain file it cannot read. Each card's\n              <em>What it can see</em> ",
      "setup_only": true,
      "status": 200,
      "url": "http://127.0.0.1:8082/health",
      "working": false
    },
    "evidence_strength": "nothing_checked",
    "example_checks": [
      {
        "claim": "Start server for local dashboard",
        "command": "",
        "deferred": false,
        "evidence": "Verified manually with mcc-server and stopped; HTTP replay represented by probe.",
        "expected": "documented command completes successfully",
        "input": "",
        "kind": "example",
        "outcome": "Verified manually with mcc-server and stopped; HTTP replay represented by probe.",
        "source": "README.md#Your first five minutes",
        "verdict": "blocked"
      }
    ],
    "status": "FAIL"
  },
  "deviations": [
    "First installer pipeline invocation had incorrect shell argument placement; reran through saved script."
  ],
  "fault_owner": null,
  "main_blocker": "HTTP health response verifies startup only; a full probe must exercise a useful product operation. Keep this as check=start for a partial result.",
  "operation": "Install and run local MCC proxy",
  "operation_scope": "Installed release and checked local health endpoint.",
  "outcome": "blocked",
  "plain_failure": null,
  "steps": [
    "Read README and usage guide.",
    "Ran scripts/install.sh --no-start; installed Python 3.14.0 and verified release wheel.",
    "Started mcc-server; observed {\"status\":\"healthy\"} at /health; stopped server."
  ],
  "stuck_step": "<guest-path>",
  "suggested_fix": null
}