Open issue deep dive: wave 2 backlog plan#2815
Conversation
…n-issue-deep-dive-wave-2 * jg-codex/open-issue-deep-dive-wave-1: Refine wave-1 deep-dive notes from review feedback
…n-issue-deep-dive-wave-2 * jg-codex/open-issue-deep-dive-wave-1: Tighten wave-1 scope and clarify cross-repo PR references
…n-issue-deep-dive-wave-2 * jg-codex/open-issue-deep-dive-wave-1: Clarify snapshot scope for triage-comment metric
WalkthroughThe changes update documentation about issue triage waves and introduce a new backlog snapshot. The README refines wave definitions, clarifies metrics for separate wave counts, and adds a "Format Notes" section. A new Wave 2 Backlog file documents 166 lines of issue metadata from the March 2026 triage pass, recording issues without active pull requests. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryThis PR adds three new planning/analysis documents under
Confidence Score: 5/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["85 Open Issues\n(2026-03-22 Snapshot)"] --> B["10 Already linked\nto open PRs"]
A --> C["75 Without an open PR"]
B --> B1["Existing PR Coverage\n(10 issues → listed in README)"]
C --> W1["Wave 1 Active\n34 issues\nPR #2815 / wave-1-active.md\nP1/P2, release-critical,\nnewly scoped"]
C --> W2["Wave 2 Backlog\n20 issues\nwave-2-backlog.md\nPrimarily P3"]
C --> W3["Wave 3 Long-tail\n21 issues\nStacked follow-up PR\nParked / low priority"]
W1 --> D1["Domains: docs,\ncore/runtime,\npro/rsc, ci/tooling"]
W2 --> D2["Domains: ci/tooling,\ndiscussion/rfc,\ndeveloper-experience,\ntesting"]
W3 --> D3["Future planning"]
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| Generated from open-issue triage snapshot dated 2026-03-22. | ||
|
|
There was a problem hiding this comment.
wave-2-backlog.md introduces two Field note: lines at the top that describe formatting conventions, but wave-1-active.md has no equivalent header and the README.md Format Notes section does not mention the Field note key. Consider either:
- Adding
Field notelines towave-1-active.mdfor consistency, or - Documenting
Field noteinREADME.md's Format Notes section alongsideTriage note.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
|
|
||
| - 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 |
There was a problem hiding this comment.
Missing blank line between the ## Format Notes list and ## Execution Notes heading — most Markdown renderers handle this fine, but it's inconsistent with the spacing used between other sections in this file.
| ## Execution Notes | |
| - `Triage note` captures inferred scope, blocker history, pending verification, and other non-quoted analyst context. | |
| ## Execution Notes |
Review: Open issue deep dive — wave 2 backlog planDocumentation-only, no runtime/CI/security impact. Overall this is clean and well-structured. Verified:
One nit: Missing blank line between the |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@analysis/open-issue-deep-dive/wave-2-backlog.md`:
- Line 165: Replace the inline fenced snippet that currently reads the
JavaScript wait call with a standard inline code span; locate the text
containing await new Promise(resolve => setTimeout(resolve, 5000)); in the
markdown (the Context excerpt / problem description) and change the surrounding
backticks/spaces so it becomes an inline code span (e.g., `await new
Promise(resolve => setTimeout(resolve, 5000));`) to satisfy markdownlint MD038.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7ef31cdf-d844-430d-b1d6-917d1e56c579
📒 Files selected for processing (2)
analysis/open-issue-deep-dive/README.mdanalysis/open-issue-deep-dive/wave-2-backlog.md
| - 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 ... |
There was a problem hiding this comment.
Fix inline fenced snippet formatting to satisfy markdownlint (MD038).
Line [165] uses an inline fenced block with backticks and surrounding spaces; this is likely the lint warning source. Use a normal inline code span for the snippet.
Proposed markdown-safe edit
-- 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: `await new Promise(resolve => setTimeout(resolve, 5000));` This approach has several iss ...📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - 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: `await new Promise(resolve => setTimeout(resolve, 5000));` This approach has several iss ... |
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)
[warning] 165-165: Spaces inside code span elements
(MD038, no-space-in-code)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@analysis/open-issue-deep-dive/wave-2-backlog.md` at line 165, Replace the
inline fenced snippet that currently reads the JavaScript wait call with a
standard inline code span; locate the text containing await new Promise(resolve
=> setTimeout(resolve, 5000)); in the markdown (the Context excerpt / problem
description) and change the surrounding backticks/spaces so it becomes an inline
code span (e.g., `await new Promise(resolve => setTimeout(resolve, 5000));`) to
satisfy markdownlint MD038.
💡 Codex Review Include the Wave 3 issue list in this snapshot
This README says the "new PR stack references all issues that had no open PR at review time," but this commit only adds Replace the Pro-approval question on issue #2409
The context excerpt here says issue #2409 is only about aligning ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
## Summary - Stamp `### [16.5.0.rc.0]` version header with today's date - Add 10 new changelog entries for PRs merged since v16.4.0 - Fix incomplete PR 2818 entry (missing author link) ### New entries added **Added:** - `create-react-on-rails-app --pro` support (PR 2818) - Global prerender env override `REACT_ON_RAILS_PRERENDER_OVERRIDE` (PR 2816) - `react_on_rails:sync_versions` rake task (PR 2797) - Pro/RSC setup checks in `react_on_rails:doctor` (PR 2674) **Changed:** - [Pro] Canonical env var for worker count is now `RENDERER_WORKERS_COUNT` (PR 2611) **Improved:** - Smoother `create-react-on-rails-app` and install generator flows (PR 2650) - Pro upgrade hint after install (PR 2642) **Fixed:** - Preserve runtime env vars across `Bundler.with_unbundled_env` (PR 2836) - Fix doctor prerender check and ExecJS display for Pro/RSC apps (PR 2773) - Fix doctor false positives for custom layouts (PR 2612) ### Skipped PRs (not user-visible) Docs-only: #2845, #2842, #2826, #2830, #2820, #2809, #2803, #2785, #2801, #2791, #2789, #2788, #2772, #2778, #2780, #2784, #2671, #2676, #2662, #2657, #2669 CI/internal tooling: #2825, #2817, #2819, #2812, #2815, #2810, #2808, #2807, #2634, #2798, #2761, #2760, #2658, #2639, #2667, #2656 ## Test plan - [x] Verified version header and diff links are correct - [x] Verified all entries follow changelog formatting conventions - [x] Verified file ends with newline - [ ] After merge, run `rake release` to publish 16.5.0.rc.0 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Documentation-only change updating `CHANGELOG.md` with a new `16.5.0.rc.0` section and compare links; no runtime code is modified. > > **Overview** > Adds a new `16.5.0.rc.0` (2026-03-25) section to `CHANGELOG.md`, consolidating recent PR entries under **Added/Changed/Improved/Fixed** and correcting the previously incomplete `--pro` CLI entry author attribution. > > Updates the bottom compare links so `[unreleased]` now compares from `v16.5.0.rc.0` and adds a link definition for `[16.5.0.rc.0]`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 481a71c. 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 --> ## Summary by CodeRabbit ## Release Notes - v16.5.0.rc.0 * **New Features** * Added sync_versions task for streamlined version management * Expanded doctor checks for Pro and RSC support * **Improvements** * Enhanced generator workflow and Pro upgrade guidance * Improved environment variable handling and preservation * **Bug Fixes** * Fixed detection issues with doctor tools and ExecJS/prerender functionality <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 participant
Replacement for #2811, which auto-closed when its stacked base branch was merged and deleted.\n\nContains the Wave 2 backlog plan and all follow-up review fixes from that thread.
Note
Low Risk
Low risk documentation-only change that adds/adjusts triage notes; no runtime, CI, or dependency changes.
Overview
Updates
analysis/open-issue-deep-dive/README.mdto clarify wave counts, tighten thewave-1definition, and document formatting conventions (truncated context excerpts andTriage noteusage).Adds
analysis/open-issue-deep-dive/wave-2-backlog.md, capturing the Wave 2 backlog plan: a curated list of snapshot issues with domain/label metadata, brief context excerpts, and the exact triage questions posted for follow-up.Written by Cursor Bugbot for commit 862b7e7. This will update automatically on new commits. Configure here.
Summary by CodeRabbit