Keep interrupts responsive during host service-tier updates (#60644)

## Why

Waiting for host acceptance of a service-tier update in the submission loop can block interrupts while the host receipt is pending.

## What changed

Move the host acceptance wait out of the submission loop while keeping explicit thread settings replies pending until acceptance completes. Report handoff failures to the caller while preserving the locally committed settings, and allow a subsequent explicit request for the same tier to retry a failed handoff.

## Testing

Add a WebSocket regression test covering interrupts with pending host receipts, failure reporting, same-tier retries, and continued thread operation after startup caller cancellation.

GitOrigin-RevId: 1b27d156eba3ebb47e717a987f41f4f595635be8
This commit is contained in:
rhan-oai
2026-11-10 19:13:55 +00:00
committed by copyberry
parent 3f797555cd
commit 30b42cb802
8 changed files with 302 additions and 33 deletions
+7 -4
View File
@@ -8,7 +8,7 @@ use futures::FutureExt;
use futures::future::BoxFuture;
use futures::future::Shared;
pub(crate) type ServiceTierAcceptance = Shared<BoxFuture<'static, ()>>;
pub(crate) type ServiceTierAcceptance = Shared<BoxFuture<'static, Result<(), String>>>;
/// The host's view of the service tier shared within an agent session.
///
@@ -27,9 +27,12 @@ pub trait AgentServiceTier: Send + Sync {
/// Hand off the committed tier in call order and return a receipt for local acceptance.
/// Core calls this method under its commit locks: the handoff must be fast and nonblocking.
/// Drive the update independently of the receipt: dropping the receipt only cancels the wait.
/// Core awaits it outside the state and registry locks. Explicit settings updates that
/// request the same committed tier share this receipt until the tier changes.
fn update(&self, service_tier: Option<String>) -> BoxFuture<'static, ()>;
/// Core waits outside the state and registry locks. `Ok(())` confirms local acceptance.
/// `Err` leaves acceptance unconfirmed and carries a caller-safe message. Core surfaces it
/// in an explicit thread settings reply. A later settings request with a reply can hand off
/// the same tier again after Core observes a failed receipt. The host must preserve commit
/// order and tolerate repeated handoffs.
fn update(&self, service_tier: Option<String>) -> BoxFuture<'static, Result<(), String>>;
}
pub(crate) fn host_child_uses_shared_service_tier(session: &Session) -> bool {