Matthew Zeng 6d377e96eb Propagate Apps tool refreshes to existing threads (#43900) ...

## Why

Refreshing installed Apps without a thread should update the tools available to existing threads on their next turn.

## What changed

- Publish live tool catalogs to clients with matching transport, auth, protocol, and listing settings within the same account and home directory. Ignore the thread attribution header when matching scopes.
- Adopt updated tools before catalog reads and new calls, preserving running calls and rejecting calls prepared against an outdated catalog revision.
- Keep the newest successful fetch per scope so older refreshes cannot overwrite newer tools, and exclude disk snapshots from live updates.

## Testing

Add regression coverage for refresh propagation to an existing thread without another tools listing, scope and account isolation, out-of-order refreshes, late client startup, and running versus stale prepared calls.

GitOrigin-RevId: 7a5ee34e23742ce374c6647dc8928b76ea622448

2026-09-08 19:56:25 +00:00

..

src

Propagate Apps tool refreshes to existing threads (#43900)

2026-09-08 19:56:25 +00:00

BUILD.bazel

[apps] Add tool_suggest tool. (#14287)

2026-03-11 22:06:59 -07:00

Cargo.toml

Fetch workspace connectors concurrently (#33421)

2026-07-15 20:38:26 +00:00