FA-30218 / HTTP retries / Member archive

In-flight retry policy capture: Cap boundary violates retry transition semantics · case 03

Cap boundary violates retry transition semantics

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

configure(version,cap,statuses) sets current policy. begin(request) snapshots it with zero retries used; failure(request,status) uses that request snapshot and admits retry only for configured statuses below cap. update configuration affects later requests only. finish removes request; unknown failures report unknown. Return retry decisions with pinned policy version.

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
2	`[["retry", 3], ["retry", 3], ["retry", 3]]`	`[["retry", 3], ["retry", 3], ["exhausted", 3]]`	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.