# 0.10.1 Quality Gates

Status: Current
Audience: release managers

Before publishing, the release candidate must pass the same gates locally and in CI.

```bash
bun run typecheck
bun run lint
bun run check:public-api
bun run check:target-boundaries
bun run check:docs-drift
bun run test:packages
bun run test:smoke
bun run test:edge:build
bun run perf:baseline:check
bun run perf:ci
bun run check:publish
```

## Required Review Points

- Quickstart commands use `create`, not `init`, for new projects.
- Official docs use `http://localhost:3333` for the default Mandu dev server.
- CLI `generate` supports dry-run and diff preview for safe scaffolding.
- MCP tool responses include `_meta.ok` and `_meta.nextAction`.
- Agent verify reports changed-file reasons and flags internal API edits.
- Transaction commit/rollback requires the active MCP lock when one exists.
- Performance artifacts are retained under `.perf/latest/`, and `perf:ci` enforces budget failures while annotating >10% baseline regressions.
- Workers edge smoke emits `.mandu/workers/worker.js` without target-unsafe optional dependency strings.

## Publish Boundary

Do not publish if any package test, smoke test, edge build smoke, docs drift check, public API check, target-boundary check, performance budget gate, or release checklist fails.
