- PrdService owns create/read/update/link/import/export; wizard and package
CLI become prompt layers over the service (no second writer path)
- PRD documents gain a content version and a missions linkage array persisted
in the YAML authority store (survives restart); linkage writes do not bump
the content version
- exportMarkdown renders a labeled generated view (id + version + do-not-edit
header) that no code path reads back; the store loads .yaml/.yml only
- importDocument validates structure with zod before anything else, persists
valid imports as draft (validity is not approval), and refuses conflicts
with a typed PrdImportConflictError carrying a proposed successor; the
original document stays byte-identical until acceptSuccessor
- raw store writers (createPrd/savePrd) are no longer exported from the
package entry point
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
fargo
jason.woltje
jarvis