FA-26314 / Filter interfaces / Member archive

Import staging validates field identity without dropping falsy operands · case 04

Import staging validates field identity without dropping falsy operands is violated by the widget projection.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

Importing filter configurations stages known and unresolved constraints, applies an explicit duplicate policy, and requires review when scope or version differs. This example checks: Import staging validates field identity without dropping falsy operands.

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	`{"duplicate-policy": [{"field": "gone", "value": 2}], "import-replacement": [{"field": "gone", "value": 2}], "publish-reviewed": false, "review-trigger": false, "staged-known": [{"field": "gone", "value": 2}], "unresolved-review": [{"field": "gone", "value": 2}]}`	`{"duplicate-policy": [{"field": "gone", "value": 2}], "import-replacement": [{"field": "gone", "value": 2}], "publish-reviewed": false, "review-trigger": false, "staged-known": [], "unresolved-review": [{"field": "gone", "value": 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.