FA-25913 / Filter interfaces / Member archive

Removed endpoint options are explicitly marked unresolved · case 03

Removed endpoint options are explicitly marked unresolved is violated by the widget projection.

Member previewVariant 3 · 3 implementations · 10 checks per implementation

Case contract

A discrete range selector uses ordered option indices, preserves endpoint option identities across rerender, and renders unavailable selected options as unresolved. This example checks: Removed endpoint options are explicitly marked unresolved.

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	`{"endpoint-payload": ["large", "a"], "full-domain": false, "lower-index": 2, "range-order": false, "unresolved-endpoints": [], "upper-index": null}`	`{"endpoint-payload": ["large", "a"], "full-domain": false, "lower-index": 2, "range-order": false, "unresolved-endpoints": ["a"], "upper-index": null}`	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.