Recut the v1 lane around live Rust observation and interpreter dispatch authority

[gunbai-bot]

Roadmap reconciliation only. No implementation, and no finish line is accepted in this PR.

Scope is deliberately two files — dag/gunbc/roadmap_authority.dag and the regenerated ROADMAP.md.

What this recuts

v1-rust-source-observation did not exist as a node. #7562 delivers the observation mechanism but never added its row, so the dependency edges this lane needs pointed at nothing. The node is added, with two edges:

v1-rust-source-observation → v1-honest-frontier → v1-hand-queue-drain

That ordering is the point of the PR. It prevents hand-queue work from starting before the Rust population it drains is derived — which is how the queue previously became "whatever someone had inspected". A queue cannot be worked before its denominator exists.

The interpreter roster node is split into R0 and R1. v1-interpreter-primitive-roster described R0 while naming R1 inside its own first_slice, which made it un-acceptable: R0 is finished, but the node could not be accepted without appearing to claim an inversion that has not happened.

It keeps its durable identity and is now R0 only — derived-from-dispatch, mechanically preventive for the sites it covers, explicitly not structural, and acceptable at that narrower bar. A new v1-interpreter-primitive-dispatch-authority carries R1: the roster becomes the authority, arm identity and spelling/form lookup are generated from it, and hand Rust supplies only handler bodies behind an exhaustive match whose mismatch fails compilation rather than a test.

The quarantine edge is corrected. v1-interpreter-quarantine keeps two parents — that was never the defect. The defect was that its second parent named R0, and R0 itself admits that a whole new Rust dispatch site remains writable. So the quarantine could have been reached without the primitive denominator ever being closed. It now depends on v1-ci-floor-cutover and on the dispatch-authority node.

Two bars are also tightened: v1-hand-queue-drain now requires its count be derived by enumeration (a test-only consumer is not product-reachable), and v1-test-migration puts new Rust-only test debt explicitly out of bounds.

Status of the work this depends on

• Activate tracked Rust host observation with typed refusals #7562 supplies the observation mechanism, not acceptance. v1-rust-source-observation is not accepted here and should not be: its three live witnesses are excluded because the wet cadence is dark, and the exact-head live receipt is not scheduled. Its follow-on modeling corrections are in Make the Rust observation a call, type its identities, re-home seed growth #7607.
• Bring every match-arm primitive dispatch site in the v1 interpreter under one token authority (roster R0) #7558 closes R0, not R1. That is exactly why the node is recut before being accepted.

Verification

38/38 roadmap authority witnesses green by execution. ROADMAP.md regenerated, never hand-edited.

🤖 Generated with Claude Code

[gunbai-bot]

Fixed in cef828c6ea1. Review 46519 is correct and it caught a defect the recut itself introduced.

Splitting R0 and R1 into two nodes moved the inversion to v1-interpreter-primitive-dispatch-authority, but v1_interpreter_roster_seed_scaffold.target_roadmap_node still named v1-interpreter-primitive-roster — while its own deletion_condition describes R1 verbatim ("the .dag roster generates the interpreter's local dispatch identity and lookup, rather than the dispatch generating the roster"). So the scaffold said its discharge is owned by the node that explicitly disclaims doing the inversion, and the roadmap said otherwise. Two authorities for one discharge, which is the §3 defect the split was meant to sharpen rather than create.

target_roadmap_node now names the dispatch-authority node.

I also fixed a second reference the same recut staled, which the review did not name: added_hand_rust_accounting_note still read "which is why v1-interpreter-quarantine now depends on v1-interpreter-primitive-roster". The quarantine depends on the dispatch-authority node now, with the roster as that node's prerequisite. Same drift, one file over.

The part worth more than the fix: nothing checks this binding. No witness pins target_roadmap_node against the roadmap's node set, so a scaffold can name a node that was renamed, split, or never existed and all 24 witnesses still pass — which is precisely why this drifted silently instead of redding, and why it took a reviewer rather than the suite.

That is the same shape as the roster's hand-typed denominators that took main red for ~5 hours today (#7614): a derived mechanism with an unchecked hand-written reference sitting beside it. The derived half tracks reality; the hand-typed half rots; every name-level check passes throughout. I have not added a pinning witness here because the honest version is a cross-module resolution check (scaffold target → roadmap node identity), which is real work and wider than this roadmap-only PR — but it belongs on the same list as the denominator inversion, and I would rather state that than land a second hand-typed constant to guard the first.

24/24 roster witnesses green by execution.

— sent from clever-crab-111