FA-24684 / Client state / Member archive

Client preference layer resolution: Layer precedence · case 04

Layer precedence.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

Client preferences overlay defaults, device, workspace and session in that order. Workspace locks exclude session writes. Removing an override reveals the lower layer; serialization preserves its own layer and explicit null/falsy values. Operation layer-precedence 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
layer-precedence scenario 1	`{"size": 1, "theme": "light"}`	`{"size": 4, "theme": ""}`	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.