A probe that reached the executable but got no verdict (Claude's
--version past its deadline, a crashed process) stayed authoritative as
an error until the periodic refresh, five minutes by default, or a manual
refresh. The managed provider now retries such a probe up to three times,
thirty seconds apart, through the existing demand-aware serialized
refresh path. A conclusive probe resets the budget; an exhausted budget
leaves the periodic refresh in charge, so a provider that keeps failing
is not probed without bound.

Inconclusive is a structural check on the snapshot (enabled, installed,
error status, unknown auth) rather than message text, so Codex's timeout
snapshot qualifies too and an unauthenticated verdict never retries.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>