FA-25707 / Filter interfaces / Member archive

Undo is unavailable while its constraint transaction is applying · case 02

Undo is unavailable while its constraint transaction is applying is violated by the widget projection.

Member previewVariant 2 · 3 implementations · 10 checks per implementation

Case contract

Each filter edit transaction records before and after snapshots. Undo/redo moves whole constraint snapshots and does not resurrect history after a new branch edit. This example checks: Undo is unavailable while its constraint transaction is applying.

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	`{"branch-future": [], "noop-history": [["a"]], "redo-snapshot": ["a", "b"], "undo-available": true, "undo-snapshot": ["a"], "undo-tail": []}`	`{"branch-future": [], "noop-history": [["a"]], "redo-snapshot": ["a", "b"], "undo-available": false, "undo-snapshot": ["a"], "undo-tail": []}`	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.