Memory, queue, and storage registry copies at 0.0.3 are stale — they
were built and published before M5 added registerMemoryCommand,
registerQueueCommand, and registerStorageCommand to their src/index.ts.
Because the source changed in M5 without a version bump, the publish
workflow's "already published, skipping" tolerance silently left the
old 0.0.3 tarballs in place.
This is the same systemic bug that affected macp (fixed in PR #421) and
brain/forge/log (fixed in PR #422): whenever a package's source changes
in a PR, its version must also be bumped, or the publish workflow will
not propagate the change.
- @mosaicstack/memory 0.0.3 -> 0.0.4
- @mosaicstack/queue 0.0.3 -> 0.0.4
- @mosaicstack/storage 0.0.3 -> 0.0.4
- @mosaicstack/mosaic 0.0.23 -> 0.0.24 (deps changed)
After publish, 'npm i -g @mosaicstack/mosaic@latest && mosaic --help'
must exit 0 and print the alphabetized command list.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
