{
  "id": "page:docs-harness-features-backlog-gaps-json-interaction-gap-json-001",
  "_kind": "Page",
  "_file": "wiki/docs/harness-features-backlog/gaps/json-interaction/gap-json-001.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/harness-features-backlog/gaps/json-interaction/GAP-JSON-001.md",
    "sourceKind": "repo-docs",
    "title": "GAP-JSON-001: JSON API for Run Creation and Management",
    "displayName": "GAP-JSON-001: JSON API for Run Creation and Management",
    "slug": "docs/harness-features-backlog/gaps/json-interaction/gap-json-001",
    "articlePath": "wiki/docs/harness-features-backlog/gaps/json-interaction/GAP-JSON-001.md",
    "article": "\n# GAP-JSON-001: JSON API for Run Creation and Management\n\n| Field | Value |\n|-------|-------|\n| Category | json-interaction |\n| Priority | Critical |\n| Effort | L |\n| Status | Partial |\n\n## Description\nProgrammatic JSON API to create, iterate, and manage runs without CLI shell invocation. Enables headless orchestration, CI/CD integration, and web UI backends.\n\n## Current State\nMCP server (`mcp:serve`) exposes `createRun` and other tools as JSON-in/JSON-out. SDK exports `createRun`, `orchestrateIteration` as importable functions. However, no standalone HTTP/REST API exists, MCP coverage is incomplete (no iterate/status/events tools), and the programmatic API is undocumented.\n\n## Target State\nProgrammatic API for run lifecycle: create, iterate, status, events. JSON request/response protocol. Usable from Node.js, Python, or any HTTP client. No shell invocation required.\n\n## Dependencies\n- [GAP-REMOTE-007](../remote-integration/GAP-REMOTE-007.md) -- host contract layer as API surface (note: co-located in M1 per roadmap, not a hard blocker; roadmap lists no blocking dependency for JSON-001)\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| CLI commands | `packages/sdk/src/cli/` |\n| MCP server | `packages/sdk/src/mcp/` |\n| Runtime | `packages/sdk/src/runtime/` |\n\n## Recommendation\nPhase 1 implementation. Extract CLI command logic into importable API functions. Expose via both direct import and HTTP/MCP endpoints.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-harness-features-backlog",
      "to": "page:docs-harness-features-backlog-gaps-json-interaction-gap-json-001",
      "kind": "contains_page"
    }
  ]
}