The `mosaic gateway install` command had three UX problems:
1. Admin API token was silently saved to meta.json and never shown to
the user — no way to retrieve it without reading the file.
2. If install crashed mid-way (e.g. daemon health-check failure), the
next run prompted "Reinstall? [y/N]" and aborted on N, leaving a
half-configured install with no resume path.
3. Health-check failures only pointed at `mosaic gateway logs` — user
had to run a separate command to see the actual error.
Changes:
- **Prominent admin token banner** printed immediately after bootstrap
creates the first admin user. Clear "save now, won't be shown again"
warning.
- **Resumable install state machine.** Detects partial installs from
meta.json + .env + mosaic.config.json + daemon state, and picks up
where a prior attempt stopped instead of prompting. Fully set up
installs now offer "re-run config wizard" with explicit warnings
about what it does (regenerates .env, clears admin token, may change
backend storage).
- **Inline log tail on health failure.** Last 30 non-empty lines of
gateway.log printed automatically when the daemon fails to become
healthy, so the user sees the underlying error without running a
second command.
- **Corrupt-state detection.** If exactly one of .env / mosaic.config.json
exists (from an interrupted prior install), refuses to guess and
directs the user to `mosaic gateway uninstall`.
- **BETTER_AUTH_SECRET preservation** across config regeneration so
existing Better Auth sessions aren't silently invalidated.
- **Admin token dropped on any config regeneration** (the wizard may
point at a different backend; the old token is unverifiable).
- **Daemon stopped before config rewrite** so the live process never
serves stale config.
- Bump `@mosaic/mosaic` 0.0.19 → 0.0.20.
Known follow-ups (noted in review):
- `--port 14242` as an explicit override cannot be distinguished from
commander's default value; requires plumbing an `explicit` flag.
- No automated test coverage for the new state branches; requires
mocking fs/readline/fetch/spawn.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@mosaic/mosaic is now the single package providing both:
- 'mosaic' binary (CLI: yolo, coord, prdy, tui, gateway, etc.)
- 'mosaic-wizard' binary (installation wizard)
Changes:
- Move packages/cli/src/* into packages/mosaic/src/
- Convert dynamic @mosaic/mosaic imports to static relative imports
- Add CLI deps (ink, react, socket.io-client, @mosaic/config) to mosaic
- Add jsx: react-jsx to mosaic's tsconfig
- Exclude packages/cli from workspace (pnpm-workspace.yaml)
- Update install.sh to install @mosaic/mosaic instead of @mosaic/cli
- Bump version to 0.0.17
This eliminates the circular dependency between @mosaic/cli and
@mosaic/mosaic that was blocking the build graph.
Two bugs causing 'EACCES: permission denied, copyfile' when source
and target are the same path (e.g. wizard with sourceDir == mosaicHome):
1. No same-path guard — syncDirectory tried to copy every file onto
itself; git pack files are read-only (0444) so copyFileSync fails.
2. excludeGit only matched top-level .git — nested .git dirs like
sources/agent-skills/.git were copied, hitting the same permission
issue.
Fixes:
- Early return when resolve(source) === resolve(target)
- Match .git dirs at any depth via dirName and relPath checks
- Skip files inside .git/ paths
Added file-ops.test.ts with 4 tests covering all cases.
Publish pipeline:
- Add publish-npm step to .woodpecker/publish.yml — publishes all
@mosaic/* packages to Gitea npm registry on main push/tag
- Requires gitea_npm_token Woodpecker secret (package:write scope)
- publish-npm runs after build, parallel with Docker image builds
- pnpm publish resolves workspace:* to concrete versions automatically
Package configuration:
- All 20 packages versioned at 0.0.1-alpha.1
- publishConfig added to all packages (Gitea registry, public access)
- files field added to all packages (ship only dist/)
- @mosaic/forge includes pipeline/ assets in published package
Meta package (@mosaic/mosaic):
- Now depends on @mosaic/forge, @mosaic/macp, @mosaic/prdy,
@mosaic/quality-rails, @mosaic/types
- npm install @mosaic/mosaic pulls in the standalone framework
Build fixes:
- Fix forge and macp tsconfig rootDir: '.' -> 'src' so dist/index.js
resolves correctly (was dist/src/index.js)
- Exclude __tests__ and vitest.config from build includes
- Clean stale build artifacts from old rootDir config
Required Woodpecker secret:
woodpecker secret add mosaic/mosaic-stack \
--name gitea_npm_token --value '<token>' \
--event push,manual,tag
