[codex] Fix roadmap progress sync for padded phase arguments#3380
Conversation
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR fixes roadmap progress mutations to normalize phase-number matching, allowing zero-padded phase arguments like ChangesRoadmap Phase-Padding Fix
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
|
Summary
Fixes roadmap progress sync when
roadmap.update-plan-progressis called with a zero-padded phase argument such as03whileROADMAP.mduses unpadded phase labels such asPhase 3and| 3. ... |.Root cause
The roadmap progress mutation found
.planning/phases/03-*through the existing phase-directory normalization path, but reused the rawphaseNumargument to build ROADMAP markdown regexes. That meant03matched plan IDs like03-01, but missed the top-level phase checkbox, phase detail**Plans:**line, and progress table row written as3.Changes
Standards followed
Follows
CONTEXT.mdvocabulary for the Planning Workspace / Planning Path Projection surfaces anddocs/adr/0005-sdk-architecture-seam-map.md/docs/adr/0006-planning-path-projection-module.mdby keeping the SDK query handler and CJS compatibility path aligned without introducing a new seam. No ADR required: this is a scoped bugfix under confirmed issue #3378.Validation
cd sdk && npm test -- roadmap-update-plan-progress.test.tsnode --test tests/roadmap.test.cjsnpm run lint:changesetnpm testCloses #3378
Summary by CodeRabbit
Bug Fixes
Tests