Fleet CLI Local Canary Dogfood — 2026-06-20

Objective

Move the durable tmux fleet PoC into a functional local canary on this server. This is not production deployment. It is a canary/dogfood path for a small local agent fleet using an isolated tmux socket.

Issue

Gitea issue: #562 — feat(fleet): local CLI canary dogfood

Scope

Implement enough product surface to use the fleet locally:

mosaic fleet init/install/start/stop/restart/status/verify
mosaic agent roster/status/send/reset/tail
roster schema and examples
local canary docs and rollback instructions
tests for CLI behavior where practical
canary verification on named tmux socket mosaic-factory

Non-goals

No production rollout.
No migration of existing default tmux sessions.
No image build/deploy work.
No hardcoded USC/local roster as product default.

Acceptance Criteria

CLI can initialize a minimal roster outside product defaults.
CLI can install user systemd units and fleet helper scripts to a configurable Mosaic home.
CLI can start/stop/status/verify a canary fleet using mosaic-factory.
mosaic agent send uses existing named-socket/exact-target tmux tooling.
mosaic agent reset targets only the named agent session on the named socket.
Verification proves default tmux sessions remain untouched.
Baseline repo gates pass.
PR CI is green before merge.
Local canary evidence is captured after merge/install.

Budget / Routing

Agent: codex preferred.
Estimate: 25K-40K tokens.
Worker owns implementation/tests/docs in branch feat/fleet-cli-local-canary.
Orchestrator owns docs/TASKS.md, issue/PR/merge, and local canary install verification.

Progress

2026-06-20: #557 PoC primitives merged to main as 45e2c2a.
2026-06-20: issue #562 created for local CLI canary dogfood.
2026-06-20: worktree created at /home/jarvis/src/mosaicstack-stack-worktrees/fleet-cli-local-canary.

1.9 KiB Raw Blame History