FA-30829 / HTTP retries / Member archive

Retry hook failure containment: Observer only failure violates retry transition semantics · case 04

Observer only failure violates retry transition semantics

Member previewVariant 4 · 3 implementations · 8 checks per implementation

Case contract

begin(cap) starts pending request. fail(eligible,before-hook-ok) calls retry hook only for eligible failures with remaining cap; a failing hook terminally records hook-error without spending retry budget. Otherwise admit consumes one cap and enters waiting. wake starts it. success(observer-ok) stores success before observer invocation; observer failure is diagnostic only and never creates a retry. cancel is terminal. Return lifecycle decisions and remaining cap.

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
1	`[["scheduled", "ignored", "started", "success", "ignored"], 1, "done"]`	`[["scheduled", "ignored", "started", "success", "observer-error", "ignored"], 1, "done"]`	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.