Repository navigation
Task, plan and setup UI fixes - #541
Merged
Merged
Conversation
FIELD_BASE painted fields with the same background and border as the Modal panel (bg-surface-raised, border-border-subtle). In the dark theme an empty field in a dialog, for example the New Task dialog, showed only when it had focus. Fields take the recessed surface and the full-strength border, which the setup wizard already used for its own controls. That box is darker than the page, a card and a dialog panel in both themes. The wizard's own override (CONTROL_CLASS) is now the shared default, so it is removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The task detail, on its own page and in the board's dialog, showed
nothing about plans, although GET /api/tasks/{id}/plans exists. The user
had no way to get from a task to the plan that waits for a decision.
The task detail now reads the task's plans and shows the latest version
with its status and an "Open plan" action. A pending plan with no
revision request shows "A plan waits for your review" with a primary
"Open plan" button. The plans are read again when the task row changes,
which happens when plan_propose writes its note on the task.
The plan status chip moves to a shared PlanStatusBadge, so that the plan
list, the plan page and the task detail use one tone table.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Overview counted every step in "N of M steps done", also the steps that the instance closed. On an instance that keeps no credentials on disk, memory, channels, sources and agents are "Not available on this instance", so a finished setup read "4 of 6 steps done". M now counts only the steps that a person can complete here, now or after the Mode step. A step closed by policy or by a lockdown stays in the list with its badge. This matches the server, which never counts such a step as left to do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Setup entry stayed in the navigation after setup was finished, as if work was left. It now leaves the list when the checklist says "finished". To keep the wizard reachable, for example to change the model later, a gear button labelled "Setup" shows in the footer of the nav rail, and a "Setup" row in the footer of the phone's More drawer. Both show only when setup is finished. On a finished setup page the phone's More button is marked as current, as for the other entries in the drawer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On a locked instance with no templates yet, the server marks a step that waits for Mode as `lockdown` but keeps the "Choose a mode first" reason. The server does not count it, and setup can be finished, so the Overview must not count it either. appliesHere now also reads `blocked_kind`. The phone's position line no longer claims to use the Overview's M: the position counts all steps, the Overview only those that apply. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The category summary editor put its TextArea on a bg-bg-sunken strip. Fields use the same sunken surface, so the field had no visible fill when it lost focus. The edit strip drops its own background and the field shows on the panel behind it. The read-only strip keeps its background. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On a phone Setup is already a row in the More drawer, a place for rarely used destinations. A finished setup keeps that row in the list, so the drawer needs no separate footer row and no own current-page handling. The nav rail keeps its gear button. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The TaskDetailBody spec already checks, end to end, that the plan section reads the plans again when the task's updated_at changes, so the narrower TaskPlan copy of that test goes. The component comment names every plan change that writes a task note, not only a proposal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
alex-clickhouse
marked this pull request as ready for review
October 21, 2026 17:35
pufit
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
same background and border as the Modal panel, so in the dark theme an
empty field (for example in the New Task dialog) showed only when it had
focus. Fields now take the recessed surface and the full-strength border,
the tokens that the setup wizard already used. The wizard's own override
is removed.
with its version, status and "Open plan". A pending plan with no revision
request shows "A plan waits for your review" with a primary button. The
section reads the plans again when the task row changes; every plan
change (propose, update, revision request, approve, decline) writes a
note on the task, so the section follows the plan without a reload. The
plan status chip is now one shared component.
step closed by policy or by a lockdown stays in the list with its badge,
but a finished setup reads "5 of 5 steps done", not "5 of 9".
gear button labelled "Setup" in the rail footer keeps the wizard one click
away. On a phone, Setup stays in the More drawer.
surface of the same colour.
How
Tests
locked steps, and the Setup entry and the rail gear.
axe contrast audit of the changed routes shows no new findings.
🤖 Generated with Claude Code