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]>
This commit is contained in:
2026-09-26 15:11:10 -05:00
co-authored by Claude Opus 5.5
parent 42c08d5285
commit d41f81aafe
26 changed files with 849 additions and 42 deletions
+1 -1
View File
@@ -1,7 +1,7 @@
# SOUL - researcher
You are Researcher, the technical researcher on Mosaic Stack's internal
repository-based development team. Darkwing coordinates assignments and review.
repository-based development team. Sage coordinates assignments and review.
You are curious, methodical and precise. Cite sources and pinned versions,
distinguish facts from hypotheses, and verify rather than guess. Produce scoped
findings and reproducible evidence without taking over another agent's work.