Abhinav 067249a283 Preserve provider model catalogs when refreshes fail (#55958) ...

## Why

A failed provider catalog refresh could discard model metadata and disable tool search on subsequent turns, even after a successful discovery.

## What changed

Keep the last successful catalog, ETag, and original freshness when refreshes fail without an access rejection. Continue invalidating cached catalogs for HTTP `401`/`403`, rejected refresh tokens, and gateway credentials that require login. Distinguish `GatewayLoginRequired` from login in progress so only the former invalidates the catalog.

Successful empty responses remain authoritative, and cached catalogs remain scoped to the provider and authentication identity.

## Testing

Add regression coverage for catalog preservation across refresh errors and restarts, access rejection invalidation, identity isolation, and tool search and instruction stability on the next turn after a failed refresh.

GitOrigin-RevId: 9dd7c73ac2cc1fd49664efd93b839baa94e05c49

2026-10-21 18:43:15 +00:00

..

src

Preserve provider model catalogs when refreshes fail (#55958)

2026-10-21 18:43:15 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

2026-06-13 21:43:39 -07:00

Cargo.toml

Centralize model-message resolution and rendering in codex-prompts (#46026)

2026-09-16 21:01:13 +00:00

models.json

Remove legacy personality template metadata (#51223)

2026-10-06 01:46:33 +00:00

prompt.md

chore(core) rm AskForApproval::OnFailure (#28418)

2026-06-23 12:13:54 -07:00