FA-23214 / Autocomplete interactions / Member archive

Search normalization versus displayed autocomplete text: result query is compared with unnormalized visible draft · case 04

The match-key completion transition produces an incorrect observable state.

Member previewVariant 4 · 3 implementations · 22 checks per implementation

Case contract

This controlled ASCII picker normalizes lookup by stripping outer whitespace and lowercasing, while preserving exact user draft and canonical option labels for display and commit. Matching offsets apply to the normalized query only; a normalization-equivalent edit still advances the display epoch.

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 match-key	`false`	`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.