Ahmed Ibrahim f046cf35df Scope model catalog caches to the current provider and auth identity (#43906) ...

## Why

Switching providers or authentication could reuse a previous identity's model catalog, including its default service tier. An in-flight refresh could also overwrite a newer account's catalog after cache storage completed.

## What changed

- Require a matching provider and auth identity for disk and in-memory catalog reuse. Treat legacy entries without an identity as cache misses and fall back to bundled metadata when the in-memory identity no longer matches.
- Recheck identity after fetching and storing a catalog before publishing it.
- Renew cache freshness only when the client version, identity, and ETag match the stored entry.
- Update cache fixtures to include the configured provider and auth identity.

## Testing

Add regression coverage for provider and auth switches, credential rotation, legacy and mismatched cache entries, conditional TTL renewal, and an account switch during cache storage. Verify that API-key requests do not inherit a ChatGPT catalog's default `service_tier`, while explicit tier selection still works.

GitOrigin-RevId: e15d7ffff238d951d7a1c6a68381cbb479994146

2026-09-08 20:37:30 +00:00

..

src

Scope model catalog caches to the current provider and auth identity (#43906)

2026-09-08 20:37:30 +00:00

BUILD.bazel

build: run buildifier from just fmt (#28125)

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

Cargo.toml

Use static instructions for the Default collaboration mode (#42904)

2026-09-05 01:25:06 +00:00

models.json

Exclude base instructions from the bundled model catalog (#43604)

2026-09-07 22:11:52 +00:00

prompt.md

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

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