mosaicstack/stack
1
0
Fork 0
Code Issues 32 Pull Requests 3 Actions Packages Projects Releases 15 Wiki Activity

refactor(fleet): rename tmux socket mosaic-factory → mosaic-fleet #630

Merged
jason.woltje merged 1 commits from feat/socket-rename-mosaic-forge into main 2026-06-22 21:08:45 +00:00
Conversation 0 Commits 1 Files Changed 21 +84 -84
jason.woltje commented 2026-06-22 20:07:44 +00:00
Owner
Copy Link

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

## 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)
jason.woltje added 1 commit 2026-06-22 20:07:45 +00:00
refactor(fleet): rename tmux socket mosaic-factory → mosaic-fleet
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Details
ci/woodpecker/pr/ci Pipeline was successful
Details
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
jason.woltje merged commit d539d61e0e into main 2026-06-22 21:08:45 +00:00
jason.woltje deleted branch feat/socket-rename-mosaic-forge 2026-06-22 21:08:45 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#630
Delete Branch "feat/socket-rename-mosaic-forge"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?