plastic-releasing

# Releasing Merge, bump, tag, push. Annotated tags with changelogs. Semantic versioning. Project configuration drives the workflow - no hardcoded assumptions. ## Checklist - [ ] Read project config - [ ] All tests pass (or verification skipped per config) - [ ] Merge feature branch to main - [ ] Bump version in configured version files - [ ] Stable-cut guard passes (version files agree, no pre-release suffix; stable/latest cuts only) - [ ] Commit version bump - [ ] Create annotated tag - [ ] Push to remote with tags - [ ] Run post-push actions (GitHub release, npm publish, etc.) - [ ] Verify release sync (npm dist-tag, GitHub "Latest", git tag all show the new version) - [ ] Clean up the intent's worktrees (merge-then-remove) - [ ] Complete active intent ## Workflow ### 0. Read Project Config Before anything else, determine which project we are releasing and load its config. 1. Read `~/.plastic/projects.yml` - find the project whose `path` matches the current working directory. 2. Extract the project slug (the key under `projects:`). 3. Read `~/.plastic/projects/{slug}/project.yml` - this contains the `release:` section. Expected `release:` keys in project.yml: ```yaml release: verify: "bin/rails test" # command to run before release version_file: package.json # single file containing the version version_files: # multiple files (overrides version_file) - package.json # list EVERY file carry...