Skip to content

🐛🧑‍💻 - Recover a uniquely identifiable accepted Bugbot status dispatch without a returned run ID #976

Description

@efraespada

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:

copilot Version

Unreleased develop at ccefb27627cd627ccdb7d5666fd174c2ac1da07b (PR #951); this is not a released or activated profile.

Additional context and comments

Priority and dependencies

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.

Activity

  1. added
    bugSomething isn't working
    bugfixSomething isn't working
    priority: mediumImportant but not urgent, should be addressed soon.
    on Nov 19, 2026
  2. added theissue type on Nov 19, 2026
  3. moved this to Todo in vypdevon Nov 19, 2026
  4. changed the title [-]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[/+] on Nov 19, 2026
  5. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    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 help to see the available commands, or mention @vypbot with your question.

  6. moved this from Todo to In Progress in vypdevon Nov 19, 2026
  7. added
    branchedIndicates that a branch has been created for this issue.
    on Nov 19, 2026
  8. changed the title [-]🐛 - 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[/+] on Nov 19, 2026
  9. added
    state:workingWork can proceed on the verified branch or without a branch.
    on Nov 19, 2026
  10. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Implementation plan

    Current status: Ready to start. No action is required from maintainers before implementation.

    1. Ground the recovery contract
      • Review the status-card dispatcher, its GitHub read port, setup_permission_actions_probe.ts, and the owning Bugbot SDDs.
      • Define the accepted-run identity from repository, workflow, ref, and handoff operation; preserve source/head/policy checks and serialized publication.
    2. Recover an accepted run safely
      • Keep a returned workflow_run_id as the direct path; after an accepted response without an ID, perform a bounded lookup and adopt only one exact identity match.
      • Never repeat the dispatch POST or adopt a recent, ambiguous, or foreign run; fail safely when lookup permissions or reads are unavailable.
    3. Preserve failure and retry behavior
      • On unresolved acknowledgment, retain the last verified comment and Check fallback, issue no completed publication receipt, and provide a safe retry action.
      • Keep acknowledgment lookup bounded and separate from model investigation limits and public configuration.
    4. Add controlled-provider coverage
      • 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.
      • Assert request counts, exact run identity, retained publication state, absent receipt, and retry guidance for failure cases.
    5. Align specifications and documentation
      • Update the catalogued SDD, tests, and docs/bugbot/failure-scenarios.mdx together if the public contract changes; validate specifications.
      • After code changes, update Graphify and retain the repository's coverage and contract gates.

    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.

  11. added
    size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.
    on Nov 19, 2026
  12. vypbot commented on Nov 19, 2026

    @vypbot
    Contributor

    Progress · 60% estimated

    Assessed head 1b024481 · 3/8 supported
    0 need implementation · 5 need verification or clarification

    Verification or clarification needed

    Issue · Linked pull request · Full assessment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

60%Progress: 60%branchedIndicates that a branch has been created for this issue.bugSomething isn't workingbugfixSomething isn't workingin-progressStart work on an admitted issue.priority: mediumImportant but not urgent, should be addressed soon.size: XXLIndicates an extremely large task or issue that requires significant time and effort to complete.state:workingWork can proceed on the verified branch or without a branch.

Type

Projects

  • Status
    In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions