Update CLAUDE.md with explicit release workflow and session learnings

- Added CRITICAL Release Workflow section with complete git commands
- Documented v0.3.0 release details (commit hash, tag, branches pushed)
- Added learnings about git fast-forward merge workflow

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

CLAUDE.md

@@ -128,6 +128,31 @@ for po in languages/*.po; do msgfmt -o "${po%.po}.mo" "$po"; done
 - Commit messages should follow the established format with Claude Code attribution
 - `.claude/settings.local.json` changes are typically local-only (stash before rebasing)
 
+**CRITICAL - Release Workflow:**
+
+On every new version, ALWAYS execute this complete workflow:
+
+```bash
+# 1. Commit changes to dev branch
+git add <files>
+git commit -m "Description of changes (vX.X.X)"
+
+# 2. Merge dev to main
+git checkout main
+git merge dev --no-edit
+
+# 3. Create annotated tag
+git tag -a vX.X.X -m "Version X.X.X - Brief description"
+
+# 4. Push everything to origin
+git push origin dev main vX.X.X
+
+# 5. Switch back to dev for continued development
+git checkout dev
+```
+
+Never skip any of these steps. The release is not complete until all branches and the tag are pushed to origin.
+
 #### What Gets Released
 
 - All plugin source files
@@ -468,3 +493,12 @@ Admin features always work; frontend requires valid license.
 - Calendar displays bookings color-coded by status for quick visual overview
 - HTML email templates with inline CSS for better email client compatibility
 - Status transitions can trigger different email notifications via hooks
+- **Release workflow** must always include: commit to dev → merge to main → create tag → push all to origin
+- Git fast-forward merge works well when dev is ahead of main with no conflicts
+
+**Released:**
+
+- Committed: `0c601df` on dev branch
+- Merged to main (fast-forward)
+- Tagged: `v0.3.0`
+- Pushed to origin: dev, main, v0.3.0