docs: refresh roadmap after v5.3.3 review cycle#22
Conversation
📝 WalkthroughWalkthroughUpdates ROADMAP.md and STATUS.md to reflect v5.3.3 (M17 Ledger) as the current release and establishes M18 Relay as the next milestone. Restructures tables, updates sequences, and revises narrative descriptions throughout both documents. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 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)
📝 Coding Plan
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
ROADMAP.md (1)
128-130: 🛠️ Refactor suggestion | 🟠 MajorConsider adding acceptance criteria for the technical follow-up items.
The current acceptance section only covers JSONL contract tests for the core agent CLI. The new technical deliverables (actionlint CI, workflow automation, Docker regression coverage) lack explicit acceptance criteria. Consider adding criteria such as:
- actionlint runs clean in CI and fails on workflow issues
- GitHub Actions dependency updates execute successfully on schedule
- Docker regression tests verify unprivileged execution and Deno Node binary availability
This would clarify the "done" definition for these items.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ROADMAP.md` around lines 128 - 130, Add explicit acceptance criteria for the technical follow-ups in the Acceptance section: append bullets for "actionlint CI" (e.g., actionlint runs clean in CI and fails the build on workflow issues), "workflow automation" (e.g., scheduled GitHub Actions dependency update workflow runs successfully and creates PRs on schedule), and "Docker regression coverage" (e.g., regression tests confirm unprivileged container execution and presence/compatibility of Deno/Node binaries and reproducible artifacts). Reference these items by name (actionlint CI, GitHub Actions dependency updates, Docker regression tests) so the done definition is unambiguous.
🧹 Nitpick comments (1)
ROADMAP.md (1)
79-79: Consider clarifying the maintenance release grouping.The notation
M17 Ledger + v5.3.1/v5.3.2/v5.3.3 maintenancecould be read as either "M17 plus three maintenance releases" or "M17 (which is v5.3.3) plus the earlier maintenance releases." Since the Shipped Summary shows v5.3.1/v5.3.2 as standalone maintenance and v5.3.3 as M17, you might considerM17 Ledger (v5.3.3) + v5.3.1/v5.3.2 maintenancefor precision.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@ROADMAP.md` at line 79, Update the ambiguous release notation line "M17 Ledger + v5.3.1/v5.3.2/v5.3.3 maintenance ✅" to explicitly show M17 corresponds to v5.3.3 by changing it to "M17 Ledger (v5.3.3) + v5.3.1/v5.3.2 maintenance ✅"; locate and edit the exact string in the ROADMAP entry so the shipped summary matches the clarified grouping.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@ROADMAP.md`:
- Around line 128-130: Add explicit acceptance criteria for the technical
follow-ups in the Acceptance section: append bullets for "actionlint CI" (e.g.,
actionlint runs clean in CI and fails the build on workflow issues), "workflow
automation" (e.g., scheduled GitHub Actions dependency update workflow runs
successfully and creates PRs on schedule), and "Docker regression coverage"
(e.g., regression tests confirm unprivileged container execution and
presence/compatibility of Deno/Node binaries and reproducible artifacts).
Reference these items by name (actionlint CI, GitHub Actions dependency updates,
Docker regression tests) so the done definition is unambiguous.
---
Nitpick comments:
In `@ROADMAP.md`:
- Line 79: Update the ambiguous release notation line "M17 Ledger +
v5.3.1/v5.3.2/v5.3.3 maintenance ✅" to explicitly show M17 corresponds to v5.3.3
by changing it to "M17 Ledger (v5.3.3) + v5.3.1/v5.3.2 maintenance ✅"; locate
and edit the exact string in the ROADMAP entry so the shipped summary matches
the clarified grouping.
1 participant
Summary
Validation
Summary by CodeRabbit