Open issue deep dive: wave 3 long-tail plan (#2812)

- Add Wave 3 execution plan for 19 long-tail backlog issues that had no
open PR at snapshot time.
- Stacked on top of #2811 to preserve mergeable review slices.

- Not run (documentation/analysis only).

- Refs #2527
- Refs #2524
- Refs #1999
- Refs #1985
- Refs #1959
- Refs #1958
- Refs #1949
- Refs #1929
- Refs #1862
- Refs #1828
- Refs #1746
- Refs #1692
- Refs #1658
- Refs #1627
- Refs #1590
- Refs #1583
- Refs #1468
- Refs #1465
- Refs #1196

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk because it only adds an analysis/markdown planning document
and does not change runtime, build, or CI behavior.
>
> **Overview**
> Adds `analysis/open-issue-deep-dive/wave-3-long-tail.md`, documenting
the Wave 3 execution plan for **19 long-tail issues** from the
2026-03-22 triage snapshot.
>
> The doc includes a domain breakdown, notes on issues resolved as
duplicates after the snapshot, and per-issue triage context plus the
*exact* follow-up question posted to each issue.
>
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
75c95ed. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

* **Documentation**
* Added Wave 3 Long-Tail Issues report documenting open issues without
active pull requests, including domain analysis, issue metadata, labels,
creation dates, and triage context.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Author: justin808

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