Pure rename of the named production-isolation socket to match the product brand (Mosaic Fleet) — per Jason ("keep consistent on the branding": socket matches the product, not the internal forge engine). Behavior is identical — only the socket name changes.
Changed (single find/replace)
6 example presets: socket_name: mosaic-factory → mosaic-fleet
fleet.ts: DEFAULT_SOCKET_NAME = 'mosaic-fleet' (+ all literals)
systemd units (mosaic-tmux-holder.service) + READMEs, roster.schema.json, start-agent-session.sh
The PoC roster is socket-less (default tmux socket, no -L) → unaffected by the rename.
docs/fleet/north-star.md is intentionally EXCLUDED — it's owned by the in-flight doctrine PR #629; its mosaic-factory references are renamed there to avoid a merge conflict. (Merge order: #629 → this, or vice-versa, then the other rebases cleanly since they touch disjoint files.)
The live legacy canary fleet (_holder, canary-pi, dogfood-*) 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 (e.g. back to mosaic-forge).
Note: the branch is named feat/socket-rename-mosaic-forge (created before the mosaic-fleet correction); the content is correctly mosaic-fleet. Left as-is to avoid a CI re-run churn.
Verification
172 fleet + onboarding tests green; tsc/eslint/prettier/sanitize clean. Docs+packages/mosaic only → cheap under #619.
## refactor(fleet): rename tmux socket `mosaic-factory` → `mosaic-fleet`
Pure rename of the named production-isolation socket to match the **product brand (Mosaic Fleet)** — per Jason ("keep consistent on the branding": socket matches the product, not the internal `forge` engine). **Behavior is identical** — only the socket *name* changes.
### Changed (single find/replace)
- 6 example presets: `socket_name: mosaic-factory → mosaic-fleet`
- `fleet.ts`: `DEFAULT_SOCKET_NAME = 'mosaic-fleet'` (+ all literals)
- systemd units (`mosaic-tmux-holder.service`) + READMEs, `roster.schema.json`, `start-agent-session.sh`
- `docs/guides` + fleet `PRD`/`TASKS` + scratchpads; tests updated to assert `mosaic-fleet`
### Safety / scope
- The **PoC roster is socket-less** (default tmux socket, no `-L`) → unaffected by the rename.
- **`docs/fleet/north-star.md` is intentionally EXCLUDED** — it's owned by the in-flight doctrine PR **#629**; its `mosaic-factory` references are renamed there to avoid a merge conflict. (Merge order: #629 → this, or vice-versa, then the other rebases cleanly since they touch disjoint files.)
- The **live legacy canary fleet** (`_holder`, `canary-pi`, `dogfood-*`) 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 (e.g. back to `mosaic-forge`).
> Note: the branch is named `feat/socket-rename-mosaic-forge` (created before the mosaic-fleet correction); the **content is correctly `mosaic-fleet`**. Left as-is to avoid a CI re-run churn.
### Verification
172 fleet + onboarding tests green; tsc/eslint/prettier/sanitize clean. Docs+packages/mosaic only → cheap under #619.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 <[email protected]>
Claude-Session: https://claude.ai/code/session_01EsgTQzV5YUGk1JtCLP4B83
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
refactor(fleet): rename tmux socket
mosaic-factory→mosaic-fleetPure rename of the named production-isolation socket to match the product brand (Mosaic Fleet) — per Jason ("keep consistent on the branding": socket matches the product, not the internal
forgeengine). Behavior is identical — only the socket name changes.Changed (single find/replace)
socket_name: mosaic-factory → mosaic-fleetfleet.ts:DEFAULT_SOCKET_NAME = 'mosaic-fleet'(+ all literals)mosaic-tmux-holder.service) + READMEs,roster.schema.json,start-agent-session.shdocs/guides+ fleetPRD/TASKS+ scratchpads; tests updated to assertmosaic-fleetSafety / scope
-L) → unaffected by the rename.docs/fleet/north-star.mdis intentionally EXCLUDED — it's owned by the in-flight doctrine PR #629; itsmosaic-factoryreferences are renamed there to avoid a merge conflict. (Merge order: #629 → this, or vice-versa, then the other rebases cleanly since they touch disjoint files.)_holder,canary-pi,dogfood-*) still running on the old socket is a separate retire/migrate op, not this PR.mosaic-forge).Verification
172 fleet + onboarding tests green; tsc/eslint/prettier/sanitize clean. Docs+packages/mosaic only → cheap under #619.
🤖 Generated with Claude Code