Stop a late search response replacing the current queue
On a slow connection, searching DL-42 and immediately clearing the field sometimes repopulates the screen with DL-42 results. Make response ownership follow the active query.
- Focused work estimate
- 1h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Async state · Race conditions · Testing
Estimated field mix
- Frontend100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
The fictional Alder support team handles billing and delivery conversations in a browser console. Agents keep several tickets open, share filtered queues, and work through unreliable office Wi-Fi. The API contract returns ticket revisions and cursor-based pages; work stays within the console and its test adapter.
Setup prerequisites
- A ticket-list and reply API contract to implement or stub
- Synthetic conversations across two organizations with revision conflicts
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Only a response for the active query updates rows, counts, or errors.
- Changing filters abandons the previous page cursor.
- Unmounting the queue prevents late responses from changing visible state.
Implementation constraints
- Guard against adapters that resolve after cancellation.
Verification to include
- Resolve two requests in reverse order and confirm the last selection wins.
- Reject a superseded request after the current one succeeds; no stale error appears.
Deliverables
- Query ownership fix and deterministic out-of-order response test
Rollout and recovery
Canary with the support pilot; revert the coordinator if current-query results stop loading.
Value of the work
For the engineer: Practice state ownership, asynchronous races, accessible interaction, and recovery in bounded changes.
For the team: Inspect how an engineer protects agent work and handles failures that interrupt support operations.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.