docs(backlog): empty Active work; move shrinks to Cancelled#11
Merged
Conversation
The 2026-06-14 cull PR optimistically left 4 "shrink" items + a winget-configure migration in Active. Hours later, on reflection, they all fall into the exact pattern the cull rejected: speculative cleanup on a personal-use script with no consumer asking for it. Moving them to Cancelled with rationale, alongside the already-cancelled Sprint 7 and Tier 4. Replaced Active with two prose sections: - "What WOULD legitimately add work here" — fix from real failure, repeated workaround worth scripting, external-dep change, new external trigger. - "What WOULD NOT" — aesthetic improvements, speculative tests, LOC-target rewrites. The file stays as a record of the cull and the policy, not a punch list of imagined work.
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.
Summary
The 2026-06-14 cull PR (#9) optimistically left 4 "shrink" items + a winget-configure migration in Active work. On reflection, they all fall into the exact pattern the cull rejected: speculative cleanup on a personal-use script with no consumer asking for it.
Changes
system-updates873→150,Manage-Docker1198→100,Repair-CommonIssues677→200,Set-StaticIP298→30), thewinget configureYAML migration, and the PR template. Each with a one-line rationale.Why
The file stays as a record of the cull and the policy, not a punch list of imagined work. The temptation to keep "just one more cleanup item" warm in BACKLOG is itself the failure mode.
Test plan