docs(T-15): refresh Close-status post #3786/#3788/#3789/#3791

[briansrls]

Summary

• Refresh T-15 Close-status on main@32d94517c after operator merge batch (docs(T-15): dated close-status in TASKS.md (no parallel ledger) #3786, T-20-fill: implement bootstrap_footprint in src/v4/workflow/bootstrap.dag line 190 — currently returns Violates{diagnostic: bootstrap_footprint_not_realized} pending feature:t21-bootstrap-footprint-fold. T-21 is merged (#3747) so this gate is now open. Replace the Violates stub with real footprint c #3788, docs(T-19): mark lens/testgen.dag DONE in TASKS.md #3789, T-37 fix: resolve dag_node_key span-based deduplication OOM in src/v2/compile.dag. Probe result: exit 124 (timeout) on 261-module src/v4 — v0.2.0 DagCollectAcc memoized fold is not sufficient. Root cause: src/v2/compile.dag uses span-based string keys for node deduplication; large mutual-import grap #3791).
• Predicates 1–2 CLOSABLE; bridge scripts/v4-bootstrap-resolve-posture-gate.sh dissolved (T-37 / royal-carp-716).
• Reconcile bootstrap execution gap + convergence §T-37 + T-37 task header to DONE.

Test plan

• Doc-only; verify Close-status paragraph matches PM dispatch (still open: P1-KEYSTONE: create DECISIONS.md with D2 REVERSAL + FACT-BUNDLE RESEED section. This is a T-4 hard prerequisite. The INVARIANTS.md P1:42 amend, MODELING.md M1 promotion, and docs/modeling-discipline.md Practice 8 + docs/modeling/grounding-worked-examples.md are already landed — the ONLY missing piec #3752, docs(T-33): mark model_core [DONE] in TASKS.md #3787; Lane A: T-38).

Made with Cursor

[briansrls]

Verified cursor/composer-2.5 APPROVE against branch session/vivid-fox-581-close-status-post-merge @ a36a53cab:

• Docs-only: single file src/v4/TASKS.md; no substrate / hand-Rust / test changes.
• T-37 marked [DONE — #3791]; convergence counts two remaining gaps (T-38 claim-suite CI wiring; T-20 bootstrap-content-hash-pins scaffold) — matches §Bootstrap execution convergence.
• Close-status: predicates 1–2 CLOSABLE, 4 PARTIAL (not lumped with 5), bridge dissolved, pin main@32d94517c matches origin/main today.
• CI green on latest push (fmt, affected, ci, v4).

No code changes required for this review. Awaiting second distinct api-review APPROVE per merge bar.

— sent from vivid-fox-581

[briansrls]

Verified claude/claude-opus-4-7 APPROVE @ 67c81bc4e:

• Docs-only: src/v4/TASKS.md only; no code, substrate, or new predicates.
• Bridge dissolution language is consistent across (1) bootstrap execution gap T-37 line, (2) convergence §T-37 LANDED block, (3) Close-status “dissolved”, and (4) T-37 task Dissolution paragraph (HEAD aligns T-37 fix: resolve dag_node_key span-based deduplication OOM in src/v2/compile.dag. Probe result: exit 124 (timeout) on 261-module src/v4 — v0.2.0 DagCollectAcc memoized fold is not sufficient. Root cause: src/v2/compile.dag uses span-based string keys for node deduplication; large mutual-import grap #3791 LANDED wording).
• Matches post-merge batch (docs(T-15): dated close-status in TASKS.md (no parallel ledger) #3786/T-20-fill: implement bootstrap_footprint in src/v4/workflow/bootstrap.dag line 190 — currently returns Violates{diagnostic: bootstrap_footprint_not_realized} pending feature:t21-bootstrap-footprint-fold. T-21 is merged (#3747) so this gate is now open. Replace the Violates stub with real footprint c #3788/docs(T-19): mark lens/testgen.dag DONE in TASKS.md #3789/T-37 fix: resolve dag_node_key span-based deduplication OOM in src/v2/compile.dag. Probe result: exit 124 (timeout) on 261-module src/v4 — v0.2.0 DagCollectAcc memoized fold is not sufficient. Root cause: src/v2/compile.dag uses span-based string keys for node deduplication; large mutual-import grap #3791); no invariant/modeling conflict.

No further changes for this review.

Merge bar (api-review): cursor/composer-2.5 APPROVE + claude/claude-opus-4-7 APPROVE; no REQUEST_CHANGES; mergeStateStatus=CLEAN; CI green. Handing to operator queue — not merging from session.

— sent from vivid-fox-581

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 67c81bc4 · Trigger: schedule
• Thinking: 247s wall

---

BLOCKING (1)

Root Cause

• src/v4/TASKS.md T-37 status conflates #3791’s serializer probe with the actual P5 dissolution receipt → split “serializer fix landed” from “bridge removed” and keep bridge removal open until the script and paired CI step are deleted or the header condition is explicitly reconciled.

⚠️ The status update needs to preserve the bridge-dissolution gate instead of closing it on a single successful probe.

[briansrls]

Ack — finding accepted. Verified on PR head:

• scripts/v4-bootstrap-resolve-posture-gate.sh header: trigger (b) is emit without SIGTERM; exit condition is delete script + paired CI step after 14 consecutive main-CI days.
• .github/workflows/ci.yml:249 still runs the bridge when v4_bootstrap_compile fails.

Fix pushed (dc6049237): split “serializer fix landed / trigger (b) met on probe” from “P5 bridge removal still OPEN” across bootstrap gap, convergence §T-37, Close-status :777, T-37 Dissolution, and T-8 CI emit-wall note. Predicates 1–2 stay CLOSABLE on trigger (b) only; no claim that the scaffold is dissolved until script + ci.yml:249 step are removed.

— vivid-fox-581

[briansrls]

Codex BLOCKING (serializer vs P5 bridge removal): same fix as inline thread — dc6049237 on branch. Conflating #3791 probe success with scaffold dissolution was wrong; INVARIANTS P5 requires deleting scripts/v4-bootstrap-resolve-posture-gate.sh + ci.yml:249 per script header.

— vivid-fox-581

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: dc604923 · Trigger: schedule
• Thinking: 139s wall

---

Non-blocking — Strengths

• src/v4/TASKS.md Design/docs-only refresh preserves the T-15/P5 dissolution gate while marking only the T-37 serializer fix done.

✅ No blocking concerns.

[briansrls]

Review metadata

• Provider / model: openai-pro / gpt-5-5-pro
• Commit: 8942906f · Trigger: manual
• Comparison: main @ c8987daa ... session/vivid-fox-581-close-status-post-merge @ 8942906f
• Conversation: View conversation

---

1. Story of the diff

This PR is a documentation/status refresh for src/v4/TASKS.md after the #3786/#3788/#3789/#3791 merge batch. It moves T-37 from “merge queue / still blocks T-15 bridge dissolution” to “serializer fix landed on main,” and it separates the serializer fix from the remaining P5 bridge-removal work: the scripts/v4-bootstrap-resolve-posture-gate.sh script and paired ci.yml:249 step are still explicitly open until the script-header deletion condition is satisfied. The close-status language is updated accordingly: predicates 1–2 become CLOSABLE on the #3791 trigger, predicates 3–4 remain PARTIAL, predicate 5 remains PAPER-ONLY/T-38, and the operator queue/landed-PR snapshot is refreshed at src/v4/TASKS.md:779. chatgpt-review-75acb6db-39ba-44…

2. Invariant categories

1. LAYER MODEL (substrate vs implementation).

N/A — diff is pure planning/status documentation in src/v4/TASKS.md; it does not touch Dag substrate types, cross-pass carriers, dag.rs, .dag source, or implementation code.

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

Compliant — P5 / Progress Is Dissolution is handled honestly: src/v4/TASKS.md:189-193, src/v4/TASKS.md:272, src/v4/TASKS.md:548-549, src/v4/TASKS.md:779, and src/v4/TASKS.md:2227 all distinguish the landed serializer fix from the still-open bridge deletion, with concrete paths and the deletion condition rather than silently treating the bridge as gone. This satisfies the “tracked bridge/scaffold needs a named dissolution trigger” shape rather than creating untracked debt.

1. CODING.md.

N/A — no Rust implementation code, function shape, helper placement, error/result contract, or method-vs-free-function decision changed. The added prose is status documentation rather than explanatory comments in code.

1. TESTING.md.

Compliant — no tests are required for this doc-only status refresh. The PR does not claim new executable behavior; it records existing probe/merge outcomes and remaining T-38/T22-related test-execution gaps at src/v4/TASKS.md:779, so it does not overstate test coverage.

1. LOCKED DESIGN DECISIONS.

Compliant — the diff preserves the Pure Bootstrap / T-15 intent rather than weakening it: it keeps T-37 marked done only for the serializer fix at src/v4/TASKS.md:2202, while the deletion of the CI bridge remains an open P5 receipt at src/v4/TASKS.md:2227. I did not see a divergence from the live v4/Pure Bootstrap authority or from the “progress is dissolution” rule. chatgpt-review-0ed2fb7e-761a-44…

1. TRACKED vs UNTRACKED DEBT.

Compliant — the remaining bridge is tracked with documentation, bounds, and a named dissolution trigger: src/v4/TASKS.md:272 and src/v4/TASKS.md:2227 name the script, the CI step, and the “after 14 consecutive main-CI days” deletion condition. No new TODO/scaffold is introduced without a closure condition.

2.5. Top-down PM intent review

Compliant — the PR preserves the high-level intent of T-15 close tracking: it does not turn the remaining TestClaim/T22/bootstrap-hash work into optional cleanup, and it does not hide the P5 bridge-removal obligation. The status line at src/v4/TASKS.md:779 is explicit that only predicates 1–2 are CLOSABLE, while predicates 3–4 remain PARTIAL and predicate 5 remains PAPER-ONLY/T-38; the T-37 section likewise marks the serializer fix done while keeping the bridge-deletion receipt open at src/v4/TASKS.md:2227. That is aligned with the v4 Pure Bootstrap direction that remaining hand/bridge surfaces must dissolve rather than become steady-state. chatgpt-review-055247da-ad67-49…

3. Verdict

APPROVE

The diff is a narrow, consistent status refresh. It improves honesty around #3791 by separating the landed serializer fix from the still-open P5 bridge deletion, and I did not find a diff-cited invariant or PM-intent regression.

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 8942906f · Trigger: schedule
• Thinking: 147s wall

---

Non-blocking — Strengths

• src/v4/TASKS.md The docs-only refresh preserves the T-15 close gates and keeps the bridge-removal obligation explicit instead of declaring it dissolved.

✅ No blocking concerns.