Format open-issue deep-dive analysis markdown files

Author: justin808

analysis/open-issue-deep-dive/README.md

@@ -11,6 +11,7 @@
 - Triage comments posted at snapshot time: 85/85
 
 ## Existing Open PR Coverage
+
 - #2802 RSC migration docs: fix fictional API names, missing associations, form_with, and CSRF token patterns -> #2803
 - #2794 Track B: add react_on_rails:sync_versions for gem/npm lockstep -> #2797
 - #2781 Docs: Add missing content pages (RSC landing, ExecJS, debugging, benchmarks) -> #2785
@@ -32,6 +33,7 @@
 
 - Context excerpts in wave files are intentionally truncated with `...`.
 - `Triage note` captures inferred scope, blocker history, pending verification, and other non-quoted analyst context.
+
 ## Execution Notes
 
 - Every issue received a triage comment with domain, current PR coverage, and a concrete next-step question.

analysis/open-issue-deep-dive/wave-1-active.md

@@ -7,7 +7,7 @@ Generated from open-issue triage snapshot dated 2026-03-22.
 - Domain: documentation
 - Labels: (none)
 - Created: 2026-03-22
-- Context excerpt: ## Context In `.claude/commands/update-changelog.md`, the Version Stamping section header (line 153) reads: > When this command is invoked with `release`, `rc`, or `beta`, **use the rake task to stamp the version header* ...
+- Context excerpt: ## Context In `.claude/commands/update-changelog.md`, the Version Stamping section header (line 153) reads: > When this command is invoked with `release`, `rc`, or `beta`, \*_use the rake task to stamp the version header_ ...
 - Posted question: Should this be batched with related docs issues in a single docs PR, or handled separately?
 
 ## #2805 Improve /address-review with merge-ready quick actions and follow-up issue workflow
@@ -79,7 +79,7 @@ Generated from open-issue triage snapshot dated 2026-03-22.
 - Domain: documentation
 - Labels: (none)
 - Created: 2026-03-20
-- Context excerpt: ## Summary Several docs pages have fenced code blocks without language identifiers (e.g., bare ``` instead of ```ruby or ```bash). This prevents syntax highlighting on reactonrails.com and anywhere else the docs are rend ...
+- Context excerpt: ## Summary Several docs pages have fenced code blocks without language identifiers (e.g., bare `instead of`ruby or ```bash). This prevents syntax highlighting on reactonrails.com and anywhere else the docs are rend ...
 - Posted question: Should this be batched with related docs issues in a single docs PR, or handled separately?
 
 ## #2771 Doctor: migrate from regex config parsing to runtime config queries

analysis/open-issue-deep-dive/wave-2-backlog.md

@@ -29,7 +29,7 @@ Field note: Most `ci/tooling` entries intentionally share the same routing quest
 - Context excerpt: ## Summary After reviewing [everything-claude-code](https://github.com/affaan-m/everything-claude-code) (50K+ stars, Anthropic hackathon winner), several patterns would enhance our already solid Claude Code setup. ## Cur ...
 - Posted question: Is this still active for implementation, or should it remain a discussion-only backlog item?
 
-## #2552 RFC: Rename bundler-agnostic config files from *WebpackConfig.js to bundler-neutral names
+## #2552 RFC: Rename bundler-agnostic config files from \*WebpackConfig.js to bundler-neutral names
 
 - Domain: discussion/rfc
 - Labels: enhancement, P3
@@ -58,7 +58,7 @@ Field note: Most `ci/tooling` entries intentionally share the same routing quest
 - Domain: ci/tooling
 - Labels: P3
 - Created: 2025-12-15
-- Context excerpt: Currently our CI caches gems manually, but https://github.com/ruby/setup-ruby/?tab=readme-ov-file#caching-bundle-install-manually says > It is also possible to cache gems manually, **but this is not recommended because i ...
+- Context excerpt: Currently our CI caches gems manually, but https://github.com/ruby/setup-ruby/?tab=readme-ov-file#caching-bundle-install-manually says > It is also possible to cache gems manually, \*\*but this is not recommended because i ...
 - Posted question: Should this run in the CI/tooling maintenance wave, or be deferred behind release-critical runtime work?
 
 ## #2214 Finish merging linting between Core and Pro
@@ -162,5 +162,5 @@ Field note: Most `ci/tooling` entries intentionally share the same routing quest
 - Domain: ci/tooling
 - Labels: enhancement, low priority, P3
 - Created: 2025-11-12
-- Context excerpt: ## Problem The `run-skipped-ci.yml` workflow uses a fixed 5-second wait before verifying that workflows are queued: ```javascript await new Promise(resolve => setTimeout(resolve, 5000)); ``` This approach has several iss ...
+- Context excerpt: ## Problem The `run-skipped-ci.yml` workflow uses a fixed 5-second wait before verifying that workflows are queued: `javascript await new Promise(resolve => setTimeout(resolve, 5000)); ` This approach has several iss ...
 - Posted question: Should this run in the CI/tooling maintenance wave, or be deferred behind release-critical runtime work?

analysis/open-issue-deep-dive/wave-3-long-tail.md

@@ -6,13 +6,13 @@ Field note: `Posted question` is the exact question posted to each issue during
 
 ## Domain Breakdown (19 Issues)
 
-| Domain               | Count |
-| -------------------- | ----- |
-| core/runtime         | 9     |
-| ci/tooling           | 4     |
-| documentation        | 4     |
-| discussion/rfc       | 1     |
-| pro/rsc integration  | 1     |
+| Domain              | Count |
+| ------------------- | ----- |
+| core/runtime        | 9     |
+| ci/tooling          | 4     |
+| documentation       | 4     |
+| discussion/rfc      | 1     |
+| pro/rsc integration | 1     |
 
 ## Resolved After Snapshot, Before Execution
 
@@ -48,7 +48,7 @@ Field note: `Posted question` is the exact question posted to each issue during
 - Domain: documentation
 - Labels: documentation, P3
 - Created: 2025-11-12
-- Context excerpt: ## Overview Add compelling React Server Components (RSC) migration success stories to our documentation to give readers incentive to migrate. ## Success Stories to Feature ### 1. **Mux: 50,000 Lines Migrated** - **Articl ...
+- Context excerpt: ## Overview Add compelling React Server Components (RSC) migration success stories to our documentation to give readers incentive to migrate. ## Success Stories to Feature ### 1. **Mux: 50,000 Lines Migrated** - \*\*Articl ...
 - Posted question: Should this be batched with related docs issues in a single docs PR, or handled separately?
 
 ## #1959 CI/Build improvements: prepack scripts and yalc workflow fixes
@@ -129,7 +129,7 @@ Field note: `Posted question` is the exact question posted to each issue during
 - Domain: core/runtime
 - Labels: P3
 - Created: 2024-06-08
-- Context excerpt: ```ruby ReactOnRails::PacksGenerator.instance.generate_packs_if_stale ``` Have this call create a lock file so it can't run concurrently. The lock file should expire within a short time. Here is how to do this: https://w ...
+- Context excerpt: `ruby ReactOnRails::PacksGenerator.instance.generate_packs_if_stale ` Have this call create a lock file so it can't run concurrently. The lock file should expire within a short time. Here is how to do this: https://w ...
 - Posted question: Do you want this scheduled in the next implementation wave, or parked until after active release work?
 
 ## #1590 Add support for Vite