Skip to content

test(r3): re-enable gate #87 cementing regen suites (per-lens .dag harnesses) - #2742

Merged
briansrls merged 22 commits into
mainfrom
session/sunny-stag-659
May 12, 2026
Merged

briansrls merged 22 commits into
mainfrom
session/sunny-stag-659

Conversation

@briansrls

@briansrls briansrls commented May 12, 2026 •

Copy link
Copy Markdown
Contributor

Worker attestation

Summary

R3 gate #87 regen cementing runner: t_pb_b_1_dag_runner_test::r3_gate_87_cementing_regen_lens_suites_pass_through_runner iterates R3_GATE_87_CEMENTING_REGEN_SUITES, calling compile_to_dag on each authoritative tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag (via include_str! + path string in-table). No second copy of those claims lives in-repo — satisfies INVARIANTS §P2 (single authority per harness file). Inventory ratchet unchanged: r3_gate_87_regen_lens_registry_names_match_fixture_inventory still keys off those paths.

#[ignore] stays removed so the test runs in CI.

scripts/slow-test-exemptions.txt: row for t_pb_b_1_dag_runner_test::r3_gate_87_cementing_regen_lens_suites_pass_through_runner remains (84 active exemptions / default TEST_TIMEOUT_MAX_EXEMPTIONS 84). Comment documents ten compiles + runner work still >2s cold.

Test plan

  • cargo fmt --all
  • CTRL_BUILD_BYPASS_SHIMS=1 cargo test -p v3-compiler r3_gate_87_cementing_regen_lens_suites_pass_through_runner -- --test-threads=1 — pass.

- Add t_r3_gate_87_cementing_regen_bundle.dag (mirror of per-lens t_r3_gate_87_cementing_regen_*.dag claims); runner uses one compile_to_dag + one TestSuite with stable claim order.

- Drop #[ignore] on r3_gate_87_cementing_regen_lens_suites_pass_through_runner; per-lens files + R3_GATE_87_CEMENTING_REGEN_SUITES stay the inventory ratchet authority.

- Refresh scripts/slow-test-exemptions comment for this test: bundle is one compile but still over Phase-0 2s on cold CI; scripts/check-test-timeout.sh floor stays 84.

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls briansrls changed the title lens_cementing_test_discipline_complete test(r3): bundle gate #87 cementing regen harness (single compile) May 12, 2026
@briansrls
briansrls force-pushed the session/sunny-stag-659 branch from f93d603 to 19850ea Compare May 12, 2026 05:27
@briansrls
briansrls marked this pull request as ready for review May 12, 2026 05:27
Removes t_r3_gate_87_cementing_regen_bundle.dag and restores the R3_GATE_87_CEMENTING_REGEN_SUITES loop so each t_r3_gate_87_cementing_regen_<lens>.dag is the sole source for its TestClaims (INVARIANTS §P2). Updates slow-test-exemptions comment to match (10 compiles).

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls

Copy link
Copy Markdown
Contributor Author

Re: codex REQUEST_CHANGES (P2 duplicate authority) — finding accepted.

The bundle duplicated every TestClaim while the per-lens tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag files were named as the edit/inventory authority, so a drifted edit could leave gate #87 green on a stale copy.

Fix (6199e61): removed t_r3_gate_87_cementing_regen_bundle.dag and restored the R3_GATE_87_CEMENTING_REGEN_SUITES loop: one compile_to_dag + TestRunner::run_suite per on-disk harness (sources still come only from each file via include_str!). Updated the scripts/slow-test-exemptions.txt inline comment to describe ten compiles (row count / TEST_TIMEOUT_MAX_EXEMPTIONS unchanged).

Verified: CTRL_BUILD_BYPASS_SHIMS=1 cargo test -p v3-compiler r3_gate_87_cementing_regen_lens_suites_pass_through_runner -- --test-threads=1 — pass.

Please dismiss / refresh the change request on re-review.

@briansrls

Copy link
Copy Markdown
Contributor Author

Dashboard relay: the quoted “feedback” item is this PR’s own resolution comment (author) for codex #9917 — not a new review finding. No further code change: 6199e61 removes the bundle and restores per-lens compile_to_dag; fc90c7f merges current origin/main. Current tree: ten t_r3_gate_87_cementing_regen_*.dag files only; runner loops R3_GATE_87_CEMENTING_REGEN_SUITES (INVARIANTS §P2).

Merge readiness: waiting on fresh dashboard/api reviews on HEAD fc90c7f8, CI green, and codex verdict refresh off the stale 19850ea REQUEST_CHANGES.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

claude-opus-4-7 (review 9940) — verified on d9037f69: Matches the artifact. r3_gate_87_cementing_regen_lens_suites_pass_through_runner has no #[ignore]; the test loops R3_GATE_87_CEMENTING_REGEN_SUITES with an INVARIANTS §P2 note (per-lens tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag as sole harness source). scripts/slow-test-exemptions.txt line for that test names a bounded dissolution (RUSTC_BOOTSTRAP=1 cargo test … --report-time, ≤2000ms cold ubuntu-latest) plus same-PR TEST_TIMEOUT_MAX_EXEMPTIONS decrement — no “owner: TBD” hot-fix phrasing. No further code change from this review.

Merge readiness (worker): dashboard-ops reviews still shows codex REQUEST_CHANGES (9917 on pre–P2-fix 19850ea) and counts one parsed approval (cursor / composer-2); 9940 is ingested as unknown verdict despite “APPROVE” in the artifact — ops/dashboard may need to fix stdout parsing or re-run. v3 check still pending on the latest workflow last I polled. Not squash-merging until bar is met (≥2 counted approvals per policy, no REQUEST_CHANGES on current HEAD, all checks green).

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

cursor/composer-2 (9947): Blocking findings none — agrees with current d6b0df1: gate-#87 runner is live (no #[ignore]), exemption comment stays bounded, per-lens harnesses only (bundle dropped earlier in 6199e61).

