{
  "repo": "jiraport",
  "full_name": "tidbcloud/jiraport",
  "status": "scan_complete",
  "scan_started_at": "2026-03-26T15:30:00Z",
  "scan_completed_at": "2026-03-27T20:05:00+08:00",
  "expected_binaries": [
    {
      "name": "api",
      "path": "cmd/api/main.go",
      "status": "completed",
      "role": "primary_service"
    },
    {
      "name": "resolver",
      "path": "cmd/resolver/main.go",
      "status": "completed",
      "role": "worker"
    }
  ],
  "scanned_binaries": [
    {
      "name": "api",
      "output_file": "cmd-api"
    },
    {
      "name": "resolver",
      "output_file": "cmd-resolver"
    }
  ],
  "skipped_binaries": [
    {
      "name": "scheduler",
      "path": "cmd/scheduler",
      "skip_reason": "legacy_commented_out_entrypoint_no_buildable_main"
    }
  ],
  "files_generated": [
    "interfaces/cmd-api.json",
    "service-mapping/cmd-api.json",
    "interfaces/cmd-resolver.json",
    "service-mapping/cmd-resolver.json"
  ],
  "review_status": "pending_review",
  "review_participants": [
    "codex"
  ],
  "review_cycles": 0,
  "codex_rescan_at": "2026-03-27T20:05:00+08:00",
  "codex_rescan_verdict": "scan_complete",
  "codex_rescan_note": "Fresh codex rescan rebuilt the repo around the real runtime surface of cmd/api and cmd/resolver, excluded the legacy commented-out scheduler entrypoint, traced event-driven dependencies down through notification transitions, action command fan-out, Lambda-or-HTTP self dispatch, and Jira/Lark/Clinic/DevOps/MySQL conditions, and keeps cmd/resolver classified as a worker-style event runtime rather than a user-facing primary API.",
  "scan_progress": "2/2",
  "statistics": {
    "total_binaries": 2,
    "total_services": 5,
    "total_methods": 22,
    "output_files": 4
  }
}