FA-25504 / Filter interfaces / Member archive

False-only filtering remains an active constraint · case 04

False-only filtering remains an active constraint is violated by the widget projection.

Member previewVariant 4 · 3 implementations · 10 checks per implementation

Case contract

A boolean filter has any/true/false states; false is an active constraint, and the UI does not coerce string labels into booleans. This example checks: False-only filtering remains an active constraint.

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	`{"active-false": false, "choice-caption": "No", "false-badge": "negative", "hydrate": "any", "invert": "true", "typed-operand": false}`	`{"active-false": true, "choice-caption": "No", "false-badge": "negative", "hydrate": "any", "invert": "true", "typed-operand": false}`	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.