fix: revert mosaic to 0.0.22 alpha + republish macp (#421)

docs/MISSION-MANIFEST.md

@@ -12,7 +12,7 @@
 **Progress:** 8 / 8 milestones
 **Status:** completed
 **Last Updated:** 2026-04-05
-**Release:** [`mosaic-v0.1.0`](https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.1.0) (`@mosaicstack/mosaic@0.1.0`)
+**Release:** [`mosaic-v0.0.22`](https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.0.22) (`@mosaicstack/mosaic@0.0.22`, alpha — stays in 0.0.x until GA)
 
 ## Success Criteria
 

docs/scratchpads/cli-unification-20260404.md

@@ -199,9 +199,26 @@ Parallel-dispatched in isolated worktrees. All merged:
 - Git tag: `mosaic-v0.1.0` (scoped to avoid collision with existing `v0.1.0` repo tag) — pushed to origin on merge sha.
 - Gitea release: https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.1.0 — "@mosaicstack/mosaic v0.1.0 — CLI Unification".
 
+### Wave 6 — M8 correction (version regression)
+
+PR #419 bumped `@mosaicstack/mosaic` 0.0.21 → 0.1.0 and released as `mosaic-v0.1.0`. This was wrong on two counts:
+
+1. **Versioning policy violation.** The project stays in `0.0.x` alpha until GA. Minor bump to `0.1.0` jumped out of alpha without authorization.
+2. **macp exports fix never reached the registry.** PR #415 fixed `packages/macp/package.json` `exports.default` pointing at `./src/index.ts`, but did NOT bump macp's version. When the post-merge publish workflow ran on #419, it published `@mosaicstack/mosaic@0.1.0` but `@mosaicstack/macp@0.0.2` was "already published" so the fix was silently skipped. Result: users running `mosaic update` got mosaic 0.1.0 which depends on macp and resolves to the still-broken registry copy of macp@0.0.2, failing with `ERR_MODULE_NOT_FOUND` on `./src/index.ts` at CLI startup.
+
+Correction PR:
+
+- `@mosaicstack/mosaic` 0.1.0 → `0.0.22` (stay in alpha)
+- `@mosaicstack/macp` 0.0.2 → `0.0.3` (force republish with the exports fix)
+- Delete Gitea tag `mosaic-v0.1.0` + release
+- Delete `@mosaicstack/mosaic@0.1.0` from the Gitea npm registry so `latest` reverts to the highest remaining version
+- Create tag `mosaic-v0.0.22` + Gitea release
+
+**Lesson captured:** every package whose _source_ changes must also have its _version_ bumped, because the publish workflow silently skips "already published" versions. `@mosaicstack/macp@0.0.2` had the bad exports in the registry from day one; the in-repo fix in #415 was invisible to installed-from-registry consumers until the version bumped.
+
 ### Mission outcome
 
-All 8 milestones, all 8 success criteria, merged to main, green CI on every PR, released. Two sessions total (~10h combined). No rollbacks, no blocked milestones, no escalations required.
+All 8 milestones, all 8 success criteria met in-repo. Released as `mosaic-v0.0.22` (alpha) after correcting an incorrect 0.1.0 version bump + missed macp republish. Two sessions total (~10h combined) plus a follow-up correction PR.
 
 ## Verification Evidence
 

packages/macp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/macp",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",

packages/mosaic/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/mosaic",
-  "version": "0.1.0",
+  "version": "0.0.22",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",