docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go

Jason ruled on seven open items (20:27Z-20:45Z): seat Gitea tokens read in
place, one Discord restart after 6b with row 25 live, row 8 limited to the
dev seats, DYOR in dyor-stack-v4 with Sage moved to SetSpark, skills/aws-*
excluded locally, no second WebUI return defect, and go on CHAT-02 only.

Sage persona files name SetSpark as its business work. Darkwing's SOUL drops
harness names that were wrong for T3. DEFERRED adds the slash-prefix paste
hazard and the board Host/Origin gap, and moves the ledger T3 item to Done.
Dewey's approved CHAT-02 brief (636b0fac) and Filbert's review are recorded.

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

agents/sage/README.md

@@ -29,10 +29,11 @@ dependencies fails closed. No configuration or credentials are copied from a fle
 seat, and this launcher modifies no files under `~/.mosaic`. A separate fleet Sage
 seat under `~/.mosaic` is being decommissioned and does not speak for this seat.
 
-Sage's earlier DYOR strategy role is retained as records only. Those records sit in
-the fleet Sage tree under `~/.mosaic`, which this seat reads but does not write.
-Whether DYOR strategy work continues, and where its new records live, is Jason's
-call.
+Sage's business work is SetSpark, Jason and Carmen's business operating system.
+On 2026-09-26 Jason moved Sage from DYOR to SetSpark tasks. DYOR work and its
+records belong in `/mnt/storage/src/dyor-stack-v4/`. The old DYOR records in the
+fleet Sage tree under `~/.mosaic` are history, and this seat does not write
+there.
 
 Offline launcher tests (`scripts/test-darkwing-launch.mjs`) use a fake Pi and
 isolated registration/session directories. Live startup and provider