FAILURE MAP
← Case archive

FA-25765 / Filter interfaces / Member archive

Migrated constraints require complete resolution and review confirmation · case 05

Migrated constraints require complete resolution and review confirmation is violated by the widget projection.

Member previewVariant 5 · 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: Migrated constraints require complete resolution and review confirmation.

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 fixtureActualExpectedOutcome
contract fixture 0{"field-map": "same", "migration-apply": true, "operator-map": "eq", "unresolved-count": 0, "unresolved-retain": [], "version-advance": 2}{"field-map": "same", "migration-apply": false, "operator-map": "eq", "unresolved-count": 0, "unresolved-retain": [], "version-advance": 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.

Sign in to the archive ↗