docs(r2-structure): allow pre-R1-close spawn for 5 of 6 R2 managers (PB stays gated)

docs/r2-structure.md

@@ -253,7 +253,9 @@ Rationale: consistent with anti-deferral stance — tail-shaped work closes befo
 2. **R1 residual sweep** — every open R1 ledger row gets an R1-or-R2 assignment. No orphaning. Done in the R1 closure PR. Expected to be short under all-gates-green criterion.
 3. **R1 manager dissolution** — all R1 standing managers (Surface, Substrate, Testgen, Self-hosting, Release) archive with closure banners. Their scopes are fully absorbed by R1's gate acceptance; no inheritance into R2 managers.
 4. **R2 manager spin-up** — six standing managers initialized per the revised manager structure above. Each manager gets a dedicated brief (`docs/briefs/r2-grounding-manager.md`, `docs/briefs/r2-substrate-manager.md`, `docs/briefs/r2-modeling-manager.md`, `docs/briefs/r2-impossible-bugs-manager.md`, `docs/briefs/r2-pure-bootstrap-manager.md`, `docs/briefs/r2-release-manager.md`) naming program scope + owned deliverables + cross-program dependencies + autonomous dispatch authority + reporting cadence. **Pre-stage skeleton briefs before R1 closes** (Director authors skeletons during R1 final week; promotion PR fills in scope-final details) so the R1→R2 transition is not gated on six fresh authoring cycles. Existing `docs/briefs/grounding-manager.md` migrates content into `r2-grounding-manager.md` and archives. Existing `docs/briefs/pure-bootstrap-zero-manager.md` migrates content into `r2-pure-bootstrap-manager.md` and archives.
-5. **R2 open** — this doc promotes to `ROADMAP.md` as `## Release R2 Program` section.
+
+   **🔄 REVISED 2026-04-26.** Of the six R2 managers, only **Pure Bootstrap is definitionally R1-close-gated** — its scope is "what survives R1 close" (mirror dissolutions, Tier 2 patch retirement, post-R1 emergent dissolutions); R1's PB gates (T-PB-A + T-PB-B census reduction) own the R1-side work, and PB Manager picks up the residual. The other five managers (Grounding, Substrate, Modeling, Impossible-Bugs, Release) **may spawn pre-R1-close** when (a) their brief queue is authored, (b) at least one owned deliverable is dispatchable, and (c) spawning does not conflict with R1 closure work. In particular, **R2 Substrate Manager's ValueBody-list/sum sub-lane is a PREREQ for R1C-A Sub-deliverable A** (M1(2.8) list-body lowering depends on the substrate variant landing) — pre-R1-close Substrate spawn actively unblocks R1 closure rather than competing with it. This refines the original "spawn at R1 close" framing of step 4 without superseding the dissolution discipline of step 3 (R1 manager dissolution still happens at R1 gates green).
+5. **R2 open** — this doc promotes to `ROADMAP.md` as `## Release R2 Program` section. Promotion still gates on R1 close — pre-R1-close R2 manager activity is operating under PROPOSAL authority of this doc; the ROADMAP `## Release R2 Program` section lands at step 1 + step 5 sequencing.
 
 **v2 retirement (explicit non-scoping note):** The v2 compiler at `src/v2/` persists as test oracle into R2 and is NOT on the R2 ledger. Its retirement is external post-R2 operational cleanup — no thesis claim depends on v2 being absent. Differential-test-oracle retirement is bounded by adoption/documentation concerns, not release-gate discipline.
 
@@ -281,6 +283,7 @@ Purpose: proof-of-work visibility at director cadence. Without it, program slips
 - **Anti-deferral principle is the frame, not velocity numbers.** Per Director observation: 16-hour R1 execution was a peak-day sample, not a baseline. The principle "if dissolution direction is clear and named, deferral is problem-finding not problem-solving" is what survives cadence shifts.
 - **`sub_charclass_in_std_unicode` phase-2 reclassified R1 → R2** (2026-04-24, ROADMAP amendment paired with this revision). Surface Manager handoff (sub-child `quiet-gull-882` triage) confirmed the remaining work is Class 5 Gap 3 substrate-capability scope, not T-Sub-only surface fix; reclassifying lets R1 close on T-Sub Day-1 + DB-11 without waiting on substrate-capability work. Phase-2 lands in R2 as a 4th T-Substrate scoped sub-lane (consumer: tokenizer). Reclassification scope is bounded — full Class 5 Gap 3 substrate-capability close remains outside R2 unless additional R2 items demand it; only the tokenizer-charclass-unblock subset is R2-committed.
 - **Post-R2 stance = STRONG.** R2 is thesis close. Post-R2 work is external (adoption, documentation, community, ecosystem buildout). R3 is reserved as escape hatch only, not as a structural release program. User-locked 2026-04-24 after pressure-test framing: *"real programs are probably required to confirm the thesis is real, but we can keep R2 theoretical to stay fair — future work would pressure test the claims."* The R2 doc's "close-everything" claim is thus scoped to the **structural thesis** (what the compiler proves by construction); practical validation via modeling real programs (e.g., the user's `../ctrl/` follow-up) is a separate post-R2 stream that *tests whether the thesis holds in practice*, without itself being a thesis claim.
+- **Pre-R1-close R2 manager spawn allowed for 5 of 6 managers** (locked 2026-04-26 per user direction). Per-manager R1-gating audit found only Pure Bootstrap is definitionally R1-close-gated (scope = "what survives R1 close"); the other 5 (Grounding, Substrate, Modeling, Impossible-Bugs, Release) have no technical R1 dependency and may spawn pre-R1-close. R2 Substrate spawn actively *unblocks* R1 closure (ValueBody-list/sum is prereq for R1C-A Sub-deliverable A). This is the targeted exception to step 4's "spawn at R1 close" framing in Transition mechanics; refined inline at step 4. ROADMAP `## Release R2 Program` promotion (step 5) still gates on R1 close — pre-R1-close R2 manager activity operates under this doc's PROPOSAL authority, not under ROADMAP authority.
 
 ## Open calls