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

F3-m3 — mosaic update re-seeds framework + relaunches agents (R13) #609

New Issue
Open
opened 2026-06-22 03:24:32 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-06-22 03:24:32 +00:00
Owner
Copy Link

F3-m3 — mosaic update re-seeds framework + relaunches agents (closes R13)

Operator-critical gap (found in 0.0.39 production validation): mosaic update installs the new npm CLI but does not re-seed the framework files into ~/.config/mosaic/. So after update, tools/fleet/start-agent-session.sh and runtime/pi/mosaic-extension.ts stay stale — the shipped custom Pi harness (agent-name export + native HB) won't activate until a re-seed. Operators get the new CLI but a stale framework.

Scope

  • After a successful mosaic update install of @mosaicstack/mosaic, re-seed the framework from the freshly-installed package's framework/install.sh with MOSAIC_SYNC_ONLY=1 MOSAIC_INSTALL_MODE=keep (the P4 data-safe reconcile: FRAMEWORK_OWNED overwrite + backup-once; SOUL/USER/*.local/credentials preserved). Default-on; --no-reseed to skip.
  • Relaunch durable agents so the new launcher/extension takes effect (systemctl --user restart mosaic-agent@<name>). Opt-in --relaunch (restarting running agents is disruptive); default = print clear guidance to run mosaic fleet restart.
  • Unit tests for the re-seed command/env construction + the relaunch gating.

Flow

drain → update CLI → re-seed framework → relaunch agents — closes R13, activates the native harness for every operator.

Notes

  • Data-safety of the sync is already proven (P4 5-fixture matrix + live dragon-lin validation, zero data loss).
  • Framework ships in the npm package (files: [dist, framework]), so the re-seed uses the local installed copy — no network.
## F3-m3 — `mosaic update` re-seeds framework + relaunches agents (closes R13) **Operator-critical gap (found in 0.0.39 production validation):** `mosaic update` installs the new npm CLI but does **not** re-seed the framework files into `~/.config/mosaic/`. So after update, `tools/fleet/start-agent-session.sh` and `runtime/pi/mosaic-extension.ts` stay **stale** — the shipped custom Pi harness (agent-name export + native HB) won't **activate** until a re-seed. Operators get the new CLI but a stale framework. ### Scope - [ ] After a successful `mosaic update` install of `@mosaicstack/mosaic`, **re-seed the framework** from the freshly-installed package's `framework/install.sh` with `MOSAIC_SYNC_ONLY=1 MOSAIC_INSTALL_MODE=keep` (the P4 data-safe reconcile: FRAMEWORK_OWNED overwrite + backup-once; SOUL/USER/*.local/credentials preserved). Default-on; `--no-reseed` to skip. - [ ] **Relaunch durable agents** so the new launcher/extension takes effect (`systemctl --user restart mosaic-agent@<name>`). Opt-in `--relaunch` (restarting running agents is disruptive); default = print clear guidance to run `mosaic fleet restart`. - [ ] Unit tests for the re-seed command/env construction + the relaunch gating. ### Flow `drain → update CLI → re-seed framework → relaunch agents` — closes R13, activates the native harness for every operator. ### Notes - Data-safety of the sync is already proven (P4 5-fixture matrix + live dragon-lin validation, zero data loss). - Framework ships in the npm package (`files: [dist, framework]`), so the re-seed uses the local installed copy — no network.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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#609
Delete Branch "%!s()"

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?