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

Release harden Mosaic fleet before official rollout #564

New Issue
Closed
opened 2026-06-20 20:17:49 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-06-20 20:17:49 +00:00
Owner
Copy Link

Fleet has passed local deterministic dogfood, but before official release we need a focused hardening pass.

Scope:

  • Fix operator-origin source-label correctness for mosaic agent send outside tmux.
  • Preserve inter-agent preamble behavior and named-socket isolation.
  • Strengthen regression tests around send source labels, fleet verify/status semantics, install-systemd/env behavior, and package inclusion of fleet assets.
  • Update fleet canary/release docs with preflight expectations.
  • Verify locally, run Codex review/security review, push PR, wait CI, merge, then run mosaic update and retest from the installed CLI.

Evidence from dogfood:

  • deterministic orchestrator/coder/reviewer flow completed on tmux socket mosaic-factory.
  • default tmux server remained untouched.
  • operator-origin trigger was mislabeled because source auto-detection queried the named socket outside an agent pane.
Fleet has passed local deterministic dogfood, but before official release we need a focused hardening pass. Scope: - Fix operator-origin source-label correctness for mosaic agent send outside tmux. - Preserve inter-agent preamble behavior and named-socket isolation. - Strengthen regression tests around send source labels, fleet verify/status semantics, install-systemd/env behavior, and package inclusion of fleet assets. - Update fleet canary/release docs with preflight expectations. - Verify locally, run Codex review/security review, push PR, wait CI, merge, then run mosaic update and retest from the installed CLI. Evidence from dogfood: - deterministic orchestrator/coder/reviewer flow completed on tmux socket mosaic-factory. - default tmux server remained untouched. - operator-origin trigger was mislabeled because source auto-detection queried the named socket outside an agent pane.
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#564
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?