docs: BRIEF-TEMPLATE makes TMPDIR with shell mktemp -d only (no Python mkdtemp, one per run) and sets nice absolutely to 19 in each child, recording the nice each run saw (mos-1598, Vikunja 623); reports for Sage go to Sage's thread (mos-1591); doc only

docs/plans/BRIEF-TEMPLATE.md

@@ -59,6 +59,17 @@ fails it on any commit (row 323, mos-1561). A builder whose cli suite
 can't run says so in the row, and the cli suite counts from the lead's
 landing gate.
 
+Make the TMPDIR with shell `mktemp -d` and that template only. Python's
+`tempfile.mkdtemp` adds `_` and runs to 48 bytes, which fails
+`claude-session.test.mjs:298` and the socket limit (Vikunja 590). A
+script that starts several runs makes one TMPDIR per run.
+
+Set nice absolutely, not relative. The host's ananicy renices node, so
+`nice -n 10` can land at 16 or at -4. In shell use
+`nice -n $((19 - $(nice))) CMD`. In a Node or Python launcher set 19 in
+each child (`os.setpriority` or `os.nice(19 - os.nice(0))` in preexec).
+Record the nice each run saw in BUILD.md (Vikunja 623, mos-1598).
+
 Evidence that lands with a row is plain text: logs, diffs, manifests. No
 gzip or other binary file, so the lead's push guard runs its binary and
 secret checks with no waiver. If a log is too big, cut it to the lines
@@ -103,4 +114,8 @@ pushes a build or a new round, or the reviewer posts a verdict, that seat
 messages the next seat's T3 thread and Sage's with
 `mcp__t3__t3_send_message`. Claude and Codex seats both have it. Copy
 Mos's thread only when Mos has a step. Nobody waits on a date or a
-schedule when the next step is ready.
+schedule when the next step is ready. Reports, questions and slot
+requests for Sage go to Sage's thread,
+`1ef1e4f8-3ead-4208-beca-38f9f1add079`, with the `[from: ... -> to: ...]`
+header, never to Mos's thread in Sage's place (mos-1591, after Beakley,
+Fethry and Herb reports reached Mos).