docs(planning): tag REQ-* with P0/P1/P2 priorities + add OPEN_QUESTIONS - #394
Merged
Conversation
- Annotate all 61 REQ-* bullets with an inline {priority: P0|P1|P2}
tag and add a legend line in the header (P0=current core, P1=quality/
observability depth, P2=deferred/frozen hot-tier derivatives).
- Add .planning/OPEN_QUESTIONS.md to centralize unresolved decisions
(hot-tier unfreeze gate, license boundary, Redis version matrix, TOML
config, StreamAppend RPC, Engine trait disposal, format-version/migration,
topology persistence, dual-runtime RFC, unified test strategy), each
anchored to a real issue/REQ.
Closes #389 is unrelated; this closes the P2 governance gaps noted in the
PRD audit (add REQ priorities + a consolidated open-questions registry).
📝 WalkthroughWalkthrough本次变更更新规划治理文档:为所有验收需求补充 P0/P1/P2 优先级,并新增包含 OQ-1 至 OQ-10 及维护流程的开放问题清单。 Changes规划治理
Estimated code review effort: 1 (Trivial) | ~5 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
AlexStocks
commented
Jul 30, 2026
AlexStocks
commented
Jul 30, 2026
AlexStocks
commented
Jul 30, 2026
AlexStocks
commented
Jul 30, 2026
Align the priority model and open-question lifecycle with accepted D001, D002, and D005 so future planning work cannot treat fixed baselines as undecided. Constraint: Limit this follow-up to PR #394 planning priorities and open-question semantics. Rejected: Delete resolved sections entirely | It would remove tracking for still-required license review and Redis 8.8.1 compatibility gates. Confidence: high Scope-risk: narrow Tested: git diff --cached --check; 61 unique requirement IDs and priorities; 10 complete OPEN question records; LF line endings. Not-tested: No Rust build or runtime test was run because this follow-up changes planning Markdown only; new remote CI is pending after push. Co-authored-by: OmX <omx@oh-my-codex.dev>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.planning/OPEN_QUESTIONS.md:
- Around line 55-60: Update OQ-10’s first “待确认” bullet to reference OQ-3 as the
authoritative question for the Redis 8.8.1 Oracle fast-gate/full-gate split,
removing the duplicated decision wording while leaving the remaining bullets
unchanged.
🪄 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: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 122cd679-e7b8-4e75-acbe-87d524083cc0
📒 Files selected for processing (2)
.planning/OPEN_QUESTIONS.md.planning/REQUIREMENTS.md
Make OQ-3 the sole decision point for Redis 8.8.1 gate layering while OQ-10 consumes that result as an input to the broader test strategy. Constraint: Limit this follow-up to the current CodeRabbit finding on PR #394. Rejected: Repeat the gate split in OQ-10 | Two writable descriptions can drift into conflicting planning decisions. Confidence: high Scope-risk: narrow Tested: git diff --cached --check; OQ section structure and single-source assertions; LF line endings. Not-tested: No Rust build or runtime test was run because this follow-up changes one planning Markdown line; new remote CI is pending after push. Co-authored-by: OmX <omx@oh-my-codex.dev>
25 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
PRD 审计(deliverables/software-company/kiwi-prd-audit-2026-07-30.md)指出
.planning/REQUIREMENTS.md的 61 条REQ-*缺少统一优先级,且项目缺少一份集中的"待确认问题"清单。本 PR 补齐这两项 P2 治理缺口(均为文档,不触碰任何源码/CI/构建)。改动
.planning/REQUIREMENTS.md:REQ-*bullet 追加行内{priority: P0|P1|P2}标签(P0×30 / P1×11 / P2×20)。判定口径:P0=当前产品核心/不可协商;P1=质量与可观测深度;P2=未来派生/延期热层(冻结中,未授权实现)。.planning/OPEN_QUESTIONS.md(新增):集中收录 10 项当前未闭合、需 owner/决策/证据才能推进的问题,每项锚定到真实 issue 或REQ-*:热层解冻门禁、许可证边界(Apache-2.0 vs AGPL-3.0)、Redis 兼容版本矩阵、TOML 配置、StreamAppend RPC、Engine trait 处置、存储格式版本与迁移、实例拓扑持久化、双 Runtime RFC、统一测试策略。附维护规则(结论落DECISIONS.md,并从本清单移除)。验证
grep -cE '^\s*-\s*\REQ-'= 61,与priority:` 标签数 61 一致,全部 bullet 均已标注。.planning/治理文档,工作区其余文件(.omx/、.workbuddy/、deliverables/)未纳入。注意
kiwi-github/下与本项目无关的 C++ "quantclaw" CI 仍建议另行清理(删除类操作需手动)。Summary by CodeRabbit