Rennie 559264d92e Preserve invalid_prompt as a distinct error classification (#47353) ...

## Why

`invalid_prompt` responses were classified as generic invalid requests, losing the server's specific error classification.

## What changed

Add `InvalidPrompt` variants to the API and core error types and serialize the core protocol classification as `invalid_prompt`. Recognize the code in HTTP 400 responses, wrapped WebSocket errors, and SSE `response.failed` events while preserving server messages and keeping the error non-retryable. Map it to `other` in the app-server v2 protocol.

## Testing

Extend coverage for typed error mapping, missing and blank messages, protocol conversion, and guardian retry handling. Exercise HTTP and SSE failures in core integration tests, asserting the error message, serialized classification, and a single request without retry.

GitOrigin-RevId: 5d9a299a013b06158a4dc27a4054f3dbc5fd0f4d

2026-09-22 20:07:50 +00:00

..

src

Preserve invalid_prompt as a distinct error classification (#47353)

2026-09-22 20:07:50 +00:00

BUILD.bazel

extract models manager and related ownership from core (#16508)

2026-04-02 23:00:02 -07:00

Cargo.toml

extract models manager and related ownership from core (#16508)

2026-04-02 23:00:02 -07:00