FA-23573 / Client state / Member archive

Persisted client snapshot admission: Serialized field order · case 03

Serialized field order.

Member previewVariant 3 · 3 implementations · 60 checks per implementation

Case contract

Persist only declared nontransient keys. Missing defaults are filled without replacing null/falsy data. Older schema versions migrate through each intermediate step; future versions stay read-only and keep their version stamp. Operation serialized-field-order 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
serialized-field-order scenario 1	`["a", "b", "temp"]`	`["a", "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.