backlog: close 9 landed items, retire a stale marker, progress-note 3 that stay open - #587
Merged
Conversation
…ming other items #1005 (CRL checking, ASVS 12.1.4 band B1): landed 3c5cb98 (PR #458, 2026-08-22), squashed alongside #1268 -- the commit subject names #1268, not this row, which is why a subject screen never found it. All four scope items verified present by content. Ceiling stays partial per the row's own ASVS note; not described as clearing the cell. #1010 (licence-header gate): landed 4d3a72e (PR #398, 2026-08-15). Gate, negative control, backfill, and both callers (pre-commit + required CI) verified present and wired. Neither closure is complete: #1005's vault-side ASVS cell and #1010's security deviation register both need a matching correction that this checkout cannot see or verify (vaulted/ gitignored). Noted in each banner rather than silently left. Also: #1010's own text claims backlog_status_check.py hard-errors on a shipped item still carrying Priority -- tested empirically (--min-items 300), it does not, at least in this checkout's version. Left Priority as-is rather than acting on the unverified claim. Both ancestor claims verified directly before closing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wshallwshall
enabled auto-merge (squash)
August 25, 2026 18:36
…sh-orphan The threat-model gate's rename (test_transcribed_bounds_match_the_live_constants) and failure-message fix both landed at 9022b2c (PR #562, 2026-08-23). The row's own body cited a5d5a9a as the rename commit -- a5d5a9a is not an ancestor of origin/main, same squash- orphan class PR 587 fixed on two other rows tonight. Corrected in the same edit as the closure rather than left for a separate pass. Skipped #1061 and #1249 from the same evidence batch: both are landed by content but each carries a prior, on-main, deliberate decision not to close (12aa067/9847d267 for #1061; an unwitnessed owner ratification for #1249). Closing either would override a standing decision, not just flip a stale banner. Verified the ancestor claim and the rename directly before writing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wshallwshall
changed the title
wshallwshall
disabled auto-merge
August 25, 2026 18:40
wshallwshall
enabled auto-merge (squash)
August 25, 2026 18:40
…, one record still owed
Builder 1's claude/builder-1-1022-self-exclusion adds self-exclusion to POST
/users/{user_id}/reset-mfa. Per standing dispatcher guidance #1022 is not a clean closure,
so this is a progress note, not a banner flip -- status glyph unchanged.
Of the row's three OWED record corrections, verified which landed: (1) SECURITY.md and
(2) ADR 0068 both corrected on that branch. (3) is not -- the ADR gained retraction prose
but no new formal AC entry (checked directly: existing ACs run AC-10 through AC-16).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wshallwshall
changed the title
wshallwshall
disabled auto-merge
August 25, 2026 18:45
wshallwshall
enabled auto-merge (squash)
August 25, 2026 18:45
…ays open logging_setup.py now imports controlchars and states its own table as that alphabet minus TAB, proved byte-identical to the pre-change table entry-for-entry rather than asserted. Verified before writing this note. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…ress-note 2 Closed, each verified independently (ancestor sha or byte-identical content match against the row's own cited branch tip, not adopted from the evidence pass): #1262 (doc-guards lane membership + anti-vacuity test), #1263 (citation_line_check.py with all four required controls), #1301 (banner-sha agreement check, narrowed trigger), #1306 (worktree gate read/write fix, heredoc half correctly left to #1332), #1331 (connscale smoke test split into 9 named properties), #1338 (duplicate-banner-field detector, both must-fire/ must-not-fire controls pinned). #1235: retired the 2026-08-24 must-not-close marker. Its stated condition -- the closing PR falsified the detector's header and left it uncorrected -- has cleared: read the header on main directly, it now says plainly that the script is wired into no workflow and distinguishes itself from its CI-wired sibling. Closed alongside. Two stay open with a progress note rather than closing: #1254 (option (a) landed and resolves the measured defect; options (b)/(c) are an unbuilt branch-protection decision, not a build) and #1324 (mechanism is live -- verified with a fresh parse_items run, not the evidence pass's snapshot -- data migrations landed, but real fill-in work remains: 2 mechanical, 5 needing an owner ruling the row forbids flattening). Deliberately not touching #1086 from the same evidence batch: closing it declined-by-design rests on an owner ruling relayed via the Liaison that I have not seen directly, for a security-relevant gate. Leaving it rather than acting on a relayed claim for a call of that weight. Verified every landed sha against origin/main myself before writing any of this (ancestor checks plus, where the cited sha was a squash-orphan, a content diff against the row's own branch tip) rather than trusting the evidence pass's citations. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
wshallwshall
changed the title
wshallwshall
disabled auto-merge
August 25, 2026 19:28
wshallwshall
enabled auto-merge (squash)
August 25, 2026 19:28
Content is PR 527's own #1330 filing, re-numbered: the original #1330 allocation belonged to a different, now-gone Lander worktree, and this one's ledger gate correctly refused to let me commit under someone else's allocation. Re-allocated fresh in this worktree per the owner's call, after confirming nothing in the tracked tree cites "#1330" expecting this content -- the number was never published anywhere main-visible. Filed clean off current main rather than resolving PR 527's own conflict: PR 527 also carried a competing #1321 edit, but #1321 (and #1322, the item it was a duplicate of) are both already closed on main via a separate path, so that half of PR 527 is moot -- dropped rather than replayed. This item's own text records that as done rather than repeating the stale "banner needs flipping" framing from the original filing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
All three confirmed one-hop via the Liaison, who put each question to the owner directly and read the answer -- not relayed through a third party. This is the same tokeniser-family ruling I held #1086 on earlier this session pending exactly this kind of confirmation. #1086 + #1070: both fold into the 2026-08-23 tokeniser ruling's family (#1066/#1070/#1086/#1305/#1336). Verified the code claim behind "one string asked two questions" myself before writing this: Remove-QuotedSpans is real at worktree_gate.ps1:425, called on the scan path at :960/:967, Raw and Scan are genuinely separate fields at :1319-1321/:1290-1291. Did not re-verify #1070's three design refutations (Builder 2's own measurement, not independently re-run by anyone since) -- recorded as such in the row. #1057: a tier move off the row's own Verdict: build line, so asked rather than stamped, matching this ledger's existing declined-by-design rows (all of which carry an owner date). Declines because rule 3d has no allow path -- zero Write-Allow in its span -- so the row can only ever act as an authorization, which prune-merged.ps1 forbids occupancy from being, in its own comment, for the same no-heartbeat-on-this-host reason. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The conftest name-collision guard landed as PR 600. Records that the row's own recommended fix (option B, __init__.py in both roots) was measured and makes the collision FATAL rather than fixing it -- verified before writing this note, not taken from the PR's own claim. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
# Conflicts: # docs/BACKLOG.md
…ed them, #1086's closure missed them #1086's own closure text cites an owner ruling "extending the 2026-08-23 tokeniser ruling to the family (#1066/#1070/#1086/#1305/#1336)" -- but only #1086 and #1070 were actually closed against it. This closes the other three named members on the same ruling: #1336: the row the ruling actually turns on -- it named the tokeniser requirement and recorded the 2026-08-23 out-of-scope verdict. Also re-applies a metadata fix (Verdict/Closing-act -> owner-ruling) that Dispatcher's 883f773 made and an unrelated PR (#581, 0d38d1e) silently reverted by merging from a stale base -- confirmed via git blame, not assumed. #1305: already self-diagnosed the same outcome in its own 2026-08-23 amendment ("as filed, this item is probably UNBUILDABLE"); this formalizes what its own text anticipated. #1066: the banked second fix remains open evidence of why a narrower attempt still fails without the declined tokeniser -- rejected by four verifiers finding five new fail-opens and two new false-deny classes. All three bypasses remain real and live on the installed gate. The ruling accepts that risk rather than building the tokeniser needed to close any of them without reopening one of the others. Co-Authored-By: Claude Sonnet 5 <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.
Ledger updates, mostly from the Dispatcher's already-on-main evidence pass, each verified
independently before writing (ancestor sha, or a content diff against the row's own branch
tip where the cited sha was a squash-orphan) -- not adopted from the pass's citations.
Closed, landed by content:
3c5cb988(PR auth,store: username identity is case-sensitive and must not depend on store collation (BACKLOG #1268), plus the ledger parse hook #458).4d3a72eb(PR feat(quality): licence-header gate with its negative control and backfill (BACKLOG #1010) #398).9022b2cc(PR test(threat-model): name the assertion for what it checks (BACKLOG #1214) #562); row's own citation was a squash-orphan, corrected.4a8f062d(PR builder 1: eight items across 29 commits, incl. #1242 limb 4 (evidence emitter carries unknown keys) #394) + the anti-vacuity test the row's own amendment named as the last remaining piece.a8f5d10a, byte-identical to branch tip4cc38a05, all four required controls present.4d76bd6e(PR ledger + coord: banner-sha agreement check, unbacked_check false alarm, dependabot harness diagnosis, and 4 promoted banner fields #542), byte-identical to branch tip5a513350, the 2026-08-23-narrowed trigger.5eb261de(PR fix(worktree-gate): rule 3c decided on command SHAPE, so a read-only git config query was refused (BACKLOG #1306) #541), same patch-id as the row's own cited (non-ancestor) sha.df8acc95(PR ci,crypto-gate,tests: four gates that could not fail for the reason they existed (BACKLOG #1319, #1322, #1323, #1331) #537), byte-identical to branch tip2ac5be6a.f402a2d3(PR fix(ledger): a duplicated banner field was invisible to every count-preserving check (BACKLOG #1338) #550), byte-identical to branch tip9873b38a, both required controls pinned.Stay open, progress note only:
parse_itemsrun), data migrations landed; 2 mechanical fill-ins plus 5 owner-ruling items remain.Deliberately not touched: #1086 from the same evidence batch. Closing it declined-by-design
rests on an owner ruling relayed via the Liaison that I have not seen directly, for a
security-relevant gate -- leaving it rather than acting on a relayed claim for a call that size.
backlog_status_check.py --min-items 300passes after every commit: 599 items, each declaringexactly one status.