[Reconciliation][P2] Publish the complete REST Context operation contract and MCP mapping #329

Parent workstream: #320
Epic: #318

Priority: P2 · Audit findings: API-DOC-05

Outcome and problem

The audited Context schema accepts 27 operations, but context.json describes only ingest/read/brief/save_brief/read_brief. The remaining 22 action contracts are undiscoverable to REST clients even though individually named OAuth tools expose them. Marketing lacks the Context spec entirely; that publication gap must be coordinated with the docs ownership work.

Scope and ownership

• Extend the contract from processContextOperation and releaseCaseOperationSchemas rather than inventing behavior.
• Document action-specific inputs/outputs, authorization, idempotency, readiness, cost/error semantics and supported provenance boundaries.
• Maintain an explicit mapping from REST action discriminators to delegated MCP tool names.
• Deliver under the existing app#2134 release-verification work and coordinate publication to both public surfaces.

Planning is tracked in Mono. Implementation and release PRs belong in the owning repositories under their current branch rules.

Acceptance criteria

• Every supported action discriminator has a resolvable request/response contract; at the audited baseline the expected action count is 27.
• Discriminated request examples validate against the corresponding API schemas, including representative ingestion, planning/execution, identity review, release-case and brief actions.
• REST-to-MCP mappings match the released registry and unsupported/private implementation details are not exposed as public operations.
• Published Context pages and LLM discovery are verified at the shipped docs revision, with rollout evidence linked to app#2134.

Evidence and existing work

Baseline: October 10, 2026 audit of July 10–October 10 merges. Recheck current source and existing tracker comments before implementation. Source findings do not establish authenticated production behavior.

• Source evidence 1
• Source evidence 2
• Source evidence 3
• Source evidence 4

Related existing work:

• Document Context Engine and guest account handoff docs#341
• Document saved Context Engine briefs docs#343
• Expose release metadata review cases through API and MCP api#973
• Fix MCP plugin review findings and expose context operations api#980
• [Context] Release the Context Engine with docs, rollback and deployed verification app#2134

Continue or reconcile the linked implementation work; this ticket owns the stated audit correction and does not replace the original feature tracker.

Source corrections released — October 12, 2026

The source accepts 27 actions; the preview reference now covers 26 provider-neutral request schemas and their delegated MCP names/annotations. It documents workspace ownership, disabled verification, Spotify-only pilot ingestion despite wider URL parser syntax, company_onboarding briefs, and detailed brief/snapshot results. plan_catalog_members remains implemented/callable but omitted from the preview union pending a stable provider-neutral module input; omission is not an access restriction. Keep the full-contract criterion open. Remaining root work: stable module identifiers/compatibility, rollout readiness, and a real hosted/connected-client journey. Schema tests and static MCP mapping do not close those gates.

All five approved source PRs are merged: API #1032, Marketing #152, Docs #373, CLI #26, and App #2242. Mono #373 records the five source references at e650245fe3267a08b94abbb75dc30a8a4108c020. The immutable provenance chain is API 0a590490c0e005045e4cbf399fe552dc41e6b9a3 → Marketing 62cc352c4c90d4578bea4352001fc459b7566e1b → Docs fa6dc9e761056066299dde4525552b0d14442f1f. App source is d13bdcb7b112ff0ed8d9d243ae7c6fd56f9a80d4; CLI source is a11bff0a36e339e94ad6921e55d82ec9472d0e35.

Verified publication: API, App and Marketing main checks pass and their canonical Vercel aliases are READY at those actual merge commits. All 231 merged Docs files/navigation match Marketing. Five representative Markdown pages pass on both public hosts; all 12 downloadable split specs on both hosts exactly match source. Canonical Marketing human pages and both LLM catalogs pass. Both human catalog pages show the 1–366 range; the separate playcount maximum remains 31.

Remaining release gates: CLI build/typecheck/77 tests passed, but npm publication failed with HTTP 404; the registry still serves 0.1.15. The release bot bumped source to 0.1.16 without publishing it. A valid NPM_TOKEN replacement and installed-registry-package verification are required; no token value belongs in an issue. Retained-host normal /llms-full.txt still returns cached v0.1.13/--room-id guidance (cf-cache-status: HIT, max-age=86400); a cache-busted read shows the corrected CLI/Context/Sites content. Its human /mcp still returns 405. Docs main's Mintlify deployment succeeds, but these URL/cache problems are not thereby resolved. Mintlify connection/routing repair and host cutover remain explicitly deferred. No hosted Context, media, OAuth/client, or unresolved-feature acceptance is inferred from this source release.