Repository navigation
Description
Is there an existing issue for this?
- I have searched the existing issues.
Which actions are affected?
Pull Request, Commits
Which platforms are affected?
Linux, macOS
Description
The older normal-flow runner supplies cancellation to provider requests but omits bugbotReviewSignal from projectBugbotReviewOperationContext. An interrupted verifier can be retained as a technical failure while the surrounding dry-run operation is incorrectly completed.
Scope and acceptance criteria
- Pass the existing review signal through the ordinary operation projection and preserve explicit cancellation across detector, preparation and verification.
- At least six deterministic cases cover cancellation before detection, during detection, between preparation and verification, during verification, after a technical provider interruption, and an uninterrupted completion. Interrupted work cannot mint a completed result/receipt.
- Capture the actual interrupted attempt and pending request, with zero GitHub write attempts. Keep historical ledgers intact and require a new driver pin before measured reuse.
- Preserve unlimited investigation time/tokens/turns and optional usage telemetry; do not replace cancellation with automatic research cutoffs.
Reproducing the issue
Use a controlled provider in the normal-flow runner, abort during shadow verification, and inspect the operation result. Reproduce without model or GitHub access.
Pinned source references:
copilot Version
Unreleased develop at ccefb27627cd627ccdb7d5666fd174c2ac1da07b (PR #951); this is not a released or activated profile.
Additional context and comments
Priority and dependencies
- Priority: medium. Stage: Qualification prerequisite.
- Blocked by: None; may be prepared independently.
- Follow-up to ✨🧑💻 - Verify Bugbot findings against repository evidence before publication #950 and merged PR feat: Verify Bugbot findings against repository evidence before publication (#950) #951, not a request to reopen or extend that delivery.
- Final closure and observed limitations. Review thread.
Documentation and implementation boundary
Documentation: docs/development/testing.mdx.
Keep Clean Architecture and current coverage/contract gates. When a later implementation changes a public contract, update its catalogued SDD, tests and docs together and validate specifications; update Graphify after code changes.
Read the effective #950 contract in the owning SDD and its current reconciliation amendments; historical pilot deadlines are not current investigation limits.
Fixed invariants and planning state
Backlog only: no in-progress, branch creation, model execution, deployment or activation requested by this planning step.
Keep BUGBOT_VERIFICATION_MODE=disabled. Evaluated PRs must have zero write attempts; retain frozen pilots and independent evaluator/oracle evidence.
Token usage is optional telemetry and cannot stop investigation or reject a supported verdict. Elapsed time and turn count do not impose research cutoffs; explicit cancellation and evidence/SHA integrity remain mandatory. Post-run latency qualification criteria remain distinct from session deadlines.
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsIn Progress
Activity
[-]Forward explicit cancellation into the normal-flow Bugbot shadow review operation[/-][+]🐛 - Forward explicit cancellation into the normal flow Bugbot shadow review operation[/+]vypbot commentedon Nov 19, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.2 remaining items
vypbot commentedon Nov 19, 2026
Implementation plan
Acceptance: Deterministic tests prove all six cancellation and completion cases; every interrupted case retains its attempt and pending request, makes zero GitHub write attempts, and cannot mint a completed result or receipt, while uninterrupted completion succeeds and historical ledgers remain intact.
Need something else? Mention the bot with a question or use
/copilot help.bugfix-972-forward-explicit-cancellation-into-the-normal-flow-bugbot-…
bugfix-972-forward-explicit-cancellation-into-the-normal-flow-bugbot-…
bugfix-972-forward-explicit-cancellation-into-the-normal-flow-bugbot-…
bugfix-972-forward-explicit-cancellation-into-the-normal-flow-bugbot-…
vypbot commentedon Nov 19, 2026
Progress · 65% estimated
Assessed head
e1b7d2d2· 4/8 supported0 need implementation · 4 need verification or clarification
Verification or clarification needed
Issue · Linked pull request · Full assessment