You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7743291
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): refuse launch-confirmation runner steps the deadline cannot hold
The deadline only shrank the alert payload's timeout before the readiness
preflight, and a spent deadline still dispatched with a 1 ms floor. An alert
runner command now carries a host-side deadline that the exchange turns into
the runner timeout right before the payload, after the preflight; a press
left less than its whole watchdog, or any command left no time, is refused
unsent with the typed `runner_command_deadline_spent`. Once the deadline has
passed, the launch confirmation sends nothing, and a press refused unsent
leaves the confirmation unanswered. Runner startup and transport overhead stay
outside this bound.
Refs #3861
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments