Apply CodeRabbit formatting suggestions to documentation

Address all CodeRabbit review comments from PR #2101:
- Add language specifications to code blocks (text, bash)
- Fix heading structure (use #### instead of bold emphasis)
- Add hyphen to compound adjective "React on Rails-specific"
- Remove duplicate "Related Documentation" section in INDEX.md

Changes:
- CI_FAILURES_2024-11-21.md: Add 'text' language to 3 code blocks
- INDEX.md: Remove duplicate Related Documentation section
- pr-splitting-strategy.md: Add 'text' language to code blocks, fix heading levels
- CLAUDE.md: Add 'text' language to code block, fix hyphenation

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

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

Author: justin808

.claude/docs/analysis/CI_FAILURES_2024-11-21.md

@@ -55,7 +55,7 @@ This is a **REGRESSION** introduced by changes in this branch related to:
 
 #### Error Pattern
 
-```
+```text
 Uncaught SyntaxError: Unexpected token '<'
 ```
 
@@ -81,7 +81,7 @@ The webpack infrastructure partially works, but specific bundles aren't being ge
 
 #### Sample Failing Tests
 
-```
+```text
 Pages/Index when rendering All in one page
   with Server Rendered/Cached React/Redux Component
     ✗ is expected to have visible css "div#ReduxApp-react-component-0"
@@ -225,7 +225,7 @@ buildConsoleReplay(previouslyReplayedConsoleMessages, consoleHistory, nonce);
 
 **Files Changed**:
 
-```
+```text
 package-scripts.yml (path updates)
 packages/react-on-rails-pro-node-renderer/package.json
 packages/react-on-rails-pro/package.json

.claude/docs/analysis/INDEX.md

@@ -188,16 +188,6 @@ Outside the analysis directory:
 - 📝 Recommendations
 - ✓ Checklists and criteria
 
-## Related Documentation
-
-Outside this analysis directory:
-
-- **Main Migration Plan**: `/docs/MONOREPO_MERGER_PLAN.md` (authoritative source)
-- **Path Management Guide**: `/managing-file-paths.md` (validation procedures)
-- **Build Script Testing**: `/testing-build-scripts.md` (artifact verification)
-- **CI Monitoring**: `/master-health-monitoring.md` (CI status checks)
-- **Contributing Guide**: `/CONTRIBUTING.md` (developer instructions)
-
 ## Workflow Tips
 
 ### Before Starting Work

.claude/docs/pr-splitting-strategy.md

@@ -59,7 +59,7 @@ Look for commits that:
 
 **Example groups from PR #2069**:
 
-```
+```text
 Group 1 (Documentation & Analysis):
 - CI failure analysis documents
 - Testing requirement documentation
@@ -149,13 +149,13 @@ Group 4 (Monorepo Node Renderer):
 
 ### Step 4: Handle the Original PR
 
-**Option A: Close and Replace**
+#### Option A: Close and Replace
 
 - Close original PR with note: "Split into smaller PRs for easier review"
 - Link to all new PRs
 - Advantage: Clean history, easier to review
 
-**Option B: Rebase and Reduce**
+#### Option B: Rebase and Reduce
 
 - Remove commits that went into other PRs
 - Rebase remaining commits
@@ -344,7 +344,7 @@ ls packages/*/lib/
 
 ## Decision Tree
 
-```
+```text
 Is PR failing CI?
 ├─ YES → Continue
 └─ NO → No need to split

CLAUDE.md

@@ -603,7 +603,7 @@ end
 
 ### Test Organization
 
-```
+```text
 spec/dummy/e2e/
 ├── playwright.config.js          # Playwright configuration
 ├── playwright/
@@ -627,7 +627,7 @@ spec/dummy/e2e/
 
 - Use `app('clean')` in `beforeEach` to ensure clean state
 - Leverage Rails helpers (`appFactories`, `appEval`) instead of UI setup
-- Test React on Rails specific features: SSR, hydration, component registry
+- Test React on Rails-specific features: SSR, hydration, component registry
 - Use component IDs like `#ComponentName-react-component-0` for selectors
 - Monitor console errors during tests
 - Test across different browsers with `--project` flag