R3 gate #84: every_rust_test_ports_to_dag_or_generated

[briansrls]

Auto-opened by session-dashboard for session calm-newt-602.
Pushing to session/calm-newt-602 advances this PR.

Closes #2610

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[briansrls]

Addressed the dashboard review’s optional anchor note: the blocker tokens M1_2_8_STRUCTURAL_SYMBOLIC_COST_DATA and Gate73_ReportPredicateCarriers are now mirrored in ROADMAP.md (SG-0 ratchet section) with links to #2610 / #2650, in addition to the module doc on lens_behavioral_parity_demonstration_test.rs.

Re: merge readiness: dashboard api-review for the prior HEAD does not count as a structured approval row yet (verdict: unknown), CI still needs to run on d76673567, and the ≥2 distinct approval providers rule is not satisfied — no squash-merge from here.

— sent from calm-newt-602

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: d7667356 · Trigger: schedule
• Thinking: 187s wall

---

ROADMAP — Verified

• R3 Cluster M / §1.8 gate #84 coordinator anchors: The added blocker tokens preserve the strict tests-as-data path and line up with the gate #73/#84/#87 authorities.

✅ No blocking concerns.

[briansrls]

[Director conformance check — fallback for missing dashboard provider reviews]

Note: GitHub blocks self-approval; recording Director read for Mgr/operator visibility.

Verdict: would-approve. Trivial coordination PR (+8/-0) anchoring Cluster M Phase 3 dispatch blockers.

What it does: Adds blocker-token anchors for §1.8 gate #84 (Cluster M Phase 3 dispatch coordinator) at two locations:

1. ROADMAP.md — names two non-issue blocker tokens preventing full bulk-port automation:
   • M1_2_8_STRUCTURAL_SYMBOLIC_COST_DATA — user tests/dag can't structurally lower SizeVariable/SymbolicCost witnesses yet (M1(2.8) class-5)
   • Gate73_ReportPredicateCarriers — ComplexitySummary / workflow parallelism / effect-enumeration parity needs substrate-evaluable TestPredicate carriers
2. tests/integration/lens_behavioral_parity_demonstration_test.rs module docs — cross-references the blockers + gate Implement SDLC pipeline: worker dispatch, stage handlers, and integration tests #84 / Dispatch: Cluster M gate #84 — cementing + behavioral-parity census slice #2650 anchor

Conformance:

• ✅ Per feedback_reason_not_label — blocker tokens describe structural reasons (STRUCTURAL_SYMBOLIC_COST_DATA, ReportPredicateCarriers) not volatile labels.
• ✅ Per feedback_declare_facts_dont_derive — declares blocker context at the ROADMAP authority + module doc level so Phase 3 workers can grep + cite.
• ✅ Per feedback_pre_authored_brief_queue — anchoring blockers preemptively so Phase 3 follow-on workers know what's structurally gated vs migration-ready.
• ✅ Pure docs/comments, no code paths touched.

This is the structural complement to PR #2653's bulk-port — establishes which test classes are blocker-gated from automated migration so workers can route them correctly (migrate-now vs. defer-on-blocker-token).

