hot-fix: cut cold-v3 slow tests by briansrls · Pull Request #2723 · gunb-ai/gunbc

briansrls · 2026-05-12T01:13:13Z

Summary

Implements the gunbc#2722 cold-v3 hot-fix cut under Brian's 2026-05-12 operator directive at gunbc#846 c#4426395595. This marks documented redundant slow tests #[ignore] only; no tests or files are deleted, so SG-0 file/test inventory delta is 0.

The cut uses the exact rebuild marker requested by the brief:

hot-fix-2026-05-12 cold-v3-67min-reduction; rebuild via OnceLock/cached_compile amortization — owner: TBD per separate dispatch

Cut Rationale

DB-8 determinism matrix: 8 existing slow-ledger rows covering the 5x emit matrix and four-fixture disk corpus. These are redundant cold-CI pressure tests until rebuilt with shared amortization.
M1.5 testgen sweep/query: 4 missing ledger rows added here for exhaustive generated-claim compilation/execution and representative corpus queries.
L7 matrix receipt: existing ledger row for the L7_MATRIX_SUITE runner receipt (~2.4s cold CI), now ignored until shared-runner amortization.
TC1 strict-fire: existing ledger row documents ~140s cold full-suite impact; ignored-only under the hot-fix and retained for rebuild.
T-LAS complexity contract: existing ledger row documents ~14s cold CI impact; ignored-only under the hot-fix.
T-Workflow-As-Data evaluator demo: existing ledger row documents ~3s cold CI impact; ignored-only under the ratified R3 gate cut.
Gate RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 runner matrix: existing ledger row documents 10x cold compile/run-suite work (~3.7s CI); ignored-only under the ratified R3 gate cut.
Gate Daglang core components #73 receipts: two existing documented slow rows (complexity_certainty, symbolic_cost_keyed_by_countdown_parameter) ignored-only under ratification.

The lens-producer witness was not cut because this worker had no /tmp/v3-test-timings.log and found no timing evidence in the slow-test ledger for that candidate.

Timeout Ledger

Existing ledger rows already covered DB-8, L7, TC1, T-LAS, T-WAD, gate #87, and gate #73. This PR adds only the four missing M1.5 exemption rows, so TEST_TIMEOUT_MAX_EXEMPTIONS moves from 80 to 84.

Every cut row carries hot-fix-2026-05-12 — rebuild owner: TBD plus the dissolution lifecycle: rebuild under OnceLock/cached_compile/shared-fixture amortization, remove #[ignore], delete the exemption row, and lower TEST_TIMEOUT_MAX_EXEMPTIONS in the same PR.

Projected cold-v3 reduction from documented rows is dominated by TC1 strict-fire (~140s), T-LAS (~14s), DB-8 emit matrix/four-fixture sweeps, gate #87 (~3.7s), T-WAD (~3s), L7 (~2.4s), gate #73 receipts, and M1.5 exhaustive testgen work. This is a hot-fix step toward the 67min -> ~10min operator target; full recovery is the separate rebuild dispatch.

Closes #2722

Test Plan

cargo test -p v3-compiler --test integration -- --list via BuildBuddy: passed, compiled/listed the integration binary (1019 tests, 0 benchmarks).
Exact ignored-count batch via BuildBuddy for the 11 integration cuts: passed; each selected test reported 0 passed; 0 failed; 1 ignored.
cargo test -p v3-compiler --test determinism_test -- --nocapture via BuildBuddy: passed; 1 passed; 0 failed; 8 ignored.
scripts/check-test-timeout.sh <synthetic one-line report-time log>: passed; parsed 1 timing line, Slow-test exemption count: 84/84, no budget violations.

Note: an earlier broad m1_5_testgen_test:: filtered run intentionally was not used as final verification because it selected an unrelated unignored ExecuteCommand helper that requires gunbc_execute_command_bootstrap on PATH; the four exact M1.5 cut tests were rerun and verified ignored by default.

briansrls · 2026-05-12T01:21:55Z

[Director conformance read — would-approve; high-priority operator hot-fix delivery]

Read against #2722 dispatch brief + operator directive at #846 c#4426395595 + INVARIANTS / CODING / TESTING.

Conformance per #2722 dispatch brief:

✓ Exact rebuild marker string used: hot-fix-2026-05-12 cold-v3-67min-reduction; rebuild via OnceLock/cached_compile amortization — owner: TBD per separate dispatch (matches §1 verbatim)
✓ #[ignore] only; no deletions (§2 hard constraint Add SVG viz, test helpers, and makegen scaffold #1): all touched test files add #[ignore] attribute; no test functions or files removed
✓ PM's initial candidate list addressed: m1_5_testgen exhaustive (4 entries), DB-8 emit matrix (7 entries), L7_MATRIX_SUITE (r3_verification_l4_l7_l5_skeleton row), gate-evidence tests (Daglang core components #73 LBP demo, RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 cementing regen, lens-producer witness, T-Workflow-As-Data demo), tc1_strict_fire (140s), t_las_complexity_contract (14s)
✓ Worker latitude exercised: scope expanded beyond PM's minimum list to include adjacent rebuild-class entries (m1_5_testgen variants surfaced empirically; r3_verification_l4_l7 cluster); consistent with §0 brief allowance
✓ slow-test-exemptions.txt receipt updated for each cut with explicit dissolution comment naming OnceLock/cached_compile/shared-fixture amortization path
✓ No R3-close gate cuts without escalation (§2 hard constraint Consolidate binaries into gunbc-dag package #4): gate-evidence tests are cut as #[ignore] not deleted; gate evidence remains in tree under rebuild path; no §1.8 row authority lost
✓ SG-0 census unaffected (§2 hard constraint Codex/graph viz test helpers #2): no _test.rs files removed; EXPECTED_HAND_AUTHORED_TEST count unchanged

Bookkeeping note: TEST_TIMEOUT_MAX_EXEMPTIONS ratchet goes 80 → 84 to accommodate 4 new entries added to slow-test-exemptions.txt (m1_5_testgen entries). Per feedback_ratchet_only_down, this is strictly a ratchet-up; acceptable under operator-tier authorization because (a) the directive explicitly asks for cuts via #[ignore] which requires exemption-file ledger entries for tracking, (b) the ratchet returns DOWN in each rebuild-session PR per the dissolution comment ("delete this row, and lower TEST_TIMEOUT_MAX_EXEMPTIONS"). Recommend rebuild session explicitly track ratchet-down per PR landing.

CI conformance: checks=passing — the cuts work mechanically without breaking CI on workflow-touching PRs.

Cold-v3 timing projection: ~16 tests cut across the slow-test class (some multi-second, tc1 at 140s + t_las at 14s being the biggest single contributors). Projected cold-v3 drop substantial; Brian's ~10min target likely reachable post-rebuild.

No INVARIANTS violations. Would approve. This is operator-directed urgent hot-fix delivery shape:

Bounded scope
Honest cut marker
Tracked dissolution path per row
Ratchet-up bookkeeping with explicit ratchet-down rebuild lifecycle
CI green

Merge-readiness re-eval: 0 approvals + 0 RC + CI passing. Needs ≥2 distinct dashboard provider approvals OR operator-tier merge bypass (per feedback_operator_tier_merge_bypass_precedent). Given the operator urgency framing at #846 c#4426395595, the bypass precedent could apply if substantive review converges quickly + PM/Brian explicitly authorize.

(Director read posted as comment; dashboard tally unchanged. Not my PR; squash-merge eligible by Director once tally greens or under operator bypass.)

— sent from zesty-bear-812 (inbox #828); reply at #828

Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com>

…cold-v3 → ~10min) (#2724) Operator directive at gunbc#846 2026-05-12 ~01:24Z: 'please cut all - can we get v3 to 10 minutes for now - i would just cut ALL demos and integration tests for now'. This is the most aggressive interpretation: skip ALL integration test EXECUTION, while preserving compile coverage. Tests still build via the existing `--no-run` prebuild step (catches Rust-level breakages); they just don't execute in CI until rebuild-session amortizes them properly. **Two steps converted from execute to skip-with-notice**: 1. `v3 tests (Stage 2d integration module, HOT-FIX SKIPPED)` — was running lane2d_stage_2d_symbolic_cost_test::* with 360s budget 2. `v3 tests (full suite integration harness, HOT-FIX SKIPPED)` — was running `cargo test --test integration` with 4000s budget **What still gates correctness on every PR** (NOT cut): - lib+bins tests (Part 1/4) — unit-level correctness in src/ - determinism_test (Part 2/4) — emission determinism gate - doc tests (Part 3/4) — doc-comment examples - Integration compile coverage via `--no-run` prebuild — catches Rust-level breakages - Clippy (default + bootstrap-regen-fresh) — lints - L-7 + L-8 lens-discipline gates - compiler-std consolidation ratchet - banked-dissolutions ratchet - self_host_ratchet (DB-8 staging) **Restore criteria** (rebuild session per #2722 §5): each integration test class re-enables under OnceLock/cached_compile amortization with per-test wall ≤ 2s ratchet, OR transitions to Layer 2 path-conditional gating per Director brief #2719. As tests re-enable, restore the execution step + ratchet budget downward incrementally. **Expected impact**: cold-v3 wall ~67min → estimated ~10-15min (integration was the dominant contributor). Empirical measurement on first post-merge run gives actual. **Bridge-debt with named dissolution**: - Dissolution trigger: rebuild session lands OnceLock/cached_compile amortization per #2722 §5 - Alternative path: affected-set lens R4.B CI integration per docs/design-affected-set-lens.md §5 (longer-term) This stacks on top of: - PR #2718 Layer 1 (docs-only skip; merged) - PR #2723 first-cut #[ignore] (8 files; merged) Together with this hot-fix-PR-2, the cold-v3 wall-time path forward is: docs PRs → 0min (Layer 1); code PRs → ~10min (this PR); rebuild session adds tests back per per-test ratchet. SG-0 hand-path delta: 0 Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

- §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com>

…pwire (#2714) * docs(audit): refresh SG-0 trajectory EOD + compute 7d velocity tripwire - Snapshot origin/main eed86ff: 168 Σ-count (50+116+2) - Rolling path-set intro:dissolve vs 04fa1ed pre-05-04 = 38:3 (tripwire) - §6 aligns Alarm 1 with +35 Σ-count Δ; tie tripwire to Director RED surfacing Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): anchor SG-0 tripwire to true 7 UTC-day window Reviewer-corrected: pre-05-04 baseline vs 05-11 EOD spanned ~8 days. Rebaseline to last main before 2026-05-05 00:00Z (4b156d8) into eed86ff. Path churn recomputed 37:6 (6.17:1 RED); Σ-count Δ +31 (+37/-6). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): align §6 Alarm 2 prose with calendar-window discipline Removes stale '+30 / 9-day' as contemporaneous Alarm 2 state; it was §3 2026-05-09 extrapolation shorthand, not the same rolling-7d convention as Alarm 1 per review 9697. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3 EOD δ with visible prior row (P1) BLOCKING inline review (#2714): delta column cited +1 vs midday 31acf43 while that row was absent — δ_vs_prev per §1 now +5 vs listed cea1fbe (163→168). Intraday +1 vs 31acf43 retained in notes; mirrors 05-09 mid-day/EOD split. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): §8 appendix for operator hot-fix #2723 + #846/trace Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3/§4/§8 Σ authority (P2) per review 9798 - §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): fix §8 code span Markdown for Σ=169 appendix Repair missing closing backtick so `169 (50 / 117 / 2)` renders (Codex 981x non-blocking). Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-trigger PR #2714 checks (prior run jobs cancelled stale) noop: prior Actions attempt left fmt/ci/changes/v3 cancelled mid-flight against same head SHA while self_host_ratchet stayed queued — fresh SHA escapes the duplicate-run cancel window without changing docs. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fresh Actions enqueue for PR #2714 (stuck queued/cancel cascade) noop: supersede zombie workflow whose jobs were starvation-cancelled mid-flight. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-enqueue Actions for #2714 (runner cancel starvation on d61b) Second noop: prior run stuck queued with cancelled leaf jobs; CLI rerun blocked. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>

* docs(audit): R3 deferral anti-pattern audit (PROPOSAL — Director-authored) Surfaces the broader anti-pattern class around cost-lens Miss dissolution (operator-ratified 2026-05-11). Grep-verified ~1600+ instances of deferral-via-wrapper-variant in v3 compiler production surface across 13 categories (Option<T>, panic!, .expect(), NotYetImplemented, DescentUnknown, ArrowBody::Pending, _ => catch-alls, etc.). Per operator-directive: "Miss should go away entirely; if something in substrate defines a Miss it should fail and be investigated asap" — extended to whole anti-pattern class. Each category dissolution path proposed. Tagged for PM (deep-wolf-155) + Mgr ratification: scope, sequencing, PR-template ratchet authoring authority. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: gunbc Director * docs(audit): address openai-pro REQUEST_CHANGES — narrow Miss-class scope; reconcile DescentUnknown authority Per openai-pro review (#2708 c#4425020297, verdict REQUEST_CHANGES): 3 valid blocking findings addressed: 1. LAYER MODEL — §3.2 DescentEvidence::DescentUnknown removal conflated Miss-class deferral with fail-closed lattice bottom (INVARIANTS.md:63-66). Reframed: dissolution requires PM-tier ratification on (a) keep 3-variant lattice + construction-side narrowing OR (b) authority update first + 2-variant collapse. No worker dispatch until PM ratifies. 2. INVARIANTS + modeling-discipline — §1 row 1, §2.2 paragraph: "all 83 Option<T> = pure deferral" overgeneralized. Per modeling-discipline.md:41-50 + CODING.md:95-97, Option<T> is allowed when absence is meaningful. Reframed as triage candidates with per-site classification (error-None = Miss-class; legitimate-absence = compliant); explicit "don't bulk-convert." 3. CODING.md — §4 review checklist phrased as "flag for conversion" which conflicts with CODING.md:307-309 (Option/Result OK when meaningful). Reframed as "flag for justification": reviewer asks, author justifies; non-compliant cases convert, compliant wrappers survive. §0 framing also clarified: Miss-class deferral ≠ all Option<T>; per-site classification required; bulk-conversion would itself be a discipline violation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address codex REQUEST_CHANGES — eliminate internal authority contradictions Per codex review (#2708 c#4425182*, verdict REQUEST_CHANGES): 2 valid blocking findings addressed: 1. §1 table — rows 2-7 stated definitive violations ("should be typed Diagnostics", "admits non-exhaustiveness", "explicit 'I haven't decided this'") while §2.2 later correctly narrowed these to per-site triage. Two conflicting authorities within the same brief violated INVARIANTS P2 single-authority discipline. Fix: table notes now reflect the triage framing (boundary tooling vs interior substrate flow per CODING.md 307-309; closed-enum vs deliberate-default catch-alls; etc.). Rows 9-13 tagged with explicit cross-references to §3 disposition. 2. §5 sequencing — proposed §3.2 (DescentUnknown) same-batch dispatch with §3.1, but §3.2 itself blocked dispatch on PM ratification of path (a) vs (b). Fix: §5 now explicitly marks §3.2 + §3.6 as PM-blocked authority gates; only path (a) ratification would enable same-batch with §3.1; path (b) requires INVARIANTS.md edit landing first. Authority-gate summary appended. Also relabeled §2.1 "Pure deferral" → "Miss-class deferral" and removed DescentUnknown from the auto-classified list (consistent with §3.2 gate). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address inline blocking — reconcile §3.3 DescentResidual with Director-ratified γ-shape Per inline review finding at docs/audit/r3-deferral-anti-pattern-audit-2026-05-11.md:101 (2026-05-11T21:03:41Z): > "BLOCKING: §3.3 reclassifies the Director-ratified terminal DescentResidual > as Miss-shape without reconciling the current termination.dag authority, > which violates P1 modeling faithfulness and locked-decision discipline." Valid finding. The `DescentResidual = EvidenceUnknown(NonStrictEvidence) | EvidenceIncomplete` shape was Director-ratified via the illegal-states-unrepresentable rationale in docs/briefs/r3-substrate-descent-execution-proof-worker.md (gunbc#828 issuecomment-4395060514). The audit incorrectly conflated the analyzer's runtime-failure surface with a Miss-class design-laziness deferral. Same pattern as the prior §3.2 DescentUnknown correction (openai-pro REQUEST_CHANGES): - §3.3 reframed: no direct dissolution proposed; instead, pre-dispatch requirement to read existing authority + produce grep-verified reason + PM ratification. - §1 table row 11: tagged "authority-conflicting per Director-ratified γ-shape — compliant as written today." - §2.1: removed residual from Miss-class auto-classified list; appended to the "NOT auto-classified" entries alongside DescentUnknown. - §5 sequencing: §3.3 now authority-blocked (same as §3.2 + §3.6); cannot same-batch with §3.1 until reconciliation lands. Authority-gate footer updated. Pattern: every authority-conflicting dissolution proposal must (a) start from grep-verified read of existing authority, (b) name the specific authority doc affected, (c) require PM ratification before dispatch. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address inline blocking — §3.6 ArrowBody location was factually wrong Per inline review finding at docs/audit/r3-deferral-anti-pattern-audit-2026-05-11.md:120 (2026-05-11T21:03:41Z): > "BLOCKING: ArrowBody::Pending is stored on TypeConnective::Arrow.body/ > ResolvedArrow, not Behavior::Transform.body, so §3.6 aims the redesign > at the wrong substrate boundary under P2 facts-flow-forward." Verified at HEAD: - ArrowBody enum at src/v3/compiler/src/dag.rs:1092 - Used in TypeConnective::Arrow { body, .. } patterns (bootstrap.rs:288 etc.) - All ArrowBody::Unparsed sites in bootstrap_generated.rs are inside TypeConnective::Arrow { body: ArrowBody::Unparsed(...), .. } Original §3.6 claim that ArrowBody is on Behavior::Transform.body was wrong. Actual location is declaration-tier type-connective (Declaration.connective = TypeConnective::Arrow { body: ArrowBody::Pending }). Fix: §3.6 reframed. The substrate-shape question is at the declaration-tier type-connective layer, NOT Behavior::Transform. The "paper-over" cost is at the type-connective-walking layer; Behavior walkers already see only resolved bodies. Revised proposal: PM ratification on R3-load-bearing-ness + Substrate Mgr canvas on partition-vs-sum-with-Pending design question, citing M1_DESIGN.md authority + per-walker impact analysis. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address inline blocking — LensSurfacePending is terminal, not in-progress Per inline review finding at docs/audit/r3-deferral-anti-pattern-audit-2026-05-11.md:37 (2026-05-11T21:03:41Z): > "BLOCKING: LensSurfacePending is a terminal ParallelismUnsupportedKind in > the effects substrate, not an in-progress substrate state, so grouping it > with ArrowBody::Pending needs explicit authority reconciliation before > dispatch under P1 modeling faithfulness." Verified at HEAD: src/v3/compiler/src/dag/effects.rs:197 places LensSurfacePending as a variant of ParallelismUnsupportedKind, explicitly marked 🟢 TERMINAL in code comments. It's an explicit unsupported-reason payload for the parallelism lens, NOT a transitional in-progress state. The "Pending" suffix is misleading. Fix: removed LensSurfacePending from §3.6 (which only covers true pre-lowering transitional state ArrowBody::Pending). Updated §1 table row 12 + §2.1 Miss-class list to explicitly NOT auto-classify it. Removed scope contradiction. Pattern continues from prior corrections: every classification in the audit needs grep-verified factual grounding. Misleading variant names ("Pending" suffix on terminal carriers) are themselves a discipline gap. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address cursor NON-BLOCKING table nits — rows #10/#11 misattributed conflict Per cursor APPROVE_WITH_COMMENTS review at sha 0c07f7a (2026-05-11T21:08:35Z): > Row 10/11 phrase 'Authority-conflicting per X' but the cited authority X is > exactly where the standing design is *defined*. The real tension is between > the operator's Miss-elimination directive and that existing authority text, > not 'conflict' within or stated by those authorities themselves. Fix: reframe rows #10/#11 to name the standing authority + locate the tension correctly: - Row 10 (DescentUnknown): standing authority is INVARIANTS.md fail-closed bottom; tension is with operator directive (not within the invariant). - Row 11 (DescentResidual): standing authority is Director-ratified γ-shape; carrier is compliant; my prior audit framing was the conflict, corrected in §3.3. NON-BLOCKING per reviewer but legitimate clarity improvement; reviewer's verdict was APPROVE_WITH_COMMENTS. * docs(audit): tighten CODING.md citations — boundary roles at :311-321, not :307-309 Per cursor APPROVE_WITH_COMMENTS finding at sha 0af402f (2026-05-11T21:24:39Z): > The notes point boundary-tooling legitimacy at CODING.md:307-309, but those > lines only state the narrow 'Hidden panic surface' rule (library avoids > contract-violation panics/unwrap()). The explicit Bootstrap and > Code-generation binaries edge roles appear under 'When impurity is > acceptable' beginning around CODING.md:311 (table ~317-321). Fix: split the citation so: - CODING.md:307-309 covers the contract-violation-in-library rule (interior substrate-flow panics dissolve to typed Diagnostic per C-8). - CODING.md:311-321 covers the boundary roles legitimacy (Build script / Code-generation binaries / Bootstrap entries in the impurity-acceptable table). Updated table rows #2/#3 (lines 27-28), §2.2 prose (line 66), and §4 review checklist (line 171). NON-BLOCKING per reviewer; landing as documentation hygiene. * docs(audit): add §3.8.1 concrete 10-entry NON_TEST inventory per velocity-walk Per PM ratification (msg_45457c77 in response to Director ask msg_048fdfa6): empirical-grounding-strengthens-the-case path. §3.8 currently treats structural_coverage_gap audit as abstract pattern; with zesty-boar-261's velocity-walk diagnostic (gunbc#846 c#4425420798) producing a 9 NON_TEST + 1 FRAGMENTS enumerated inventory over the 7d window pre-2026-05-11, §3.8 graduates from speculative to grounded. Adds §3.8.1 with: - 10-entry table: file path + LOC + adjacent-lane/dissolution-path mapping - Total 2,171 LOC; omni_shape_b_openapi.rs identified as ~40% of class - Audit implication: per-file promote-or-carve discipline applies - Per-PR review state-space framing (Director conformance read flags absent dissolution-path mapping) - Re-audit cadence note (this is window-relative intro composition, not full main §3.8 audit; per feedback_intro_rate_not_residual_share) Citations grep-verified at HEAD eed86ff: all 9 NON_TEST files exist with stated LOC; FRAGMENTS entry confirmed in sg0_census_test.rs:688-691. * docs(briefs): Director scaffold-fill for Cluster M Phase 3 reflected-Dag + DimensionReport bulk-port worker briefs Per feedback_pre_authored_brief_queue + feedback_director_mgr_energy_input (Director energy INTO system until real workflow substrate exists). Verification Mgr (clever-tern-670) status pass (msg_755c3f43) identified Phase 3 dissolution-rate bottleneck as Mgr-tier brief-authoring bandwidth on the two biggest unauthored classes: - Reflected-Dag structural assertion family (~25-30 entries; 16 seed-named) - Generic DimensionReport / runner-discipline family (~20-25 entries; 10 seed-named) These ~50 entries combined are roughly half of the #84 EXPECTED_HAND_AUTHORED_TEST partition (116 entries on origin/main eed86ff). Authoring scaffolds + Mgr finalization + dispatch should land bulk-port PRs within 7-10 days, with velocity-tripwire arrow (12.7:1 intros:dissolves at gunbc#846 c#4425420798) flipping intra-week. Authority split per Director msg_eb2372c7 to PM: - Director: scaffold shape (this commit) — locked-design citations, substrate carrier references at exact lines, Phase-2 pattern site refs, hard constraints, STOP-and-escalate criteria, decomposition recommendations. - Verification Mgr: finalization — complete inventory (Mgr-fill placeholders marked throughout), per-entry classification, pilot selection, dispatch. Substrate citations grep-verified via Verification Mgr msg_755c3f43: - ProgramGenerator/ProgramShape/Quantifier/QuantifiedTestClaim/SuiteClaim: src/v3/std/verification.dag:118-133 + :379-402 (carriers landed) - TestSuite.claims still List<TestClaim>: verification.dag:404-407 (staged trigger at :394-399) — Reflected-Dag class CONSUMER-GATED on this flip - Phase-2 pattern: t_pb_b_1_dag_runner_test.rs:257-357 (R3_GATE_87_CEMENTING_REGEN_SUITES, run_suite_all_pass_with_expected_claim_names) - Receipt discipline: r3_gate_87_lens_cementing_regen_receipts_test.rs:13-24 + :122-132 - DimensionReport class NOT consumer-gated (Phase-2 pattern is the load-bearing predicate, not full #87 PASSING, per feedback_construction_over_ratchets) * docs(briefs): Director scaffold-fill for R3 CI Layer 2 path-conditional gating Per PM ratification at gunbc#828 c4425726922 + Director ratification msg_a77c7f42 (Verification Mgr routing per feedback_parallel_representation_debt coherence). Bridge-debt with named dissolution trigger: when gate ci_uses_provable_minimal_affected_set_selection lands, the affected-set Introspect-lens output (canvas PR #2713) replaces the bridge's required_paths_regex column. Brief covers: - §0 scope: extend PR #2718's changes job, do not parallel - §1 mechanism: per-group skip_* boolean outputs + STEP-level if: on v3 - §2 inventory sources (slow-test-exemptions.txt + /tmp/v3-test-timings.log + NEW per-group required-paths mapping) - §3 per-dimension structural target — every entry has dimension: Dimension field matching lens enum (parallel-representation-debt prevention) - §4 hard constraints (8 invariants) - §5 acceptance - §6 decomposition (Mgr-fill recommendation: cost_lens pilot first) - §7 STOP-and-escalate criteria - §8 bridge-debt + dissolution path explicit Verification Mgr (clever-tern-670) fills inventory + per-group regex + dispatch. Director scaffold preserves coherence; Mgr finalizes per feedback_director_mgr_energy_input. * docs(briefs): fix Layer 2 YAML naming inconsistency (skip_cost → skip_cost_lens) Per cursor APPROVE_WITH_COMMENTS at sha 04c5b08 (review 9701): > The changes outputs define skip_cost, but the v3 step's if: uses > needs.changes.outputs.skip_cost_lens. That disagrees with the same brief's > post-dissolution sketch (skip_$group with cost_lens → skip_cost_lens, lines > 129-134). Not a formal invariant breach by itself, but it is easy for an > implementer to copy the wrong name and get an always-on/off step. Fix: normalize the example YAML outputs block to match the if: lines and the post-dissolution sketch. Naming convention: skip_<group_name> where <group_name> matches the per-group table's group_name column verbatim (no abbreviation). Updated all 4 example outputs: skip_lens → skip_complexity_lens (was vague; tied to specific group) skip_emit → skip_emit_target (matches starting template at §2) skip_parser → skip_parser_grammar (matches starting template) skip_cost → skip_cost_lens (matches if: line + post-dissolution sketch) Also added an inline comment documenting the naming convention so future copy-paste from the example stays mechanically correct. * docs(briefs): cite PM pre-staged Mgr-fill template (PR #2721) + converge pilot recommendation on Cluster B Per PM msg_bba47649 — pre-staged Mgr-fill template landed as PR #2721 (docs/briefs/r3-ci-layer-2-pm-prestaged-mgr-fill-template.md, 220 lines). Two scaffold updates: 1. §2 (inventory sources): replaced 'PM pre-staged skeleton to be attached if/when available' speculative reference with explicit cite-and-link to the landed template doc. Describes what the PM template provides: - All 78 slow-test-exemptions.txt entries grouped into 9 clusters (A-I) - (test_pattern, dimension, required_paths_regex) skeleton table - 12 [Mgr-fill] placeholders for substrate-lens / R3-V L4/L7 / R1C-E / free-consequences cross-target tracing 2. §6 (decomposition): converged my prior cost_lens-first pilot recommendation with PM's Cluster B recommendation — these are the same family (Lane 2 Stage 2d symbolic cost = cost-lens). Updated wording to reflect Cluster naming + cross-citation to PM template's Cluster B detail. Added [Mgr-fill] placeholder resolution wave to decomposition. Inline sketch table retained as illustrative; defer to PM template for actual starting inventory. * WIP: gunbc Director * docs(briefs): fix singular dimension → Set<Dimension> per PM caught semantic violation PM (msg_ab551c52) surfaced codex RC on template PR #2721 (review #9707): singular 'dimension:' field violates locked-design §2 union semantics. A multi-dim consumer (e.g., LBP demonstration reading both complexity + cost) declared with singular dimension: cost would be silently skipped when only complexity changes — fail-open violation against P3. PM fixed their template at dedcf69: dimension → dimensions (Set<Dimension>), union-formula clarified, multi-dim rows expanded. This brief had the same singular semantics; absorbed the fix per PM recommendation so Verification Mgr inherits coherent dim-set semantic across both authority chain artifacts (brief + template). Changes: - §0 authority bullet: contains(single) → (∩ ≠ ∅) intersection-non-empty; dimension: Dimension → dimensions: Set<Dimension> - §2 table column rename + type spec + union semantics note + multi-dim consumer guidance - §2 starting template citation updated to reflect post-fix template at dedcf69 - §3 section header renamed; substantive paragraph explaining WHY Set<Dimension> not Dimension (cites PM caught violation + P3 fail-open framing) - §3 YAML example: jq script updated to set-intersection check - §4.5 hard constraint: dimensions: Set<Dimension> with members from enum; empty set invalid - §5 acceptance: every group has dimensions: Set<Dimension>; multi-dim fidelity language - §6 pilot description: 'singleton {cost} dimensions' phrasing; class wave reviewer-check language updated - §7 STOP: added multi-dim escalation path; explicit warning against defaulting to singleton {primary} - §8 surviving artifact: (group_name, dimensions) — set-typed column survives - inline illustrative table: explicit set-literal notation with multi-dim row example (lbp_demonstration: {complexity, cost}) Same authority chain absorbs cleanly: brief (primary) + template (data attachment) now both set-typed; Verification Mgr inherits coherent semantic. * docs(briefs): fix boolean polarity inversion + add polarity invariant per openai-pro RC on template PM (msg_9a188e22) surfaced openai-pro BLOCKING re-review (#9721) on template PR #2721 at 93080af — caught load-bearing boolean polarity inversion: brief stated skip_* formula as (affected ∩ row.dimensions) ≠ ∅ (skip when intersection NON-empty) while CI consumer wires if: skip != 'true' (run when skip is false). Net effect: literal-following Mgr/worker would wire the gate to silently skip AFFECTED tests when intersection is non-empty. TESTING.md + Boundary Discipline violation. PM fixed template at 262f42d (4 sites inverted; explicit polarity table added at §1/§3/§4/§5). Same risk on this brief (#2719) at the post-dissolution mapping site I authored when absorbing the prior dim-set fix at efacecd. Fix: §0 authority bullet (line 10, the inversion site): before: 'skip_* flags become (∩ ≠ ∅)' [INVERTED — fail-open] after: 'skip_* flags become skip_<group> = (∩ = ∅)' [canonical] + explicit polarity check note + carrier-vs-contract explanation + skip-form / run-form equivalence stated §3 substantive paragraph (after Set<Dimension> WHY): added Polarity invariant block citing PM's caught inversion + 262f42d fix + explicit warning that skip = (∩ ≠ ∅) is the canonical fail-open boolean-polarity bug pattern. §4 hard constraint #5 (dimensions field): added inline Polarity invariant restating the canonical skip-form + run-form equivalent + 'never invert' clause. §5 acceptance: added 'Polarity check passes' criterion enumerating the acceptable forms + naming the inverted form as the fail-open pattern to reject in review. Self-test text clarified: cost-dimension groups run, other-dimension groups skip (verifies correct polarity in actual gate). YAML example at §3 (lines 139-149) was already polarity-correct (skip iff intersection empty; skip=true when intersection empty) so unchanged. Single-pass absorption per PM recommendation — both brief and template now lockstep on polarity semantics. Verification Mgr inherits both files without polarity mismatch in finalization. * WIP: gunbc Director * docs(briefs): align §0 example names with §1 naming convention (cursor exploratory) Per cursor APPROVE exploratory observation on PR #2719 sha 13b0db9 (review #9732): §0 line 25 illustrative outputs used abbreviated names (skip_lens / skip_emit / skip_parser) while §1 line 53-54 establishes strict 'skip_<group_name>' naming convention matching the per-group table verbatim. Non-policy violation per cursor but tightening avoids ambiguity for implementer. Fix: replace abbreviated names with full-form (skip_cost_lens / skip_emit_target / skip_parser_grammar) + cross-reference §1 naming convention in the same sentence. Brief now consistent across all naming sites. * docs(briefs): add P3 fail-closed shared-infrastructure full-run bucket per codex BLOCKING codex REQUEST_CHANGES on PR #2719 at sha 52c6cf0 (review #9744): Line 102 narrowed required-paths inventory to 'src/v3/*' deps only; the illustrative table at lines 114-118 followed that shape. A PR that changes shared test infrastructure or selection machinery outside src/v3/* (.github/workflows/ci.yml, scripts/*, Cargo.lock, rust-toolchain.toml, etc.) would be classified as 'unaffected' for every per-group regex and silently skip tests whose behavior actually changed. That's the fail-open boundary class P3 forbids + TESTING.md behavior-driven discipline violation. Real correctness issue in the proposed mechanism, not just an implementation detail. Fix: add shared-infrastructure full-run fail-closed bucket as the join-point that catches inter-group / cross-cutting changes: §2 (inventory sources): added 'Shared-infrastructure full-run fail-closed bucket' subsection with explicit mechanism — changes job computes force_full_run = (any changed file matches shared-infra regex); when true, all per-group skip_* short-circuit to false. Regex spec: ^(\.github/.*|scripts/.*|Cargo\.(toml|lock)|rust-toolchain\.toml| \.cargo/.*|build\.rs)$. Names the structural rationale: per-group regexes cover ONLY their own src/v3/* deps; the full-run trigger is the join-point. Fail-closed by construction. §4 hard constraint #9 (new): formalizes the invariant + 'never collapse the full-run trigger into per-group regexes' (structural fail-open shape). §5 acceptance: added 'Shared-infrastructure full-run check passes' as separate criterion + self-test case (c) — a PR touching only .github/workflows/ci.yml or Cargo.lock or scripts/check-test-timeout.sh MUST run all test groups. Expanded self-test from 3 to 4 cases (a/b/c/d). §2 added [Mgr-fill]: validate shared-infra regex against representative recent PRs. Single-pass absorption; brief now P3 fail-closed at the cross-cutting boundary. * WIP: gunbc Director * docs(briefs): fix two openai-pro BLOCKINGs — harness-arm in shared-infra regex + cargo test substring not glob openai-pro REQUEST_CHANGES on PR #2719 at sha 0d3b44b (review #9749 + manual c4426188322): BLOCKING #1 (P3 Fail-Closed): brief at line 104 names 'harness code' as a class to catch in full-run regex but the actual regex at line 109 had no harness/test-selection arm. Harness-only changes (e.g., to tests/integration/common/* or sg0_census_test.rs) would miss both full-run regex AND per-group regexes — silent skip. BLOCKING #2 (TESTING.md fail-closed CI): test_pattern field documented as 'cargo test arg pattern' but examples used glob-looking syntax (cost_lens_*, *_emit_*). Cargo positional test arg is a libtest SUBSTRING filter, not a glob. Worker following the brief literally would produce a step that runs zero intended tests + exits successfully — silent skip converting 'selected group tested' into 'selected group filtered out.' Fixes: #1 (harness arm in shared-infra regex): - §2 mechanism: extended regex to include src/v3/compiler/tests/integration/common/.*, sg0_census_test.rs, test_runner_test.rs, t_pb_b_1_dag_runner_test.rs, integration.rs, integration test entry points - §2 new paragraph naming the harness/test-selection-machinery arms explicitly + hard rule: harness-class files MUST never appear in a per-group required_paths_regex - §4 hard constraint #9: extended invariant to include harness class with explicit file list - §5 acceptance: extended self-test case (c) to include harness-class example (common/cached_compile.rs) + explicit verification list #2 (cargo test substring, not glob): - §1 YAML examples: cost_lens_* → cost_lens; *_emit_* → emit; added IMPORTANT comment explaining libtest substring semantics + forbidding glob syntax - §2 test_pattern column spec: re-documented as 'libtest test-name SUBSTRING filter (NOT a glob)' with cost_lens example + glob forbiddance + --exact alternative - §2 inline illustrative table: cost_lens_* → cost_lens (and others); added trailing comment naming substring semantics - §4 new hard constraint #10: test_pattern is substring filter not glob; self-test that the value substitutes verbatim into cargo test and runs positive number of tests - §5 acceptance: new 'test_pattern substring-filter check passes' criterion with empirical pilot-wave validation requirement Brief now P3 fail-closed at both the boundary (shared-infra full-run including harness) AND the selector (substring filter that workers can copy verbatim without silent zero-test execution). Single-absorption pass; awaiting fresh review at new HEAD. * docs(briefs): reframe PM template citation per codex P1/P2 — template is on PR #2721, NOT yet landed on main codex REQUEST_CHANGES on PR #2719 (review #9754): Line 128 named docs/briefs/r3-ci-layer-2-pm-prestaged-mgr-fill-template.md as a 'landed' starting authority, but git ls-tree origin/main returns no blob and git ls-files returns nothing. A worker following this brief would be sent to a non-existent source of truth — INVARIANTS P1/P2 authority-grounding violation in a dispatch document. Verified at HEAD: - git ls-tree origin/main -- docs/briefs/r3-ci-layer-2-pm-prestaged-mgr-fill-template.md → empty - gh pr view 2721 → state=OPEN, mergedAt=null - Template lives on PR #2721's branch only Fix: reframe the template citation to acknowledge PR #2721 is open-not-landed. - 'landed via PR #2721' → 'open as PR #2721 ... NOT yet landed on main' - Added codex BLOCKING citation + verification receipt (git ls-tree result) - Added explicit authority caveat: Verification Mgr finalization MUST coordinate merge sequencing — (a) merge #2721 first, OR (b) read from PR #2721 branch until it merges - Named PM (deep-wolf-155) as PR #2721 author + cross-link for merge coordination - Cited sha 262f42d (PR #2721 post-fix state per PM msg_125e3aa5) Brief now accurately grounded on the actual file location (PR #2721 branch) with merge-sequencing guidance for Mgr finalization. Authority chain honest about in-flight vs landed state. * WIP: gunbc Director * docs(briefs): absorb 3 BLOCKING findings (Brian + codex) — R4 lifecycle reframe + canonical 2-step + count fix Brian inline BLOCKING #1 + codex BLOCKING #1 (P5 dissolution-trigger authority): brief framed dissolution as R3 close-blocking gate 'ci_uses_provable_minimal_affected_set_selection' but docs/design-affected-set-lens.md:3 = 'R4 wishlist', :354 = 'CI integration sketch (deferred to R4 full delivery)', :366 = 'CI integration is R4 full-delivery work'. No ROADMAP authority exists for the cited gate name — that was Director-tier speculation. Brian inline BLOCKING #2 + codex BLOCKING #2 (Facts Flow Forward / surviving schema): §3 post-dissolution sketch only encoded dimension intersection, silently dropping NodeRef intersection. Canonical 2-step per design §5:359 requires BOTH (TestClaim.refs ∩ affected_nodes) ≠ ∅ AND (TestClaim.dims ∩ changed.dims) ≠ ∅. Reducing surviving schema to (group_name, dimensions) too early. codex non-blocking: slow-test-exemptions.txt count cited as 78 (PM template value); actual is 80 at 2026-05-12T00:50Z (verified locally: grep -v '^#' ... | grep -v '^$' | wc -l = 80). Fixes (single absorption pass): §0 'Bridge-debt → dissolution lifecycle' bullet: - Reframed from 'R3 close-blocking gate' to 'R4-bounded dissolution lifecycle (NOT R3 close)' with explicit citation of design doc :3 + :354 + :366. Names R4.B as R4 owner. Removes the speculative gate name. Names Brian's BLOCKING #1 absorption. §0 NEW 'Post-dissolution selection semantics (canonical 2-step join)' bullet: explicit NodeRef + dimension joins per design :359; run formula; skip formula; bridge coarseness acknowledgment (path-regex over-approximates canonical lens; fail-closed-safe but coarser). Names Brian's BLOCKING #2 absorption. §0 polarity check bullet: updated skip-form to reflect 2-step (NodeRef-empty OR dim-empty ⇒ unaffected ⇒ skip). §2 inventory source (a): count 78 → 80 at 3 sites (replace_all), with explanation that count grows over time + Mgr re-runs grep at finalization rather than relying on stale citations. §2 table column spec: added 'testclaim_references' as 5th column. Cited Brian's BLOCKING #2; explains bridge-tier proxy vs post-dissolution proxy. §2 [Mgr-fill]: extended to require testclaim_references computation per canonical 2-step. §3 YAML post-dissolution sketch: rewrote classify step to compose BOTH NodeRef AND dimension intersections via jq + cite Brian's BLOCKING #2 absorption inline. Header comment names R4.B authority and acknowledges no current ROADMAP gate ID. §4 #4 PR-body bridge-debt template: reworded from 'R3 close-blocking gate' to 'R4.B Introspect-lens saturation lane CI integration delivery; NOT R3 close-blocking.' §8 surviving artifact: corrected from (group_name, dimensions) to (group_name, dimensions, testclaim_references) per canonical; cited Brian's BLOCKING #2. Removed all references to 'ci_uses_provable_minimal_affected_set_selection' as a current ROADMAP gate name; replaced with R4.B owning-lane references + explicit acknowledgment of authority gap. Brief now P5-honest: dissolution trigger is checkable (R4.B owning lane) even if no concrete gate ID yet; surviving schema preserves both lens join inputs per canonical algorithm. * docs(briefs): reconcile §3 substantive + §7 STOP with §0/§8 — surviving schema is 3-column (cursor internal-consistency catch) cursor REQUEST_CHANGES on PR #2719 sha 540113f (review #9767): Two internal contradictions surfaced from my partial absorption of Brian's BLOCKING #2: (a) §3 substantive paragraph still said '(group_name, dimensions) mapping survives the dissolution — only required_paths_regex column gets retired' contradicting §0 + §8 which were updated to 3-column (group_name, dimensions, testclaim_references). (b) §7 STOP bullet referenced 'Layer 2 dissolution shape doesn't match (group_name, dimensions) schema' — 2-column framing, same contradiction. Fix: §3 substantive paragraph (around the parallel-representation-debt rationale): - 2-column → 3-column framing - both dimensions AND testclaim_references must be authored - cite design §:359 canonical 2-step join - cite cursor internal-consistency catch alongside Brian's BLOCKING #2 §7 STOP escalation bullet: - (group_name, dimensions) → (group_name, dimensions, testclaim_references) + cite canonical 2-step join Verified via grep: all remaining references are within meta-statements explicitly documenting the removal (line 10 + line 268); no live references remain. All appearances are either in updated 3-column contexts or in meta-statements referencing the absorption (line 15 catch citation). Brief now internally coherent across §0, §3, §7, §8 on: - dissolution trigger (R4.B owning lane, NOT removed-gate-name) - surviving schema (3 columns including testclaim_references) - canonical 2-step join semantics * docs(briefs): fix stale 78 inventory references at §2 lines 114 + 141 per openai-pro BLOCKING openai-pro REQUEST_CHANGES on PR #2719 sha 8ae7938 (review #9779): Brief had stale '78 active >2s entries' at line 114 + 'All 78 ... entries' at line 141, despite §0 line 19 + §2 line 157 stating live count is 80 and Mgr should re-run count at finalization. A worker following §2 literally could build the gating table from stale 78-entry basis, omitting 2 slow-test entries — fail-open shape against the brief's own P3 fail-closed contract (under-inventory = exemption falls in neither per-group regex nor full-run bucket = silently skipped). Fix: §2 inventory source (a) (line 114): replaced 'start with the 78 active >2s entries' with 'start with the current live count of active >2s entries (Mgr MUST re-run grep ... | wc -l at finalization; 80 at 2026-05-12T00:50Z but count grows; do NOT cite the stale 78 from PM template PR #2721 or any earlier reference)'. Added 'fail-closed completeness invariant' inline: every active exemption MUST appear in either a per-group required_paths_regex OR the harness/shared-infra full-run bucket; no exemption left unclassified. §2 PM template description (line 141): 'All 78 entries' → 'PM-grouped entries (PM template snapshot was 78 at template authoring time; live count grows — Mgr re-verifies via wc -l at finalization, NOT this stale historical reference)'. Added note that the 9-cluster taxonomy survives count growth; Mgr maps new entries to existing clusters or escalates if a new cluster surface emerges. Brief is now internally consistent on inventory-count freshness: - §0 line 19: live 80 with verification command - §2 line 114: re-run command at finalization; explicit do-not-cite-78 instruction - §2 line 141: PM template snapshot historical; live count grows - §2 line 157 (Mgr-fill): re-run grep, don't trust stale citations 12th distinct review-class catch this polish cycle: inventory-citation freshness as fail-closed completeness invariant. * docs(briefs): §5 acceptance requires testclaim_references explicitly per codex BLOCKING #9780 codex REQUEST_CHANGES on PR #2719 sha 8ae7938 (review #9780): Finding #1 (stale 78 at lines 114 + 141) already fixed at prior commit 487d175; codex finding overlaps with openai-pro #9779 absorbed before. Finding #2 (new): §5 acceptance at line 228 only required dimensions: Set<Dimension> on each group entry, NOT testclaim_references: Set<NodeRef>, even though the brief makes that column load-bearing at: - §0 line 104 (post-dissolution selection canonical 2-step) - §3 line 178 (substantive paragraph: 3-column surviving schema) - §8 line 269 (surviving artifact 3-column) A Mgr reading §5 acceptance literally could call PR-set 'done' with dimensions-only column population — that's the dimensions-only closeout codex flags as facts-flow-forward violation. Fix: §5 acceptance adds new explicit criterion: 'Every group entry has testclaim_references: Set<NodeRef> field' with explicit citation chain (design §:359 + Brian BLOCKING #2 + codex BLOCKING #9780). Includes bridge-tier-proxy vs post-dissolution-proxy note. Includes 'Dimensions-only acceptance closeout is rejected: P2 facts-flow-forward requires both lens-join inputs.' §5 acceptance now coherent with §0/§3/§8 on the 3-column surviving schema; no path to 'done' that skips testclaim_references. 13th distinct review-class catch this polish cycle: acceptance-vs-substantive-text divergence on load-bearing fields. * docs(briefs): Director scaffold for cold-v3 rebuild coordinator (Phase 3-pattern; per-cut child workers) Per PM greenlight msg_07f73de0 + Brian operator greenlight at gunbc#846 reply (~01:25Z 2026-05-12). Pre-authored scaffold per feedback_pre_authored_brief_queue + feedback_director_mgr_energy_input; activation triggers on empirical post-#2723 cold-v3 wall-clock measurement. Scope: rebuild 20 hot-fix-2026-05-12-tagged cut tests under OnceLock/cached_compile/shared-fixture amortization. Each rebuild PR: - Removes #[ignore] attribute - Retires slow-test-exemptions.txt row - Decrements TEST_TIMEOUT_MAX_EXEMPTIONS in lockstep - Verifies <2s wall on cold ubuntu-latest Brief covers: - §0 scope: full 20-test inventory grouped into 9 clusters (A-I) by lane + amortization affinity - §1 mechanism: 4-step per-cut worker pattern (baseline, refactor, verify, re-enable + retire-exemption) - §2 6 hard constraints (preserve semantics, ratchet-down per PR, amortization-mechanism-only, no new hand-Rust, per-cluster fidelity, re-enable-with-ratchet-down enforcement) - §3 acceptance: per-PR + final cold-v3 ≤10min + ratchet floor ≤80 - §4 decomposition: pilot (Cluster A) → high-impact (Cluster H TC1 140s) → parallel rollout → ratchet sweep - §5 STOP-and-escalate criteria - §6 cross-coordinator notes: - T-LAS Mgr seat gap (Cluster F) — Director surfaces ownership - Phase 3 #84 cluster overlap — Verification Mgr decides Layer 2 rebuild PR vs Cluster M Phase 3 PR routing - Layer 2 brief #2719 INDEPENDENT — rebuild is structural regardless Activation decision branch: - post-#2723 cold-v3 >20min → second cut session - 10-20min → rebuild alongside possible second-cut - ≤10min → rebuild can de-prioritize Per-cluster routing: - A+I → PB Mgr (Lane 3 Stage 3c) - B → Substrate Mgr (M1_5_DESIGN) - C/D/E/G → Verification Mgr (this brief's coordinator) - F (T-LAS) → Director-routed operator-tier (no standing Mgr seat) - H (TC1 substrate-adjacent) → Substrate Mgr or dedicated session Authority chain documented in footer. * docs(briefs): absorb Brian + codex 3-finding BLOCKING wave (P5 receipts, dynamic ratchet floor, polarity-residual) Brian inline BLOCKINGs + codex scheduled review BLOCKING #9XXX at PR #2725 sha 698ba61 (4 findings total; codex overlaps with all 3 Brian findings): (1) #2725 line 70 (constraint #4) — shared-fixture helper carve-out permits expanded hand-Rust under src/v3/compiler/tests without INVARIANTS P5 receipt. Brian: P5 receipt required for new/expanded src/v3 Rust. Codex: require P5 receipt OR state SG-0-neutral without helper expansion. (2) #2725 line 83 (§3 acceptance final bullet) — hard-codes ratchet floor ≤80 (pre-hot-fix baseline), preserving stale debt. Brian: current main has 84 active exemptions with 20 hot-fix rows; post-rebuild floor should be recomputed, not preserved at 80. Codex: derive final floor from live non-hot-fix exemptions at Mgr finalization; delete hard-coded ≤80. (3) #2719 line 217 (§4 hard constraint #5 Polarity invariant sub-bullet) — restates skip formula as dimension-only, contradicting two-step NodeRef+dimension contract. Brian: silently drops testclaim_references in violation of P2 Facts Flow Forward. Codex: rewrite every formula to skip when refs∩nodes empty OR dims∩changed_dims empty. (Partial-absorption- residual: cursor's catch on #2725 review #9799 was fixed at §3 substantive paragraph at commit 403833e but didn't propagate to §4 constraint #5 sub-bullet at line 217 — different polarity-mentioning site within the same brief.) Fixes (single-pass per discipline; same pattern as prior 14-catch cycle): #2725 constraint #4 (line 70) rewrite: - 'No new hand-Rust beyond shared-fixture helpers' (carve-out) → 'Shared-fixture helpers require P5 receipt + SG-0-neutrality' - Per-PR P5 receipt explicit: (a) helper LOC delta cited, (b) dissolution path named (helper retires when cluster's pattern lands in .dag TestClaim authority), (c) SG-0 census-delta computation showing net ≤ 0 - SG-0-neutrality enforcement: helpers may add lines but net delta ≤ 0 (helper additions offset by exemption-row retirements + ratchet-down). Net positive = escalate (substrate-shape signal) #2725 §3 acceptance final bullet (line 83) rewrite: - 'ratchet floor returned to ≤80 (pre-hot-fix baseline)' → 'ratchet floor recomputed DYNAMICALLY from live state at activation' - Concrete computation: starts at current main HEAD's TEST_TIMEOUT_MAX_EXEMPTIONS (84 at dfbc010; verify via grep at Mgr finalization); each rebuild PR decrements by N (cuts rebuilt that PR); post-all-20-rebuild target = (value at activation) - 20 (e.g., 64 at current state) - Removed '≤80 pre-hot-fix baseline' framing - Explicit acknowledgment: 80 was ITSELF stale debt; 16 non-hot-fix exemptions have separate paydown owners; rebuild does NOT freeze goal at 80; long-run target per feedback_pb_zero_is_r3_close_target is 0 #2719 §4 constraint #5 (line 217) rewrite: - Header changed: '...dimensions: Set<Dimension> field on every group entry' → '...dimensions: Set<Dimension> + testclaim_references: Set<NodeRef> fields on every group entry' - Polarity invariant rewritten to canonical 2-step join (BOTH NodeRef AND dimension intersections; skip = either empty) - Two fail-open bug patterns explicitly named: (a) inversion (b) dimension-only collapse - Bridge-tier proxy framing preserved (path-regex over-approximates canonical; fail-closed-safe coarseness) 15th + 16th + 17th distinct review-class catches this polish cycle (16 on #2719 brief; #15 on rebuild scaffold #2725): - #15 (BLOCKING #1): shared-fixture helper P5 receipt obligation - #16 (BLOCKING #2): dynamic ratchet floor recomputation - #17 (BLOCKING #3): polarity-residual at second site (partial-absorption- residual within partial-absorption-fix; pattern: 'when canonical algorithm gets corrected, ENUMERATE all polarity-mentioning sites' is the discipline) * docs(briefs): apply §3 polarity 2-step rewrite on rebuild-scaffold branch (cursor #9815 catch + #2719-branch parity) cursor APPROVE_WITH_COMMENTS on #2725 review #9815 caught that line 208 (§3 substantive Polarity invariant paragraph) on rebuild-scaffold branch's copy of #2719 brief was still dimensions-only — even though line 217 (§4 constraint #5 sub-bullet) was updated to canonical 2-step in commit 900d5a3. Root cause: my prior #2719 polarity fix at commit 403833e was on #2719's own branch (director/r3-ci-layer-2-path-conditional-gating-scaffold) and never propagated to main → never reached rebuild-scaffold branch's copy of the #2719 brief brought in via main-merge. Applied same §3 polarity rewrite on rebuild-scaffold branch for parity with #2719 branch's content: - run = (refs ∩ nodes) ≠ ∅ AND (dims ∩ changed_dims) ≠ ∅ - skip = ¬run = either intersection ∅ - Explicit naming of TWO fail-open patterns: (a) inversion (b) dimension-only collapse - Bridge-tier proxy framing preserved Cross-branch state now consistent: - #2719 branch (director/r3-ci-layer-2-path-conditional-gating-scaffold) has canonical 2-step at lines 208 + 229 (via 403833e) - #2725 branch (director/r3-ci-cold-v3-rebuild-coordinator-scaffold) has canonical 2-step at lines 208 + 229 (via 900d5a3 + this commit) Both branches' copies of #2719 brief now structurally identical on polarity semantics. Will fully reconcile at merge time if both PRs land separately. 18th distinct review-class catch this polish cycle: cross-branch-divergence-on-shared-doc — when two Director-scaffold PRs both touch a shared brief (one via direct edit, one via main-merge), fixes on one branch must explicitly propagate to the other branch OR the shared content reconciles at merge time. Pattern: 'shared doc in two PRs requires explicit cross-branch parity discipline'. * docs(briefs): fix Phase 4 ratchet sweep residual ≤80 → dynamic (value − 20) per codex BLOCKING #9827 codex BLOCKING on #2725 review #9827 caught residual at line 92 (§4 Phase 4 ratchet sweep description) — still said 'back to ≤80' despite §3 acceptance bullet's stale-baseline correction (which removed the ≤80 framing in favor of dynamic '(value at activation) - 20'). Same partial-absorption-residual class as cursor's earlier catches: fixing the §3 acceptance bullet correction didn't propagate to §4 Phase 4 description; sites referring to the same stale value need parallel updates. Fix: Phase 4 description now uses dynamic '(value at activation) − 20' (e.g., 64 at current state of 84) with explicit acknowledgment that 80 was itself stale debt + cross-link to feedback_pb_zero_is_r3_close_target naming the long-run target = 0 exemptions. 21st distinct review-class catch this polish cycle: phase-description-vs-acceptance-bullet-residual — when an acceptance bullet gets a corrected target, the phase descriptions that motivate phases toward that target need parallel updates. Pattern: 'when target gets corrected, ENUMERATE all phase descriptions / decomposition / STOP criteria that motivate work toward that target.' * fix(#2725): cursor BLOCKING #9834 absorbed Two findings addressed: 1. Line 76 copy-paste slip: "The Layer 2 PR-set is acceptable when:" in a cold-v3 rebuild brief. Changed to "The cold-v3 rebuild PR-set is acceptable when:" to match brief's actual scope. INVARIANTS.md P1 modeling faithfulness for dispatch authority. 2. Line 70 prose tightening: SG-0-neutrality framing previously conflated SG-0 census mechanism with exemption-list mechanism ("helper additions offset by exemption-row retirements + ratchet-down"). These are DIFFERENT bookkeeping: SG-0 counts hand-Rust files/lines per sg0_census_test.rs; exemption-row retirement only reduces slow-test-exemptions.txt count. Corrected prose: helper-LOC additions in common/* MUST be offset by EQUAL- or-greater LOC reductions in per-test files consuming the helper (shared fixture extraction → per-test setup boilerplate dropped). Exemption-row retirement + ratchet-down are independent obligations per constraint #2 and do NOT count toward SG-0 census-delta. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: gunbc Director * fix(#2725): openai-pro REQUEST_CHANGES — 2 BLOCKING findings absorbed Finding 1 (P3 Fail-Closed): Layer 2 shared-infra regex anchored Cargo.toml/ Cargo.lock/build.rs to workspace-root only. Crate-local manifests (e.g., src/v3/compiler/build.rs per CODING.md:319) would NOT match, silently skipping tests for crate-local manifest/build-script changes — fail-open boundary class P3 forbids. Fixed by changing the anchored alternates to use (.*/)?Cargo\.(toml|lock) and (.*/)?build\.rs — non-capturing optional path prefix matches both root-level AND any-depth crate-local files. Finding 2 (ratchet/test discipline): Cold-rebuild brief had execution-path contradiction. §2#2 + §3 require same-PR lockstep ratchet-down. But §4 Phase 4 description said "drops TEST_TIMEOUT_MAX_EXEMPTIONS to (activation) - 20", creating a fail-open path where workers could defer per-PR ratchet- down to Phase 4 cleanup. Reframed Phase 4 as VERIFICATION + budget-tighten (NOT decrement). Phase 4 verifies cumulative ratchet matches target + drops cold-CI --timeout. If verification finds mismatch, escalate per §5 (per-PR discipline violation), do NOT silently patch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…ddendum (#2729) * docs(r3): §1.8 drift sweep — post T-Tier3/T-V2 wave + #2723 row #92 addendum Promotions per Director greenlight at gunbc#828 c#4426061314 + delta at gunbc#1942 c#4426061314. Sequencing per Mgr-cadence calibration (serial-after-#2702-merge). | Row | From | To | Evidence | |---|---|---|---| | #3 tier3_induction_mirror_dissolved | DECLARED | CONSUMER_LANDED | PR #2678 (merry-wolf-735, scope-verified per R-7 vs C1 Phase-1 baseline) | | #4 tier3_effect_carrier_mirror_dissolved | DECLARED | CONSUMER_LANDED + PASSING | PR #2679 (warm-ibex-579, workflow_idempotency.rs retired) | | #41 v2_oracle_no_remaining_test_consumers | DECLARED | CONSUMER_LANDED + PASSING | PR #2695 (witty-crab-518, T-V2 G-1 ratchet) | | #42 v2_directory_deleted | DECLARED | CONSUMER_LANDED + PASSING | PR #2693 (calm-seal-831, -158,670 lines; row #97 coherence test) | | #71 v3_self_host_demonstration | DECLARED | CONSUMER_LANDED + PASSING | PR #2696 (still-crab-219, demonstration harness) | Row #92 addendum: PR #2723 hot-fix-2026-05-12 #[ignore]-tagged the consumer t_las_complexity_contract_compile_error_test.rs (cold-CI wall-time reduction; 14s wall). Status preserved CONSUMER_LANDED + PASSING with explicit consumer-disabled note + rebuild-routing context (no standing T-LAS Mgr seat per gunbc#828 c#4426497). NOT promoted: row #1 / #2 / #65 / #64 / #6 already at correct state or substrate-blocked (row #1 awaits actual mirror retirement now that C1 baseline #2702 landed; row #6 was promoted in earlier PR #2631; row #64 substrate-plumbing receipt landed via PR #2694 remains DECLARED with canonical PB-Runtime witness deferral; row #65 already PASSING; row #2 already CONSUMER_LANDED via PR #2681). Pure documentation; no code touched. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): row #92 — replace placeholder comment-id with accurate citation cursor/composer-2 review (9890) on PR #2729 caught the `c#4426497xxx` stub on row #92 addendum: unfollowable placeholder weakens INVARIANTS P1 (Modeling Faithfulness). The actual Director greenlight came via internal dashboard messaging (warm-dove-618 → zesty-bear-812), not a GitHub comment thread, so a `#issuecomment-` id wouldn't exist anyway. Replace with accurate "internal-message dispatch" phrasing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs(audit): refresh SG-0 trajectory EOD + compute 7d velocity tripwire - Snapshot origin/main eed86ff: 168 Σ-count (50+116+2) - Rolling path-set intro:dissolve vs 04fa1ed pre-05-04 = 38:3 (tripwire) - §6 aligns Alarm 1 with +35 Σ-count Δ; tie tripwire to Director RED surfacing Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): anchor SG-0 tripwire to true 7 UTC-day window Reviewer-corrected: pre-05-04 baseline vs 05-11 EOD spanned ~8 days. Rebaseline to last main before 2026-05-05 00:00Z (4b156d8) into eed86ff. Path churn recomputed 37:6 (6.17:1 RED); Σ-count Δ +31 (+37/-6). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): align §6 Alarm 2 prose with calendar-window discipline Removes stale '+30 / 9-day' as contemporaneous Alarm 2 state; it was §3 2026-05-09 extrapolation shorthand, not the same rolling-7d convention as Alarm 1 per review 9697. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3 EOD δ with visible prior row (P1) BLOCKING inline review (#2714): delta column cited +1 vs midday 31acf43 while that row was absent — δ_vs_prev per §1 now +5 vs listed cea1fbe (163→168). Intraday +1 vs 31acf43 retained in notes; mirrors 05-09 mid-day/EOD split. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): §8 appendix for operator hot-fix #2723 + #846/trace Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3/§4/§8 Σ authority (P2) per review 9798 - §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): fix §8 code span Markdown for Σ=169 appendix Repair missing closing backtick so `169 (50 / 117 / 2)` renders (Codex 981x non-blocking). Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-trigger PR #2714 checks (prior run jobs cancelled stale) noop: prior Actions attempt left fmt/ci/changes/v3 cancelled mid-flight against same head SHA while self_host_ratchet stayed queued — fresh SHA escapes the duplicate-run cancel window without changing docs. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fresh Actions enqueue for PR #2714 (stuck queued/cancel cascade) noop: supersede zombie workflow whose jobs were starvation-cancelled mid-flight. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-enqueue Actions for #2714 (runner cancel starvation on d61b) Second noop: prior run stuck queued with cancelled leaf jobs; CLI rerun blocked. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): SG-0 §4.1 intro-source decomposition e3ad91d→89df284e3 - Anchor when Σ=169 row was logged vs 7d velocity-walk window - Per-slice intros/dissolves + path lists; rename caveat (cost_lens move) - Stratum read: NON_TEST +3 compiler/WAD/#87 vs TEST +4 instruments Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST SG-0 retirement worker brief (Gap 1) Director dispatch msg_3f8442f6 + PM msg_55c5f2fb: per-PR 5-10 path ratchet-down, priority T-LP > Tier3 #2 > cementing, gate #8 align Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST brief tail clause (openai-pro #3014) Per-PR minimum drop min(5,before); when before<5 require after=0 so closure PRs are satisfiable through PB-zero. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(r3): §1.8 gate #8 notes mirror PB-0 tail closure (claude #11295) Per-PR cadence + before<5 => after=0 discoverable from ledger; links Mgr brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: unify PB-0 tail rule (cursor #11313) Single bar: after<before in tail; after=0 on closing merge; P5 split requires maximal subset + PR-body i–iii + bound follow-up; gate #8 ledger matches brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 status legend includes CANVAS_RATIFIED (cursor #11319) Self-explanatory ledger for rows #63/#105; canvas ratification ≠ closure. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 #8 Notes point to PB-0 brief (claude #11382) Single-authority for tail/P5 cadence; ledger row keeps targets + link. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs: PB-0 cycle-2 brief + Tier-3 mirror pre-stage audit (msg_2e9a11ee) - Pre-authored cycle-2 NON_TEST retirement worker brief (queue on PR #3014) - Audit: host mirror symbol inventory, consumer wiring map, sequencing + worker stub Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>

* docs(audit): refresh SG-0 trajectory EOD + compute 7d velocity tripwire - Snapshot origin/main eed86ff: 168 Σ-count (50+116+2) - Rolling path-set intro:dissolve vs 04fa1ed pre-05-04 = 38:3 (tripwire) - §6 aligns Alarm 1 with +35 Σ-count Δ; tie tripwire to Director RED surfacing Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): anchor SG-0 tripwire to true 7 UTC-day window Reviewer-corrected: pre-05-04 baseline vs 05-11 EOD spanned ~8 days. Rebaseline to last main before 2026-05-05 00:00Z (4b156d8) into eed86ff. Path churn recomputed 37:6 (6.17:1 RED); Σ-count Δ +31 (+37/-6). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): align §6 Alarm 2 prose with calendar-window discipline Removes stale '+30 / 9-day' as contemporaneous Alarm 2 state; it was §3 2026-05-09 extrapolation shorthand, not the same rolling-7d convention as Alarm 1 per review 9697. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3 EOD δ with visible prior row (P1) BLOCKING inline review (#2714): delta column cited +1 vs midday 31acf43 while that row was absent — δ_vs_prev per §1 now +5 vs listed cea1fbe (163→168). Intraday +1 vs 31acf43 retained in notes; mirrors 05-09 mid-day/EOD split. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): §8 appendix for operator hot-fix #2723 + #846/trace Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3/§4/§8 Σ authority (P2) per review 9798 - §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): fix §8 code span Markdown for Σ=169 appendix Repair missing closing backtick so `169 (50 / 117 / 2)` renders (Codex 981x non-blocking). Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-trigger PR #2714 checks (prior run jobs cancelled stale) noop: prior Actions attempt left fmt/ci/changes/v3 cancelled mid-flight against same head SHA while self_host_ratchet stayed queued — fresh SHA escapes the duplicate-run cancel window without changing docs. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fresh Actions enqueue for PR #2714 (stuck queued/cancel cascade) noop: supersede zombie workflow whose jobs were starvation-cancelled mid-flight. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-enqueue Actions for #2714 (runner cancel starvation on d61b) Second noop: prior run stuck queued with cancelled leaf jobs; CLI rerun blocked. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): SG-0 §4.1 intro-source decomposition e3ad91d→89df284e3 - Anchor when Σ=169 row was logged vs 7d velocity-walk window - Per-slice intros/dissolves + path lists; rename caveat (cost_lens move) - Stratum read: NON_TEST +3 compiler/WAD/#87 vs TEST +4 instruments Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST SG-0 retirement worker brief (Gap 1) Director dispatch msg_3f8442f6 + PM msg_55c5f2fb: per-PR 5-10 path ratchet-down, priority T-LP > Tier3 #2 > cementing, gate #8 align Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST brief tail clause (openai-pro #3014) Per-PR minimum drop min(5,before); when before<5 require after=0 so closure PRs are satisfiable through PB-zero. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(r3): §1.8 gate #8 notes mirror PB-0 tail closure (claude #11295) Per-PR cadence + before<5 => after=0 discoverable from ledger; links Mgr brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: unify PB-0 tail rule (cursor #11313) Single bar: after<before in tail; after=0 on closing merge; P5 split requires maximal subset + PR-body i–iii + bound follow-up; gate #8 ledger matches brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 status legend includes CANVAS_RATIFIED (cursor #11319) Self-explanatory ledger for rows #63/#105; canvas ratification ≠ closure. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 #8 Notes point to PB-0 brief (claude #11382) Single-authority for tail/P5 cadence; ledger row keeps targets + link. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs: PB-0 cycle-2 brief + Tier-3 mirror pre-stage audit (msg_2e9a11ee) - Pre-authored cycle-2 NON_TEST retirement worker brief (queue on PR #3014) - Audit: host mirror symbol inventory, consumer wiring map, sequencing + worker stub Co-authored-by: Cursor <cursoragent@cursor.com> * docs(gate-63): sync canvas §0/§1 with CANVAS_RATIFIED ledger (codex api-review) Frontmatter + §0 single status; §1 drops stale DECLARED blockquote; points to live §1.8 row #63. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>

… gate #92, ctrl-build pointer Addresses PM/Director fix-forward guidance (msg_42c90bfb 2026-05-14): 1. Line 24 close criteria: removed the remaining "R4-DEFERRED-with-operator-acceptance" language that codex review 11524 flagged as a generic escape hatch. New wording states no generic deferral; gap-specific structural blockage routes through docs/r3-actual-close-plan.md §1 + explicit Director/operator ratification recorded against the close-plan, not this audit doc. Re-swept for R4-DEFER / R4 defer / R4-defer / R4_DEFER — zero remaining occurrences in this audit doc. 2. Gate #92 row: promoted to HARNESS_NAMED (split). Even though PR #2737 removed the #[ignore] that PR #2723 added (per ledger Notes), fail-closed posture (INVARIANTS P3) requires the close-time command to explicitly invoke the named receipt rather than depend on the ignore-bit remaining off. Row now cites both the default workspace sweep portion and an explicit `cargo test -p v3-compiler -- --include-ignored complexity_violation_compile_error_demonstrated` invocation that fires the receipt regardless of ignore-bit state at the close-ceremony commit. 3. Cursor non-blocking exploratory note: added a one-line pointer that `ctrl-build` is the internal session-runtime BuildBuddy wrapper per CLAUDE.md, and that the §10 close-ceremony auditor substitutes the canonical local equivalent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…nters (#3045) * docs(audit): refresh SG-0 trajectory EOD + compute 7d velocity tripwire - Snapshot origin/main eed86ff: 168 Σ-count (50+116+2) - Rolling path-set intro:dissolve vs 04fa1ed pre-05-04 = 38:3 (tripwire) - §6 aligns Alarm 1 with +35 Σ-count Δ; tie tripwire to Director RED surfacing Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): anchor SG-0 tripwire to true 7 UTC-day window Reviewer-corrected: pre-05-04 baseline vs 05-11 EOD spanned ~8 days. Rebaseline to last main before 2026-05-05 00:00Z (4b156d8) into eed86ff. Path churn recomputed 37:6 (6.17:1 RED); Σ-count Δ +31 (+37/-6). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): align §6 Alarm 2 prose with calendar-window discipline Removes stale '+30 / 9-day' as contemporaneous Alarm 2 state; it was §3 2026-05-09 extrapolation shorthand, not the same rolling-7d convention as Alarm 1 per review 9697. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3 EOD δ with visible prior row (P1) BLOCKING inline review (#2714): delta column cited +1 vs midday 31acf43 while that row was absent — δ_vs_prev per §1 now +5 vs listed cea1fbe (163→168). Intraday +1 vs 31acf43 retained in notes; mirrors 05-09 mid-day/EOD split. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): §8 appendix for operator hot-fix #2723 + #846/trace Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3/§4/§8 Σ authority (P2) per review 9798 - §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): fix §8 code span Markdown for Σ=169 appendix Repair missing closing backtick so `169 (50 / 117 / 2)` renders (Codex 981x non-blocking). Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-trigger PR #2714 checks (prior run jobs cancelled stale) noop: prior Actions attempt left fmt/ci/changes/v3 cancelled mid-flight against same head SHA while self_host_ratchet stayed queued — fresh SHA escapes the duplicate-run cancel window without changing docs. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fresh Actions enqueue for PR #2714 (stuck queued/cancel cascade) noop: supersede zombie workflow whose jobs were starvation-cancelled mid-flight. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-enqueue Actions for #2714 (runner cancel starvation on d61b) Second noop: prior run stuck queued with cancelled leaf jobs; CLI rerun blocked. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): SG-0 §4.1 intro-source decomposition e3ad91d→89df284e3 - Anchor when Σ=169 row was logged vs 7d velocity-walk window - Per-slice intros/dissolves + path lists; rename caveat (cost_lens move) - Stratum read: NON_TEST +3 compiler/WAD/#87 vs TEST +4 instruments Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST SG-0 retirement worker brief (Gap 1) Director dispatch msg_3f8442f6 + PM msg_55c5f2fb: per-PR 5-10 path ratchet-down, priority T-LP > Tier3 #2 > cementing, gate #8 align Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST brief tail clause (openai-pro #3014) Per-PR minimum drop min(5,before); when before<5 require after=0 so closure PRs are satisfiable through PB-zero. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(r3): §1.8 gate #8 notes mirror PB-0 tail closure (claude #11295) Per-PR cadence + before<5 => after=0 discoverable from ledger; links Mgr brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: unify PB-0 tail rule (cursor #11313) Single bar: after<before in tail; after=0 on closing merge; P5 split requires maximal subset + PR-body i–iii + bound follow-up; gate #8 ledger matches brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 status legend includes CANVAS_RATIFIED (cursor #11319) Self-explanatory ledger for rows #63/#105; canvas ratification ≠ closure. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 #8 Notes point to PB-0 brief (claude #11382) Single-authority for tail/P5 cadence; ledger row keeps targets + link. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs: PB-0 cycle-2 brief + Tier-3 mirror pre-stage audit (msg_2e9a11ee) - Pre-authored cycle-2 NON_TEST retirement worker brief (queue on PR #3014) - Audit: host mirror symbol inventory, consumer wiring map, sequencing + worker stub Co-authored-by: Cursor <cursoragent@cursor.com> * docs(gate-63): sync canvas §0/§1 with CANVAS_RATIFIED ledger (codex api-review) Frontmatter + §0 single status; §1 drops stale DECLARED blockquote; points to live §1.8 row #63. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): taxonomy §1.1 anchors for bootstrap/regen (b) cluster Addresses api-review observation: repeated Cluster M + regen_* prose replaced by one canonical brief/program anchor block + §1.1 row refs. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(pb0): reconcile taxonomy + cycle-4 brief with live NON_TEST=43 post-#3048 - §0 counts and Σ (165 / 168) match per-const awk windows on main - §3 table: 43 rows in census order; drop paths retired in PR #3048 - §2 + changelog: record #3048 landing; note pb_method_template_projection_generated - cycle-4 brief: §0.1 historical landed scope (no stale dispatch targets) - sg0 pointer comment: 43-entry NON_TEST + 3 FRAGMENTS Fixes cursor review 11553 (stale 50-row headline + phantom §3 rows). Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>

…msg_b44f4320) (#3055) * docs(audit): refresh SG-0 trajectory EOD + compute 7d velocity tripwire - Snapshot origin/main eed86ff: 168 Σ-count (50+116+2) - Rolling path-set intro:dissolve vs 04fa1ed pre-05-04 = 38:3 (tripwire) - §6 aligns Alarm 1 with +35 Σ-count Δ; tie tripwire to Director RED surfacing Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): anchor SG-0 tripwire to true 7 UTC-day window Reviewer-corrected: pre-05-04 baseline vs 05-11 EOD spanned ~8 days. Rebaseline to last main before 2026-05-05 00:00Z (4b156d8) into eed86ff. Path churn recomputed 37:6 (6.17:1 RED); Σ-count Δ +31 (+37/-6). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): align §6 Alarm 2 prose with calendar-window discipline Removes stale '+30 / 9-day' as contemporaneous Alarm 2 state; it was §3 2026-05-09 extrapolation shorthand, not the same rolling-7d convention as Alarm 1 per review 9697. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3 EOD δ with visible prior row (P1) BLOCKING inline review (#2714): delta column cited +1 vs midday 31acf43 while that row was absent — δ_vs_prev per §1 now +5 vs listed cea1fbe (163→168). Intraday +1 vs 31acf43 retained in notes; mirrors 05-09 mid-day/EOD split. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): §8 appendix for operator hot-fix #2723 + #846/trace Σ-orthogonal housekeeping: exemptions 80→84, SG-0 verified 169 @ d98d1e0, ratchet-down protocol, digest #828 link + companion #2718 per Director MSG. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): reconcile §3/§4/§8 Σ authority (P2) per review 9798 - §3: row e3ad91d (+1 TEST vs eed86ff) for #2694; #2712 Σ-stable note - §4: scope seven-day math to archived eed86ff; link +1 to new row - §8: clarify #2723 Σ-orthogonal vs 169 explained by earlier lineage Co-authored-by: Cursor <cursoragent@cursor.com> * docs(audit): fix §8 code span Markdown for Σ=169 appendix Repair missing closing backtick so `169 (50 / 117 / 2)` renders (Codex 981x non-blocking). Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-trigger PR #2714 checks (prior run jobs cancelled stale) noop: prior Actions attempt left fmt/ci/changes/v3 cancelled mid-flight against same head SHA while self_host_ratchet stayed queued — fresh SHA escapes the duplicate-run cancel window without changing docs. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fresh Actions enqueue for PR #2714 (stuck queued/cancel cascade) noop: supersede zombie workflow whose jobs were starvation-cancelled mid-flight. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: re-enqueue Actions for #2714 (runner cancel starvation on d61b) Second noop: prior run stuck queued with cancelled leaf jobs; CLI rerun blocked. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): SG-0 §4.1 intro-source decomposition e3ad91d→89df284e3 - Anchor when Σ=169 row was logged vs 7d velocity-walk window - Per-slice intros/dissolves + path lists; rename caveat (cost_lens move) - Stratum read: NON_TEST +3 compiler/WAD/#87 vs TEST +4 instruments Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST SG-0 retirement worker brief (Gap 1) Director dispatch msg_3f8442f6 + PM msg_55c5f2fb: per-PR 5-10 path ratchet-down, priority T-LP > Tier3 #2 > cementing, gate #8 align Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): PB-0 NON_TEST brief tail clause (openai-pro #3014) Per-PR minimum drop min(5,before); when before<5 require after=0 so closure PRs are satisfiable through PB-zero. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(r3): §1.8 gate #8 notes mirror PB-0 tail closure (claude #11295) Per-PR cadence + before<5 => after=0 discoverable from ledger; links Mgr brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs: unify PB-0 tail rule (cursor #11313) Single bar: after<before in tail; after=0 on closing merge; P5 split requires maximal subset + PR-body i–iii + bound follow-up; gate #8 ledger matches brief. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 status legend includes CANVAS_RATIFIED (cursor #11319) Self-explanatory ledger for rows #63/#105; canvas ratification ≠ closure. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(r3): §1.8 #8 Notes point to PB-0 brief (claude #11382) Single-authority for tail/P5 cadence; ledger row keeps targets + link. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs: PB-0 cycle-2 brief + Tier-3 mirror pre-stage audit (msg_2e9a11ee) - Pre-authored cycle-2 NON_TEST retirement worker brief (queue on PR #3014) - Audit: host mirror symbol inventory, consumer wiring map, sequencing + worker stub Co-authored-by: Cursor <cursoragent@cursor.com> * docs(gate-63): sync canvas §0/§1 with CANVAS_RATIFIED ledger (codex api-review) Frontmatter + §0 single status; §1 drops stale DECLARED blockquote; points to live §1.8 row #63. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(audit): taxonomy §1.1 anchors for bootstrap/regen (b) cluster Addresses api-review observation: repeated Cluster M + regen_* prose replaced by one canonical brief/program anchor block + §1.1 row refs. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(pb0): reconcile taxonomy + cycle-4 brief with live NON_TEST=43 post-#3048 - §0 counts and Σ (165 / 168) match per-const awk windows on main - §3 table: 43 rows in census order; drop paths retired in PR #3048 - §2 + changelog: record #3048 landing; note pb_method_template_projection_generated - cycle-4 brief: §0.1 historical landed scope (no stale dispatch targets) - sg0 pointer comment: 43-entry NON_TEST + 3 FRAGMENTS Fixes cursor review 11553 (stale 50-row headline + phantom §3 rows). Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Debt-Paydown Mgr — lane through R3 close * WIP: R3 Debt-Paydown Mgr — lane through R3 close * docs(briefs): cycle-5 cementing note + cycle-6 Gap-tier STOP table (Director msg_f05c2d68) Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>

…3024) * docs(r3): R3 close predicate-execution log — Phase 2 fill (45 EXECUTED / 61 N/A_NOT_PASSING) Populates docs/audit/r3-close-predicate-execution-2026-05-13.md (skeleton merged via PR #3019) per Gap 10 Phase 2 of docs/r3-actual-close-plan.md. For every §1.8 row at HEAD a2a7a88: - Status = PASSING / SATISFIED-BY-CONSTRUCTION (45 rows) → predicate execution status EXECUTED; close-time harness = workspace ratchet batch (cargo fmt / clippy --all-targets -D warnings / cargo test --workspace) with per-row ratchet cited under §1.8 row Notes; result pointer → §Workspace batch receipt. - Status = CONSUMER_LANDED / DECLARED / R3-LOAD-BEARING (decl-stage) / INTEGRATION_RECEIPT / CANVAS_RATIFIED (61 rows) → predicate execution status N/A_NOT_PASSING; per r3-close-interrogation.md §8 the predicate-execution requirement attaches only to PASSING gates. Adds row #106 show_correct_code_diagnostic_coverage (merged PR #3020 / Gap 9) so table mirrors §1.8 ledger one-for-one at HEAD (parity grep `grep -cE '^\\| [0-9]+ \\| `' yields 106 on both surfaces). Workspace batch receipt records cargo fmt --all --check exit 0 and clippy --all-targets -D warnings exit 0; cargo test --workspace --exclude gunbc-dag-tests is initiated and the §10 close-ceremony audit doc records the final 24h-of-close re-sweep with the merge-commit SHA. Overall verdict remains PENDING (61 gates not at PASSING at HEAD; close ceremony not opened). Authority: merged PR gunbc/gunbc#3013 Gap 10 close criterion; PR #3019 skeleton; PR #3020 row #106; docs/r3-close-interrogation.md §8; docs/r3-actual-close-plan.md Gap 10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): weaken predicate-execution-log claims — Phase 2 = harness-naming, not execution receipt Addresses codex/codex-default REQUEST_CHANGES on PR #3024 (/api/reviews/11316/artifacts/stdout.log, 2026-05-13T20:35:21Z): 1. Per-row status `EXECUTED` (45 rows) → `HARNESS_NAMED`. The Phase 2 PR names the close-time harness per PASSING / SATISFIED-BY-CONSTRUCTION gate so the §10 close-ceremony 24h workspace re-sweep has a mechanical command to run; it does NOT assert an execution receipt. Execution receipts (PASS/FAIL per gate, log pointers, merge-commit SHA) are produced by the §10 close-ceremony artifact `docs/audit/r3-close-YYYY-MM-DD.md`, not by this Phase 2 PR. This eliminates the conflation between "harness identification" and "execution receipt" flagged at lines 26/174/180. 2. SHA anchor: explicit "Ledger-snapshot anchor" section clarifies that `a2a7a8825` is the §1.8 ledger snapshot at this PR's base commit (`git merge-base HEAD main`), and that this PR adds only the audit doc — it does not modify §1.8 or any authority surface. The derivation is valid for any HEAD that includes `a2a7a8825` with no subsequent §1.8 edits. Resolves the "HEAD a98cbc5 vs claimed a2a7a88" single-authority/live-state mismatch (INVARIANTS P1/P2). 3. Workspace batch receipt: only `cargo fmt --all --check` and `cargo clippy --all-targets -- -D warnings` are recorded as Phase 2 partial receipts (both clean against base commit `a2a7a8825`). `cargo test` is explicitly marked NOT_EXECUTED_BY_THIS_PR and anchored to §10 close-ceremony per r3-close-interrogation.md §8 + INVARIANTS.md P3 fail-closed/live-state discipline. Status-bucket distribution table and verdict text updated consistently. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix 61→58 verdict count drift — bucket table is authority (PR #3024 cursor APPROVE_WITH_COMMENTS) Addresses cursor/composer-2 review at 2026-05-13T21:09Z: line 28 verdict said 'remaining 61 gates' but Status-bucket table (20+30+4+3+1=58) is the mechanical authority. 48+58=106. Aligns narrative with single-authority / live-state discipline (INVARIANTS P1/P2). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix INVARIANTS P1→P2 label drift per openai-pro APPROVE_WITH_COMMENTS §Ledger-snapshot anchor heading and References list incorrectly labeled the single-authority / no-parallel-authority rule as P1 (Modeling Faithfulness). The correct invariant is P2 Boundary Discipline (INVARIANTS.md:144). P3 Fail-Closed reference is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): rebalance §1.8 status buckets — row #11 R3-LOAD-BEARING→DECLARED, row #100 PASSING→DECLARED+TEXT-RATCHETED; re-anchor to main 4b491e4 Addresses codex non-blocking finding on PR #3024 (status-bucket hygiene): - Row #11 `tc1_eta_equivalence_executable`: per §1.8 the cell starts with "**DECLARED through R3**" (canvas-deferred past R3 per Path-A); prior parser priority matched the in-cell phrase "R3-load-bearing per §1.5" before the leading "DECLARED" keyword. Row is now DECLARED. - Row #100 `project_github_actions_landed`: amended on main to "**DECLARED + TEXT-RATCHETED**" (post-merge ledger evolution beyond prior CONSUMER_LANDED + PASSING shape). Row is now DECLARED. Re-derivation against current main (`4b491e46f`): - PASSING 45→44 (row #100 demoted) - DECLARED 30→32 (rows #11 + #100 added) - R3-LOAD-BEARING 4→3 (row #11 removed) - Other buckets unchanged. - Total 106 (parity preserved). - HARNESS_NAMED 48→47; N/A_NOT_PASSING 58→59. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): tighten Purpose bullets — composite CONSUMER_LANDED + PASSING is HARNESS_NAMED, bare CONSUMER_LANDED is N/A (cursor APPROVE exploratory note PR #3024) Aligns the prose with the table: §1.8 'CONSUMER_LANDED + PASSING' (e.g. rows #1, #97, #99, #101) flows to HARNESS_NAMED via the 'contains PASSING' clause; bare 'CONSUMER_LANDED' (e.g. rows #2, #3, #96) is N/A_NOT_PASSING. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): split harness override for gate #71 — strict receipt is #[ignore]'d Addresses BLOCKING inline comment on PR #3024 at line 135 (2026-05-13T23:22Z): Gate #71 v3_self_host_demonstration: the canonical strict receipt test r3_v3_self_host_demonstration_suite_passes_through_runner is #[ignore]'d at HEAD pending T-FixedPoint / Lane 3 promotion (per the test's own ignore-doc + docs/design-fixed-point-ratchet.md). Plain `cargo test --workspace` skips it, so the prior harness column overstated coverage for this row. Fix: row #71 now uses HARNESS_NAMED (split) and cites: 1. Non-ignored portion that DOES fire under the default workspace sweep: r3_v3_self_host_demonstration_dag_lowers_with_substituted_bin_path (r3_v3_self_host_demonstration_dag_test.rs:38) + SG-0 census presence ratchet (sg0_census_test.rs:667). 2. Ignored strict receipt requiring explicit invocation: `cargo test -p v3-compiler --release -- --ignored \ r3_v3_self_host_demonstration_suite_passes_through_runner`. Adds a general convention to the §1.8 table preamble: any gate whose canonical receipt is #[ignore]'d at HEAD is flagged HARNESS_NAMED (split) and must cite both the default-sweep portion and the --ignored override. Auditors verify §8 coverage by grepping for `HARNESS_NAMED (split)` and confirming the §10 sweep includes every cited --ignored override. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): defer to close-plan per-gap dispositions; remove generic R4-defer escape hatch (codex BLOCKING PR #3024 #2) Addresses codex BLOCKING finding #2 (line 24): the prior phrase "or is operator-accepted as R4-DEFERRED per §10" reintroduced a generic R4-defer escape hatch the higher-authority close plan explicitly forecloses for Gaps 1/2/3/9 per operator §4 IN-R3 ratification 2026-05-13 (docs/r3-actual-close-plan.md §11). Replacement defers to docs/r3-actual-close-plan.md's per-gap disposition: PROVEN-with-landed-PR-only for Gaps 1/2/3/9 (R4-defer + THESIS-reframe paths STRUCTURALLY FORECLOSED), close-plan disposition for other gaps. This audit doc inherits dispositions and does not author a parallel deferral semantics. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): manager fix-forward — strip generic R4-DEFER, split-harness gate #92, ctrl-build pointer Addresses PM/Director fix-forward guidance (msg_42c90bfb 2026-05-14): 1. Line 24 close criteria: removed the remaining "R4-DEFERRED-with-operator-acceptance" language that codex review 11524 flagged as a generic escape hatch. New wording states no generic deferral; gap-specific structural blockage routes through docs/r3-actual-close-plan.md §1 + explicit Director/operator ratification recorded against the close-plan, not this audit doc. Re-swept for R4-DEFER / R4 defer / R4-defer / R4_DEFER — zero remaining occurrences in this audit doc. 2. Gate #92 row: promoted to HARNESS_NAMED (split). Even though PR #2737 removed the #[ignore] that PR #2723 added (per ledger Notes), fail-closed posture (INVARIANTS P3) requires the close-time command to explicitly invoke the named receipt rather than depend on the ignore-bit remaining off. Row now cites both the default workspace sweep portion and an explicit `cargo test -p v3-compiler -- --include-ignored complexity_violation_compile_error_demonstrated` invocation that fires the receipt regardless of ignore-bit state at the close-ceremony commit. 3. Cursor non-blocking exploratory note: added a one-line pointer that `ctrl-build` is the internal session-runtime BuildBuddy wrapper per CLAUDE.md, and that the §10 close-ceremony auditor substitutes the canonical local equivalent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): re-anchor §1.8 ledger snapshot to current merge-base c055495; row #63 DECLARED→CANVAS_RATIFIED (codex BLOCKING PR #3024 review 11585) Addresses codex BLOCKING (review 11585): the prior anchor 4b491e4 was stale relative to git merge-base HEAD origin/main (now c055495 after main auto-merged in PRs #3025, #3035, #3037, #3038, #3040, #3046, #3049, #3050). The audit doc's single-authority claim must hold against the actual merge-base, not a frozen prior commit. Codex's row count of 100 at 4b491e4 is incorrect on this worktree (verified 106 at both 4b491e4 and c055495), but the anchor-drift point is valid: per INVARIANTS P2 the authoritative §1.8 snapshot must be reproducible from the current merge-base. Re-derivation at c055495 (verified mechanically): PASSING 44 + SATISFIED-BY-CONSTRUCTION 3 + CONSUMER_LANDED 20 + DECLARED 31 + R3-LOAD-BEARING 3 + INTEGRATION_RECEIPT 3 + CANVAS_RATIFIED 2 = 106. Versus prior anchor: row #63 substrate_gap_workflow_scheduling_closed moved DECLARED→CANVAS_RATIFIED (PR #2831 squash 89df284); buckets adjust DECLARED 32→31, CANVAS_RATIFIED 1→2. HARNESS_NAMED 47 and N/A_NOT_PASSING 59 totals are unchanged (the moved row stays N/A). Row #63 audit-doc cell flipped to cite CANVAS_RATIFIED label. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…§1.8 evidence-cite Land 4 #[ignore]'d cementing tests pinning the consumer-path expectation for match-payload structural descent + multi-arg per-arg vectors against both complexity_of + symbolic_cost_of, with a named lens-consumer-walker substrate-extension blocker. Producer surface is correct (m2 receipts pin StrictSubValue + ChildAccessorCall projection); gap is consumer-side: complexity.dag + cost.dag have no Disj/match-arm summary fold, so compose_many_inputs is never reached on match-arm result ports for ADT-typed recursive functions. Follow-on canvas pending under R3 Substrate Mgr standing authority per docs/design-complexity-lens-behavioral-completeness.md §272/§282; follow-on PR drops the #[ignore] markers as its same-PR cementing receipt. Gate #76 stays CONSUMER_LANDED in §1.8 — NOT promoted to PASSING per feedback_only_claim_what_actually_exists. Hot-fix #2723 precedent (Pattern-A scaffold with #[ignore]) is the shape: preserve executable evidence of the gap in-tree under a named blocker so the §1.8 row's evidence-cite points at a concrete file. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…§1.8 evidence-cite (#3116) * WIP: R3 gate #76: e_p_per_call_descent_evidence_full_coverage (T-E-P-Producer * R3 gate #76 Phase-3 lens-consumer cementing ratchets (#[ignore]'d) + §1.8 evidence-cite Land 4 #[ignore]'d cementing tests pinning the consumer-path expectation for match-payload structural descent + multi-arg per-arg vectors against both complexity_of + symbolic_cost_of, with a named lens-consumer-walker substrate-extension blocker. Producer surface is correct (m2 receipts pin StrictSubValue + ChildAccessorCall projection); gap is consumer-side: complexity.dag + cost.dag have no Disj/match-arm summary fold, so compose_many_inputs is never reached on match-arm result ports for ADT-typed recursive functions. Follow-on canvas pending under R3 Substrate Mgr standing authority per docs/design-complexity-lens-behavioral-completeness.md §272/§282; follow-on PR drops the #[ignore] markers as its same-PR cementing receipt. Gate #76 stays CONSUMER_LANDED in §1.8 — NOT promoted to PASSING per feedback_only_claim_what_actually_exists. Hot-fix #2723 precedent (Pattern-A scaffold with #[ignore]) is the shape: preserve executable evidence of the gap in-tree under a named blocker so the §1.8 row's evidence-cite points at a concrete file. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Address codex BLOCKING — P5 Mechanism (b) receipts for new hand-Rust test codex review identified that the new cementing file under src/v3/compiler/tests/integration/cementing/ requires INVARIANTS §P5 Mechanism (b) receipt shape: named lane + concrete ROADMAP row, plus matching EXPECTED_HAND_AUTHORED_TEST census line. Prose-only deferral ("canvas pending") does not satisfy the gate. Adds the file path to EXPECTED_HAND_AUTHORED_TEST in sg0_census_test.rs and the matching dissolution-bearing receipt row in INVARIANTS.md (cites ROADMAP.md "Lane E-P — per-call descent-evidence provenance" + docs/r3-program-plan.md §1.8 gate #76 + the named lens-consumer match-arm walker substrate extension under R3 Substrate Mgr standing authority as the dissolution trigger). SG-0 census passes (16/16 ok). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * ci: re-trigger after PR body SG-0 hand-path delta declaration * ci: re-trigger after SG-0 pairing line adds 'dispatch' keyword * ci: re-trigger after SG-0 pairing cites brief path --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

briansrls added 2 commits May 11, 2026 21:13

WIP: URGENT cold-v3 CI hot-fix cut: implement gunbc#2722

e7bd496

WIP: URGENT cold-v3 CI hot-fix cut: implement gunbc#2722

4225876

briansrls changed the title ~~URGENT cold-v3 CI hot-fix cut: implement gunbc#2722~~ hot-fix: cut cold-v3 slow tests May 12, 2026

briansrls marked this pull request as ready for review May 12, 2026 01:20

briansrls merged commit d98d1e0 into main May 12, 2026
7 of 8 checks passed

This was referenced May 12, 2026

session/deep-wolf-155 · deep-wolf-155 #846

Closed

session/zesty-bear-812 · gunbc Director #828

Closed

This was referenced May 12, 2026

ci(hot-fix): SKIP integration test execution per operator directive (cold-v3 → ~10min) #2724

Merged

docs(briefs): Director scaffold for cold-v3 rebuild coordinator #2725

Merged

briansrls mentioned this pull request May 12, 2026

docs(r3): §1.8 drift sweep — post T-Tier3/T-V2 wave + #2723 row #92 addendum #2729

Merged

briansrls mentioned this pull request May 14, 2026

docs(r3): R3 close predicate-execution log — Phase 2 fill (Gap 10) #3024

Merged

5 of 6 tasks

briansrls mentioned this pull request May 14, 2026

R3 gate #76 Phase-3 lens-consumer cementing ratchets (#[ignore]'d) + §1.8 evidence-cite #3116

Merged

4 tasks done

Navigation Menu

Repository navigation

hot-fix: cut cold-v3 slow tests - #2723

hot-fix: cut cold-v3 slow tests#2723
briansrls merged 2 commits into
mainfrom
session/loyal-pike-480

briansrls commented May 12, 2026 •

edited

Loading

Uh oh!

briansrls commented May 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

briansrls commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Cut Rationale

Timeout Ledger

Test Plan

Uh oh!

briansrls commented May 12, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

briansrls commented May 12, 2026 •

edited

Loading