FA-22335 / Autocomplete interactions / Member archive

Cached autocomplete presentation: cache-backed rows falsely claim the current network response provenance · case 05

The cache-provenance completion transition produces an incorrect observable state.

Member previewVariant 5 · 3 implementations · 22 checks per implementation

Case contract

Cached result presentation is bound to exact query and dependency scope. A cache hit may render immediately but must be marked stale until refreshed. Empty cached results are valid hits. Cache misses preserve no previous-query selectable rows; selected labels are independently retained.

Why this case matters

Autocomplete couples draft text, suggestion identity and asynchronous presentation; this bounded lifecycle model isolates one observable interaction defect.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
normal cache-provenance	`{"epoch": 5, "origin": "network", "query": "pe"}`	`{"epoch": 4, "origin": "cache", "query": "p"}`	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.