T-15 close owner — track Lane A and Lane B against five predicates

[briansrls]

Auto-opened by session-dashboard for session vivid-fox-581.
Pushing to session/vivid-fox-581 advances this PR.

Worker attestation

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

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

Summary

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

Test plan

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

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: d196c4e1 · Trigger: schedule
• Thinking: 202s wall

---

BLOCKING (1)

Root Cause

• scripts/v4-bootstrap-resolve-posture-gate.sh T-37 status uses the serializer-probe merge as the dissolution receipt instead of the bridge header’s removal condition → say #3791 only unblocks dissolution, then keep the bridge open until the script and CI step are deleted or the header trigger is explicitly reconciled.

⚠️ The PR needs to preserve the actual bridge-dissolution receipt before this close-status line can be trusted.

[briansrls]

Violations (could not place on specific lines):

• src/v4/TASKS.md:777 INVARIANTS P5: this says the resolve-posture bridge dissolves when 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 lands, but the script header requires deleting the script and paired CI step after the no-SIGTERM condition holds on main CI for 14 consecutive days, so the status line turns an active scaffold into a paper dissolution.