{
  "checker": {
    "details": {
      "argv": [
        "/opt/prodex-bin/prodex",
        "info"
      ],
      "kind": "cli",
      "needs_browser": false,
      "needs_credentials": false,
      "returncode": 0,
      "scope": "product operation",
      "stderr": "",
      "stdout": "[ Info ] =====================================================================================================\nProfiles:               0\nActive profile:         -\nProviders:              none\nProvider routes:        none\nRuntime policy:         disabled\nRuntime preset:         default\nRuntime proxy contract: scoped gateway, policy-visible selection, bounded precommit retry, cheap hot path,\n                        quota/transport split, structured observability, connection reuse, profile-isolated\n                        secrets\nSecret backend:         file\nRuntime logs:           /tmp (text)\n[excerpt truncated]",
      "working": true
    },
    "status": "PASS"
  },
  "deviations": [
    "README Installation (`install.sh` from GitHub releases): the README's documented installer was used instead of a source build. The pinned source (Cargo.toml version 0.438.2) matches the release version, but cargo and rustup 1.99.0 (rust-toolchain.toml) were not installed and no source build was run. The installed binary is the published release, not a build of commit 8707027.",
    "README 'Utilities and diagnostics' / gateway docs (`prodex gateway providers --json`, also in docs/harness-modes.md): this command failed with `error: unexpected argument 'providers' found`. The pinned source's GatewayArgs (crates/prodex-cli/src/runtime_args.rs) defines no providers subcommand, so the README documents a command the CLI does not implement. The HTTP alternative, GET /v1/prodex/gateway/providers, could not be checked: `prodex gateway --listen 127.0.0.1:4000` exits with 'no active profile selected' (with and without --base-url), and `prodex gateway --provider gemini --api-key ...` exits with 'requires --api-key / GEMINI_API_KEY(S)' even when the key is supplied. The placeholder key was not a real credential, so that path is blocked here. No source or README change was made, because the working documented operation does not depend on it.",
    "Earlier stuck step `prodex doctor`: it now exits 0 with the current binary and reports Codex missing. It is not a failure of the operation; the missing Codex CLI is a prerequisite."
  ],
  "main_blocker": null,
  "operation": "Ran the README 'Utilities and diagnostics' command `prodex info` with the installed prodex 0.438.2 binary. It exits 0 and prints the profile, runtime, and version summary.",
  "operation_scope": "Verifies the installed binary runs and reports runtime and version state. It does not exercise any provider call, quota lookup, or Codex session. Unmet prerequisites: the Codex CLI is not installed (`prodex doctor --install` reports Codex CLI, Claude Code, Gemini CLI, Node.js, and npx as missing), and no profiles or API keys are configured. No credentials were obtained. No browser was used or needed.",
  "outcome": "working",
  "steps": [
    "curl -fsSL https://github.com/christiandoxa/prodex/releases/latest/download/install.sh -o /tmp/prodex-install.sh",
    "PRODEX_INSTALL_DIR=/opt/prodex-bin sh /tmp/prodex-install.sh (installed prodex 0.438.2; matches Cargo.toml version at the pinned commit)",
    "prodex --version",
    "prodex info (README 'Utilities and diagnostics'; exit 0; the probe operation)",
    "prodex profile list (exit 0, 'No profiles configured')",
    "prodex doctor (exit 0; reports Codex binary not found)",
    "prodex doctor --install (exit 0; reports missing optional prerequisites)"
  ],
  "stuck_step": null,
  "suggested_fix": "Repo documentation: correct README.md line ~103 and docs/harness-modes.md line ~124 so `prodex gateway providers --json` is either implemented in the CLI or replaced with the live endpoint GET /v1/prodex/gateway/providers, which needs a profile or a valid provider key to start the gateway."
}