prepare-release

# Prepare Release End-to-end release workflow. Reads commits since the last release tag, infers the semver bump, drafts a user-facing changelog, confirms with you, creates a release PR, merges it, verifies CI is green, tags the release, and monitors the Docker build to completion. **Usage:** `/prepare-release` Run this from any branch after all feature PRs have been merged to `main`. --- ## Step 1 — Ensure Clean Main Switch to `main` and pull latest: ```bash git checkout main git pull origin main git status ``` If `git status` shows uncommitted changes, stop and resolve them before continuing. The working tree must be clean. --- ## Step 2 — Find Last Release Tag ```bash git describe --tags --abbrev=0 ``` Note this as `LAST_TAG` (e.g., `v2.0.2`). All commits after this tag are candidates for the release. If this command fails (no tags exist yet), use the full history — note the first commit hash as the baseline and treat the release as the initial version. --- ## Step 3 — Gather Commits Since Last Tag ```bash git log <LAST_TAG>...HEAD --oneline git diff <LAST_TAG>...HEAD --stat git diff <LAST_TAG>...HEAD --name-only ``` Collect the full output of each. Do not truncate. --- ## Step 4 — Filter and Synthesize (Critical Reasoning Step) **This is not a raw dump of commit messages.** Analyze the material and produce a curated, user-facing summary. ### 4a. Discard internal-only commits Ignore commits that match any of the following: - Subject starts with: `wip`...