Eric Traut 95db2cd5d5 Keep remote app-server events deliverable during shutdown (#53155) ...

## Why

Dropping the event receiver before shutdown lets an in-flight notification fail delivery and terminate the worker before it sends the WebSocket close frame.

## What changed

Keep the event receiver alive until `RemoteAppServerClient::shutdown` finishes waiting for the worker, allowing it to process the shutdown command and close the WebSocket.

## Testing

Extend regression tests to verify that an event remains deliverable after shutdown is queued and that the server receives `Message::Close(None)` with an extra notification in flight.

GitOrigin-RevId: ba14bc97ffa3453b7b59660144db6da9e688983d

2026-10-11 15:57:06 +00:00

..

tests

Add connection-bound reply handles for app-server requests (#53049)

2026-10-11 06:08:41 +00:00

lib.rs

Keep remote app-server events deliverable during shutdown (#53155)

2026-10-11 15:57:06 +00:00

path.rs

[1 of 3] Support long raw TUI goal objectives (#27508)

2026-06-11 22:26:31 -07:00

remote.rs

Keep remote app-server events deliverable during shutdown (#53155)

2026-10-11 15:57:06 +00:00

server_request_tests.rs

Add connection-bound reply handles for app-server requests (#53049)

2026-10-11 06:08:41 +00:00

server_request.rs

Add connection-bound reply handles for app-server requests (#53049)

2026-10-11 06:08:41 +00:00