docs(specs): correct feature 009 docs that still call #263 open - #289
Merged
Conversation
The third /speckit-converge run on feature 009 found two documents asserting a state the recent merges had falsified. PR #263 (sigstore/sigstore 1.10.8 -> 1.10.9) merged as 5291807 once T071/PR #287 migrated operator/internal/verify/verify.go off the deprecated fulcioroots API and cleared the staticcheck SA1019 finding that had been failing lint (operator). quickstart.md still listed #263 among the open PRs and, further down, in the SC-002 acceptance ledger — so the document contradicted itself: the summary said 18 merged while the section a reader uses to verify SC-002 said 19. Every count claim now agrees: 19 merged, 1 closed without merging (#269), 1 deferred (#272), 21 total. The Historical baseline (2026-08-28) section and the per-PR module inventory table are left untouched; #263 correctly appears there as it was. contracts/dependency-upgrade.md is an append-only research record, so the superseded T035 disposition ("#263 stays open and unmerged") is left intact and a dated update note added beneath it. Appends Phase 13 (T075, T076) to tasks.md and marks both complete. The only tasks still open are T055/T056, blocked upstream on no published @typescript-eslint accepting TypeScript 7. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SgeYHZV5dBRpRB1BTM5Pd1 Signed-off-by: valgulnecron <39313199+ValgulNecron@users.noreply.github.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.
Implements Phase 13 (T075, T076) of feature 009, appended by the third
/speckit-convergerun.Why
PR #263 (
sigstore/sigstore1.10.8 → 1.10.9) merged as5291807once T071 / PR #287 migratedoperator/internal/verify/verify.gooff the deprecatedfulciorootsAPI and cleared the staticcheckSA1019finding that had been failinglint (operator). Two feature-009 documents still described the pre-merge world.Worse,
quickstart.mdhad begun to contradict itself: the summary near the top said 18 merged, while the SC-002 acceptance ledger further down — the section a reader actually uses to verify SC-002 — still said 18 merged / 2 deferred. Anyone checking SC-002 today would have gotten the wrong answer.What changed
quickstart.md— every current-state claim about #263 corrected. All count claims now agree:Both enumerated merged lists contain exactly 19 PR numbers, matching their stated counts; the Go/npm split is 9 + 10. The "
#263has 1 failing check, cause not yet diagnosed" special case is rewritten as the resolved outcome it now is.contracts/dependency-upgrade.md— this is an append-only research record, so the superseded T035 disposition ("#263 stays open and unmerged") is left intact and a dated update note added beneath it.Deliberately untouched: the "Historical baseline (2026-08-28)" list and the per-PR module inventory table, where #263 correctly appears as it was at the time.
#272’s descriptions are unchanged — it is still genuinely blocked upstream.Notes
specs/009-remediate-security-dependabot/. No code, nogo.mod, nopackage.json— so this PR is expected to show no CI checks.@typescript-eslint(including canary) accepts TypeScript 7, sonpm cifails at ERESOLVE beforetscruns.🤖 Generated with Claude Code
https://claude.ai/code/session_01SgeYHZV5dBRpRB1BTM5Pd1