docs-stale: upstream contract sources changed

[github-actions]

One or more upstream files that own Coven documentation facts changed after the recorded verification boundary.

• Workflow run: https://github.com/OpenCoven/coven-docs/actions/runs/35899047981
• Lock: docs/source-lock.json
• Evidence: docs-source-drift.json workflow artifact

Review the changed implementation or contract, update affected public pages, run pnpm verify, and advance the relevant verifiedAt and verifiedCommit only after that review is complete.

[BunsDev]

E2E repair and bounded remaining review — #95

Opened #95 at 44f10e33604c2abfb659baca965006a0c2e545f7 to repair two evidence defects without clearing this incident: browser verification previously never ran when freshness failed; freshness itself used timestamp-filtered history against repeatedly read main.

Exact-head hosted run 34814168620 now proves:

• complete documentation build/browser verification and clean generated tree: success;
• all 83 new CLI/gate regression cases: success;
• live pinned-tree freshness: failure, four actual path differences;
• canonical Verify documentation release: failure, correctly refusing publication despite browser success.

Both retained ZIP digests were verified after download. Freshness artifact 10336191598 / docs-source-drift-34814168620 has SHA-256 d54d84e78e30b8b34e2e50768a4f1323d05b86da516432431a19b42b9b530642. Unlike the prior report's null refCommit, this report pins upstream a566c26d2bf725a0dee6b4c290fe8718ab52375b against reviewed 9c7615a75c0a84dc9ef6f323bc542f30633189f0.

Remaining source-to-page review set

Watched source	Reviewed blob	Current blob
crates/coven-cli/src/main.rs	f77636f9b334e44559e3803e08eb5941296736c8	01e8398f7a4af79123fd0eb2347f3b3f4d9cc989
crates/coven-cli/src/api.rs	ab228d35ad0a717dd9e9ac19f16be0701a2c4c0d	a6d126c4aae80030594a1bd7b186e2d66e0e27aa
crates/coven-cli/src/setup/process.rs	86519963bfb8f0f5b37f16b1996f15d5107974e3	78d0f1b6415017fdf50db87f9d32de585c5bdb66
docs/API-CONTRACT.md	bed795fb70c2ed222a47ffefc8b190860d080e9a	14f5fdd65003a4ebcaf10bfd65665916f31e6ba9

The other eight watched path identities match. This narrows the review inputs; it is not a completed review of public claims. Do not use the large comparison's missing patch statistics as evidence that no semantic change occurred.

Next step: review these exact source differences against the lock's affected public sections, patch only inaccurate or missing contract claims, then advance the lock with an actual completed-review timestamp and rerun full canonical CI. Preserve #95's independent browser job and strict rollup. docs/source-lock.json has not been advanced, no gate has been bypassed, no production deployment is certified, and this issue remains open.