FA-23532 / Client state / Member archive

Persisted client snapshot admission: Default overlay order · case 02

Default overlay order.

Member previewVariant 2 · 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 default-overlay-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
default-overlay-order scenario 1	`{"a": 0, "b": true, "temp": 7}`	`{"a": 2, "b": false, "temp": 7}`	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.