docs: sweep the backlog's orphaned checkboxes - #602
Merged
Merged
Conversation
Counting gave 49 open / 69 done, and 25 of the 49 sat inside entries whose heading announced completion - RESOLVED, FIXED, ACCEPTED or struck through. Scanning headings said the work was finished; the boxes said otherwise. Same defect this file documents in the infrastructure, reproduced in the document that records it. Four were done and never ticked: pihole config modes (#485), the dns-group identity (the inventory already had the right shape), services.md:21, and 1.12's git question - which had an answer in git log the whole time. Seven were not tasks: 4.17's four conditions sat under a heading reading 'Revisit if any of these become true', and 3.9 had a cross-reference. A checkbox that cannot be ticked inflates the count forever. Found on the way: services.md:20 still claimed the NAS exports via smbd, eighteen days after CLAUDE.md recorded it measured absent; services.md:21 had gone wrong a second time when 1.9 disabled the offsite timer; and 1.12's verification step prefix-matched '5' as a snapshot ID and silently ignored its own --tag filter. Records the remaining 16 grouped by what closes each - eight are a single command away. Adds two follow-ups: 17 prose bullets in 7 and 9 that have no checkbox at all, and n150-3, which is in the inventory, in one group, and in no fleet list.
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.
Counting gave 49 open / 69 done, and 25 of the 49 sat inside entries whose heading announced completion - RESOLVED, FIXED, ACCEPTED or struck through. Scanning headings said the work was finished; the boxes said otherwise. Same defect this file documents in the infrastructure, reproduced in the document that records it.
Four were done and never ticked: pihole config modes (#485), the dns-group identity (the inventory already had the right shape), services.md:21, and 1.12's git question - which had an answer in git log the whole time. Seven were not tasks: 4.17's four conditions sat under a heading reading 'Revisit if any of these become true', and 3.9 had a cross-reference. A checkbox that cannot be ticked inflates the count forever.
Found on the way: services.md:20 still claimed the NAS exports via smbd, eighteen days after CLAUDE.md recorded it measured absent; services.md:21 had gone wrong a second time when 1.9 disabled the offsite timer; and 1.12's verification step prefix-matched '5' as a snapshot ID and silently ignored its own --tag filter.
Records the remaining 16 grouped by what closes each - eight are a single command away. Adds two follow-ups: 17 prose bullets in 7 and 9 that have no checkbox at all, and n150-3, which is in the inventory, in one group, and in no fleet list.