docs(references): verify announced tickets exist (I5), resolve nonexistent batch keys - #47
Merged
Merged
Conversation
…stent batch keys Two learnings from a six-ticket batch review (2026-08-27): Checklist gains I5 - when a description or comment announces follow-up work as "separate tickets", verify each announced ticket exists via a tracker query instead of trusting the prose, and file the missing ones during QA with paired icons. In the exercising batch, twelve announced follow-ups across two tickets existed only as prose. batch-review Stage 0 gains the nonexistent-key resolution: search the same project's QA queue for the near-miss, proceed on a single plausible candidate with the substitution marked as an explicit assumption, ask otherwise. Assisted-by: claude-code:claude-fable-5 Agent-Session: https://claude.ai/code/session_015SA4wLVRnk7jERWMctyqP2 Agent-Host: 0493f0 Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Member
Author
|
Self-review: 214b169 The review this pull request demands is unsatisfiable (Copilot quota wall or repeated bot failures on this head). Per the documented fallback, the diff on this head was reviewed by the PR author; this comment is the on-the-record attestation the merge gate reads back. It stops matching on the next push. |
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.
Two learnings from a six-ticket batch review (2026-08-27). Checklist gains I5: when a description or comment announces follow-up work as "separate tickets", verify each announced ticket exists via a tracker query instead of trusting the prose, and file the missing ones during QA with paired icons — in the exercising batch, twelve announced follow-ups across two tickets existed only as prose. batch-review Stage 0 gains the nonexistent-key resolution: search the same project's QA queue for the near-miss, proceed on a single plausible candidate with the substitution marked as an explicit assumption, ask otherwise.
Assisted by claude-code:claude-fable-5 — Session