docs: lead decision 146, ready for decision 78 is row 42's acceptance run

Jason via Mos (sage-0204, DECISIONS Q161): "D4 yes". refactor is ready
to merge to next when row 42's acceptance run passes with Jason on the
live mosaic-stack business. The merge itself stays Jason's (R2).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

docs/plans/2026-09-26_lead-decisions.md

@@ -3301,3 +3301,24 @@ which stay with him. Each item names who decided it and what happened.
       file and a second copy of the human proof, which is bound to the
       bus's own `human-cli.mjs` path (#225). A one-time migration doesn't
       justify a new security boundary.
+
+146. **"Ready" for decision 78 is row 42's acceptance run passing
+    (2026-10-15, Jason via Mos sage-0204, DECISIONS Q161 in brain-redux).**
+    Mos put D4 to Jason: refactor is ready to merge to next when row 42's
+    acceptance run passes with Jason on the live mosaic-stack business.
+    Jason, verbatim: "D4 yes".
+    - This answers the question decision 78 left open, what "ready" means.
+      It amends nothing else in decision 78: refactor stays the dev branch
+      until then.
+    - Row 42 (S7, #1524) is the gate. Its gate owner is Jason, and the run
+      has to be on the live mosaic-stack business with him, not a scratch
+      business. Jason judges the pass from the five trails, as the row's
+      gate says.
+    - The merge plan (docs/plans/2026-10-08_refactor-to-next-merge-plan.md)
+      still waits as a whole, steps 1 to 3 included, until that run passes.
+      Then I start step 1.
+    - Step 4, the PR into next and its merge, stays Jason's to approve and
+      merge (R2). "Ready" starts the plan; it doesn't authorize the merge.
+      main stays out of scope.
+    - This replaces the "waits for your ready" line under Needs Jason in
+      my 2026-10-15 AM standup. Nothing goes to Jason for it now.