chore(docs): file curated backlog issues (#39–#58) + rot-free work map (#37)#59
Conversation
|
Warning Review limit reached
Next review available in: 57 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughDocumentation updates replace static in-file backlog listings and cross-references with links to GitHub issues. BACKLOG.md restructures around label-based navigation and named anchor issues, while DESIGN.md and the MNDP README add direct issue links ( ChangesDocumentation restructuring
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Second half of #37: with the Issue->PR scheme merged (#38), triage BACKLOG.md's "not yet filed" checklist into a curated set of GitHub Issues (the "one list" to comment on) -- grouped, not 1-to-1: - #39 anchors an optional centrs `exec` passthrough (needs-decision) and folds the centrs-owned cluster (exec soft-error, protocol-adapter, MAC-Telnet) as checklist items there, not as separate quickchr issues -- they're more involved than QEMU-focused quickchr and drove centrs' design. - #40 Windows, #41 platform-gaps, #42 cross-platform, #43 REST-grounding, #44 CLI/UX polish, #45 QEMU watch-items are triage umbrellas (research, done-when = break out sub-issues then close). - #46-#55 crisp singles; #56-#58 the port/config needs-decision calls. BACKLOG.md is now a rot-free map: browse-by-label query links for the live list, explicit numbers only for grounding anchors (#39/#40/#56-#58). Repoint the centrs MAC-Telnet note (examples/mndp) and the DESIGN port open-questions to the real issues. Left the self-contained REST-timeout rule in routeros-rest.instructions.md as-is (rules, not work pointers). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR completes the second half of the backlog→issues migration by converting the old “unfiled checklist” in BACKLOG.md into a rot-resistant work map that points to live GitHub label views, and by repointing a couple of existing docs to the newly filed grounding/decision issues.
Changes:
- Slim
BACKLOG.mdinto a work map with browse-by-label links plus a small set of “grounding anchor” issues. - Repointed existing documentation references from
BACKLOG.mdto the corresponding GitHub Issues (#39, #56, #57). - Kept decision/grounding pointers close to the relevant design notes (port layout decisions in
DESIGN.md).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| examples/mndp/README.md | Updates the MAC-Telnet note to reference the new concept/anchor issue (#39) instead of BACKLOG.md. |
| DESIGN.md | Links the two open port-layout “needs-decision” items directly to issues #56 and #57. |
| BACKLOG.md | Replaces the stale per-item list with label-based browsing links and a short set of explicitly named anchor issues. |
977c4e1 to
3d25a53
Compare
What
Second half of #37. With the Issue→PR scheme merged (#38), triage BACKLOG.md's
"not yet filed" checklist into a curated set of GitHub Issues — the "one list"
to comment on and use as a starting point for discussion — and slim BACKLOG.md to a
rot-free map.
Curated, not 1-to-1 (per the steer: umbrella where triage is still owed).
Issues filed (#39–#58)
Concept anchor — #39 optional centrs
execpassthrough (needs-decision). Tracksthe concept (opt-in route through centrs' validate→explain→run for richer
warnings/tips; name TBD), explicitly not designed here. Folds the centrs-owned
cluster —
exec()soft-error detection, protocol-adapter reuse, bidirectionalMAC-Telnet — as checklist items there, not as separate quickchr issues: they're more
involved than QEMU-focused quickchr and drove centrs' design ("in a sense done, in
centrs").
Triage umbrellas (
research; done-when = break out sub-issues or land aREPORT.md,then close) — #40 Windows (the "ground yourself before claiming X fails on Windows"
anchor) · #41 platform gaps · #42 cross-platform validation · #43 REST lab grounding ·
#44 CLI/UX polish · #45 QEMU watch-items.
Singles — #46 user-settings
P1· #47doctor· #48 config audit · #49 wizardremediation · #50 evidence descriptor · #51 SSH transport · #52
sudohandling ·#53 agent teaching · #54 error diagnostics · #55 multi-CHR examples.
Decisions owed (
needs-decision) — #56 port-base randomness · #57 service-blockredesign · #58 config-schema split.
Docs in this PR
BACKLOG.md→ rot-free map: browse-by-label query links for the live list (nevergoes stale), explicit numbers only for grounding anchors (exec: optional passthrough to centrs for richer validation #39/Windows support: first-class support research and alignment (umbrella) #40/decision: move off the fixed 9100 port base #56–decision: split desired config from runtime state in machine.json #58). No
per-issue mirror to maintain — the "not yet filed" checklist is gone.
examples/mndp/README.md) → exec: optional passthrough to centrs for richer validation #39 and the DESIGNport open-questions → decision: move off the fixed 9100 port base #56/decision: fixed service-block redesign (Windows +6..+8 IPC collision) #57.
routeros-rest.instructions.mdas-is —instruction files hold rules, not work-tracking pointers (the reconciliation work is
tracked in REST behaviour: standalone lab grounding (blocking / async / error edges) #43).
Verification
bun run checkgreen (biome · tsc · markdownlint · cspell · validate-examples ·shellcheck);
git diff --checkclean.🤖 Generated with Claude Code
Summary by CodeRabbit