FA-25653 / Filter interfaces / Member archive

Explicit empty user filters suppress initial defaults · case 03

Explicit empty user filters suppress initial defaults is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

Default filters are applied only before user intent exists; an explicit cleared state differs from absence, and changes to defaults do not overwrite user-owned settings. This example checks: Explicit empty user filters suppress initial defaults.

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	`{"clear-origin": "user", "default-badge": true, "default-update": ["c"], "initial-default": ["b"], "persist-empty": false, "reset-to-default": ["c"]}`	`{"clear-origin": "user", "default-badge": true, "default-update": ["c"], "initial-default": ["a"], "persist-empty": false, "reset-to-default": ["c"]}`	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.