FA-29904 / HTTP retries / Member archive

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 04

Reservation identity violates retry transition semantics

Member previewVariant 4 · 3 implementations · 9 checks per implementation

Case contract

configure(capacity) resets a shared retry pool. reserve(request) consumes one token only for a new reservation; commit spends its token and removes the reservation, abort refunds exactly once, refill is capped. Repeated reserve is idempotent; unknown commit/abort does nothing. Return admissions and available token count.

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
0	`[["reserved", "reserved"], 1, ["global"]]`	`[["reserved", "reserved"], 2, ["b"]]`	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.