Capture P396 + P397: verifying-queue drain cadence gap + evidence-close auto-closes reporters' issues#298
Open
tompahoward wants to merge 1 commit into
Open
Capture P396 + P397: verifying-queue drain cadence gap + evidence-close auto-closes reporters' issues#298tompahoward wants to merge 1 commit into
tompahoward wants to merge 1 commit into
Conversation
…dence, and evidence-close auto-closes reporters' issues Two governance defects surfaced when the user asked why issues were being auto-closed and why they had to ask to examine the verifying queue. P396: the verification-queue drain (verifying -> closed) has no self-firing cadence — it runs only on manual invocation or the narrow work-problems Step 0c AND-gate, so the verifying queue bloats unbounded (188 on 2026-06-28) until a human asks, then drains in one large batch. P375 cadence-rollup class; sibling P295. P397: the silent evidence-based close auto-closes external reporters' GitHub issues (gh issue close via update-upstream / the P363 inbound leg) against the "we'll close after your confirmation or a 14-day quiet period" promise we post — it closes on our in-session evidence, reporter-independent, often within days. Captured via /wr-itil:capture-problem (hang-off-check cap short-circuit, both deferred to next review-problems). One commit covers both per the single user-directed capture-both action. Refs: P396, P397
tompahoward
added a commit
that referenced
this pull request
Jun 28, 2026
…ncurrent #298 A concurrent worktree session (PR #298) independently captured a different P396 (verification-queue drain cadence) plus a P397. Per user direction, the VP-carve-out ticket I merged this session yields the 396 slot and moves to 398 so #298 can merge its 396/397 without an ID collision. Pure docs renumber: ticket file rename + README WSJF row + line-3 fragment + holding-README batch note references updated. No code, no changeset. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01LK7ZeKyzoCkkAVaCDepepU
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.
Summary
Captures two governance defects surfaced when reviewing why GitHub issues were being auto-closed and why the verification queue had to be drained on request.
P396 — the verifying-queue drain has no self-firing cadence (the trigger side). The Verification Pending → Closed drain runs only on a manual
/wr-itil:review-problems/run-retro/manage-problem review, or the narrow work-problems Step 0c AND-gate. So the verifying queue grows unbounded — 188 tickets as of 2026-06-28 — until a human asks, then closes in one large batch. Same class as P375 (a named re-entry point is not a self-firing cadence); closest sibling is P295.P397 — the silent evidence-based close auto-closes external reporters' issues against the promise we post (the close side). The drain closes verifying tickets on our in-session evidence, and the close runs
gh issue closeon the linked issue for inbound-reported and reported-upstream tickets. But the fix-released comment we post says "we'll close after your confirmation or a 14-day quiet period." So a reporter's issue is closed before they confirm and before 14 days, contradicting our own comment.The two are the same broken loop: the trigger is manual, but the close is automatic and silent — and reaches out to close external reporters' issues against a stated promise.
Changes
docs/problems/open/396-...md— P396 ticketdocs/problems/open/397-...md— P397 ticketdocs/problems/README.md+README-history.md— WSJF rows + last-reviewed rotationBoth are deferred-placeholder captures (Priority/Effort re-rated at the next review). No code changes.
🤖 Generated with Claude Code