docs: Track CLAUDE.md so the release workflow stays discoverable

CLAUDE.md was previously gitignored as a per-machine scratch file, but
the release instructions inside it are now the single source of truth
for how to ship a new version (\`bump Info.plist → tag → push\`, CI does
the rest). Without it in the repo a fresh clone or a different machine
loses that knowledge, and the next maintainer is back to manually
running \`make dist\` and \`gh release create\`.

Author: cuiko

.gitignore

@@ -6,4 +6,3 @@ Package.resolved
 .DS_Store
 *.o
 *.swp
-CLAUDE.md

CLAUDE.md

@@ -0,0 +1,31 @@
+# TermIMS
+
+A macOS menu bar app. Swift Package Manager layout, no Xcode project.
+
+```
+Sources/TermIMS/*.swift   # one file per logical class / concern
+Scripts/package-app.sh    # wraps the SPM binary into TermIMS.app
+Resources/AppIcon.png     # source for the generated AppIcon.icns
+Info.plist                # bundle metadata, copied into the .app
+Package.swift             # SPM manifest (executable target)
+Makefile                  # thin shell over package-app.sh + DMG packaging
+```
+
+Build/install/run/dist all go through `make` (which calls `swift build -c release` under the hood). Adding a new file just means dropping a `.swift` into `Sources/TermIMS/` — SPM picks it up automatically.
+
+## Release
+
+When the user asks to publish a release, follow these steps:
+
+1. **Update version** in `Info.plist` — bump both `CFBundleVersion` and `CFBundleShortVersionString` (use x.y.z format).
+2. **Commit, tag, push** — version bump should be its own commit:
+   ```sh
+   git add Info.plist
+   git commit -m "chore: Bump version to x.y.z"
+   git tag vx.y.z
+   git push origin main --tags
+   ```
+
+That's it. The `release` workflow at `.github/workflows/release.yml` picks up the `v*` tag, builds `dist/TermIMS.dmg` on a macOS runner via `make dist`, and creates a GitHub Release with auto-generated notes (from PRs merged since the previous tag). No local `make dist` / `gh release create` needed.
+
+Ask the user for the version number if not provided. Release notes are derived automatically — only ask if they want to customise.