Repository navigation
chore: package session changes for Lane 2 initiation (L2-0) - #74
Merged
Merged
Conversation
- Package resolve_config boundary mocks (4 graph_mock.rs) - Add HandlerKind variants (daglang-emit) - Fix TypeExpr::Record (daglang-syntax, daglang-typecheck) - Update credential_lifecycle.rs and workflow catalog - Update resolve.rs - Pass clippy checks and prepare for Lane 2 compilation path
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 83f06c1f04
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | ("tools.clippy", "clippy") | ||
| | ("tools.codegen", "codegen") | ||
| | ("tools.dag_viz", "dag_viz") | ||
| | ("tools.deps", "deps") |
There was a problem hiding this comment.
The resolver now fails closed for unknown callables, but this allowlist only permits ("tools.deps", "deps"). The deps DSL module still defines callable entrypoints like deps_install/deps_generate (and lowering still emits nodes such as tools.deps::deps_install), so resolving those graphs now returns unknown callable and breaks DSL-backed deps workflows that call resolve_lowered_dag.
Useful? React with 👍 / 👎.
| | ("tools.dag_viz", "dag_viz") | ||
| | ("tools.deps", "deps") | ||
| | ("tools.docgen", "docgen") | ||
| | ("tools.gist", "gist") |
There was a problem hiding this comment.
With fail-closed resolution enabled, allowing only ("tools.gist", "gist") is too narrow for the current DSL module, which exposes mode-specific callables (gist_snapshot, gist_diff, gist_recent). When those lowered callables are resolved, they now hit the unknown-callable path, so DSL-backed gist subdag construction can fail at runtime.
Useful? React with 👍 / 👎.
Comment on lines
+247
to
+250
| fn is_stage_label(label: &str) -> bool { | ||
| matches!( | ||
| label, | ||
| "idea" | "design" | "design-review" | "accepted" | "implementation" | "closed" | ||
| "idea" | "design" | "design-review" | "accepted" | "implementing" | "code-review" | "testing" | "done" | "terminal-failed" |
There was a problem hiding this comment.
This stage-label matcher no longer recognizes the previously used implementation/closed labels, so existing issues carrying those labels are parsed as having no stage (defaulting to Idea). In that state, compare-and-set transitions can fail unexpectedly and set_stage_label will not strip old stage labels, which breaks reconciliation for repos with pre-migration issues.
Useful? React with 👍 / 👎.
Also scope RESOURCE_FILE import to fs_env tests to avoid non-test warning.
briansrls
added a commit
that referenced
this pull request
May 6, 2026
…tion + V6 ACTIVE Per Verification Mgr partition response at gunbc#846 #issuecomment-4385074816. Second Mgr to engage substantively with design schedule. §2 header updated with 3-track worker partition table: - Track A (executable/ledger): bold-crane-790 — V1 (TC1 hold pending Q-PAFS + EVAL-3) + V6 (active) - Track B (corpus/demos/data): cool-heron-521 — V2 + V4 + V5 (post-R2- Evaluator-gated; prep now via design + skeleton) - Track C (Mgr-reserved/cross-lane): cool-owl-579 (Mgr) — V3 (post- cascade) + V7 (hold pending Director Q-ValueBody-Isomorphism scope) V6 marked ACTIVE — only Verification item proceeding without Director hold. Worker pin: bold-crane-790. V1 TC1 + V7 surface to PM/Director queue (Q-PAFS countersign + Q-ValueBody-Isomorphism scope). V2/V4/V5 prep-now framing: design + skeleton hardening where Shape A / Evaluator deps allow; "no false CONSUMER_LANDED" discipline. Per-claim gate mapping to §1.8 ledger rows #43-#52 (V5) / #84-#87 (V4) / #74 (V4 demonstration). Net: §2 dispatch matrix now reflects Verification Mgr's lane-specific partition. Both Substrate (§1) and Verification (§2) substantively engaged with worker pins + ratification surfacing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 6, 2026
…1810) * docs(r3): comprehensive R3 design schedule — per-Mgr dispatch matrix per Brian directive Per Brian directive 2026-05-06 (chat): "can we schedule all the design now?" Authors `docs/r3-design-schedule-2026-05-06.md` — central PM-tier dispatch matrix covering all 6 R3 Mgrs + cross-program / Director-tier decisions. Per-Mgr design queue: §1 Substrate Mgr (12 design items): Q-Class-2 gap-test (S1) + LBP scope- calibration canvas (S2) + MachineConstraint<C> carrier (S3) + Workflow* family (S4) + variant-aware projection (S5) + EmissionPathProjection (S6) + PR-F (S7) + ApproximateField<F> Float migration (S8) + T-Numeric- Construction brief (S9) + T-E-P-Producer-Broadening dispatch (S10) + Slice C #1795 follow-up (S11) + F2/F8 doc-sharpening (S12) + 5 demonstration gates. §2 Verification Mgr (7 design items): Pattern-A executable cluster (V1) + L4/L7 exhaustive coverage (V2) + T-Lens-Self-Application stronger demo (V3) + T-Tests-As-Data lane work (V4) + T-Free-Consequences 10 gates (V5) + bridge_retirement_ledger_zero audit gate (V6) + ValueBody isomorphism (V7). §3 PB Mgr (5 design items): T-LensProducer-Retirement (P1) + T-FixedPoint completion (P2) + T-V2-Retirement post-FP+LP (P3) + 3 PB-owned bridges (P4) + F2/F8 cross-lane (P5) + 4 demonstration gates. §4 Evaluator Mgr (5 design items): E6-G0d constructor execution (E1) + E5 Descent termination contract (E2) + E6-G1.a static lens fold (E3) + E6-G1.b generic dispatch (E4) + X1.b S1 coordination (E5). §5 Grounding Mgr (5 design items): L6 row population (G1) + T-Ground-Rust full coverage (G2) + Coercion-Fold scratch retirement (G3) + F10 cleanup (G4) + Anthropic #1702 re-dispatch (G5). §6 Debt-Paydown Mgr (5 design items): Q-Drift-Reconcile (DP1) + SG-0 CI gate (DP2) + velocity tripwire (DP3) + closure-receipt cadence (DP4) + #1566 rollup hygiene (DP5). §7 Cross-program / Director-tier (5 decisions): Q-LBP-R3-Closeability (CP1) + Q-Tier4-Inclusion (CP2) + Q-WEDGE-A framing (CP3) + Q-Class-6 (CP4) + PR #1794 merge (CP5). §8 Sequencing summary: critical path (T-E-P-Producer-Broadening → T-LBP → T-LAS||T-WAD → T-LSA) + parallel longest single-lane (T-V2-Retirement) + Verification-internal path + bottleneck escalations. §9 Status update cadence: daily Mgr-internal + weekly Mon/Wed/Fri PM compilation. Cross-Mgr coord via Director queue. §10 References: r3-structure.md / r3-program-plan.md (incl. §1.8 ledger) / audit/r3-debt-sweep-2026-05-06.md / 6 Mgr inboxes + Director + Research PM. Total design items: ~44 across 6 Mgrs + 5 Director-tier decisions. Net: per-lane Mgr design work scheduled in parallel with Brian/Director scope-calibration decisions. Mgrs do NOT wait for all decisions to resolve — design dispatches in flight as escalations resolve. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb Substrate Mgr §1 partition response — worker pins + S3∥S8 + demo as Acceptance bullets Per Substrate Mgr partition response at gunbc#846 #issuecomment-4385074769. Substrate Mgr provided clean trigger-state partition for §1 12 items + worker pins + structural corrections. Updates absorbed: S7 PR-F: worker pin narrowed to loyal-wolf-828 (per Q-PR-F bandwidth-aware routing + Substrate Mgr explicit partition); valiant-ant-72 reserved for S3 MachineConstraint<C> implementation post-design (cleaner separation of authoring vs implementation phases). S8 ApproximateField<F> Float migration: dispatch trigger updated from "post-S3 (sequential) OR parallel" → "**parallel with S3**" per Substrate Mgr correction. MachineConstraint<C> and ApproximateField<F> are INDEPENDENT axes (machine width vs algebra approximation); both Mgr-tier design now with cross-reference at brief-landing. S10 T-E-P-Producer-Broadening: worker pin = quick-koi-190 (currently on #1799 termination-contract; T-E-P consumes descent-evidence, natural follow-on). S11 Slice C: dispatch trigger refined to "post-#1795 (Slice A) + #1801 (Slice B) merge" cascade-clearance; worker pin = smart-ram-167 (Slice B precedent owner; pattern-familiar). 5 demonstration gates (#67/#68/#70/#72/#73): per Substrate Mgr structural correction — fold demonstration scope into parent worker brief Acceptance bullets, NOT separate dispatches. Each gate becomes Acceptance bullet on parent lane's brief. Worker assignment now explicit: - S5 (variant-aware projection): quiet-boar-160 (in flight) - S7 (PR-F): loyal-wolf-828 (post-#1782 merge) - S10 (T-E-P): quick-koi-190 (post-#1782 merge; post-#1799 close) - S11 (Slice C): smart-ram-167 (post-#1795 + #1801 merge) - S3 implementation: valiant-ant-72 (post-S3 design) Mgr-tier authoring queue (Substrate Mgr): S1 + S2 + S3 + S9 + brief packets for S6/S10/S11/S7. Surfaces ratification needs to PM/Director queue as canvases land. Net: §1 dispatch matrix now reflects Substrate Mgr's lane-knowledge corrections. Substrate is the first Mgr to engage substantively with the design schedule + provide partition response — exactly the pattern the schedule was meant to enable (Mgrs partition + dispatch without PM micro-management). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb Verification Mgr §2 partition — 3-track worker partition + V6 ACTIVE Per Verification Mgr partition response at gunbc#846 #issuecomment-4385074816. Second Mgr to engage substantively with design schedule. §2 header updated with 3-track worker partition table: - Track A (executable/ledger): bold-crane-790 — V1 (TC1 hold pending Q-PAFS + EVAL-3) + V6 (active) - Track B (corpus/demos/data): cool-heron-521 — V2 + V4 + V5 (post-R2- Evaluator-gated; prep now via design + skeleton) - Track C (Mgr-reserved/cross-lane): cool-owl-579 (Mgr) — V3 (post- cascade) + V7 (hold pending Director Q-ValueBody-Isomorphism scope) V6 marked ACTIVE — only Verification item proceeding without Director hold. Worker pin: bold-crane-790. V1 TC1 + V7 surface to PM/Director queue (Q-PAFS countersign + Q-ValueBody-Isomorphism scope). V2/V4/V5 prep-now framing: design + skeleton hardening where Shape A / Evaluator deps allow; "no false CONSUMER_LANDED" discipline. Per-claim gate mapping to §1.8 ledger rows #43-#52 (V5) / #84-#87 (V4) / #74 (V4 demonstration). Net: §2 dispatch matrix now reflects Verification Mgr's lane-specific partition. Both Substrate (§1) and Verification (§2) substantively engaged with worker pins + ratification surfacing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb Debt-Paydown Mgr §6 partition — DP2 IN-FLIGHT at PR #1807 Per Debt-Paydown Mgr partition response at gunbc#846 #issuecomment-4385074935. Third Mgr to engage substantively. §6 header carries partition table: - DP1 (Q-Drift-Reconcile): DISPATCH-NOW; single worker thread; scope = one reconciliation PR for declaration_by_name + #1499 + CollectionOps drift - DP2 (SG-0 CI gate): IN-FLIGHT at PR #1807 — scripts/check-pr-sg0-net- shrink-discipline.sh + workflow + template + ROADMAP. Closes §1.8 gate #75 pr_anticipation_discipline_ci_active. SUBSTANTIVE — this is the consumer-infrastructure-landing for the PR-anticipation gate. - DP3 (velocity tripwire): CONTINUOUS — recurring report; no single landed event - DP4 (closure-receipt cadence): CONTINUOUS — feeds r3_debt_paydown_zero_ remaining Pass surface - DP5 (#1566 rollup hygiene): HOLD pending DRAFT close No §6 items currently Director-blocked; clean dispatch. PR #1807 actively executing closes §1.8 gate #75 → CONSUMER_LANDED status update flows through §1.8 ledger when PR #1807 merges. Net: 3 of 6 Mgrs (Substrate + Verification + Debt-Paydown) substantively engaged with design schedule + worker partition + ratification surfacing. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb PB Mgr §3 partition + ratify §2.2 sequencing as HARD DAG Per PB Mgr partition response at gunbc#846 #issuecomment-4385075315. Fourth Mgr to engage substantively + surface real PM ratification ask. §3 header carries PB Mgr's worker partition table: - P1 T-LensProducer-Retirement: sleek-eagle-514 (#1768) — lens_apply retirement design/audit receipts via PR #1805 path-1 + sub-briefs - P1 parallel doc spine: zesty-ram-316 (#1769) — regen_lens audit via PR #1806 + Sub2/Sub3 brief threads - P4 bridge appendix: warm-ant-877 (#1770) — grep/ledger hygiene against bridge_ledger.dag / r3_bridge_retirement_ledger_zero.dag / verification.dag - P5 F2+F8: PB Mgr coordinates consumer-side with Substrate S12 owner (no duplicate PR unless PM ratifies co-author shape) - P2 T-FixedPoint: HOLD until P1 + SG-0 zero per F1 sequencing - P3 T-V2-Retirement: HOLD on broad ~79 .rs sweep until P2 + LP + Int<N> triggers clear §2.2 sequencing authority RATIFIED as HARD DAG (PM disposition 2026-05-06): Per PB Mgr's surface — "staffing parallelism vs hard DAG" question explicitly resolved. r3-structure.md §"Lane structure" → T-FixedPoint row names "R2-close dependency: SG-0 zero from T-LensProducer-Retirement" as explicit dependency. SG-0 zero is structural precondition for T-FixedPoint (bit-identical compile requires no remaining hand-Rust ratchet); not just resource sequencing. T-FixedPoint cannot complete until T-LP-Retirement completes. Plan §2.2 sequence is canonical authority on this; PB Mgr's HOLD on P2 is correct discipline. Net: 4 of 6 Mgrs (Substrate + Verification + Debt-Paydown + PB) engaged substantively with worker pins + ratification surfacing. PB Mgr's HARD-DAG ratification ask resolved inline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb Grounding Mgr §5 partition — G4 DISPATCHED + G1/G2/G3/G5 HELD on Substrate cascade Per Grounding Mgr partition response at gunbc#846 #issuecomment-4385080863. Fifth Mgr to engage substantively. §5 header carries Grounding Mgr's worker partition table. Clean dispatch shape — Grounding lane is largely consumer of Substrate work, so most items HELD until Substrate carriers land. Partition: - G1 L6 row population: HELD pending Substrate S6 EmissionPathProjection - G2 T-Ground-Rust full coverage: HELD pending Substrate S7 PR-F + S8 Float migration; #1783 remains draft as dispatch-guide staging artifact - G3 Coercion-Fold scratch retirement: HELD pending LanguageSpec projection - G4 F10 install_hint cleanup: DISPATCHED 2026-05-06 to silent-badger-711 (#1774) - G5 Anthropic #1702 re-dispatch: HELD pending Substrate S5 variant-aware projection + Q-Anthropic-Variant-Aware closure-scope No PM/Director ratification needed; G4 dispatched cleanly. Other items proceed when Substrate triggers land. Net: 5 of 6 Mgrs (Substrate + Verification + Debt-Paydown + PB + Grounding) substantively engaged. Pending: Evaluator only. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): absorb Evaluator Mgr §4 partition — E1 DISPATCHED + E5 DONE; ALL 6 of 6 Mgrs engaged Per Evaluator Mgr partition response at gunbc#846 #issuecomment-4385081532. **Sixth and final Mgr to engage substantively** — all 6 of 6 R3 Mgrs now have lane-specific worker partitions in design schedule. §4 header carries Evaluator Mgr's worker partition table: - E1 E6-G0d constructor execution: DISPATCHED 2026-05-06 to valiant-carp-10 (#1767); evaluator-only src/v3/compiler/src/lib.rs; brief = #1784 - E2 E5 Descent termination contract consumer: HELD pending Substrate carrier landing (quick-koi/quick-crab path) - E3 E6-G1.a static lens fold: HELD pending Director Q-PAFS / Q-EVAL-Lens-Fold-First-Slice countersignature - E4 E6-G1.b generic dispatch: HELD post-G1.a + post-Substrate X1.b - E5 X1.b S1 TransformDispatch coordination: DONE cross-lane status sent to Substrate (#1739) Additional state notes: - #1784 G0d brief green on fmt/ci/v3; self_host_ratchet in progress post-main merge — doesn't block E1 dispatch (brief stable + approved) - #1799 E5 STOP packet green on fmt/ci/v3; held semantically behind Substrate termination contract - warm-dove #1778 passing/held; existing PR needs Director/PM disposition No PM/Director ratification needed for E1/E5. E3 still needs Director countersignature. Net: 6 of 6 Mgrs (Substrate / Verification / Debt-Paydown / PB / Grounding / Evaluator) substantively engaged with design schedule. Concrete dispatches in flight: G4 (silent-badger-711) + DP1 + DP2 (PR #1807) + E1 (valiant- carp-10) + S5 (quiet-boar-160 in flight) + Substrate Mgr-tier authoring queue (S1/S2/S3/S9). Cross-lane coord working: E5 → Substrate; G* → S* trigger-cascade. Engagement scoreboard: 100% of R3 Mgrs partitioned + dispatching per schedule. PM micro-management overhead = zero per Mgr-tier dispatch discipline. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): codex BLOCKING fixes — §S4 audit-first against extdeps.github.actions + §V1 Pattern-A 5th gate routed to T-CostLens Fix 2 of 4 codex BLOCKING findings on PR #1810: 1. §S4 Workflow* family carriers (Class 4) — prepend existing-ontology audit prerequisite citing dsl/extdeps/github/actions.dag (218 lines, already declares Workflow / WorkflowTrigger / Job / Step / MatrixStrategy / RunnerSpec / WorkflowPermissions / ConcurrencySpec / DispatchInput). Reframe proposed carriers as audit targets / deltas, not fresh ontology; require Substrate Mgr audit-and-delta receipt before worker dispatch. Per feedback_audit_adjacent_authority_first + feedback_parallel_representation_debt. 2. §V1 Pattern-A executable cluster — fix count mismatch. Headline now says "4 NEW (DimensionReport-typed cluster) in V1"; explicit note that the 5th NEW Pattern-A gate (§1.8 #40 symbolic_cost_expr_equals_executable, SymbolicCost-typed) belongs to T-CostLens-Composition lane, not V1's TC cluster (per r3-program-plan.md:755 — different predicate family, distinct runner work). Closure-predicate citation updated accordingly. Findings 1 (external PM ledger) + 2 (Mgr-canvas → lane authority) rebutted on PR with grep evidence — both invalid. 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 of 3 tasks
briansrls
added a commit
that referenced
this pull request
May 6, 2026
…arkers) Per gunbc PM review on PR #1879 (deep-wolf-155, 2026-05-06T20:46:43Z): within each layer-block the CENTER mixed three origin classes — direct mirror of .dag, user-authored .dag logic, and fold-rule auto-emit — all sharing one tint. Applying the recommended Path A: light-touch inline markers that flag the auto-emit lines, plus a load-bearing qualifier on the TESTS panel. Changes: - TESTS panel header: "// tests — R3 DELIVERABLE (T-Tests-As-Data lane; not emitted today)". Legend tests row updated to match. The panel previously claimed behavior that doesn't exist yet — verified by the PM that gunbc emits 0 #[cfg(test)] markers today and that R3 closure gates #74/#84/#85/#86/#87 will deliver this. - Inline "// auto — fold rule" annotations (italic gray, via tspan) on the three impl blocks that the structural fold emits without authored source: impl<A,B> Sum<A,B> (constructors + predicates), impl HttpError (new), impl LoginRequest (new). - Subtitle updated so the auto-marker convention is explained at the top of the diagram. Not applied (intentional, lighter touch): - #[derive(...)] left as plain code — deriving is universally understood as mechanical, the layer comment + auto-marker on the impl block is enough signal. - unimplemented!() left as plain code — body filler is obviously placeholder; over-marking would clutter. - Within-helpers fact-vs-logic split (Result alias vs map/and_then) not visually separated — the helpers layer comment will gain a small clarifier in a follow-up if it reads ambiguous.
briansrls
added a commit
that referenced
this pull request
May 7, 2026
…brief (closes #1966) (#2149) * docs(briefs): cite gate IDs #84-#87 + #74 on T-Tests-As-Data unified brief Maps the four DECLARED 2026-05-06 gate ledger rows + #74 demonstration sibling to the existing unified brief authored at #1893. Routes #1966 (which asked for a unified worker brief consolidating these gates) to existing authority per brief-authoring-checklist.md Q2 + INVARIANTS P2 (single authority) — not a second parallel brief. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(briefs): align ledger section cite to §1.8 actual heading Cursor review on PR #2149 (composer-2) flagged that "§Gate ledger" doesn't match the actual heading in r3-program-plan.md. Updated to "§1.8 Canonical R3 Closure-Authority Ledger" to match line 178 verbatim. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 7, 2026
briansrls
added a commit
that referenced
this pull request
May 11, 2026
…te-landing tests) (#2665) * docs(audit): SG-0 trajectory snapshot 2026-05-11 (+4 vs prior EOD) PM standing daily-cadence duty per docs/audit/r3-sg0-trajectory-tracker.md §5. Today (31acf43): non_test=53 test=112 fragments=2 total=167. Delta vs 2026-05-10 EOD baseline (163): +4 test entries. The 4 new entries are gate-landing tests, identified via per-entry diff: - lens_behavioral_parity_demonstration_test.rs (gate #73, snappy-raven-508 PR #2525) - r3_gate_87_lens_cementing_regen_receipts_test.rs (gate #87 PR #2639) - r3_lens_producer_retirement_executable_witness_test.rs (PR #2595) - t_ci_workflow_as_data_demo_test.rs (T-Workflow-As-Data demo) Many gates landed during the 2026-05-10 → 2026-05-11 cycle (T-Tests-As-Data #84/#85/#86/#87; T-Bridge-Retirement #31; T-LensProducer #5+#6; T-V-L4 #11/#13; T-V-L7 #10/#15; #74 + #27 + #26 and many others). Cluster M Phase 3 bulk-port has NOT yet kicked in to shrink the census — calm-newt-602 (gate #84) + silent-swift-300 (cementing+behavioral-parity census slice) are active workers; their migration work is what flips trajectory from accumulating to shrinking. 11-day cumulative is +47 entries; per-day avg +4.3. Velocity tripwire status remains pending/uncomputed until Phase 3 migration begins producing dissolution events. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(audit): address codex BLOCKING on PR #2665 — PR-merge vs §1.8 gate-PASSING Same root cause as PR #2583 codex BLOCKING #5/#6 (memorized as feedback_pm_compile_audits_pre_existing_errors): PR-merge events ≠ §1.8 gate-PASSING promotion. Cell text said "T-Tests-As-Data gates #84/#85/#86/#87 landed". Verified against §1.8 ledger at HEAD: - #84 `every_rust_test_ports_to_dag_or_generated`: DECLARED — cannot promote until EXPECTED_HAND_AUTHORED_TEST = 0 (Phase 3 bulk-port close criterion) - #85 `forall_exists_quantifier_substrate_landed`: DECLARED — carriers landed via PR #2647 but CONSUMER_LANDED not yet claimed; §P2 requires generated consumer of declared surface - #86 `program_generator_carrier_landed`: CONSUMER_LANDED + PASSING ✓ - #87 `lens_cementing_test_discipline_complete`: CONSUMER_LANDED (PR #2639), NOT PASSING — 8 regen harnesses still Compiles-only placeholders per §1.8 close-criterion Only #86 is fully PASSING. Cell reframed to distinguish PR-merge evidence from canonical §1.8 status per memorized discipline; row notes the status drift sweep step that promotes evidence to PASSING. Same reframe applied to T-Bridge-Retirement #31, T-LensProducer #5/#6, T-V-L7 #10 — PR-merges with §1.8 status drift sweep pending. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 11, 2026
briansrls
added a commit
that referenced
this pull request
May 12, 2026
Codex BLOCKING: census path consolidation can be misread as T-PB-B / facet-3 closure. Document merge-visible P5(b) receipt as −3 deleted shims + .dag-native R1C-D/E predicates; runner Rust stays gate-#74 class; gate #84 dissolution remains ROADMAP T-PB-B until EXPECTED_HAND_AUTHORED_TEST is empty. Co-authored-by: Cursor <cursoragent@cursor.com>
5 of 6 tasks
briansrls
added a commit
that referenced
this pull request
May 12, 2026
…cope doc (#2710) * WIP: R3 Verification Cluster M: gate #87 cementing discipline + gate #74 test * docs(v3-compiler): cross-link gate #74 demo vs #87 regen harness table Clarifies in t_pb_b_1_dag_runner_test that tests-as-data demonstration (#74) already ships via r3_tests_as_data_demonstration_suite_passes_through_runner; this branch only tightens gate #87 regen .dag harness predicates. Co-authored-by: Cursor <cursoragent@cursor.com> * fix(v3-compiler): restore honest Compiles gate-87 regen harness placeholders Reverts PortHasState("lit", Resolved) on trivial programs: it did not exercise the named regen lens rows and violated TESTING.md name/behavior alignment (codex review). Restores Compiles wiring-only claims and documents the discipline inline; Rust receipts remain the lens-behavior authority until LensOutputEquals / structured carriers land. Co-authored-by: Cursor <cursoragent@cursor.com> * chore(ci): retrigger PR checks after stuck workflow The prior run had fmt cancelled during Rust setup while ci/v3 remained queued; no code change — refresh Actions for merge. Co-authored-by: Cursor <cursoragent@cursor.com> * chore(ci): retrigger workflow after run stuck in queued state Run 25705375618 never left `queued` (self-hosted runners). No code change. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
May 12, 2026
* WIP: R3 Cluster M #84 R1C-D/E tests-as-data pilot * refactor(v3-compiler): reuse lower() for R1C-E substituted templates Addresses api-review follow-up on #2715: generalize lower(source) to &str so r1c_e_emit_gates_* tests share the same compile_to_dag error handling as the rest of the dag-runner harness. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(briefs): align r1-closure-manager R1C-D tables with t_r1c_d_pb_census_gates.dag Editorial follow-up to cursor/composer-2 review on #2715: tables had stale r1_pb_census_gates.dag naming while cross-refs already pointed at tests/dag. Canonical path + retired alias called out for archive grep. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(brief): anchor R190C-D census DAG relocation to PR #2715 Replace stale 'through 2026-04' calendar phrasing with an explicit PR anchor so follow-up tracking is actionable (review feedback). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(test): explicit SG-0 accounting for #2715 R1C pilot vs gate #84 Codex BLOCKING: census path consolidation can be misread as T-PB-B / facet-3 closure. Document merge-visible P5(b) receipt as −3 deleted shims + .dag-native R1C-D/E predicates; runner Rust stays gate-#74 class; gate #84 dissolution remains ROADMAP T-PB-B until EXPECTED_HAND_AUTHORED_TEST is empty. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(test): call-site rustdoc for R1C-D/E runner-only vs .dag authority BLOCKING inline review: predicates/TestClaims live in t_r1c_d_pb_census_gates.dag and emit templates; #[test] bodies are compile+TestRunner wiring. Points to existing sg0 census P5(b) / not-#84 receipt. Co-authored-by: Cursor <cursoragent@cursor.com> * ci: fix self_host_ratchet error echo (no shell backticks in run script) Bash treated `changes` inside double-quoted echo as command substitution (`changes: command not found`), aborting the step before printing the diagnostic and poisoning gate-evidence validation. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: R3 Cluster M #84 R1C-D/E tests-as-data pilot * docs(brief): point R1C-D worker brief at canonical t_r1c_d_pb_census_gates.dag composer-2 exploratory: r1_pb_census_gates.dag sibling wording was stale after Co-authored-by: Cursor <cursoragent@cursor.com> #2715 relocation under tests/dag/. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced May 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Packages current session changes as required by L2-0.