Skip to content

Key-triggered runs: redraw, overlap, and errors #14

Closed

Description

@shayan-ys

Part of the map Map: integration key contract.

Question

A key press must redraw its section at once, not wait for the interval. Decide what happens when a key arrives while that integration's command is running (cancel and rerun, queue, or coalesce), how repeated presses (holding j) are handled, and how a failed key-triggered run is shown relative to the last good frame.

Activity

  1. self-assigned this
    on Oct 9, 2026
  2. shayan-ys commented on Oct 9, 2026

    @shayan-ys
    OwnerAuthor

    Resolution

    Each key press queues its action (FIFO, at most 8) behind any run in progress; runs never overlap, and the queue drains before the next interval run. Results redraw at once. A failed action run keeps the last good rows under the error line and is not retried.

    Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec: Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md (private vault).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions