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 c0ef0fa
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(ios-runner): one resend budget per error class, no status probe for structured replies
Review follow-ups on the RUNNER_BUSY resend window:
- a structured runner reply already says whether the command ran, so
executeRunnerCommand no longer sends a lifecycle status probe for it; the
raw refusal reaches the caller's resend policy unwrapped. The predicate
(isStructuredRunnerFailure) moves from runner-session.ts to the contract.
- the busy refusal is a row in RUNNER_ERROR_RULES (runner_busy_refusal, with
a drainResend verdict) so isRunnerBusyError reads the table like every
sibling predicate and diagnostics name the refusal instead of a flag.
- runner-client.ts states both resend budgets in one place
(readOnlyResendBudget) instead of splitting the busy cap into maxAttempts
and the transport cap into the predicate; the window is documented as a
heuristic with the log marker to tune it by.
- the resend tests reuse makeRunnerSession from the shared fixtures and no
longer encode status probes between attempts.
0 commit comments