FA-21984 / Autocomplete interactions / Member archive

Completion debounce lifecycle: successful flush leaves the same query ready to emit again · case 04

The after-flush completion transition produces an incorrect observable state.

Member previewVariant 4 · 3 implementations · 22 checks per implementation

Case contract

A new draft replaces the pending autocomplete job and its deadline. A deadline emits only its exact draft epoch; flush emits pending text once; cancellation discards pending text. Leading search marks its own query, and composition suspends timers. Time values are integer ticks.

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 after-flush	`{"pending": "pe", "sent": "pe"}`	`{"pending": null, "sent": "pe"}`	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.