release

# Release SemVer-aware release readiness/communication. Prepares release evidence/docs; never tag, publish, upload, or force-push. ## Input Schema ```json { "mode": "notes|prepare|audit|demo", "range": "optional git range, tag pair, or target version", "target_version": "optional SemVer version", "done_when": "release blockers, warnings, and required artifacts are explicit" } ``` ## Workflow ### 01: Create run directory Run `python PLUGIN_ROOT/shared/create_run.py --skill release` once. Retain its single printed path as `<run-directory>` and substitute that literal path into every later artifact path and helper argument. Never store or reuse the path through a shell variable; shell variables do not persist across tool calls. ### 02: Determine mode, range, and target version - `notes`: draft release notes from git range. - `prepare`: audit plus notes/changelog/migration-artifact checks. - `audit`: readiness verdict only. - `demo`: optional release-demo planning artifact; never required for non-feature releases. Unknown mode/ambiguous range => fail before release docs. ### 03: Collect release evidence Use the supplied `range`; when absent, run `git describe --tags --abbrev=0` as argv and form `<printed-tag>..HEAD`. Retain that literal release range in workflow state, run `git log --oneline <release-range>` as argv, and write stdout to `<run-directory>/commits.txt`. Record range or log collection failure instead of treating empty output as success. Inspect `p...