FA-22140 / Autocomplete interactions / Member archive

Multi-value autocomplete tokens: restoring a removed token discards surviving selections · case 05

The undo-remove completion transition produces an incorrect observable state.

Member previewVariant 5 · 3 implementations · 22 checks per implementation

Case contract

Accepting a suggestion appends its identifier once, preserving selection order and independent duplicate labels. Removing a token removes that identity only. Already-selected results are excluded, pending query text is separate from selected values, and capacity is measured in committed identities.

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 undo-remove	`["a"]`	`["a", "b"]`	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.