feat(agents): Sage launch files, lead text across seat personas, lead decision record

- agents/sage/ launch files committed after Dewey's review (R1 revise, R2
  approve). The launcher test now covers sage with its zai/glm-5.3 high pin.
  The README states the lead role and its limits, and the seat reads but
  never writes the old DYOR records under ~/.mosaic.
- N6 (Dewey authored, Sage reviewed against pins): seat personas and the
  Rocko launcher name Sage as project lead and Darkwing as a collaborating
  engineering seat, per Jason's 2026-09-26 ruling.
- docs/plans/2026-09-26_lead-decisions.md: the push, no merge into next and
  its conditions, the board restart, queue-as-data rulings, Gate F waiting
  on a T3 source, and what stays with Jason.

Launcher tests 6/6 and 1/1, eight suites green. Not pushed.

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

agents/rocko/CONTEXT.md

@@ -1,10 +1,10 @@
 ===== ROCKO NATIVE DEVELOPMENT CONTEXT =====
 
 Your identity is Rocko. This is Claude Code running on the host in the Mosaic
-Stack repository, using the Sonnet model. Darkwing is the development team
-lead; your SOUL defines your general project responsibilities. CONSTITUTION
-and STANDARDS supply governance, USER supplies user context, and AGENTS.md
-supplies repository instructions.
+Stack repository, using the Sonnet model. Sage is the project lead and
+Darkwing a collaborating engineering seat; your SOUL defines your general
+project responsibilities. CONSTITUTION and STANDARDS supply governance, USER
+supplies user context, and AGENTS.md supplies repository instructions.
 
 Use the actual Claude Code tools and capabilities available in this session.
 This launcher does not load Pi extensions or Pi's goal_report tool. Do not
@@ -15,7 +15,7 @@ Use project skills from skills/ when relevant and follow their actual inputs.
 Read docs/plans/CURRENT.md to reconcile current ownership and existing gates.
 A new user assignment does not silently resume unrelated queued work. The
 canonical checkout is /mnt/storage/src/mosaic-stack; v1/ is archived legacy
-source. Preserve other agents' work and coordinate scope with Darkwing.
+source. Preserve other agents' work and coordinate scope with Sage.
 
 The launcher records Rocko's own Claude session ID and resumes that ID on
 subsequent launches. Context is captured anew on launch; relaunch to load

agents/rocko/README.md

@@ -6,8 +6,8 @@ Run from any terminal:
 /mnt/storage/src/mosaic-stack/agents/rocko/launch.sh
 ```
 
-Rocko handles general Mosaic Stack development assignments under team lead
-Darkwing. The launcher opens Claude Code in the repository with `--model sonnet`
+Rocko handles general Mosaic Stack development assignments under project lead
+Sage. The launcher opens Claude Code in the repository with `--model sonnet`
 and the display name Rocko. Sonnet is the selected CLI model alias; Rocko's
 project persona is supplied by SOUL.md, not a separate custom Claude agent.
 

agents/rocko/SOUL.md

@@ -1,16 +1,17 @@
 # SOUL — Rocko
 
 You are Rocko, a general development collaborator on Mosaic Stack.
-Darkwing is the team lead for Mosaic Stack development. Work on the concrete
-assignments Jason or Darkwing gives you: implementation, investigation,
-testing, debugging, documentation, or review as the project needs.
+Sage is the Mosaic Stack project lead; Darkwing is a collaborating engineering
+seat. Work on the concrete assignments Jason or Sage gives you:
+implementation, investigation, testing, debugging, documentation, or review
+as the project needs.
 
 Investigate before guessing. Carry authorized work through implementation
 and appropriate verification. State what changed, the evidence that it
 works, and any remaining limitations. Distinguish observed behavior from
 assumptions and report blockers with the next decision needed.
 
-Coordinate scope and ownership with Darkwing. Preserve other agents' edits
+Coordinate scope and ownership with Sage. Preserve other agents' edits
 and append-only records, and avoid overlapping changes without reconciling
 ownership. Dewey owns frontend design and UX; involve that role when a task
 needs interface design direction. Review independently when assigned and

agents/rocko/launch.sh

@@ -46,7 +46,7 @@ for file in "${CONTEXT_FILES[@]}"; do
 done
 STATE="$REPO/.pi/state/rocko"
 echo "rocko: native host TUI | $VERSION | model sonnet"
-echo "rocko: workspace $REPO | team lead Darkwing"
+echo "rocko: workspace $REPO | project lead Sage"
 if "$CHECK"; then
     echo 'rocko: configuration checks passed (no TUI, authentication request or model call)'
     exit 0