Document retained evidence links and standard-only tools
Developers need a usable contract for linking an exact retained supporting version to existing records and retrieving the resulting receipts. This adds the three evidence actions to the canonical Context reference, with strict inputs, receipt/page responses, examples, access/retry/cursor guidance and separate standard-MCP versus delegated-OAuth mappings. Evidence tools remain excluded from delegated OAuth. A relevance receipt does not establish original-file provenance, reviewed facts, identity or rights.
Current review head: 29e9bf4e4a4fb2aad8a566e7d95dfde5ed9b57f3. The inventory now pins actual API #1049 merge 090f988060407e343d65dfdc3387156fb7dec0a5, replacing the earlier unmerged candidate pin. Current Marketing main 185fe344 is integrated. Both STATUS records are preserved; the imported implementation files match main. The posting reference, Context specification and both shared fixtures remain byte-identical to the previously reviewed ab94b651 source.
The existing producer guards preserve authored guidance, response references, field locations and nonempty examples, and reject evidence actions appearing in both connection maps. The maintained authoring tree remains content/docs/source; retained Docs must be generated from the eventual actual Marketing merge.
Validation on this prepared source: all 482 tests, 14 contract-producer checks, 11 docs checks, inventory/shared-fixture checks, TypeScript, lint and production build pass. Lint reports 39 existing warnings and zero errors. The Node 24/pnpm 10.30.3 build uses a synthetic public sign-in app ID; it does not verify authentication. Local production HTML, Markdown and Context spec requests all return 200; the served spec equals source semantically and keeps evidence actions out of the delegated map. The temporary loopback server was stopped.
Release state: this exact head is pushed for required CI, Vercel preview and independent UI delta review; those remote results are not inferred from the local checks. The API is merged and its database prerequisite was separately accepted; serving deployment verification and authenticated customer behavior remain separate evidence. No migration, provider/model call, customer write, manual deployment or main merge was performed here. Coordinator owns merge. After the actual Marketing merge, refresh retained Docs provenance from that merge and verify publication.