FA-24367 / Client state / Member archive

Editor autosave revision reconciliation: Unsent field difference · case 02

Unsent field difference.

Member previewVariant 2 · 3 implementations · 70 checks per implementation

Case contract

Autosave snapshots both revision and field set. A successful old save acknowledges its sent revision without clearing newer edits. Offline and composition defer new saves, and conflicts preserve local edits for explicit resolution. Operation unsent-field-difference 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
unsent-field-difference scenario 1	`["a", "b"]`	`["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.