FA-10504 / Caching / Member archive

Failed background refresh leaves a permanent in-flight marker · case 04

Failed background refresh leaves a permanent in-flight marker.

Member previewVariant 4 · 3 implementations · 4 checks per implementation

Case contract

Completion, successful or failed, removes only its own refresh key from the in-flight registry; output is a sorted unique key list.

Why this case matters

A deterministic cache state transformation. Inputs are copied or treated as immutable; no remote storage, real clock, or concurrent interleaving is simulated.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
fixture 1	`["a", "b"]`	`["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.