Two errors shipped in #419 (mosaic-v0.1.0 release):
1. Version policy violation — @mosaicstack/mosaic was bumped 0.0.21 →
0.1.0, jumping out of 0.0.x alpha without authorization. The project
stays in 0.0.x until GA. Revert to 0.0.22.
2. @mosaicstack/macp exports fix never reached the registry. PR #415
fixed packages/macp/package.json exports.default (was pointing at
./src/index.ts, broke installed consumers with ERR_MODULE_NOT_FOUND),
but did not bump macp's version. The post-merge publish workflow
silently skipped macp@0.0.2 as "already published", leaving the bad
copy on the registry. Installing mosaic@0.1.0 resolves macp@0.0.2
from the registry and crashes on startup. Bump macp 0.0.2 → 0.0.3 to
force republish with the correct exports map.
Follow-up cleanup after merge:
- delete git tag mosaic-v0.1.0 + Gitea release
- delete @mosaicstack/mosaic@0.1.0 from Gitea npm registry so `latest`
reverts to the highest remaining version
- create new tag mosaic-v0.0.22 + Gitea release
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Persistent document tracking full mission scope, status, and session history.
Updated by the orchestrator at each phase transition and milestone completion.
Mission
ID: cli-unification-20260404
Statement: Transform the Mosaic CLI from a partially-duplicated, manually-assembled experience into a single cohesive entry point that installs, configures, and controls the entire Mosaic system. Every Mosaic package gets first-class CLI surface. The first-run experience works end-to-end with no manual stitching. Gateway token recovery is possible without the web UI. Opt-in telemetry uses the published telemetry clients.
Phase: Complete
Current Milestone: —
Progress: 8 / 8 milestones
Status: completed
Last Updated: 2026-04-05
Release:mosaic-v0.0.22 (@mosaicstack/mosaic@0.0.22, alpha — stays in 0.0.x until GA)
Success Criteria
AC-1: Fresh machine bash <(curl …install.sh) → single command lands on a working authenticated gateway with a usable admin token; no secondary manual wizards required
AC-2: mosaic --help lists every sub-package as a top-level command and is alphabetized for readability
AC-3: mosaic auth, mosaic brain, mosaic forge, mosaic log, mosaic macp, mosaic memory, mosaic queue, mosaic storage, mosaic telemetry each expose at least one working subcommand that exercises the underlying package
AC-4: Gateway admin token can be rotated or recovered from the CLI alone — operator is never stranded because the web UI is inaccessible
AC-5: mosaic telemetry uses the published @mosaicstack/telemetry-client-js (from the Gitea npm registry); local OTEL stays for wide-event logging / post-mortems; remote upload is opt-in and disabled by default
AC-6: Install → wizard → gateway install → TUI verification flow is a single cohesive path with clear state transitions and no dead ends
AC-7: @mosaicstack/mosaic is the sole mosaic binary owner; @mosaicstack/cli is gone from the repo and all docs
AC-8: All milestones ship as merged PRs with green CI, closed issues, and updated release notes
Milestones
#
ID
Name
Status
Branch
Issue
Started
Completed
1
cu-m01
Kill legacy @mosaicstack/cli package
done
chore/remove-cli-package-duplicate
#398
2026-04-04
2026-04-04
2
cu-m02
Archive stale mission state + scaffold new mission
Shared Contracts:docs/PRD.md (existing v0.1.0 PRD — still the long-term target), this manifest, docs/TASKS.md, docs/scratchpads/cli-unification-20260404.md
Token Budget
Metric
Value
Budget
TBD
Used
~80K
Mode
normal
Session History
Session
Runtime
Started
Duration
Ended Reason
Last Task
1
claude-opus-4-6
2026-04-04
~4h
context-budget
cu-m01 + cu-m02 merged (#398, #399); open questions resolved