- The checks dot in the Session list pairs its full-round radius with
corner-shape: round, as the ui-theme stylesheet gate requires.
- The client-ui-forge README summary fits the 100-word budget again
after the merge combined both branches' descriptions.
Brings the Session list branch up to date with the forge panel, whose
held messages now wait at inbox insertion.
- client-ui-forge keeps the Session list's remote-access import and the
panel's messageOf; the agent-controller import is gone.
- The README and the forge panel Agent Note combine both sides: the
forgeWorktree projection keeps its client view next to the inbox hold,
and the Session list paragraphs stay.
- The config catalog is regenerated, and the README, forge subsystem
page, and Agent Note pairings are recorded again.
- The panel and the forge bundle ship Spanish, French, German, Russian,
and Portuguese titles and descriptions.
- Their versions follow the root release version 0.2.1-rc.3.
Master now limits CSS hover styles to hover-capable primary input, opens
tooltips from pointer events, requires a model on every Agent and a model
selection on agent/pre-step, and requires Japanese plugin metadata.
- The panel's hover styles move under @media (hover: hover); expanded,
pressed, and focus-visible styles stay outside it.
- The hover tests enter with pointer events.
- The test Agent carries an unsupported model, and proposed steps carry a
model selection.
- The panel and the forge bundle ship Japanese titles and descriptions.
The agent-controller admission hook was reverted on master, so the forge
panel now holds the next Turn with Agent maintenance started from the
agent/inbox/inserted notification. The message stays in the inbox until
the hold ends.
- A message sent before the requested worktree exists waits while the
panel creates it. After a failed or stopped attempt the message keeps
waiting until the card retries, through the new
forgePanel.retryWorktree, or withdraws the request so the message goes
on in the project directory.
- A message sent after the Session's worktree was removed waits on the
missing card until the worktree is restored or the Session returns to
the source checkout.
- Restoring a worktree reports its prepare and checkout steps. The card
shows them in place of its actions, and the tab's restore action shows
a spinner while it runs.
- The panel state names what a waiting message waits for and the running
restoration; the agent-controller dependency is removed.
The branch label left the Session header, and finding which Sessions
work in their own worktrees, or which of their change requests need
attention, meant opening each Session's tab.
- A Session row shows a branch glyph while the Session works in the
worktree the panel created for it, and the state glyph of its most
urgent change request with a dot for its checks. The row's hover card
names the worktree branch and its base, then up to three change
requests with their state and checks.
- The forgeWorktree projection follows the Session's working directory;
its client view is the created worktree while the Session works in
it. The forgeChangeRequests projection gains a client view with the
bindings, so the Session summary carries both without loading a
Session.
- The forgePanel.changeRequestStates stream serves the states of the
change requests every listed Session binds from one Host run. It
polls each until it is merged or closed and stores every change in
the forge_panel_change_requests storage domain, so a restart shows
the last known states before the next poll.
- A new Agent Note records the decision; the READMEs, the forge
subsystem page, and the catalogs follow.
The changes view cut each changed path from its end, so a long path lost
its file name, and the Session header's branch label crowded the actions
beside the title.
- A changed file in the files menu, a file's header, and the local
changes card shows its name, then its directory in smaller subdued
type. The directory shortens first, then the name shortens in the
middle and keeps its end; hovering shows the complete path, and both
paths of a renamed file. Assistive technology reads the complete path.
A rename badge names the old file name, or the old path when only the
directory changed.
- The checkout row draws a folder for the project directory and a
branch for a worktree.
- The Session header no longer carries the branch label; the tab's
checkout row names the branch, the kind of checkout, and its path.
- The README describes the collapsed strip of a large file, and the
forge bundle README lists the gh commands and branches that bind
change requests.
The panel colored merged change requests with the brand blue, which the
theme offered in place of the violet the panel design uses, and drew a
draft with failed checks, requested changes, or conflicts as needing
attention instead of as a draft.
- ui-theme adds the violet-400 and violet-600 static steps and the
--dsw-alias-state-done-primary alias for finished work: violet-600 in
the light palette and violet-400 in the dark palette.
- The merged glyph, the collapsed merged line, and the expanded status
row of a change request card use the new alias.
- An open draft always draws the draft glyph. Only an open change
request that is not a draft is drawn as needing attention, so a draft
no longer lights the header button's red dot.
yudshj