Ahmed Ibrahim aa6a57dfa2 Stabilize incomplete SSE retry test (#13879) ...

## What changed
- The retry test now uses the same streaming SSE test server used by
production-style tests instead of a wiremock sequence.
- The fixture is resolved via `find_resource!`, and the test asserts
that exactly two outbound requests were sent.

## Why this fixes the flake
- The old wiremock sequence approximated early-close behavior, but it
did not reproduce the same streaming semantics the real client sees.
- That meant the retry path depended on mock implementation details
instead of on the actual transport behavior we care about.
- Switching to the streaming SSE helper makes the test exercise the real
early-close/retry contract, and counting requests directly verifies that
we retried exactly once rather than merely hoping the sequence aligned.

## Scope
- Test-only change.

2026-03-09 22:34:44 -07:00

..

common

feat: support disabling bundled system skills (#13792)

2026-03-09 22:02:53 -07:00

fixtures

…

suite

Stabilize incomplete SSE retry test (#13879)

2026-03-09 22:34:44 -07:00

all.rs

…

cli_responses_fixture.sse

…

responses_headers.rs

chore(otel): rename OtelManager to SessionTelemetry (#13808)

2026-03-06 16:23:30 -08:00