Skip to content

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 21 Sep 13:21
· 91 commits to main since this release
  • The board pane is the fleet's triage surface: what runs next, what is
    running now, and the keys to act on both.
    A task with a run in flight is in
    a Running group above the phases — shown once, not twice — with the time it
    has been going against the timeout it was started with, marked stale past
    it. Everything below is in the order the daemon works it, so the top of
    To Do is the task the next tick picks up, which it was not before.
  • A row names the queue a task came from and the id that queue's own board
    uses — TASK-12 beside myapp, not another truncation of myapp/TASK-12 —
    in a colour that stays with the queue. A fleet with a single queue shows no
    such column. The agent column says the two ways routing can be wrong: yellow
    paused for an agent the scheduler is skipping, red ghost? for a name
    nobody answers to.
  • Three new keys and one new view. v reads the selected task — body,
    criteria and notes, the same renderer as herdr-docket task view — and s
    re-routes it to another agent. x stops the run on the selected row, which
    closes its workspace and ends the task Blocked through the path a cancelled
    run already took — and then says which of the two it found: closed TASK-12's workspace, or its workspace is already gone when the record
    outlived the run. g now shows the roster with each agent busy (and on what)
    or idle, and p pauses or resumes the agent under the cursor: pausing writes
    disabled: to its AGENT.md and never touches a run already in flight — x
    is the key that stops one, and r still runs a paused agent's task by hand.
  • An assignee written @name routes to the agent name. That is how
    Backlog.md prints an assignee and how its CLI accepts one, so the sigil
    reaches the task file; it used to carry on into the router, where the task
    went to nobody while its row looked routed. A name no agent answers to is
    still shown as unknown — the sigil comes off, the name does not.
  • a asks which queue a task belongs in when the fleet has more than one, so
    creating work from the pane no longer fails on a bare task create. Nothing
    in the pane closes a task with a verdict: see
    ADR 0008 for what it shows
    and what it deliberately refuses.