FA-30375 / HTTP retries / Member archive

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 05

Success terminal violates retry transition semantics

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

begin(ordinary retries,refresh allowance) starts a request. network_failure spends ordinary allowance, challenge spends refresh allowance only if no refresh in flight, refreshed(generation) completes only current refresh generation and records auth replay. While refreshing network failures wait. success terminates both budgets; late refresh is ignored. No credentials are represented.

Why this case matters

Offline deterministic model of HTTP request retries.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
3	`[[["refresh", 1], "stale", "retry", "auth-exhausted"], 4, 0]`	`[[["refresh", 1], "stale", "terminal", "terminal"], 5, 0]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.