docs: PROGRESS's open list should not still carry #11 and #12 - #42
Merged
Conversation
Both are built and in review as a stacked chain (#39 → #40 → #41, plus the plugin sync at claude-code-sdlc#28). The open-issue list is the thing people read to know what is left, so it going stale is the failure #35 built check_standard.py to prevent for the kit inventory — this list is prose the checker cannot police, which is exactly why it needs the discipline applied by hand. Also corrects two stale counts on the STATUS line that nobody had reason to re-measure: "100 files" and "298 passing tests" were 138 and 532/6-skipped respectively, both taken from running `sync_kit.py --check` and the plugin suite rather than estimated. Neither number is load-bearing, which is how they drifted unnoticed — the line now says to run the commands instead of quoting it. Carries the caveat forward rather than letting the PR titles imply more than was done: nothing in those three PRs has been made to fail on purpose yet, and the-rails.md section 9 is explicit that this is what proves a rail. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Both are built and in review. The open-issue list is what people read to know what is left, so it going stale is precisely the failure #35 built
check_standard.pyto prevent for the kit inventory — this list is prose the checker cannot police, so the discipline has to be applied by hand.What changed
feat: deploy promotion + rollback workflows, and a dependency-update axis #11 and feat: fleet observability — gate outcomes visible across installed repos #12 move out of the open list and into an In review block naming the stacked chain (feat: the deploy rail's second half — promotion, rollback, and the Phase 9 skeletons #39 → feat: the standard's first position on third-party components #40 → feat: fleet visibility — gate outcomes readable across installed repos #41, plus claude-code-sdlc#28) with merge order, since each PR is based on the one above it.
Two stale counts corrected, both measured rather than estimated:
sync_kit.py --check)Neither is load-bearing, which is exactly how they drifted unnoticed. The line now tells you to run the two commands instead of quoting it.
Carries forward the caveat rather than letting three PR titles imply more than was done: nothing in them has been made to fail on purpose yet, and
docs/the-rails.md§9 is explicit that this — not the YAML existing — is what proves a rail.Test plan
python scripts/check_standard.py— no drift (PROGRESS.mdis inUNSCANNED, so this confirms the change breaks nothing else)python -m pytest scripts/tests -q— 46 passing onmainIndependent of the feature chain: based on
main, mergeable in any order.🤖 Generated with Claude Code