Rasmus Rygaard eb49f491c6 Add explicit remote executor connection refresh (#40710) ...

## Why

Planned executor replacement needs a fresh session without waiting for the old
session's transient-disconnect recovery to finish.

## What changed

- Add `Environment::refresh_connection` for remote Noise registry-backed
  environments. It performs a fresh registry lookup, reuses a healthy session
  when the executor identity is unchanged, and connects to a replacement when
  it has changed.
- Retire superseded sessions and connection attempts so they cannot publish
  stale state, accept late RPC results, or replay outstanding work.
- Preserve the existing environment and filesystem handles while replacing the
  underlying client, and require a live status probe before refresh succeeds.

## Testing

Add coverage for replacement and session reuse, recovery and connection races,
lookup and handshake failures, handle preservation, and late RPC responses.

GitOrigin-RevId: f1d11208cbfe8af8feb25f6b6b8100da82169a99

2026-08-25 21:23:17 +00:00

..

tests

Cache shell snapshots in the exec server (#39756)

2026-08-20 17:39:06 +00:00

accepted_tests.rs

Support host-accepted exec-server WebSockets (#39786)

2026-08-20 19:33:48 +00:00

accepted.rs

Add explicit remote executor connection refresh (#40710)

2026-08-25 21:23:17 +00:00

http_client.rs

Decouple exec-server HTTP from reqwest types (#35059)

2026-07-24 00:53:05 +00:00

http_response_body_stream.rs

Decouple exec-server HTTP from reqwest types (#35059)

2026-07-24 00:53:05 +00:00

network_policy_audit.rs

Route executor policy audits through log-only telemetry (#38800)

2026-08-15 19:34:50 +00:00

route_aware_http_client.rs

Resolve HTTP MCP bearer tokens in executor environments (#39926)

2026-08-21 12:50:15 +00:00

rpc_http_client.rs

Resolve selected capability roots without starting executors (#31581)

2026-07-09 11:17:05 +01:00