Document beta changelog curation process in CLAUDE.md

Added comprehensive guidelines for curating changelog entries when consolidating beta releases:
- Clear criteria for what to remove (developer-only, beta-specific, Pro features)
- Clear criteria for what to keep (user-facing fixes, breaking changes)
- Investigation process with git commands
- Reference to PR #2072 as a complete example

This documents the complex analysis process performed during the v16.2.0.beta.11 changelog cleanup to help future developers with similar tasks.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: justin808

CLAUDE.md

@@ -214,6 +214,50 @@ When making changes, update the **appropriate changelog(s)**:
   - Pro: `cd react_on_rails_pro && bundle exec rake update_changelog`
 - **Examples**: Run `grep -A 3 "^#### " CHANGELOG.md | head -30` to see real formatting examples
 
+### Beta Release Changelog Curation
+
+When consolidating beta versions into a stable release, carefully curate entries to include only user-facing changes:
+
+**Remove these types of entries:**
+
+1. **Developer-only tooling**:
+   - yalc publish fixes (local development tool)
+   - Git dependency support (contributor workflow)
+   - CI/build script improvements
+   - Internal tooling changes
+
+2. **Beta-specific fixes**:
+   - Bugs introduced during the beta cycle (not present in last stable)
+   - Fixes for new beta-only features (e.g., bin/dev in 16.2.0.beta)
+   - Generator handling of beta/RC version formats
+
+3. **Pro-specific features** (move to Pro changelog):
+   - Node renderer fixes/improvements
+   - Streaming-related changes
+   - Async loading features (Pro-exclusive)
+
+**Keep these types of entries:**
+
+1. **User-facing fixes**:
+   - Bugs that existed in previous stable release (e.g., 16.1.x)
+   - Compatibility fixes (Rails version support, etc.)
+   - Performance improvements affecting all users
+
+2. **Breaking changes**:
+   - API changes requiring migration
+   - Removed methods/features
+   - Configuration changes
+
+**Investigation process:**
+
+For each suspicious entry:
+1. Check git history: `git log --oneline <last_stable>..<current_beta> -- <file>`
+2. Determine when bug was introduced (stable vs beta cycle)
+3. Verify whether fix applies to stable users or only beta users
+4. Check PR description for context about what was broken
+
+**Example reference:** See [PR #2072](https://github.com/shakacode/react_on_rails/pull/2072) for a complete example of beta changelog curation with detailed investigation notes.
+
 ## ⚠️ FORMATTING RULES
 
 **Prettier is the SOLE authority for formatting non-Ruby files, and RuboCop for formatting Ruby files. NEVER manually format code.**