FA-24848 / Filter interfaces / Member archive

Draft dirtiness ignores ordering but retains constraint identity · case 03

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

An Apply/Cancel filter panel keeps draft and committed constraints separate; validation and revision determine whether a draft may be published. This example checks: Draft dirtiness ignores ordering but retains constraint identity.

Why this case matters

Filter-widget state and serialization must preserve user constraints while the view changes.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
contract fixture 0	`{"apply-gate": true, "apply-payload": ["b", "a"], "cancel-target": {"draft": ["a", "b"], "errors": [], "open": false}, "conflict-banner": false, "dirty-order": true, "open-copy": ["a", "b"]}`	`{"apply-gate": true, "apply-payload": ["b", "a"], "cancel-target": {"draft": ["a", "b"], "errors": [], "open": false}, "conflict-banner": false, "dirty-order": false, "open-copy": ["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.