release

# Release Perform a full release for version $ARGUMENTS. ## 1. Pre-flight - Run `git status`. Working directory must show no changes and stay on `main`. - Run `git log --oneline -3`. Confirm the tip commit matches what you want tagged. - Check version format: must match `vMAJOR.MINOR.PATCH` - Get the previous version tag for use in step 4: `git tag --sort=-version:refname | grep "^v" | head -1` <!-- vale Google.Headings = NO --> ## 2. Update CHANGELOG.md Read CHANGELOG.md and make these edits: 1. Replace `## [Unreleased]` with `## [$ARGUMENTS_NO_V] - YYYY-MM-DD`, using today's date. The heading uses the version without the leading `v` to match the existing convention and to match the link reference added in step 3 (rumdl will report `MD053 Unused link/image reference` if the two get out of sync). 2. Insert a new empty `## [Unreleased]` section before it 3. Add a comparison link at the bottom of the file, before the current top link: `[$ARGUMENTS_NO_V]: https://github.com/tbhb/vale-ai-tells/compare/PREV_TAG...$ARGUMENTS` where PREV_TAG refers to the tag found in step 1 and ARGUMENTS_NO_V strips the leading `v` **Writing CHANGELOG entries**: `Metacommentary` uses `scope: raw`, which bypasses `<!-- vale off -->` inline suppression. Don't quote literal trigger phrases from that rule (the `Let's [verb]` patterns) in the CHANGELOG. Paraphrase them instead, as in v1.4.0. ## 3. Update README.md <!-- vale Google.Headings = YES --> The release workflow builds three packages ...