releaselisted

# release Wraps `bin/release.sh`. Default strategy is `conventional-changelog`: walk the commit range since the last matching tag, group commits by Conventional Commits type, prepend a CHANGELOG block, commit the changelog, then annotated-tag `v<version>`. ## 0. Drift check (quick, non-blocking) Run `bash bin/session-check.sh --flow=release`. If it produces output, surface the line to the user verbatim. Do not block the flow. ## 1. Suggest version (when not explicitly provided) When the user does **not** supply an explicit `--version`, run `bin/recommend-version.sh` to suggest one: ``` bin/recommend-version.sh --target <cwd> [--tag-prefix <p>] ``` Show the recommendation to the user: > Based on commits since `<current>`, I'd suggest **`<recommended>`** > (`<bump>` bump — `<reason>`). Shall I proceed with `<recommended>`, > or would you prefer a different version? Wait for confirmation before proceeding. The user can accept, override with a different version, or abort. When the user **does** supply an explicit version (e.g. "release v2.0.0"), skip this step entirely — don't second-guess them. When the user says "bump minor" / "bump major" / "bump patch", run `recommend-version.sh` to get the current version, then apply the requested bump type (ignore the script's own recommendation). Confirm the computed version with the user before proceeding. ## 2. Collect inputs - **`--version <x.y.z>`** — required for `release.sh`. Must be semver (or `x.y.z-prerelease`). Pop