factory-mcp-bootstrap

# Factory MCP bootstrap ## Contract | Field | Bound contract | |---|---| | Trigger | Someone outside Warp wants a third-party coding agent to reach a Warp Factory: "set up Factory MCP in Claude Code / Codex / Cursor", "add the factory MCP server", "connect my agent to Warp Factory" | | Authority | Human-only. Mints a 30-day API credential and writes a bearer-token MCP registration; both are credential and data-at-rest mutations requiring explicit human invocation | | Side effect | Confirms the oz CLI, runs oz login, mints a 30-day API key exported as WARP_API_KEY, writes a harness-specific MCP registration carrying an Authorization: Bearer header, reloads the harness, and performs read-only protocol verification calls | | Done | The MCP endpoint `{server_root}/api/v1/mcp/factory` is registered with a valid bearer token; `tools/list` shows the ten Factory tools; `list_factories` returns any non-auth-error response (empty allowed); the endpoint serves its factory setup document through both `resources/list` and `resources/read` without an auth error; the user is told setup is done and the agent hands off and stops | ## Inputs - Target harness: which coding agent to wire — Claude Code, Codex, or Cursor. Must be supplied. - Server root: the Warp Factory API root URL. Must be supplied if not inferable from oz context. - Factory creation: optional. Create a factory only when the user explicitly requests it; otherwise skip. ## Procedure 1. Confirm the `oz` CLI is installed by ...