Board

The Board is the GUI’s Kanban view of task_lifecycle work plus the locally parked backlog. One card is rooted in one GitHub issue; its latest task run decides the column. As the workflow advances, the card moves.

The Board is a GUI surface. The TUI equivalent is the Activity/Dashboard run list.

Columns

The board has eight columns:

Column	Contents
Backlog	Local parked items that are not issues yet
Queued	Issues waiting for a worker slot, plus a run still at triage
In progress	The implement, CI-fix, and rebase steps
Review	Waiting on CI checks
Deploy	Staging deploy/healthchecks, merge, production deploy/healthchecks, revert
Done	Completed runs
Failed	Failed or terminated runs
Archived	Cards you retired from the stage columns

Step-to-column mapping is exact:

• backlog and waiting_for_worker → Queued
• implementing, fixing_ci, rebasing_from_main, waiting_for_rebase_worker, waiting_for_ci_fix_worker → In progress
• waiting_for_ci_checks → Review
• deploying_to_staging, staging_healthchecks, merging_pr, deploying_to_prod, prod_healthchecks, reverting_pr → Deploy

A run at the workflow’s backlog triage step is shown as Queued: after promotion it is a real issue waiting to be worked, not a parked note.

Issue cards

Cards are collapsed per issue from the newest-first run list. The first run seen for an issue is its current stage; title and PR are backfilled from older runs (later steps drop title from step state) and from the GitHub preview.

Each card shows the status tag, #issue and pr#, the issue title, and either step · timestamp or stopped at step · timestamp when failed. Failed cards get a danger border.

Backlog column

The Backlog column lists local parked items, not workflow runs. It shows a file count per item. See Backlog for the full workflow: create, attach files, and promote to an issue.

Run modal

Select an issue card to open the run modal:

• Status, current step, timings, and any error.
• The step-transition history (GET /api/workflows/{kind}/runs/{id} returns run plus step_log), including retries recorded as step transitions.

Usage and workers panel

Toggle the info button to show the side panel:

• Usage — total input and output tokens (formatted 500, 1.2K, 3.4M) from GET /api/token-usage.
• Workers — the 10 most recent agents with role, entity, status, and step.

Archive

Retire a card without deleting anything:

Method	Path	Purpose
GET	/api/board/archive	List archived card keys
PUT	/api/board/archive/{key}	Archive a card (optional github_number)
DELETE	/api/board/archive/{key}	Restore a card

Card keys are issue-<n> or run-<uuid> — bounded and filename-safe before they reach the DB or the audit log. Archiving is recorded as operator.board.archive; restoring as operator.board.unarchive.

Data the board reads

Method	Path
GET	/api/workflows/task_lifecycle
GET	/api/backlog
GET	/api/token-usage
GET	/api/board/archive

Tip

Titles occasionally disappear from workflow state. The board backfills them from GET /api/github/preview (one gh issue view at a time, bounded and cached) so a completed card is still readable.

Gotchas

• The Backlog column count is backlog items; every other column count is issue cards.
• Archived cards are excluded from the active board and shown only when the Archived column is open.
• Archive keys must match [A-Za-z0-9._-], at most 128 characters; anything else is rejected.