{
  "repo": "data-service-example",
  "full_name": "tidbcloud/data-service-example",
  "status": "scan_complete",
  "scan_started_at": "2026-03-31T19:30:00+08:00",
  "scan_completed_at": "2026-03-31T19:30:00+08:00",
  "expected_binaries": [
    {
      "name": "next-frontend",
      "path": "package.json",
      "status": "completed",
      "role": "primary_service"
    },
    {
      "name": "gateway-api",
      "path": "pages/api/gateway/[path].ts",
      "status": "completed",
      "role": "primary_service"
    }
  ],
  "scanned_binaries": [
    {
      "name": "next-frontend",
      "output_file": "next-frontend"
    },
    {
      "name": "gateway-api",
      "output_file": "gateway-api"
    }
  ],
  "skipped_binaries": [],
  "files_generated": [
    "interfaces/next-frontend.json",
    "interfaces/gateway-api.json",
    "service-mapping/next-frontend.json",
    "service-mapping/gateway-api.json"
  ],
  "review_status": "pending_review",
  "scan_progress": "2/2",
  "current_binary": null,
  "codex_scan_at": "2026-03-31T19:30:00+08:00",
  "codex_scan_verdict": "scan_complete",
  "codex_scan_note": "Meta validation showed data-service-example was incorrectly modeled as a pure library. The source-backed scan confirms an example Next.js application with two runtime surfaces: the frontend pages and a Next.js API route that proxies Data Service requests. The repo is an example app, not a reusable library."
}