FA-30607 / HTTP retries / Member archive

Exactly one logical request completion: Terminal first violates retry transition semantics · case 02

Terminal first violates retry transition semantics

Member previewVariant 2 · 3 implementations · 12 checks per implementation

Case contract

begin resets generation and final result. launch creates next active generation; response(generation,status,payload) accepts only current active attempt. A 2xx result completes immediately, retryable statuses 429/503 leave logical request pending with a retry token, other statuses terminally fail. retry consumes token to launch next attempt. cancel wins if no final result. Once final, every later event except begin is ignored. Return result and number of attempts launched.

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	`[["cancelled", null], 2]`	`[["failure", 400], 2]`	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.