The remote control client can compress requests, cancel retries and read one agent's events.
What's wrong with this entry?
The client that talks to the Remote Control worker can send requests through an injectable compressing fetch when one is supplied, falling back to plain fetch otherwise. It also gained a read of a worker's internal events scoped to one agent, and its retry helpers can now be cancelled.
- The new read hits
/worker/internal-eventsfiltered by agent, pages 1000 items at a time, and has its own attempt cap and abort signal. - The retry and pagination helpers take a maximum attempt count and a signal, combined with the existing 30 second timeout, and stop early when aborted.
- Response bodies are drained through a helper rather than cancelled directly.
/worker/internal-events
Strings lifted out of the shipped bundle, so the claim above can be checked against them.