@staff0rd/assist 0.476.0 → 0.478.0

package/README.md

@@ -316,7 +316,7 @@ From WSL, the selector can also surface and drive Windows-host repos (requires `
 
 - `sessions.topBar` — defaults to **true**, which gives the sessions view a sticky top bar inside the terminal panel (served to the UI by `GET /api/session-layout`). The bar stacks the active session's ids (`#<session>` plus the Claude Code conversation id), its backlog chip and story name, and the phase caption; to the right it carries the restored indicator, elapsed time, the Continue/Auto-run/Dismiss switches, and the session's actions with text labels — collapsing to icon-only below 560px so the PR preview split still fits. It stays in the terminal half when that split opens and is absent in the transcript view. Cards then shed the phase caption, elapsed, restored indicator, the switches and the icon action row (keeping close/dismiss), and fold status, context % and change counts onto the chips line; a toggle away from its default leaves a small grey caption (`will auto-run`, `won't continue`, `will dismiss`). Set `assist config set sessions.topBar false -g` to keep all of that on the card, which renders the view as it was before the bar existed.
 
-- `sessions.floatWaiting` — defaults to **false**. Set `assist config set sessions.floatWaiting true -g` and the sidebar floats sessions that have been `waiting` on input for more than 5 seconds above the other cards, longest waiting first, so a stopped session in a full sidebar is not missed. Starred sessions still sort above everything. The daemon stamps `waitingSince` whenever a session enters `waiting` (and on restore of a session that comes back waiting), the flag reaches the UI over `GET /api/session-view`, and the sidebar re-sorts on a 1s tick since crossing the threshold produces no socket event.
+- `sessions.floatWaiting` — defaults to **true**: the sidebar floats sessions that have been `waiting` on input for more than 5 seconds above the other cards, longest waiting first, so a stopped session in a full sidebar is not missed. Set `assist config set sessions.floatWaiting false -g` to keep the previous star-only ordering. Starred sessions still sort above everything. The daemon stamps `waitingSince` whenever a session enters `waiting` (and on restore of a session that comes back waiting), the flag reaches the UI over `GET /api/session-view`, and the sidebar re-sorts on a 1s tick since crossing the threshold produces no socket event.
 
 A `run:` entry in `assist.yml` flagged `server: true` (with an optional display-only `port:`) is treated as a singleton **dev server**: at most one may be live per normalised git remote (`getCurrentOrigin`), i.e. across a clone and all its sibling clones of the same repo. Every session card for a repo that defines a `server: true` run shows a **▶ start** button (surfaced by `GET /api/server-runs?cwd=`); clicking it sends `create-run`. The daemon enforces the singleton on `create-run` (and on relaunch via retry) — if a server run is already live for that remote it rejects with a conflict instead of starting a second one that would collide on the port. The web UI turns that conflict into a "replace running server?" prompt; confirming stops the old server and starts the new one, declining leaves it untouched. The serving session's own card shows a `serving :<port>` chip and a **⏹ stop** button (stop leaves a relaunchable card rather than dismissing it), and the slot frees automatically whenever that session stops, exits, or is killed. Non-`server` runs (`build`, `test`, …) are unconstrained.