FA-7999 / Form lifecycle / Member archive

Form dirty-field bookkeeping: Removing a field leaves a phantom dirty baseline entry · case 04

Removing a field leaves a phantom dirty baseline entry.

Member previewVariant 4 · 3 implementations · 11 checks per implementation

Case contract

Edits change draft only; reset restores baseline; commit accepts draft; unmount removal clears both; dirty comparison includes additions and removals.

Why this case matters

A deterministic model of form dirty-field bookkeeping; this isolates one interface invariant without requiring a browser.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
remove	`[{"a": 1, "b": 2}, {"b": 2}, ["a"]]`	`[{"b": 2}, {"b": 2}, []]`	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.