docs(records): Sage lead handover, rows 23-25 state, row 8 stub, BUILD-LOG rebuilt on HEAD

Records Jason's 2026-09-26 ruling: Sage leads the project, Darkwing is a
collaborating seat, development stays in T3, and the old ~/.mosaic fleet is
being retired. The lead role adds no push, merge or deploy authority.

- QUEUE rows 23-25 show their commits and pushes; row 8 links a parked stub
  brief listing the rulings Jason must make before fleet seats move.
- Shared records from Darkwing (rows 6, 16, 18, 22, #1511, #1512) and Dewey
  (row 5) that were waiting on one owner for the shared files.
- DEFERRED: T3 headers counted as human in the ledger (#1506), #1509 engine
  test leak and busy gap, #1512 re-run outcome.
- BUILD-LOG.md rebuilt as HEAD plus the uncommitted entries; the working copy
  had dropped the row 23-25 entries. Diff against HEAD is additions only.

All eight suites green. Not pushed.

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

agents/README.md

@@ -2,14 +2,21 @@
 
 These are interactive host development agents working in the canonical
 checkout. They do not create managed fleet registrations or change role policy.
-Darkwing leads development and coordinates assignments, review, and integration.
+Sage leads the project and coordinates assignments, review, and integration
+(Jason's ruling, 2026-09-26). Development sessions run in T3 for now.
+For the current bootstrap phase, direct coding, review and research use Darkwing,
+Dewey, Filbert, Rocko, Researcher and further seats Jason launches from this repository's `agents/` directory,
+not fleet seats. Keep changes in `/mnt/storage/src/mosaic-stack`; do not modify
+`~/.mosaic` launchers/provisioning or migrate/stop live fleet processes.
 
 | Agent | Responsibility | Runtime | Launch from repository root |
 | --- | --- | --- | --- |
-| Darkwing | Development team lead and hands-on engineering | Pi, configured Mosaic model | `agents/darkwing/launch.sh` |
+| Darkwing | Hands-on engineering; collaborating seat under Sage | Pi, configured Mosaic model | `agents/darkwing/launch.sh` |
 | Dewey | Frontend design, UX, accessibility, and UI implementation | Pi, configured Mosaic model | `agents/dewey/launch.sh` |
 | Rocko | General development, investigation, testing, and review | Claude Code, Sonnet model | `agents/rocko/launch.sh` |
 | Filbert | General development, investigation, testing, and review | Pi, `openai-codex/gpt-6-astra:low` | `agents/filbert/launch.sh` |
+| Researcher | Source-grounded technical research and evidence | Pi, configured Mosaic model | `agents/researcher/launch.sh` |
+| Sage | Project lead: coordination, review, integration; earlier DYOR strategy records retained | T3 session (Claude Code); Pi launcher `zai/glm-5.3:high` retained | `agents/sage/launch.sh` |
 
 Each script supports `--check` and `--fresh`. Normal launches resume the agent's
 own conversation; a first launch starts one. See each agent's README for
@@ -26,4 +33,10 @@ its own supplied flags or the system defaults.
 
 All agents follow repository governance and current user direction. Team
 leadership does not add deployment or push authority. Coordinate overlapping
-work with Darkwing and preserve other sessions' changes.
+work with Sage and preserve other sessions' changes.
+
+Before 2026-09-26 Sage worked only on DYOR strategy and sat outside the
+development queue. Jason then made Sage the project lead and Darkwing a
+collaborating seat. A separate fleet Sage seat under `~/.mosaic` is being
+decommissioned; it does not speak for this seat. Whether the DYOR strategy work
+continues is Jason's call. Joe retains DYOR engineering.