Screen Build Order

UI is introduced before the backend is “finished” so architecture is validated against real workflows.

UI Slice 1 — Developer harness

Build after Task + fake-agent basics exist.

desktop shell;
Project selector/create-open flow;
Task list;
Task detail;
Start Task button;
simple live Run status/activity;
diagnostic errors.

No Kanban drag/drop yet. The purpose is to prove the client/core boundary and make the project usable.

UI Slice 2 — Review loop

candidate diff;
verification panel;
comments;
request changes;
approve;
revision/stale-state indicators;
review history.

This UI matters more than a polished board.

UI Slice 3 — Planning

Plan revision editor/Markdown viewer;
submit for review;
annotations;
revision history;
decomposition preview/edit/confirm.

UI Slice 4 — Decisions

Task Needs You state;
Decision panel;
global Decision Inbox;
notifications/attention indicator;
resolution history.

UI Slice 5 — Workspace views

After the core task experience works:

Kanban;
List;
Tree;
project overview.

These are multiple views over the same domain objects, not separate state systems.

UI Slice 6 — Activity quality and diagnostics

phase/step grouping;
Fact/Claim distinction;
assumptions ledger;
pageable history;
raw-log diagnostics;
explicit sync freshness/degraded states.

UI Slice 7 — Settings and provider management

Driver/Instance/Strategy selection;
capability display;
side-effect-minimal probes;
provider configuration errors;
project trust/settings;
concurrency settings.