docs(records): lead decision 41, Gate G setup (row 31, #1508)

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-28 08:28:00 -05:00
parent c989dfe9d4
commit 7a3c364b41
2 changed files with 22 additions and 0 deletions
@@ -561,3 +561,24 @@ which stay with him. Each item names who decided it and what happened.
    - **T3 seats.** The weekly run passes `--unsupported-runtime` for
      each T3 seat that owns an active row, and the output prints it.
      That matches 8.10's `exempt` class.
+41. **Gate G is set up, not run (2026-09-28).** The gate needs a fresh
+    seat launch at a terminal. `agents/<seat>/launch.sh --fresh` opens a
+    TUI, and Sage can't drive one from T3. Jason watches the run under the
+    brief. So Sage prepared the rest.
+    - Row 31 is a real piece for Rocko, whose queue was empty: refuse a
+      row's owner as its reviewer (Filbert's n2). Its brief was committed
+      at 92aeeeef, and the row is `briefed` (rev 26, c989dfe9).
+      `queue next rocko` now answers "start row 31".
+    - Rocko's launcher exports `MOSAIC_AGENT_NAME=rocko`, so a bare
+      `mosaic queue next` names the seat.
+    - Jason's part is `agents/rocko/launch.sh --fresh`, then the one
+      sentence, then a pass or fail line on #1508.
+    - Row 31 is also a brief Jason can accept toward row 11's gate.
+    - Correction: Sage ran `agents/rocko/launch.sh --help` to read its
+      usage. The launcher ignores `--help` and registered rocko before
+      printing usage. That rewrote
+      `~/.mosaic-dev/seats/repo/rocko/registration.json` with a pid that
+      has since exited. Rocko owns no active row, so the ledger doesn't
+      read it, and the next launch rewrites it.
+    - The Monday ledger (2026-09-28, #1508 comment 26592) failed on age
+      for rows 9, 10, 11 and 13, as decision 40 expected.