FA-22832 / Autocomplete interactions / Member archive

Undoable autocomplete acceptance: hovering a suggestion creates a completion undo transaction · case 02

The hover completion transition produces an incorrect observable state.

Member previewVariant 2 · 3 implementations · 22 checks per implementation

Case contract

A completion acceptance is one undo transaction containing draft, committed identity and caret. Undo restores the pre-accept snapshot; redo restores the accepted snapshot. A subsequent edit discards redo, transient hover never enters the stack, and history snapshots own their data.

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 hover	`["u1", "p2"]`	`["u1"]`	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.