shiplisted

# Ship Release a working increment. Stack-agnostic — derive deploy commands from `docs/agents/dev-environment.md`, CI config, or official docs. ## Process 1. **Pre-flight** - Review must pass before merge — this is a precondition, not a recommendation. Run or confirm `/ai:review` passed with no open blockers and no security findings ≥ high. Human review of the diff is required even when the project has only one human contributor (see ai-kit issue #52 for the 2-dev-default rationale). - CI green on the release branch (`gh run list`, GitHub Actions, GitLab CI, etc.) - All related issues linked to the PR/release - Commit messages + PR title follow [git-hygiene rule](../../../standards/rules/git-hygiene.mini.md) (conventional commits, scoped, imperative); PR body uses the project's `.github/pull_request_template.md` if present 2. **Release notes** - Summarise changes from commits or PR description - List breaking changes and migration steps if any 3. **Deploy** - Use the project's deploy path: CI pipeline, `Makefile`, README, or official hosting docs - Do not assume a specific platform — read `docs/agents/dev-environment.md` first - If deploy is manual, give exact commands and wait for user confirmation before running destructive steps 4. **Post-deploy** - Run `qa` quick tier against staging/production URL if applicable - Verify critical paths manually if no E2E exists 5. **Done** - Close release issues - Tag or ch