fix(plan): a dotted sub-item is not its parent - #72
Closed
thedancingdeveloper wants to merge 1 commit into
Closed
Conversation
Parsing a second, independently-written plan found this: '#### P0.1' truncated to id 'P0', so five distinct items collapsed onto their phase heading -- and the sync then refused the plan for stating 'P0' five times. One cause, two symptoms, and the duplicate report pointed at the wrong thing. The narrow-by-design rule is unchanged: '## 5. Architecture' is still narrative, not work. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #73, which contains this commit ( |
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
1 participant
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.
Parsing a second, independently-written plan (NGMS
UNIFIED-ARR-PLAN.md) found this:#### P0.1truncated to idP0, so five distinct items collapsed onto their phase heading — and the sync then refused the plan for statingP0five times. One cause, two symptoms, and the duplicate report pointed at the wrong thing.Before: 100 items, 11 duplicate ids,
P0.1…P0.5all reported asP0.After:
P0.1…P0.5are distinct; the 11 remaining duplicates are the genuine kind (each phase described in §7 and again in the appendix), which--allow-duplicatesalready handles.The narrow-by-design rule is unchanged:
## 5. Architectureis still narrative, not work. Two tests added, including two-digit sub-numbers and dotted dependency resolution.🤖 Generated with Claude Code