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 status-card dispatcher throws when an accepted workflow dispatch returns no workflow_run_id. The worker may still publish, but the caller cannot acknowledge it. The path currently fails closed; source-repository default installation is still pending.
Scope and acceptance criteria
- Recover only one provably matching accepted run using existing repository, workflow/ref and handoff operation identity. Never adopt a merely recent run, repeat the POST blindly, or acknowledge an ambiguous/foreign worker.
- At least eight controlled-provider cases cover direct ID, unique accepted 204 lookup, no match, ambiguous matches, wrong workflow/ref, unavailable permissions, transient read failure and replay after an accepted dispatch.
- Keep source/head/policy validation and serialized publication. Failure retains the last verified comment and Check fallback, issues no completed publication receipt, and gives a safe retry action.
- A bounded acknowledgment lookup is distinct from model investigation; add no verifier research deadline, token limit or new public configuration.
Reproducing the issue
Return HTTP 204 with no body from the dispatch adapter, then expose a matching workflow_dispatch run through a controlled GitHub read port. Compare with setup_permission_actions_probe.ts, which already handles accepted dispatch discovery.
Pinned source references:
- src/infrastructure/github/github_bugbot_status_card_dispatch.ts
- src/infrastructure/setup_permission_actions_probe.ts
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: Operational follow-up.
- 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/bugbot/failure-scenarios.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
[-]Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID[/-][+]🐛 - Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID[/+]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.[-]🐛 - Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID[/-][+]🐛🧑💻 - Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID[/+]vypbot commentedon Nov 19, 2026
Implementation plan
Acceptance: Controlled-provider tests pass for all eight specified cases; only a unique run matching repository, workflow/ref, and handoff operation is acknowledged, while unresolved cases preserve the last verified comment and Check fallback, issue no completed publication receipt, and expose a safe retry action.
Need something else? Mention the bot with a question or use
/copilot help.bugfix-976-recover-a-uniquely-identifiable-accepted-bugbot-status-dis…
vypbot commentedon Nov 19, 2026
Progress · 60% estimated
Assessed head
1b024481· 3/8 supported0 need implementation · 5 need verification or clarification
Verification or clarification needed
Issue · Linked pull request · Full assessment