docs: collapse duplicate REQ rows (REQ-1003/1200, REQ-1204/407) #389
Labels
No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
natsukium/felis#389
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
docs/reference/spec.mdhas two pairs of requirement rows that state the same requirement:Two IDs for one requirement drift independently: every fix has to find both rows. Decide whether to keep one ID per requirement and turn the other into a pointer (or retire it), and how retired IDs are marked so that external references stay resolvable.
Decision: keep one ID per requirement and delete the duplicate rows outright, with no pointer row left behind. Repoint every in-repo reference to the surviving ID (grep docs/, skills, code comments, tests).