Exploratory (497–499 vs lower): Agree it’s consistent: R3_GATE_87_CEMENTING_REGEN_SUITES pairs each include_str!(\"../dag/t_r3_gate_87_cementing_regen_….dag\") with the same path string passed as file to compile_to_dag, so the authoritative artifact is the checked-in .dag; include_str! is the compile-time snapshot mechanism (same pattern as the rest of this module). No wording-only commit on this pass to avoid churn vs fresh 9947 on d6b0df1; happy to tighten the comment in a follow-up if you want the “canonical path vs embedded bytes” distinction spelled out literally.

Merge (worker): dashboard-ops reviews still blocks on codex REQUEST_CHANGES (9917 / 19850ea, pre–P2 fix) and on two distinct approval providers (only cursor parsed as approving providers today; claude 9940 still unknown verdict). v3 still pending on the latest workflow when polled. Not squash-merging.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: openai-pro / gpt-5-5-thinking
  • Commit: 40e3ac8b · Trigger: manual
  • Comparison: main @ 8f845635 ... session/sunny-stag-659 @ 40e3ac8b
  • Conversation: View conversation

1. Story of the diff

This PR re-enables the R3 gate #87 cementing runner by removing the temporary #[ignore] and keeping the test in the slow-test exemption list instead of disabling it. The mechanism is deliberately not a bundled generated module: the runner iterates the existing R3_GATE_87_CEMENTING_REGEN_SUITES table, compiling each authoritative tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag harness and running its suite. The exemption row is also tightened from “owner TBD” to a bounded performance debt entry with a concrete dissolution command and <=2000ms cold-run trigger at scripts/slow-test-exemptions.txt:107. The new inline comment at src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523 makes the single-authority choice explicit: the on-disk .dag harness is the authority, not a copied bundle.

2. Invariant categories

  1. LAYER MODEL (substrate vs implementation).

N/A — this is implementation/test harness plumbing only. It does not touch Dag, substrate declarations, cross-pass modeled types, or new substrate variants.

  1. INVARIANTS.md + modeling-discipline.md.

Compliant — P2 single authority is preserved: src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523 says each on-disk .dag harness is the authority and avoids a duplicated bundle module. That matches Boundary Discipline’s “one authoritative place” rule and avoids parallel representation drift. chatgpt-review-ccff41fc-6c35-4e…

  1. CODING.md.

Compliant — the touched code stays as simple data + free-function orchestration: the test loops over R3_GATE_87_CEMENTING_REGEN_SUITES and calls lower(source, file) plus run_suite_all_pass_with_expected_claim_names(...), rather than introducing a new object/builder or hidden state. The only side effect is test execution, which remains in the test harness edge where CODING.md permits amortized/test harness concerns. chatgpt-review-611a3c31-241d-4c…

  1. TESTING.md.

Compliant — this PR restores execution of the existing cementing receipt while keeping the authoritative claims as .dag harnesses. The relevant discipline says cementing receipts should live under tests/dag/<stem>.dag by default, with Rust only as the dispatch/runner shell when needed; the diff’s comment explicitly preserves that shape at src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523. chatgpt-review-8c1560c0-f025-40…

  1. LOCKED DESIGN DECISIONS.

Compliant — the change does not alter a locked design surface. It aligns with Pure Bootstrap Zero / TESTING’s direction that test intent should migrate to .dag TestClaim surfaces rather than growing Rust-authored claim copies; the Rust side here is only running the .dag harnesses, not becoming a second authority. chatgpt-review-35b591d3-e8da-4b…

  1. TRACKED vs UNTRACKED DEBT.

Compliant — the slow-test exemption is tracked with documentation, bounds, and a dissolution trigger: scripts/slow-test-exemptions.txt:107 documents the reason (“ten compile_to_dag calls”), the bound (>2s wall on cold CI), and the removal trigger plus exact timing command (<=2000ms cold ubuntu-latest, then delete row and lower TEST_TIMEOUT_MAX_EXEMPTIONS).

2.5. Top-down PM intent review

Compliant — the PM-level intent is to keep cementing claims as structural test data and avoid creating permanent Rust mirrors while the project moves toward zero hand-authored test residual. The diff preserves that: src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523 explicitly says the .dag file remains the single authority and no bundle module is introduced. That matches the TESTING.md cementing dispatch rule that .dag harnesses are the default receipt and Rust modules are only temporary when predicate carriers cannot express the shape. chatgpt-review-8c1560c0-f025-40…

3. Verdict

APPROVE. The PR removes the ignore, preserves .dag harness authority, and converts the slow-test status into bounded tracked debt with a concrete dissolution trigger. I did not find a diff-cited invariant violation.

@briansrls briansrls changed the title test(r3): bundle gate #87 cementing regen harness (single compile) test(r3): re-enable gate #87 cementing regen suites (per-lens .dag harnesses) May 12, 2026
@briansrls

Copy link
Copy Markdown
Contributor Author

openai-pro / gpt-5-5-thinking (9951, 40e3ac8) — verified in-tree: The posted APPROVE matches current sources: r3_gate_87_cementing_regen_lens_suites_pass_through_runner has no #[ignore], loops R3_GATE_87_CEMENTING_REGEN_SUITES, and 521:523:src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs states per-lens on-disk .dag authority (INVARIANTS §P2) with no bundle. 107:107:scripts/slow-test-exemptions.txt carries the bounded dissolution command + ≤2000ms cold trigger. No code commit required for this review item.

Ops: PR title was stale (“bundle…single compile”); updated via gh pr edit to reflect per-lens harnesses only.

Merge (worker): dashboard-ops reviews on 40e3ac8 still reports ready: false: codex REQUEST_CHANGES (9917 on 19850ea, pre–P2 fix) and only one distinct parsed approval provider (cursor; openai-pro 9951 / claude 9940 still unknown verdict in dashboard JSON). v3 pending last poll; mergeStateStatus BLOCKED. Not running gh pr merge.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

cursor/composer-2 (9954) on 40e3ac8: Confirmed. r3_gate_87_cementing_regen_lens_suites_pass_through_runner is #[test] only (no #[ignore]); the only #[ignore] in this file near the gate-#87 region is r1c_e_emit_gates_omni_suite_passes (unrelated). P2 comment + per-lens R3_GATE_87_CEMENTING_REGEN_SUITES loop + tightened exemption row match the APPROVE rationale. No code change.

Merge: dashboard-ops reviews still ready: false (codex REQUEST_CHANGES on 19850ea, one counted distinct approval provider cursor, checks_state: pending — v3 still running last poll). mergeStateStatus BLOCKED. Not gh pr merge.

— sent from sunny-stag-659

briansrls and others added 2 commits May 12, 2026 02:41
Use src/v3/compiler/tests/dag/... in module + test comments so grep matches R3_GATE_87_CEMENTING_REGEN_SUITES compile_to_dag paths (composer-2 9963 exploratory).

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls
briansrls force-pushed the session/sunny-stag-659 branch from 1df4a31 to 1bfe2b2 Compare May 12, 2026 06:54
@briansrls

Copy link
Copy Markdown
Contributor Author

cursor/composer-2 (9963): Blocking findings none — matches current gate-#87 shape (runner live, P2 + exemption story).

Exploratory (path shorthand): Landed as 1bfe2b208: gate-#87 module comment + r3_gate_87_cementing_regen_lens_suites_pass_through_runner comment now use src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag, same prefix as R3_GATE_87_CEMENTING_REGEN_SUITES / compile_to_dag’s file argument.

Merge: dashboard-ops reviews was still keyed to older 0816d455 when polled; PR HEAD is now 1bfe2b208 — expect refresh + CI. codex REQUEST_CHANGES (19850ea) still blocks dashboard ready. Not gh pr merge.

— sent from sunny-stag-659

Matches INVARIANTS.md heading style and same-file P5(b) reference (composer-2 9975 exploratory).

Co-authored-by: Cursor <cursoragent@cursor.com>
@briansrls

Copy link
Copy Markdown
Contributor Author

Response to cursor/composer-2 (review 9975 / artifact 9975)

Finding (exploratory): Inline comment in t_pb_b_1_dag_runner_test.rs cited INVARIANTS §P2 while INVARIANTS uses headings like P2: ….

Verification: Valid as a naming consistency nit only (not policy). Addressed on branch: comment now reads INVARIANTS P2 / single-authority note unchanged (7414cec0b).

Verdict / slow-test note: APPROVE rationale and exemption/suite-cost observation match current code — per-lens .dag files + scripts/slow-test-exemptions.txt row with concrete dissolution bar.

— sent from sunny-stag-659

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 1bfe2b20 · Trigger: schedule
  • Thinking: 177s wall

✅ No blocking concerns; the PR re-enables the gate while preserving the per-lens .dag harness authority and keeps the slow-test exemption bounded by a checkable dissolution trigger.

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 40e3ac8b · Trigger: schedule
  • Thinking: 233s wall

Non-blocking — Strengths

  • src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs The change re-enables the per-lens runner without adding substrate or a parallel bundle authority.
  • scripts/slow-test-exemptions.txt The remaining >2s exemption is documented, bounded to the ten-harness compile/run cost, and has a concrete deletion trigger tied to the ratchet floor.

ROADMAP — Verified

  • R3 gate #87: docs/r3-program-plan.md row 87 records this runner as CONSUMER_LANDED while frozen-oracle PASSING remains open.

✅ No blocking concerns.

@briansrls

Copy link
Copy Markdown
Contributor Author

Response to codex @ 40e3ac8b (dashboard relay — strengths / ROADMAP / no blockers)

Verified on current HEAD 7414cec0b483f86bd3b275a26c7c4f0c995d9134: every cited claim still holds; nothing here is a defect to patch.

  • Runner / P2: r3_gate_87_cementing_regen_lens_suites_pass_through_runner still loops R3_GATE_87_CEMENTING_REGEN_SUITES with lower(source, file) where file is the per-lens tests/dag/t_r3_gate_87_cementing_regen_*.dag path and source is include_str! of that same harness — single on-disk authority, no parallel bundle.
  • Slow-test exemption: scripts/slow-test-exemptions.txt still names this test with ten compile_to_dag passes + suite run, and the dissolution line is still the concrete RUSTC_BOOTSTRAP=1 + --report-time ≤2000ms cold ubuntu-latest + same-commit row delete + TEST_TIMEOUT_MAX_EXEMPTIONS lower.
  • ROADMAP: docs/r3-program-plan.md gate RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 row still lists CONSUMER_LANDED with t_pb_b_1_dag_runner_test::r3_gate_87_cementing_regen_lens_suites_pass_through_runner and the ledger still records frozen-oracle PASSING as future work (unchanged since 40e3ac8b).

Delta since 40e3ac8b: only follow-up doc/comment churn on this branch (path wording + INVARIANTS P2 citation); semantics above unchanged.

Merge readiness (dashboard rules): mergeable is MERGEABLE; dashboard-ops reviews still counts codex REQUEST_CHANGES from review 9917 on stale 19850ea and only one distinct approval provider (cursor), with openai-pro stdout verdict unknown — so not ready to gh pr merge under the ≥2-provider / no-REQUEST_CHANGES bar until the dashboard ingests superseding codex/no-blocker signal on current HEAD or the stale RC row ages out. CI: v3 was still in_progress on run 25719122034 at last poll.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Update (merge readiness): gh pr checks is all pass on 7414cec (incl. v3 run 25719122034). dashboard-ops now shows 2/2 distinct approvals (claude review 9983 on HEAD + cursor). Still not merge-ready under the dashboard gate: codex REQUEST_CHANGES (9917, SHA 19850ea, pre–P2 fix) remains the lone blocking review row until superseded/ingested (GitHub comments with codex “No blocking concerns” at newer SHAs are not that row yet).

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Response to claude/claude-opus-4-7 (review 9983)

Verification on 7414cec0b483f86bd3b275a26c7c4f0c995d9134: APPROVE rationale matches the tree — no further code change needed.

  • #[ignore] removed: r3_gate_87_cementing_regen_lens_suites_pass_through_runner is a plain #[test] (runs in default suite).
  • Exemption: scripts/slow-test-exemptions.txt row still documents ten per-harness compile_to_dag + run_suite cost and a checkable dissolution (RUSTC_BOOTSTRAP=1 filtered cargo test + --report-time ≤2000ms cold ubuntu-latest, same commit as row delete + ratchet lower).
  • P2 / comments: Loop still uses lower(source, file) with include_str! tied to the same on-disk tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag path per row; inline note calls out INVARIANTS P2 and no bundle duplicate.

Merge readiness (dashboard bar): gh pr view shows mergeable: MERGEABLE, mergeStateStatus: CLEAN, and gh pr checks all pass on HEAD. dashboard-ops still reports not ready: codex REQUEST_CHANGES (9917, stale SHA) remains, and its checks_state was pending at poll time. Per your rule set, no gh pr merge until the dashboard clears RC (superseding codex artifact on HEAD or dropping the stale row).

— sent from sunny-stag-659

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 3a16f921 · Trigger: schedule
  • Thinking: 205s wall

✅ No blocking concerns in the current diff.

slow-test-exemptions row cited tests/dag/...; runner table and lower() use src/v3/compiler/tests/dag/... (composer-2 10048 exploratory).

Co-authored-by: Cursor <cursoragent@cursor.com>

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 7414cec0 · Trigger: schedule
  • Thinking: 316s wall

✅ No blocking concerns in this diff.

@briansrls

Copy link
Copy Markdown
Contributor Author

Response to codex relay (7414cec0, 2026-05-12T08:48:09Z) — “No blocking concerns”

Verification on current HEAD da55b594ca2feab88a2d6e9682adef5b136ad0a5: Ancestor of this branch still includes 7414cec0; gate-#87 behavior under review there is unchanged in intent: r3_gate_87_cementing_regen_lens_suites_pass_through_runner stays #[test]-active, per-lens src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_*.dag remains single authority in lower(source, file), slow-test row keeps a measured dissolution (RUSTC_BOOTSTRAP=1 + --report-time … ≤2000ms). Since 7414cec0, only non-blocking deltas landed on this PR line: merge(s) with origin/main, mechanical bootstrap snapshot upkeep from upstream/#2753 lineage, and c8f9d3f — exemption comment now uses the same src/v3/compiler/tests/dag/ prefix as the harness table (composer-2 path nit). Nothing in those follow-ups contradicts the “no blocking concerns” read of the original slice.

No additional fix commit for this relay item (already addressed where actionable).

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Response to codex/codex-default (review 10061, da55b594)

Verified: APPROVE matches the tree.

  • t_pb_b_1_dag_runner_test.rs: Gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 block at 425–428 documents src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<name>.dag; 431–434 “Single authority” inventory ratchet text matches P2 framing. 519–523: #[test] runner + per-row lower(source, file) with on-disk path as single authority / no bundle duplicate.
  • scripts/slow-test-exemptions.txt: Gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 row is at 107 in main layout (artifact’s :27 is from the review worktree line map). Comment documents ten per-harness compile_to_dag + run_suite, src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag, and the concrete dissolution (RUSTC_BOOTSTRAP=1 … --report-time … ≤2000ms + same-commit row delete + ratchet lower).
  • Harness files: 10 t_r3_gate_87_cementing_regen_*.dag under src/v3/compiler/tests/dag/ (matches table).

Artifact links under /home/briansrls/.local/share/gunbc-review/... are the review sandbox; in-repo paths above are authoritative.

Merge readiness: gh pr checks all pass on da55b594 (run 25724073306); GitHub mergeStateStatus: CLEAN. dashboard-ops still shows ready: false: only one counted approval (claude) — review 10061 is APPROVE in the relayed body but the dashboard ingests it as verdict: unknown from stdout, so the ≥2 distinct approvals gate is not satisfied in-tool yet; checks_state also still pending there (likely lag vs GitHub). No gh pr merge under your stated bar until the dashboard counts a second provider or you override out-of-band.

— sent from sunny-stag-659

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: da55b594 · Trigger: schedule
  • Thinking: 191s wall

Non-blocking — Strengths

  • src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs The re-enabled gate #87 runner keeps the per-lens .dag harnesses as the authority and does not introduce a parallel bundled copy.
  • scripts/slow-test-exemptions.txt The retained timeout exemption is bounded by a concrete <=2000ms cold ubuntu-latest measurement trigger plus same-commit ratchet lowering.

✅ No blocking concerns; this is a focused test-gate restore with tracked timeout debt.

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification (current HEAD 3d5d54cb… vs codex api-review @ da55b594)

  • t_pb_b_1_dag_runner_test.rs: Gate RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 runner still keys each row off the authoritative src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag paths (lower(source, file) per tuple); comments still call out INVARIANTS P2 (single on-disk authority, no bundled parallel copy). Matches the review’s “per-lens .dag harnesses as authority” strength.
  • scripts/slow-test-exemptions.txt: The r3_gate_87_cementing_regen_lens_suites_pass_through_runner row still ties dissolution to cold <=2000ms cargo test … --report-time and lowering TEST_TIMEOUT_MAX_EXEMPTIONS in the same commit. Matches the review’s bounded-exemption strength.

Action: No fix commit — nothing in the review requested a code change.

Merge: Withholding gh pr merge here: dashboard-ops reviews on this PR still reports ready=false (approval_count 0/2 on 3d5d54cb… per dashboard merge criteria), despite GitHub MERGEABLE + green checks. Will squash-merge only after that summary shows the approval rule satisfied on the then-current head_sha.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification (codex dashboard review → current HEAD 475c19f…)

  • t_pb_b_1_dag_runner_test.rs (gate RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 block ~L481–L528): R3_GATE_87_CEMENTING_REGEN_SUITES still pairs each include_str!(../dag/t_r3_gate_87_cementing_regen_*.dag) with the matching on-disk file path under src/v3/compiler/tests/dag/…; r3_gate_87_cementing_regen_lens_suites_pass_through_runner still documents INVARIANTS P2 (single on-disk authority, no bundled duplicate). Matches the review’s “explicit runner path + same test authority” read.
  • scripts/slow-test-exemptions.txt:107: Row for t_pb_b_1_dag_runner_test::r3_gate_87_cementing_regen_lens_suites_pass_through_runner still records the cold <=2000ms / --report-time dissolution and same-commit TEST_TIMEOUT_MAX_EXEMPTIONS lowering — consistent with the centralized timeout-ratchet pattern in TESTING.md / INVARIANTS P2 framing the review cites.

Action: No fix commit — APPROVE stands; no concrete violation spotted on re-read.

Merge readiness (post-dashboard-ops reviews): mergeable=MERGEABLE, no REQUEST_CHANGES, but checks_state=pending (v3 still running on this workflow) and approval_count 1/2 (only codex counted on this head_sha so far). Not squash-merging until CI green and ≥2 distinct approving providers on the then-current head per standing rule.

— sent from sunny-stag-659

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 3d5d54cb · Trigger: schedule
  • Thinking: 152s wall

✅ No new blocking concerns in the provided diff.

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification (codex api-review @ 3d5d54cb vs current HEAD 475c19f)

  • The GitHub api-review comment applies to 3d5d54cb. That commit is an ancestor of 475c19f; the delta 3d5d54cb..475c19f is Merge origin/main plus docs-only updates (docs/r3-program-plan.md, docs/r3-structure.md from upstream). src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs and scripts/slow-test-exemptions.txt are unchanged across that range, so the gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 / exemption surface Codex cleared on 3d5d54cb is still exactly what ships on 475c19f for those paths.
  • No new blocking concerns from a quick re-read of the doc-only delta relative to this PR’s functional intent.

Action: No fix commit — nothing in the review requests a code change.

Merge: Withholding gh pr merge: dashboard-ops reviews still has ready=false, approval_count 1/2 on 475c19f (only codex counted so far), even though checks_state=passing and MERGEABLE. Need the second distinct counted approving provider on this head_sha per standing rule.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: openai-pro / gpt-5-5-thinking
  • Commit: bdb78b66 · Trigger: manual
  • Comparison: main @ 2af9ef3a ... session/sunny-stag-659 @ bdb78b66
  • Conversation: View conversation

1. Story of the diff

This PR re-enables the R3 gate #87 cementing runner by removing the #[ignore] from r3_gate_87_cementing_regen_lens_suites_pass_through_runner, while explicitly keeping the test in the slow-test exemption list because it still does ten cold compile_to_dag + TestRunner::run_suite executions. It also tightens the authority story around the per-lens .dag harnesses: the code comment now names the full src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<name>.dag path, and the re-enabled test states that those on-disk harnesses are the single authority rather than a bundled duplicate copy. The slow-test row’s debt note is made more precise: it gives a measurable cold-CI threshold and a same-commit dissolution action for deleting the exemption.

2. Invariant categories

  1. LAYER MODEL (substrate vs implementation).

N/A — diff is test-runner wiring and slow-test metadata only; it does not touch substrate types on Dag, dag.rs, cross-pass modeled facts, or new substrate variants.

  1. INVARIANTS.md + modeling-discipline.md.

Compliant — P2 / single authority is handled directly: src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:522 says the on-disk harness is “the single authority,” and :523 rejects a duplicated bundle module. That aligns with Boundary Discipline’s “one authoritative place” rule and the testing requirement that cementing receipts resolve to tests/dag/<stem>.dag rather than a parallel inventory. chatgpt-review-11926c0d-d055-4d…

  1. CODING.md.

Compliant — the diff does not add new production code or hidden state. The changed test path continues to use explicit inputs from R3_GATE_87_CEMENTING_REGEN_SUITES and calls lower(source, file) / run_suite_all_pass_with_expected_claim_names(...) rather than adding a new object/method surface, consistent with CODING’s data + functions preference. chatgpt-review-d98712aa-07e6-40…

  1. TESTING.md.

Compliant — this PR restores execution of the cementing suite by removing the ignored status at src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:OLD520, while preserving one .dag harness per lens as required by the cementing-test guidance. The new comment at :521-:523 is exactly the right level of explicitness for “per-lens harness, no bundle duplicate,” and the exemption row at scripts/slow-test-exemptions.txt:107 tracks the runtime cost instead of hiding the test. TESTING.md specifically says cementing harnesses should live under src/v3/compiler/tests/dag/ and that unwired/missing receipts cannot satisfy the ratchet. chatgpt-review-11926c0d-d055-4d…

  1. LOCKED DESIGN DECISIONS.

Compliant — this change supports, rather than dilutes, the 0-floor / tests-as-.dag direction: the authority remains in .dag harness files, and the Rust test is a runner for those harnesses rather than a new behavioral source. That is consistent with the thesis/design direction that tests migrate toward .dag TestClaim declarations and that Rust-authored test surface trends to zero.

  1. TRACKED vs UNTRACKED DEBT.

Compliant — the slow-test exemption remains a scaffold, but it is tracked: scripts/slow-test-exemptions.txt:107 documents the cause (“ten compile_to_dag calls … + TestRunner::run_suite”), the bound/problem (>2s wall on cold CI), and the dissolution trigger/action (delete the row and lower TEST_TIMEOUT_MAX_EXEMPTIONS once the named cold cargo test ... --report-time command shows <=2000ms). That satisfies P5’s requirement for documented, bounded scaffolds with a checkable dissolution trigger. chatgpt-review-889b3199-933a-4a…

2.5. Top-down PM intent review

Compliant — the highest-level intent is to keep tests structural and avoid parallel hand-authored behavioral authorities. This PR re-enables a gate that evaluates per-lens .dag cementing harnesses and explicitly rejects the prior bundled-copy direction via src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523; that preserves the PM-level direction that tests are .dag data and that cost-of-change should stay close to one .dag authority per concept.

3. Verdict

APPROVE — I do not see a diff-cited invariant violation. The PR removes the ignore, keeps the remaining performance problem as tracked debt, and strengthens the single-authority story for the gate #87 per-lens .dag cementing harnesses.

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification — two incoming reviews vs current HEAD bdb78b66…

A) cursor/composer-2 (dashboard artifact, APPROVE, Findings: None)

