A crew route refused for its key or for payment was held back until a later call on it answered. A pinned role or the one model is never sent to such a route, so reconnecting or adding credit changed nothing. Now a refusal is lifted by a different credential than the one refused (a print taken at dispatch, CrewDispatchFor / LogCrewRouteSent; router CrewRecord.fail_cred), by a credential change after an unprinted refusal (profile crew-credentials.json: print and since per provider, written by WriteAPIKey, WriteSources, ConnectCodex and the app's keys, and when route health reads; a first sighting is a baseline), or for payment by a positive balance read after the refusal. The same key written again lifts nothing; there is no timer. |
config.LogCrewRoute names no credential and never guesses one from the settings at response time; a caller that took a CrewDispatch when it sent the call uses LogCrewRouteSent. |
config.CrewAccountState had no read time. It now has ReadAt; a positive balance with no ReadAt, or read before a payment refusal, lifts nothing. |
A balance read was dated when it finished, so a read that began before a payment refusal and answered after it lifted the refusal. config.WriteCreditsReadingAt(profileDir, key, reading, observedAt) now dates it; the v3 credit reader passes the time it began; a zero time lifts nothing and a time after now is refused (ErrCreditsObservedAhead). WriteCreditsReading is WriteCreditsReadingAt at now, for readings that were not just fetched. |
Only route health could judge whether a refusal still held. config.CrewRefusalApplies(profileDir, failure) answers it for one router.CrewRouteOutcome with the same facts; failures other than auth and payment always apply, and a failure with no time is lifted only by its print. |