FA-10472 / Caching / Member archive

An old fetch repopulates a cache after invalidation · case 02

An old fetch repopulates a cache after invalidation.

Member previewVariant 2 · 3 implementations · 4 checks per implementation

Case contract

Publish fetched value only when its captured generation equals the current generation; otherwise preserve the complete cache.

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": "stale"}`	`{}`	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.