cut-release

# Cut Release Cut a new Fabrik release. Your job is to **author the release notes**; `scripts/cut-release.sh` does everything else (commit, tag, push as @arbeithand, watch workflow, verify identity, file doc-update issue). ## Usage Invoked as `/cut-release` or `/cut-release v0.0.67`. If no version is provided, suggest the next patch bump from the current latest tag. ## Steps ### 1. Determine version - Find the latest tag: `git describe --tags --abbrev=0` - If a version arg was provided, validate semver with `v` prefix and that it's greater than the latest tag. - If no version arg, suggest the next patch bump and proceed. ### 2. Author release notes This is the part requiring judgment — do not delegate it. - `git log <last-tag>..HEAD --oneline` to enumerate commits since the last release. - Group user-facing changes by category: **Features**, **Fixes**, **Improvements**, **Internal**. Omit empty sections. - Ignore merge commits and `Co-Authored-By` lines. - Collapse internal churn into a single line under **Internal**. Don't enumerate refactors / test additions. - Write the notes to `release-notes/<version>.md` (one file per release, archived in-tree). The release workflow reads this path directly via `${{ github.ref_name }}` — there is no repo-root `release-notes.md` and you should not create one (it is `.gitignore`d). Use this schema: ```markdown # Fabrik <version> ## Summary <1-3 sentences. Punchy headline themes only. This block is what the Discussions announc...