🐛🧑‍💻 - bug Bugbot persists a review then fails reconciliation with opaque provider.unavailable #646

Is there an existing issue for this?

• I have searched the existing issues.

Which actions are affected?

Pull Request

Which platforms are affected?

Linux

Description

Dogfooding vypdev/copilot@v3 on platform PR #198 persisted a native Bugbot review and inline finding, then failed the workflow and Copilot / Review with only the generic retryable provider.unavailable message. The aggregate says one or more finding mutations could not complete. The logs do not identify the failed mutation, affected finding, provider operation, HTTP status, or safe recovery boundary.

This report is about the incomplete reconciliation and unusably vague diagnostic. It does not assume a particular GitHub/API root cause or ask Copilot to ignore incomplete evidence. Previous similar diagnostic reports #547 and #611 are closed and concern different progress/comparison paths; no matching finding-publication report was found.

Observed effects on the same exact head fb0a42edad02f9fd89088e5754cd5cf2bfddb44d:

• Five bounded analysis partitions completed successfully; analysis took 65,093ms. The failure occurred after native review publication, during the publication/projection/reconciliation portion of the run.
• Native review ID 5597906436 and inline finding comment 4335387140 exist.
• Finding ID: backend/Dockerfile:20:healthcheck-requires-curl; fingerprint fp-dacef490, semantic fingerprint sf-5f2f6b3d.
• Telemetry reports candidateFindings=1, publishedFindings=0, findingStates.open=1, outcome=failed although the native review/comment exists. This may reflect an incomplete later transition; the diagnostic does not reveal which one.
• The aggregate status says Bugbot could not complete one or more finding mutations.
• A separate coverage limitation is reported: human-conversation retained 3 items, truncated 1, limitReached=true; all 57 diff files and all 5 analysis partitions are complete. The two limitations should remain distinguishable, with the exact truncated source identified for safe recovery.

The finding itself is a verified false positive: the actual built image contains /usr/bin/curl (curl 8.18.0), the configured readiness probe succeeds, and backend plus dependent console are healthy. Adoptium's official Ubuntu 26.04 JRE Dockerfile explicitly installs curl. We are handling the finding through the documented evidence/dismissal flow rather than adding a redundant package installation or weakening checks. That false positive does not explain the reconciliation failure.

Expected: retain truthful incomplete/failed evidence, but expose a sanitized actionable failure record (stage, finding ID, operation and provider status/reference) and a bounded recovery route. A retry after provider recovery must reconcile the existing native publication without duplicate reviews/threads, lost dismissal state, or false complete coverage.

Reproducing the issue

1. Inspect workflow run 39579227152, job 119152380485, attempt 1. It reviews the exact head above in a same-repository human-authored PR.
2. Observe all five analysis partitions finishing and the native review/inline comment appearing.
3. Observe the aggregate publication reporting failed finding mutations, followed by generic provider.unavailable and a failed Copilot / Review.
4. Compare the native review/comment IDs with telemetry's zero published findings. No detailed failed provider operation is logged.

Suggested regression: fault-inject a provider failure after native review creation but before marker/thread reconciliation; verify explicit sanitized diagnostics, retained effects, conservative status and idempotent retry. Also verify the diagnostic can distinguish a bounded conversation truncation from a failed finding mutation. This fault-injection test is a proposed upstream reproduction; it has not been run in the consumer repository.

copilot Version

3.9.3. Action vypdev/copilot@v3 resolved to f7f68e699a7f7cea46e0da62388ec1a643908ae9. Planner/reviewer: Codex, OpenAI gpt-6-luna. Runner: self-hosted Linux ubuntu-runner-4; no language-specific operation was needed for this review.

Relevant Log Output

Bugbot reviewer completed partition 5/5.
Bugbot reviewer completed in 65093ms.
Bugbot workflow completed in 74522ms.
[bugbot.telemetry] candidateFindings=1 publishedFindings=0 findingStates.open=1 outcome=failed
Publishing result: 3 result(s), 4 step(s), 1 error(s).
Published Copilot / Review Check Run for fb0a42edad02f9fd89088e5754cd5cf2bfddb44d.
Impact: The provider was temporarily unavailable.
Error code: provider.unavailable
Action: Retry when the provider is available.
Retained state: Existing persisted state and completed external effects were preserved.
Retryable: Yes
Reference: a67cf9de-2a9c-4ba4-aa06-0f19e514e59c

Additional context and comments

Consumer: Kotlin/Ktor + Astro/Svelte monorepo; 57 changed files, 3,365 changed lines. Docker/Supabase foundation work is under review; no deployment, secrets, database contents or credentials are included in this report. Ordinary backend/frontend CI is independent and continues. The report is intentionally limited to observed evidence; the underlying provider/API failure is not established by the available diagnostics.