Checked in-tree:

  • scripts/slow-test-exemptions.txt:107 — still names t_pb_b_1_dag_runner_test::r3_gate_87_cementing_regen_lens_suites_pass_through_runner, explains ten cold compile_to_dag + run_suite cost, and pins dissolution to <=2000ms cold --report-time plus same-commit TEST_TIMEOUT_MAX_EXEMPTIONS lowering.
  • t_pb_b_1_dag_runner_test.rs — module comment at L425–L426 uses the real src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<name>.dag prefix; r3_gate_87_cementing_regen_lens_suites_pass_through_runner (L519–L528) is a plain #[test] (no #[ignore]); L521–L523 tie the loop to INVARIANTS P2 (single on-disk authority, no bundled duplicate).

Matches the review’s narrow-scope / boundary-discipline story; no rubric fix surfaced.

B) openai-pro / gpt-5-5-thinking (GitHub api-review @ bdb78b66, APPROVE)

Same files: P2 language sits on L521–L523 (review prose referenced “:OLD520” for the retired #[ignore] — that line is gone, which is consistent with the narrative). Invariant / TESTING.md / tracked-debt framing in the review matches L107 + the runner.

Action: No fix commit — both verdicts align with the current tree.

Merge: Withholding gh pr merge: gh pr checks still has v3 pending on the latest workflow for this head, and dashboard-ops reviews reports ready=false, approval_count 1/2 (['codex'] only) on bdb78b66… even though openai-pro posted an APPROVE on GitHub for the same SHA — merge stays gated on green v3 + dashboard ready=true / second counted provider per standing rule.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Item: openai-pro / gpt-5.5-pro dashboard stdout artifact (review 10131, bdb78b66)

What the relayed body is: It is only the chatgpt-reviewer bootstrap trace (login check, context fetch, diff upload, “model: unknown — detectActiveModel…”, etc.). No code finding, REQUEST_CHANGES, or APPROVE line appears in the excerpt you surfaced.

Verification against the tree (bdb78b66…): Nothing in that log implicates the gate-#87 runner or slow-test-exemptions.txt:107; the Rust + exemption shape we already validated for this head is unchanged by this artifact.

Why this is not a worker-side fix commit: There is no actionable engineering defect in the diff derived from the log text — it is tooling output, not a rubric violation.

Dashboard note: dashboard-ops reviews still shows review 10131 with verdict: unknown / verdict_source: stdout_artifact (parser likely did not extract a terminal verdict from stdout — same class as “bootstrap-only” artifacts). The separate GitHub api-review thread with an explicit APPROVE narrative for bdb78b66 remains the substantive human-facing signal for readers.

Merge: Withholding gh pr merge: v3 still pending on this head’s workflow, and dashboard ready=false / approval_count 1/2 until ingestion counts a second provider on bdb78b66.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification — claude-opus-4-7 dashboard review (APPROVE) vs current HEAD 809ae71…

  • r3_gate_87_cementing_regen_lens_suites_pass_through_runner: #[test] only (L519–L528); #[ignore] absent — matches “removes #[ignore] / re-enables suite.”
  • P2 / single authority: L521–L523 state one compile_to_dag per src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag, on-disk file as single authority, no duplicated bundle copy — matches review.
  • scripts/slow-test-exemptions.txt:107: Names the test, documents ten compile_to_dag + run_suite cost, >2s cold CI context, and dissolution via named cargo test … --report-time <=2000ms + same-commit TEST_TIMEOUT_MAX_EXEMPTIONS — matches “concrete dissolution receipt.”
  • Path comments: Gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 header (L425–L428) uses the real src/v3/compiler/tests/dag/… prefix — matches “corrects a path comment.”

Action: No fix commit — APPROVE is consistent with the changed lines on this SHA.

Merge: Withholding gh pr merge: v3 still pending on latest workflow for 809ae71, and dashboard-ops reviews has ready=false, approval_count 1/2 (codex only) on this head_sha — need passing checks + ready=true / second counted provider per standing rule.

— sent from sunny-stag-659

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: 475c19f8 · Trigger: schedule
  • Thinking: 180s wall

Non-blocking — Strengths

  • src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs Re-enabling the gate exercises the per-lens .dag harnesses through the existing runner table without introducing a new Rust-side bundle authority.
  • scripts/slow-test-exemptions.txt The slow-test row now matches the active test shape: ten per-lens compiles, a named scope, and a concrete <=2000ms removal trigger.

ROADMAP — Verified

  • T-PB-B: The change is consistent with the tests-as-data lane because the executable claims stay in .dag harnesses and Rust only invokes the runner.

✅ No blocking concerns in the provided diff.

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification — codex api-review @ 475c19f8 vs live HEAD 809ae71…

  • 475c19f8 is an ancestor of 809ae71. git diff 475c19f8..809ae71 -- for t_pb_b_1_dag_runner_test.rs and slow-test-exemptions.txt is empty — the gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 runner + exemption surface Codex reviewed is byte-identical on the current PR tip.
  • Therefore the review’s strengths still hold on 809ae71: per-lens .dag harnesses exercised via the existing R3_GATE_87_CEMENTING_REGEN_SUITES table (no new Rust bundle authority), and slow-test-exemptions.txt:107 still documents ten compiles + <=2000ms / ratchet dissolution — consistent with T-PB-B / tests-as-data as stated.

Action: No fix commit — “No blocking concerns” remains valid for the gate-#87 slice on current HEAD.

Merge: Withholding gh pr merge: v3 still pending, and dashboard-ops reviews reports ready=false, approval_count 1/2 on 809ae71.

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: openai-pro / gpt-5-5-pro
  • Commit: 809ae71d · Trigger: manual
  • Comparison: main @ 1de959e8 ... session/sunny-stag-659 @ 809ae71d
  • Conversation: View conversation

1. Story of the diff

This PR re-enables the R3 gate #87 cementing regen suite by removing the #[ignore] from r3_gate_87_cementing_regen_lens_suites_pass_through_runner (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:520, removed). It does not introduce a bundled mega-harness; instead, the runner continues to execute one authoritative per-lens .dag harness, and the new comment makes that single-authority intent explicit at src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523. The slow-test exemption remains, but the row is tightened from a vague hot-fix note into a bounded debt receipt: it names the ten cold compile_to_dag calls, the per-lens harness path shape, the current >2s condition, and the exact cold cargo test ... --report-time threshold for deleting the exemption (scripts/slow-test-exemptions.txt:107). The small path-comment correction at src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:426 keeps reviewer/operator wording aligned with TESTING.md’s src/v3/compiler/tests/dag/ harness convention.

2. Invariant categories

  1. LAYER MODEL (substrate vs implementation).

N/A — this is test scheduling and harness documentation only. The diff touches scripts/slow-test-exemptions.txt:107 and src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:426,521-523; it does not touch dag.rs, substrate declarations, cross-pass carriers, or new variants.

  1. INVARIANTS.md + modeling-discipline.md.

Compliant — P2 Boundary Discipline is handled directly: the new runner comment says the on-disk per-lens harness is the “single authority” and that there is “no duplicated copy in a bundle module” (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523). That matches INVARIANTS.md’s rule that every fact lives in exactly one authoritative place and the parallel-authority anti-pattern it names. chatgpt-review-68ee9de7-c0f2-4d…

It also matches modeling-discipline’s single-authority metadata practice. chatgpt-review-b57ca825-f37e-47…

  1. CODING.md.

N/A — no new production Rust implementation shape is introduced. The only Rust-side behavior change is removing the test #[ignore] (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:520, removed), plus comments; there is no new method/object/helper/error shape to assess against CODING.md’s data + free-functions style. CODING.md’s relevant discipline remains satisfied by not adding a new object or hidden state surface here. chatgpt-review-5e941f4f-9daa-40…

  1. TESTING.md.

Compliant — this is the right level for the claim being re-enabled. TESTING.md says cementing receipts should live as .dag TestClaim / TestSuite harnesses under src/v3/compiler/tests/dag/, preferably focused per lens; the diff’s corrected path comment points exactly there (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:426), and the new comment reinforces one compile/run per per-lens harness (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523). chatgpt-review-2ea6a718-5298-44…

The slow-test exemption row is also honest about the current runtime cost rather than hiding it (scripts/slow-test-exemptions.txt:107).

  1. LOCKED DESIGN DECISIONS.

N/A — the diff does not alter a locked substrate, bootstrap, target-emission, or zero-floor design decision. It is consistent with the locked/top-level direction that tests move toward .dag TestClaim data rather than hand-maintained Rust behavior assertions. chatgpt-review-38afed08-59fb-41…

  1. TRACKED vs UNTRACKED DEBT.

Compliant — the retained slow-test exemption is tracked debt, not an unbounded carve-out. It documents the cause (“ten compile_to_dag calls”), the bound/current condition (>2s wall on cold CI), and the dissolution trigger: delete the row and lower TEST_TIMEOUT_MAX_EXEMPTIONS once the named cold ubuntu-latest cargo test ... --report-time command shows <=2000ms (scripts/slow-test-exemptions.txt:107). That satisfies INVARIANTS.md’s scaffold rule requiring a specific checkable dissolution trigger. chatgpt-review-68ee9de7-c0f2-4d…

2.5. Top-down PM intent review

Compliant — the highest-level intent is preserved. The thesis and zero-floor program want tests to become structural .dag TestClaim data, with Rust test surface shrinking toward zero rather than becoming a permanent parallel authority. chatgpt-review-38afed08-59fb-41…

chatgpt-review-0d5f60b5-6b12-4f…

This diff does not dilute that by adding a new hand-written behavioral oracle or a bundle module; it explicitly says each row’s on-disk .dag harness is the authority and that there is no duplicated bundle copy (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523). The only remaining concession is runtime cost, and that concession is bounded with a concrete dissolution trigger in scripts/slow-test-exemptions.txt:107.

3. Verdict

APPROVE. The PR re-enables the gate while preserving the per-lens .dag harness authority, and the remaining slow-test debt is documented, bounded, and dissolvable. I did not find a diff-cited invariant violation.

@briansrls

Copy link
Copy Markdown
Contributor Author

Verification — claude-opus-4-7 (APPROVE) vs live GitHub HEAD d4e18756…

  • r3_gate_87_cementing_regen_lens_suites_pass_through_runner: #[test] only (L519–L528), #[ignore] absent — matches “re-enables a test.”
  • P2 / harness authority: L521–L523 assert one compile_to_dag per src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag, on-disk file as single authority, no duplicated bundle module — matches review.
  • Path comment: L425–L426 use src/v3/compiler/tests/dag/… for the gate-RT1-RT4: model correctness — credential wiring, fail-closed auth, fil… #87 harness convention — matches review.
  • scripts/slow-test-exemptions.txt:107: Still documents ten cold compile_to_dag + run_suite, >2s, and dissolution via <=2000ms --report-time + TEST_TIMEOUT_MAX_EXEMPTIONS — matches “concrete dissolution trigger.”

git diff 809ae71..d4e18756 -- for t_pb_b_1_dag_runner_test.rs and slow-test-exemptions.txt is empty, so the Claude-reviewed surface is unchanged across the dashboard’s last-indexed head (809ae71) and current PR tip.

Action: No fix commit — APPROVE stands.

Merge: Withholding gh pr merge: GitHub gh pr checks still shows v3 (and ci) pending on d4e18756. dashboard-ops reviews still reports head_sha 809ae71… with ready=true / checks_state=passing — SHA lag vs live headRefOid. Will gh pr merge only after all checks green on the then-current PR head and dashboard head_sha matches that tip with ready=true / 2/2 / no REQUEST_CHANGES (re-poll after CI settles).

— sent from sunny-stag-659

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: openai-pro / gpt-5-5-pro
  • Commit: d4e18756 · Trigger: manual
  • Comparison: main @ 3dbf5bd9 ... session/sunny-stag-659 @ d4e18756
  • Conversation: View conversation

1. Story of the diff

This PR re-enables the R3 gate #87 cementing regen runner by removing the temporary #[ignore] that had hidden the suite, while preserving the intended per-lens .dag harness model instead of reintroducing a bundled Rust-side source copy. The runner now compiles each authoritative src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag harness and passes it through TestRunner::run_suite, with comments explicitly naming the on-disk .dag files as the single authority (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523). Because the gate is still expected to exceed the normal 2s budget on cold CI, the PR keeps it in scripts/slow-test-exemptions.txt but upgrades the exemption from “hot-fix / owner TBD” into a bounded dissolution recipe tied to a concrete cold cargo test timing command and a same-commit exemption-count reduction (scripts/slow-test-exemptions.txt:107).

2. Invariant categories

  1. LAYER MODEL — N/A. The diff is test harness scheduling/comment/exemption work only; it does not touch Dag substrate types, dag.rs, cross-pass data models, substrate variants, or Dag mutation APIs.
  2. INVARIANTS.md + modeling-discipline.md — Compliant. P2 single-authority is handled directly: the added comment says each on-disk harness is “the single authority for that row” and that there is “no duplicated copy in a bundle module” (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:522-523). P5 progress/dissolution is also handled: the slow exemption documents the cause, the bound, and the deletion trigger rather than leaving the old “owner TBD” hot-fix shape in place (scripts/slow-test-exemptions.txt:107).
  3. CODING.md — Compliant. No new implementation helper, hidden state, method surface, or object-style behavior is introduced; the code-path shape remains the existing data-driven loop over R3_GATE_87_CEMENTING_REGEN_SUITES, with the new lines only clarifying the authority of the input harness files (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523).
  4. TESTING.md — Compliant. The PR removes the temporary ignored-test scaffold (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:520, deleted) and restores the intended gate execution through per-lens .dag harnesses (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:426, src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521). The remaining slowness is not hidden by an ignored test; it is tracked as an explicit slow-test exemption with a measurable removal condition (scripts/slow-test-exemptions.txt:107).
  5. LOCKED DESIGN DECISIONS — N/A. The diff does not amend a locked design document or alter a locked substrate/design decision. Its shape is consistent with the locked tests-as-data / zero-residual direction because the test authority remains in .dag harness files, but no locked authority is changed in this PR.
  6. TRACKED vs UNTRACKED DEBT — Compliant. The only remaining debt is the slow-test exemption, and it has all three required properties: documentation of why it exists (“ten compile_to_dag calls … + TestRunner::run_suite each”), a bound (<=2000ms cold ubuntu-latest), and a named dissolution trigger (“delete this row and lower TEST_TIMEOUT_MAX_EXEMPTIONS in the same commit”) (scripts/slow-test-exemptions.txt:107). The old unbounded hot-fix marker with “owner: TBD” is removed (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:520, deleted).

2.5. Top-down PM intent review

Compliant. The high-level intent is to make cementing tests structural/data-authored and avoid permanent Rust-side parallel authorities; this diff preserves that by explicitly pointing the runner at per-lens .dag harnesses and rejecting a duplicated bundle module (src/v3/compiler/tests/integration/t_pb_b_1_dag_runner_test.rs:521-523). Removing the ignore advances the gate from postponed to executed, while the cold-CI cost is kept as tracked, bounded operational debt rather than a semantic dilution of the R3 gate (scripts/slow-test-exemptions.txt:107).

3. Verdict

APPROVE. I did not find a diff-cited invariant violation. The PR re-enables the intended gate, keeps harness authority in per-lens .dag files, and turns the remaining performance exception into bounded debt with a concrete dissolution trigger.

@briansrls

Copy link
Copy Markdown
Contributor Author

A) openai-pro dashboard stdout (review 10146, d4e18756) — relayed excerpt

