Record owner acceptance and closure of #1500 fixture increment

Jason reran the two-test fixture demonstration on the canonical checkout
at 5abbabb7 (2/2 pass). Records-only: acceptance receipt, BUILD-LOG,
SESSIONS and CURRENT.md next action (MVP re-plan). No source change.

Co-Authored-By: Claude Fable 5.1 <[email protected]>

docs/plans/CURRENT.md

@@ -7,6 +7,25 @@ update this file to the next action). No ambiguity, no re-planning.
 
 ## Next action
 
+Jason accepted the #1500 fixture-only increment on 2026-09-12 by running the
+two-test demonstration himself on the canonical checkout at 5abbabb7 (2/2 pass);
+receipt `docs/plans/reviews/2026-09-12_m20-increment2-owner-acceptance.md`.
+#1500 is closed. No increment 3, launcher integration, production refresh or
+deployment is authorized by that acceptance; the headless identity-env leak
+remains a separate intake owned by Darkwing.
+
+Next action: re-plan against Jason's 2026-09-12 MVP decision MOSAIC-STACK-D-001
+(control board: one page listing running agent sessions across projects with
+status and a "waiting on you" section, deliberately smaller than the current
+registry line). Present Jason a concrete plan that reconciles the registry
+queue (increment 3 candidates, identity-env fix) with that MVP, with a
+recommendation and acceptance evidence, before starting any new implementation.
+Owner of this planning action: the active coordinator session (jarvis, Claude
+Code, taking over darkwing's pi session). The registry queue does not resume by
+inertia.
+
+## Completed checkpoint: #1500 increment 2 (historical)
+
 Registry plan review is complete. All ten gates carry owner rulings
 (2026-09-10, ms-grill-me + Q15); gate 7 closed via PI-REFRESH-ROCKO-1
 investigation and GATE7-FINAL-FILBERT-1 APPROVED. Published: 224147ec,
@@ -26,7 +45,11 @@ Source published at3daee5ad89dc6a006ca554ad7fda2b23eb96bb03; exact remote verifi
 Clean committed-tree checks: package/launcher74, config24, auth15, foundation43,
 conductor17 all pass. Task/release not run or claimed passing.
 Next action: present the two-test fixture demonstration for Jason's acceptance;
-keep #1500 open pending that response. Publication and demo receipt:
+keep #1500 open pending that response. Demo attempt 2026-09-11 failed only because
+Jason's terminal was a pre-cutover shell whose cwd followed the retired v1 copy
+(`git rev-parse HEAD` 5d277000, later pulled to next 2101c9b4); the canonical
+checkout at 5abbabb7 reruns the demo 2/2 (jarvis, 2026-09-12). Rerun after
+`cd /mnt/storage/src/mosaic-stack` in a fresh shell. Publication and demo receipt:
 `docs/plans/reviews/2026-09-10_m20-increment2-publication.md`.
 Headless identity-env fix is separate intake in the owner disposition record.
 No production refresh, live-suite effects or increment3 authority inferred. Charter: `docs/plans/2026-09-10_m20-increment2-charter.md`.
@@ -213,6 +236,8 @@ and unfinished-fixture status.
 
 ## Completed log
 
+- 2026-09-12 — #1500 closed: owner accepted the fixture-only increment by rerunning the two-test demo on 5abbabb7 (2/2). Records-only closure; no source, suite or live effect. Next: re-plan against MOSAIC-STACK-D-001 before increment 3.
+
 - 2026-09-08 — Owner-corrected Sage setup: `agents/sage/` now owns the DYOR business/strategy persona, context, launcher, and working records. Native cwd is this checkout, private history is `.pi/state/sage/sessions/`, and the prior brain command forwards here. Six offline launcher tests and both real configuration checks pass; current registry alignment queue unchanged.
 
 - 2026-09-08 — Owner-requested development team: Rocko launches Claude Code with Fable; Filbert launches Pi with `openai-codex/gpt-6-astra:low`; Darkwing is the development team lead and Dewey remains frontend/UX owner. Five offline launcher tests and both new agents’ local configuration checks pass. No model session started; inspector acceptance queue unchanged.