docs: add release workflow and document naming/gh CLI flags

Author: tw93

.agents/workflows/release.md

@@ -0,0 +1,53 @@
+---
+description: Create a new Mole release and update versions
+---
+
+# Mole Release Workflow
+
+Follow these steps when you are ready to publish a new release of Mole.
+
+1. **Update the version number** in the main executable:
+   // turbo
+
+   ```bash
+   # Replace the version number below with the target version (e.g., 1.30.0)
+   # sed -i '' 's/VERSION=".*"/VERSION="1.30.0"/' mole
+   ```
+
+2. **Generate Release Notes**:
+   Review the commits since the last release, categorize the changes (Bug Fixes, Features, Refactoring), and format them into both English and Chinese changelogs following the structure in previous releases. Save this exactly to `/tmp/release_notes.md`.
+
+3. **Commit the changes**:
+   // turbo
+
+   ```bash
+   git add mole
+   # For example: git commit -m "chore: Bump version to 1.30.0"
+   ```
+
+4. **Tag the release**:
+   // turbo
+
+   ```bash
+   # For example: git tag V1.30.0
+   ```
+
+5. **Push commits and tags to remote**:
+   // turbo
+
+   ```bash
+   git push origin main
+   git push origin --tags
+   ```
+
+6. **Create the GitHub Release**:
+   Use `gh release create` directly so GitHub does not auto-append generic commit/contributor logs. **Important:** Specify `-R tw93/Mole` to avoid the "No default remote repository" error.
+   The release title should be named after characters from either *Stranger Things* (e.g., Mike Wheeler) or *Bakemonogatari*, accompanied by a relevant emoji.
+   // turbo
+
+   ```bash
+   # For example (no auto-generated logs added when using -F):
+   # gh release create V1.30.0 -R tw93/Mole -F /tmp/release_notes.md -t "V1.30.0 Mike Wheeler 🚲"
+   ```
+
+*(Note: Adjust the commands manually for the specific version number during the actual release)*