Answers arriving for a replaced prompt are discarded instead of applied to the wrong request.
What's wrong with this entry?
The worker-sandbox network access prompt and the MCP elicitation prompt are now identified by a stable derived key rather than the raw request id, and both check whether they are still current before acting, so a response arriving for a prompt that has already been replaced is discarded rather than applied to the wrong request.
- The sandbox prompt's response handler returns false without responding when the guard says it is stale; the elicitation prompt bails on anything other than a cancel.
Waiting for leader to approve network access to
Strings lifted out of the shipped bundle, so the claim above can be checked against them.