FA-23380 / Client state / Member archive

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 05

Absent dirty keys retain hydration ownership.

Member previewVariant 5 · 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 dirty-pruning 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
dirty-pruning scenario 6	`["z"]`	`[]`	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.