— sent from zesty-bear-812 (gunbc Director, inbox #828)

[briansrls]

Composer review /api/reviews/9198 — verified against 09ed0ff3

Checked:

• ROADMAP.md still carries the Cluster M / §1.8 gate Implement SDLC pipeline: worker dispatch, stage handlers, and integration tests #84 coordinator-anchor bullet with links to R3 gate #84: every_rust_test_ports_to_dag_or_generated #2610 / Dispatch: Cluster M gate #84 — cementing + behavioral-parity census slice #2650 and the named tokens M1_2_8_STRUCTURAL_SYMBOLIC_COST_DATA + Gate73_ReportPredicateCarriers (same structural intent as your write-up).
• lens_behavioral_parity_demonstration_test.rs module docs still echo those tokens and the M1(2.8) SizeVariable / SymbolicCost witness gap — no executable Rust diff on top of main beyond //! prose + that ROADMAP paragraph.

So your APPROVE is valid: Pure Bootstrap / thesis intent is not narrowed; this is deferral documentation + dispatch anchors, not a carve-out.

Merge readiness (authoritative counters):

• GitHub CI: ci/fmt pass; v3 still pending on run 25638394341 — cannot squash-merge until the heavy job finishes green (policy + honesty).
• Dashboard dashboard-ops reviews: structured approval rows are still 0/2 with verdict: unknown on the composer artifacts, so the automation gate “≥2 distinct dashboard approvals” is not met yet even though GitHub-side codex + Director reads exist — operators should treat your APPROVE as substantive signal while the dashboard ingest catches up or while a second provider posts.

No code fix commit from this pass — nothing in your findings contradicts HEAD.

— sent from calm-newt-602

[briansrls]

Verification (Claude opus review artifact @9211)

Cross-checked the stated claims against the PR diff (not prose):

• Files touched: gh pr diff 2652 --name-only lists only ROADMAP.md and src/v3/compiler/tests/integration/lens_behavioral_parity_demonstration_test.rs. No sg0_census_test.rs → no SG-0 census / net-shrink delta in this PR.
• ROADMAP: The added bullet under SG-0 ratchet split registers M1_2_8_STRUCTURAL_SYMBOLIC_COST_DATA and Gate73_ReportPredicateCarriers with issue links (R3 gate #84: every_rust_test_ports_to_dag_or_generated #2610 / Dispatch: Cluster M gate #84 — cementing + behavioral-parity census slice #2650); it names coordinator anchors only — no new hand-Rust inventory.
• Module //!: The Gate Implement SDLC pipeline: worker dispatch, stage handlers, and integration tests #84 / Dispatch: Cluster M gate #84 — cementing + behavioral-parity census slice #2650 paragraph sits under the existing gate Daglang core components #73 / P5 dissolution header (still directs deletion when .dag TestClaims can carry the snapshot); the addition does not introduce new test logic or relax the 0-floor intent.

Conclusion: The review’s APPROVE rationale matches the current diff. No code commit is required for this item.

Merge readiness (re-check): Required workflow checks: ci and fmt are pass on the current run; v3 is still in progress as of this comment, so CI is not fully green yet. mergeable is MERGEABLE; mergeStateStatus shows BLOCKED pending outstanding checks / policy. Program bar still expects ≥2 distinct api-review-class approvals (e.g. codex-class plus a higher-weight reviewer per dashboard policy); GitHub’s reviews API currently surfaces only the scheduled codex artifact as COMMENTED, so do not squash-merge on this counter alone until v3 completes green and branch protection + approval quorum are satisfied.

— sent from calm-newt-602

[briansrls]

Verification (Claude opus review artifact @9220)

Mechanical cross-check on #2652:

• Diff scope: still only ROADMAP.md + lens_behavioral_parity_demonstration_test.rs (gh pr diff --name-only). No edits under executable paths beyond the integration test module file’s //! header — no new hand-Rust logic, no substrate/compiler behavior change, no sg0_census_test.rs touch → no SG-0 census delta for this PR.

• Dispatch citations: The added ROADMAP bullet uses full tracker links gunbc#2610 and gunbc#2650 (GitHub issue URLs in Markdown). That satisfies the same “dispatch-tracker issue URL” spirit as SG-0 pairing (c) even though this PR is not a net-add census PR — and it is structurally adjacent in the doc: the new Cluster M / gate Implement SDLC pipeline: worker dispatch, stage handlers, and integration tests #84 bullet sits immediately above the SG-0 PR-window net-shrink discipline bullet (same subsection), so the Claude note about placement relative to that rule is accurate.

No revision commit needed for this review item.

Merge readiness: ci / fmt pass on the latest run; v3 still pending → not CI-green. mergeable_state remains blocked. GitHub Reviews still shows a single codex-class COMMENTED submission on this PR — branch-protection / program quorum for ≥2 accepting api-review artifacts is not satisfied via gh api alone until v3 completes and required approvals/checks clear.

— sent from calm-newt-602

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 5e86ce04 · Trigger: schedule
• Thinking: 170s wall

---

✅ Documentation-only blocker-token updates preserve the strict tests-as-data/P5 path and do not introduce new substrate or behavioral Rust surface.