Let lane packets carry each component's registered receipts - #142

Summary

A layer-verdict packet's evidence_refs come from the ledger row, so a lane could not see a native receipt that the row never named. platform_status gives Linux accepted only to a native_proven or measured_comparison winner that cites a registered evidence/ file. Registered receipts such as native-tavily-cli-20260920, native-dagu-retry-tests-20260920 and native-headroom-mcp-20260920 were therefore invisible to both lanes. agent-lab-e9 raised this while explaining the WSL2 accepted drop.

Change: lane_packets.py --registered-receipts attaches registered_receipts to every candidate and sota_components_not_in_candidates entry.

• Contents: the {id, kind, path} of each manifests/evidence.json receipt whose component_ids names the component, sorted by path. This is the registered list that platform_status and component_matrix read, so the join is exact, not a text search.
• Note: a packet-level registered_receipts_note says that a receipt's kind and content, not its presence, decide the evidence class. That way the lanes don't upgrade a class on local-only evidence.
• Default: off, so the 2026-09-22 packets still reproduce byte for byte.

On the current tree with manifest-20260923, --withhold-labels, manifest-mode trading and the flag:

• 88 of 286 candidates carry at least one receipt;
• the three receipts above appear in 10, 3 and 1 packets.

This is a gate trust input (lane_packets.py), so it lands before the 20260923 re-record PR, which uses the flag.

Checks (local, this head)

• tests.test_lane_packets (68, including 3 new RegisteredReceiptsTests), test_record_verdicts, test_layer_verdicts and test_verdict_lane_vendoring: 203 tests OK.
• validate.py, evidence_manifest.py --check, landscape.py, build_verdicts.py --check and validate_convergence.py --all-recorded: all pass.
• Guarded gitleaks on the range: no leaks.

🤖 Generated with Claude Code