release-processlisted

# Release Process Run the repository release flow end-to-end with semantic tags and dated changelog sections. ## Scope This skill handles release preparation and publication for this repository. It is not for: - Editing unrelated product features. - Rewriting git history. - Skipping quality gates. ## Inputs - Target semantic tag (for example `v0.1.1`). - Release date in ISO format (`YYYY-MM-DD`). - Optional manual edits to changelog highlights before tagging. ## Outputs - Updated `CHANGELOG.md` section for the target tag. - Tag pushed to origin. - GitHub release created by workflow with notes sourced from changelog. - Verification summary with run URL and release URL. ## Workflow 1. Verify branch state and quality gates. - Confirm working tree is clean. - Confirm required checks pass locally (`pre-commit`, tests) when relevant. 1. Ensure release changes are committed first. - Commit any release workflow/tooling updates before generating changelog for the new tag. 1. Generate changelog section. - Run: - `uv run python .scripts/generate_release_changelog.py --tag vX.Y.Z --date YYYY-MM-DD` - This computes commit delta from previous semantic tag to `HEAD`. 1. Review changelog text for end-user clarity. - Keep a concise `### Highlights` section. - Keep `### Commit delta (auto-generated)` for traceability. - Ensure heading format is exact: `## vX.Y.Z - YYYY-MM-DD`. 1. Commit changelog update. - `git add CHANGELOG.md` - `git commit -m "docs(release): update chang