FA-25758 / Filter interfaces / Member archive

Schema versions advance only after all rows resolve · case 03

Schema versions advance only after all rows resolve is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Saved filter migration follows explicit field and operator maps, preserves unresolved rows for review, and advances the schema version only after every row is migrated. This example checks: Schema versions advance only after all rows resolve.

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	`{"field-map": "new", "migration-apply": false, "operator-map": "contains", "unresolved-count": 2, "unresolved-retain": [{"resolved": false}, {"resolved": false}, {"resolved": true}], "version-advance": 2}`	`{"field-map": "new", "migration-apply": false, "operator-map": "contains", "unresolved-count": 2, "unresolved-retain": [{"resolved": false}, {"resolved": false}, {"resolved": true}], "version-advance": 1}`	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.