FA-29413 / HTTP retries / Member archive

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 03

Reopening after a completed transaction retains terminal state

Member previewVariant 3 · 3 implementations · 7 checks per implementation

Case contract

Events open, send(nonnegative bytes), fail(known_unprocessed bool), retry, succeed. State tracks whether any bytes were emitted by a one-shot stream. A failure known unprocessed does not restore consumed stream bytes. Only an open stream with zero consumed bytes may retry. Terminal success closes the logical request. Output one decision per retry and terminal success.

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	`["terminal", "terminal", "terminal"]`	`["no-failure", "retry", "no-failure"]`	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.