jason.woltjeandClaude Opus 5.5
918a4a1937
agents/sage/work/q81/mosaic-cli.sh does install, update, undo and status.
~/.npm-global/bin/mosaic is now a wrapper that execs scripts/mosaic in a
detached worktree at ~/.local/share/mosaic-cli/stack, pinned to pushed
ee129aa6. The estate CLI symlink was renamed in place to mosaic-old.
Only commits on origin/refactor can be pinned. `mosaic queue` refuses
from the worktree (the queue runs only in the canonical checkout), so
queue work stays on scripts/mosaic. status flags a wrapper replaced by
`npm i -g --force`.
lease-gate-notes.md: no single environment location for
MOSAIC_LEASE_VERSION_PROBE_COMMAND exists outside fleet state, so the
old-path lease gate fails closed, as Mos ruled for that case.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sage
Mosaic Stack project lead (Jason's ruling, 2026-09-26). Sage coordinates
assignments, review and integration across the repository seats under
agents/. Darkwing is a collaborating seat. The lead role adds no push, merge
or deployment authority; those still need Jason's say-so. Development sessions
run in T3 for now, and a T3 session does not load this directory's SOUL or
CONTEXT. This launcher is the Pi path for the same seat.
From /mnt/storage/src/mosaic-stack:
agents/sage/launch.sh --check
agents/sage/launch.sh
agents/sage/launch.sh --fresh
--check validates configuration/context and the pinned local Pi version without
launching a TUI, registering a seat, requesting authentication or calling a model.
Normal launch registers the repository seat through scripts/mosaic, then uses
the existing host-development helper with zai/glm-5.3 and high thinking by
default; provider, model and thinking flags can be overridden per launch. It
resumes validated per-agent conversation state under .pi/state/sage; --fresh
starts another conversation without deleting history. Existing launcher locking
prevents duplicate native instances.
Bootstrap configuration remains authoritative. Missing config, context or pinned
dependencies fails closed. No configuration or credentials are copied from a fleet
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 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
authentication are separate observations, not implied by passing tests.