docs: finalize CLI unification mission at mosaic-v0.0.24

- Update MISSION-MANIFEST.md release line to v0.0.24
- Append Wave 7 to scratchpad documenting the three cascaded correction
  PRs (#421, #422, #423) that all fixed the same systemic publish-skip
  bug, plus the first-ever clean end-to-end verification evidence
- Capture systemic-fix options for follow-up (registry/dist diff check
  or CI lint requiring version bumps when src/ changes)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

docs/MISSION-MANIFEST.md

@@ -12,7 +12,7 @@
 **Progress:** 8 / 8 milestones
 **Status:** completed
 **Last Updated:** 2026-04-05
-**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)
+**Release:** [`mosaic-v0.0.24`](https://git.mosaicstack.dev/mosaicstack/mosaic-stack/releases/tag/mosaic-v0.0.24) (`@mosaicstack/mosaic@0.0.24`, alpha — stays in 0.0.x until GA)
 
 ## Success Criteria
 

docs/scratchpads/cli-unification-20260404.md

@@ -216,9 +216,28 @@ Correction PR:
 
 **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.
 
+### Wave 7 — Waves 2 & 3 correction (same systemic bug)
+
+After Wave 6's correction (PR #421) landed `mosaic-v0.0.22`, a clean global install still crashed with `Named export 'registerBrainCommand' not found` — and after fixing brain/forge/log in PR #422, the next clean install crashed with `registerMemoryCommand` not found. Same root cause: M5 (PR #416) added `registerXCommand` exports to memory, queue, storage, brain, forge, log, and config but only bumped a subset of versions. The publish workflow silently skipped every unchanged-version package, leaving the M5 exports absent from the registry.
+
+Three cascaded correction PRs were required because each attempt only surfaced the next stale package at runtime:
+
+- **PR #421** — macp 0.0.2 → 0.0.3, mosaic 0.1.0 → 0.0.22, delete `mosaic-v0.1.0` tag/release/registry version
+- **PR #422** — brain/forge/log 0.0.2 → 0.0.3, mosaic 0.0.22 → 0.0.23
+- **PR #423** — memory/queue/storage 0.0.3 → 0.0.4, mosaic 0.0.23 → 0.0.24
+
+**First clean end-to-end verification** after PR #423:
+
+```
+$ npm i -g @mosaicstack/mosaic@latest   # installs 0.0.24
+$ mosaic --help                          # exits 0, prints full alphabetized command list
+```
+
+**Systemic fix (follow-up):** The publish workflow's "already published, skipping" tolerance is dangerous when source changes without version bumps. Options to prevent recurrence: (a) fail publish if any workspace package's dist files differ from registry content at the same version, or (b) CI lint check that any `packages/*/src/**` change in a PR also modifies `packages/*/package.json` version.
+
 ### Mission outcome
 
-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.
+All 8 milestones, all 8 success criteria met in-repo. Released as `mosaic-v0.0.24` (alpha) after three cascaded correction PRs (#421, #422, #423) fixing the same systemic publish-skip bug across macp, brain, forge, log, memory, queue, and storage. First version where `npm i -g @mosaicstack/mosaic@latest && mosaic --help` works end-to-end from a clean global install.
 
 ## Verification Evidence