docs(plans): lead decision 67, S3 starts before the Vikunja runbook half (sage)

The estate Vikunja (T236) won't serve by Jason's 10-09 run. S3 builds
against the recorded fake and a scratch container; its gate still needs
the live run. R20's PM and Lead match the slice 1 brief's staffing.
Merge plan step 2 no longer holds for T235 (brief c733ac92b).

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

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

@@ -1177,3 +1177,22 @@ which stay with him. Each item names who decided it and what happened.
       then, he runs section 1 (Gitea) and leaves sections 2 to 4 for
       when it is. Don't start Path B as a stopgap, because that makes
       two Vikunjas and mints bot tokens twice.
+67. **S3 starts before the runbook's Vikunja half, and the stack's
+    PM and Lead are Sage and Darkwing (2026-10-08).** Source: Mos,
+    thread 1eba59e5, after decision 66.
+    - The estate Vikunja won't serve by Jason's 2026-10-09 run. Mos
+      dispatched it to orch-01 as T236 with no date yet. Jason runs
+      the runbook's section 1 (Gitea) on 10-09, and sections 2 to 4
+      wait for T236's base URL. The existing tasks.mosaicstack.dev runs
+      2.1.0, which is too old, and stays untouched.
+    - Row 38 (S3) no longer waits for row 35. Everything S3 builds runs
+      against the recorded fake of the v2 routes and a scratch
+      container, as its brief already says. Only the one live run needs
+      the estate instance, and S3's gate still requires that run's log,
+      so the row can't close without it. Without this change every
+      slice 1 row sits behind T236. Row 38 keeps rows 36 and 37 as
+      prerequisites.
+    - Jason's R20 gives every project a separate PM and Lead. Mos
+      proposed Sage as PM and Darkwing as Lead (the PRD's CTO role).
+      That is the slice 1 brief's staffing already: PM held by Sage,
+      CTO by Darkwing. No row changes.

docs/plans/2026-10-08_refactor-to-next-merge-plan.md

@@ -97,10 +97,11 @@ existing push authority. Steps 4 and 5 are Jason's.
    flag that CI sets and the suite reports as a skip. New queue row,
    Darkwing reviews.
 2. **Add root `.mosaic/repo.json`.** Same content as `next`'s, with the
-   notes updated to cite R10. Hold this step until the T235 enforcer
-   lands and its handling of a repo with this file is checked. An
-   enforcer that reads `integration_trunk: next` while `refactor` is
-   still the working branch must not block step 3.
+   notes updated to cite R10. No hold for T235. Mos amended its brief
+   (c733ac92b, 2026-10-08): under `trunk-release` the enforcer denies
+   direct pushes to `integration_trunk` and `release_branch` only, so
+   pushes to `refactor` and `slice1/*` stay allowed. A repo with no root
+   `repo.json` gets no branch rules at all, which is today's state.
 3. **Back-merge `origin/next` into `refactor`.** One merge commit,
    proven clean above. Re-run `merge-tree` against the then-current
    `origin/next` first, since `next` can still move. Full integration