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

chore(release): @mosaicstack/mosaic 0.0.48 #670

Merged
jason.woltje merged 1 commits from release/mosaic-0.0.48 into main 2026-06-24 20:01:18 +00:00
Conversation 1 Commits 1 Files Changed 1 +1 -1
jason.woltje commented 2026-06-24 19:50:52 +00:00
Owner
Copy Link

Release: @mosaicstack/mosaic 0.0.48

Single-field version bump (0.0.47 → 0.0.48) in packages/mosaic/package.json to publish the framework fixes already merged to main since the 0.0.47 release (#668).

What this release ships

  • #669 fix(fleet): export MOSAIC_AGENT_CLASS into the agent pane so the per-agent persona contract injects on relaunch. Root cause was the A3a env-propagation gap — the tmux pane inherited the tmux server global env, never the systemd .env, so MOSAIC_AGENT_CLASS silently dropped and personas no-op'd. Ships the corrected packages/mosaic/framework/tools/fleet/start-agent-session.sh (package ships framework/, so the script reaches the registry).
  • #665 feat(fleet): provision roster from system-type profile (H3).

Scope / coherence

  • mosaic-only bump. @mosaicstack/db stays 0.0.4 — zero db source changes on main since the #668 republish (a9857c5), so no skew risk (pre-flight confirmed by mos-claude-1).
  • npm-only release: the kaniko image builds are excluded for packages/mosaic/**-only changes (.woodpecker/publish.yml), so no platform-image rebuild.
  • publish-npm tolerates "version already published," so only @mosaicstack/mosaic@0.0.48 actually publishes; other packages no-op.

Post-merge plan

mosaic update → mosaic fleet install to converge the running fleet off the live local hotfix onto the durable, registry-shipped script. mos-claude-1 then re-runs the external two-gate persona check on the clean install to prove the durable #669 path produces correct personas end-to-end.

🤖 Generated with Claude Code

## Release: @mosaicstack/mosaic 0.0.48 Single-field version bump (`0.0.47` → `0.0.48`) in `packages/mosaic/package.json` to publish the framework fixes already merged to main since the 0.0.47 release (#668). ### What this release ships - **#669** `fix(fleet)`: export `MOSAIC_AGENT_CLASS` into the agent pane so the per-agent persona contract injects on relaunch. Root cause was the A3a env-propagation gap — the tmux pane inherited the tmux **server** global env, never the systemd `.env`, so `MOSAIC_AGENT_CLASS` silently dropped and personas no-op'd. Ships the corrected `packages/mosaic/framework/tools/fleet/start-agent-session.sh` (package ships `framework/`, so the script reaches the registry). - **#665** `feat(fleet)`: provision roster from system-type profile (H3). ### Scope / coherence - **mosaic-only** bump. `@mosaicstack/db` stays `0.0.4` — zero db source changes on main since the #668 republish (a9857c5), so no skew risk (pre-flight confirmed by mos-claude-1). - **npm-only** release: the kaniko image builds are excluded for `packages/mosaic/**`-only changes (`.woodpecker/publish.yml`), so no platform-image rebuild. - `publish-npm` tolerates "version already published," so only `@mosaicstack/mosaic@0.0.48` actually publishes; other packages no-op. ### Post-merge plan `mosaic update` → `mosaic fleet install` to converge the running fleet off the live local hotfix onto the durable, registry-shipped script. mos-claude-1 then re-runs the external two-gate persona check on the clean install to prove the durable #669 path produces correct personas end-to-end. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
jason.woltje added 1 commit 2026-06-24 19:50:53 +00:00
chore(release): @mosaicstack/mosaic 0.0.48
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
Details
ci/woodpecker/push/ci Pipeline was successful
Details
c80d21142e 
Publish the accumulated framework fixes that landed on main since 0.0.47:

- #669 fix(fleet): export MOSAIC_AGENT_CLASS into the agent pane so the
  per-agent persona contract injects on relaunch (the A3a env-propagation
  gap — pane inherited the tmux server env, never the systemd .env, so
  MOSAIC_AGENT_CLASS silently dropped and personas no-op'd). Ships the
  corrected packages/mosaic/framework/tools/fleet/start-agent-session.sh.
- #665 feat(fleet): provision roster from system-type profile (H3).

Version-only bump; npm-only release (kaniko image builds are excluded for
packages/mosaic/** changes). Publishing 0.0.48 lets `mosaic update` +
`mosaic fleet install` converge the running fleet off the live local hotfix
onto the durable, registry-shipped script.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jason.woltje commented 2026-06-24 19:51:36 +00:00
Author
Owner
Copy Link

Independent review-of-record — mos-claude-1 (two-perspective) — APPROVE

Reviewed PR head c80d211 vs origin/main. Matches my pre-flight db-coherence check exactly:

  • Single-field bump: packages/mosaic/package.json version 0.0.47 → 0.0.48. 1 file, +1/-1. git diff is that one line.
  • db untouched: stays 0.0.4. Confirmed independently that the latest packages/db change on main is a9857c5 (the #668 db 0.0.4 republish itself) — zero db source changes since publish, so a mosaic-only bump is coherent with no risk of a #668-style publish skew.
  • No stray changes. Branch is off fresh main, so it inherently ships the merged-but-unpublished delta: #669 (persona class→pane export — the corrected framework/.../start-agent-session.sh) + #665 (H3 provision).
  • mergeable=true, no conflict.

Verdict: APPROVE. Merge on green PR pipeline → publish (npm-only; kaniko excluded for packages/mosaic/** per publish.yml) → mosaic update → mosaic fleet install. I'll then run the external two-gate persona check on the clean install as the end-to-end proof the #669 fix survives a real update.

## Independent review-of-record — mos-claude-1 (two-perspective) — APPROVE Reviewed PR head `c80d211` vs `origin/main`. Matches my pre-flight db-coherence check exactly: - **Single-field bump:** `packages/mosaic/package.json` `version` `0.0.47` → `0.0.48`. 1 file, +1/-1. `git diff` is that one line. - **db untouched:** stays `0.0.4`. Confirmed independently that the latest `packages/db` change on main is `a9857c5` (the #668 db 0.0.4 republish itself) — zero db source changes since publish, so a mosaic-only bump is coherent with no risk of a #668-style publish skew. - **No stray changes.** Branch is off fresh main, so it inherently ships the merged-but-unpublished delta: #669 (persona class→pane export — the corrected `framework/.../start-agent-session.sh`) + #665 (H3 provision). - `mergeable=true`, no conflict. **Verdict: APPROVE.** Merge on green PR pipeline → publish (npm-only; kaniko excluded for `packages/mosaic/**` per publish.yml) → `mosaic update` → `mosaic fleet install`. I'll then run the external two-gate persona check on the clean install as the end-to-end proof the #669 fix survives a real update.
jason.woltje merged commit e0e7be70f5 into main 2026-06-24 20:01:18 +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#670
Delete Branch "release/mosaic-0.0.48"

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?