[WRONG BRANCH] fix: exclude caller aborts from sidecar health

[luvs01]

Motivation

• Sidecar helpers were attributing caller-initiated aborts (client disconnects / WebSocket turn cancels) as upstream connect_error, which incremented pool-account failure counters and could trigger failover.

Description

• Detect caller-initiated cancellation by comparing the original abortSignal reason with the linked sidecar signal and skip health recording when the abort came from the caller in runWebSearch (src/web-search/executor.ts).
• Apply the same caller-abort exclusion in the vision path in describeImage (src/vision/describe.ts).
• Add focused regression assertions to tests/sidecar-abort.test.ts verifying that sidecar work still aborts on the turn but does not record an upstream outcome when the client cancels.

Testing

• Ran the focused tests with bun test tests/sidecar-abort.test.ts, which passed after the changes.
• Ran type checking with bun x tsc --noEmit, which succeeded.
• Ran the privacy scan with bun run privacy:scan, which passed.
• Attempted a full bun run test; an unrelated timeout/failure in a separate management-provider test stopped the full-suite run (not caused by these changes).

---

Codex Task

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 62ce2429-3dad-4ec8-a29d-6993a578ca48

📥 Commits

Reviewing files that changed from the base of the PR and between 57140d6 and 76604f1.

📒 Files selected for processing (3)

• src/vision/describe.ts
• src/web-search/executor.ts
• tests/sidecar-abort.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.

[luvs01]

Superseded by the current-dev implementation in lidge-jun#2403. This obsolete main-based draft should not be merged.