FA-23387 / Client state / Member archive

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 02

An empty snapshot remains permanently loading.

Member previewVariant 2 · 3 implementations · 60 checks per implementation

Case contract

Server snapshot supplies untouched keys; pre-hydration edits win only for dirty keys. Missing and null differ. Revision, roots, readiness and replay are separate hydration facts. Operation hydration-status 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
hydration-status scenario 2	`"hydrated"`	`"waiting"`	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.