FA-24044 / Client state / Member archive

Observable client resource cache: Invalidate one resource · case 04

Invalidate one resource.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

Client cache presence is independent of payload truthiness. Stale data remains visible during background refresh; first-load status requires absent data. Observers retain resources, and invalidation is idempotent per key. Operation invalidate-one-resource has the six explicit input/output oracles below.

Why this case matters

An offline client lifecycle model that isolates a state-management defect without DOM rendering or network services.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
invalidate-one-resource scenario 6	`["a"]`	`["b", "a"]`	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.