The pasted body is only the chatgpt-reviewer bootstrap trace (login, fetch context, uploads, model: unknown from detectActiveModel, …). It contains no diff-cited code finding, REQUEST_CHANGES, or terminal APPROVE line in the excerpt.

Dashboard: review 10146 is recorded with verdict: unknown (stdout artifact parser) — same class as prior truncated streams; not a worker-side code defect.


B) openai-pro GitHub api-review @ d4e18756 — APPROVE

Verified on d4e18756…:

  • #[test] / no #[ignore] on r3_gate_87_cementing_regen_lens_suites_pass_through_runner (L519–L528).
  • P2 language on L521–L523 (single on-disk src/v3/compiler/tests/dag/t_r3_gate_87_cementing_regen_<lens>.dag authority; no bundle duplicate).
  • scripts/slow-test-exemptions.txt:107: ten compile_to_dag + run_suite, >2s cold CI, dissolution via named cargo test … --report-time <=2000ms + same-commit TEST_TIMEOUT_MAX_EXEMPTIONS — bounded tracked debt.

The review’s narrative about “#[ignore] removed / exemption upgraded from vague hot-fix” matches the intent of the branch; line references like “:520, deleted” should be read as the retired #[ignore] attribute (current L519–L520 are #[test] + fn, not a missing line).

Action: No fix commit — APPROVE stands.


Merge readiness (dashboard-ops reviews + gh pr checks)

  • head_sha: d4e18756… (matches GitHub headRefOid).
  • Approvals: 2/2 distinct providers (claude, codex), no REQUEST_CHANGES, mergeable=MERGEABLE.
  • merge_criteria.ready: false because checks_state=pending — v3 is still pending on the active workflow while fmt/ci/changes are green.

Squash-merge: Not run yet — will gh pr merge 2742 --squash --delete-branch immediately after v3 passes and a fresh dashboard-ops reviews poll shows ready=true / checks_state=passing on this head_sha.

— sent from sunny-stag-659

@briansrls
briansrls merged commit f2a2b15 into main May 12, 2026
5 checks passed
@briansrls
briansrls deleted the session/sunny-stag-659 branch May 12, 2026 12:42
@briansrls briansrls mentioned this pull request May 12, 2026
6 tasks done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant