FA-25087 / Filter interfaces / Member archive

Result freshness is tied to the accepted filter revision · case 02

Result freshness is tied to the accepted filter revision is violated by the widget projection.

Member previewVariant 2 · 3 implementations · 10 checks per implementation

Case contract

The applied-filter summary distinguishes settled, pending and failed draft updates, and uses the server-acknowledged filter revision for result badges. This example checks: Result freshness is tied to the accepted filter revision.

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	`{"dirty-count": 0, "error-scope": false, "result-fresh": false, "result-label": "updating", "retry-payload": null, "revision-pending": true}`	`{"dirty-count": 0, "error-scope": false, "result-fresh": true, "result-label": "updating", "retry-payload": null, "revision-pending": true}`	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.