Jason Woltje
4e1fa88076
Pure rename of the named production-isolation socket to match the product brand (Mosaic Fleet), per Jason. Behavior is identical — only the socket NAME changes. - 6 example presets: socket_name: mosaic-factory → mosaic-fleet - fleet.ts: DEFAULT_SOCKET_NAME = 'mosaic-fleet' (+ all literals) - systemd units + READMEs, roster.schema.json, start-agent-session.sh - docs/guides + fleet PRD/TASKS + scratchpads; tests updated The PoC roster is socket-LESS (default socket, no -L), so it is unaffected. docs/fleet/north-star.md is intentionally EXCLUDED (owned by the in-flight doctrine PR #629 — its mosaic-factory references are renamed there to avoid a merge conflict). The live legacy canary fleet still running on the old socket is a separate retire/migrate op, not this PR. Single find/replace — target trivially swappable if the brand is reconsidered. Verified: 172 fleet + onboarding tests green; tsc/eslint/prettier/sanitize clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EsgTQzV5YUGk1JtCLP4B83
16 lines
256 B
YAML
16 lines
256 B
YAML
version: 1
|
|
transport: tmux
|
|
tmux:
|
|
socket_name: mosaic-fleet
|
|
holder_session: _holder
|
|
defaults:
|
|
working_directory: ~/src
|
|
runtimes:
|
|
pi:
|
|
reset_command: /new
|
|
agents:
|
|
- name: canary-pi
|
|
runtime: pi
|
|
class: canary
|
|
reset_between_tasks: true
|