bullswarm 0.34.0 → 0.35.1

package/CHANGELOG.md

@@ -1,5 +1,148 @@
 # bullswarm changelog
 
+## 0.35.1 — a calmer dashboard with honest active time
+
+- durations: Home, Runs, Run, Step, and Stats use the union-based
+  `minutes.active` duration; `minutes.span` remains secondary, worker-minutes
+  still sum attempt clocks, and `workflow reprice` corrects stored terminal
+  minute fields.
+- home: today leads with up to three active-or-most-recent run cards, while the
+  licence block uses one plain-word `pool · worker-minutes · weekly share · API
+  · subscription` row per pool and keeps Running and Budget visible.
+- home: from 120 columns the three cards sit side by side, with the licence
+  block beneath them up to 159 columns and to their right from 160; below 120
+  they stack full width with the licence block beneath.
+- home: the last-7-days band and the five-row recent list are back below
+  `budget · this week`, with the `Last 30 days`/`All time` toggle, the spend
+  chart, the by-pool/by-model/by-project lists, and the summary lines; the full
+  run list still lives only on Runs.
+- run: the Run page now follows the Step grammar — `done of total` with running
+  and waiting ids, active-of-span clocks, a per-pool attempt mix, a phone glyph
+  strip (`p` opens phase boxes), and a live block backed by the selected
+  attempt's latest stream turn.
+- run: spend is an honest partial subtotal (`at least` when attempts are still
+  running or unmeasured, `≈` for estimates) with measured/estimated/running/
+  unmeasured coverage and per-pool API splits; the timeline keeps phase rules
+  and one routed attempt row per worker, folds middle phases, and removes
+  licence bars, `so far`, ETA, and started/completed filler rows.
+- money: a run, day, pool or period whose attempts were only partly priced now
+  shows the recorded subtotal marked `≈` with its coverage instead of reading
+  as unrecorded; strict totals stay strict and a subtotal is never summed into
+  one.
+- stats: `Median run` and `Longest run` fall back per record to the recorded
+  span and say so, and the Spending chart fills its panel on the desktop grid
+  instead of drawing six narrow bars beside it.
+- charts: a column chart sizes its tick gutter to the widest label the axis
+  will actually print, so a money axis reads `≈$160.00` rather than `≈$160.…`.
+- step: the page is one header and four blocks — turns, result, task, cost. The
+  header says the verdict, the purpose, `pool · model · effort · reasoning`, one
+  clock (span only when it differs) and the route sentence once; the overview
+  prints one row per turn with only its non-zero counts (`35 commands`, `no
+  tools`), the counts at the end of the response on the desk and on their own
+  row on the phone, `Enter` expands a turn's full response and its tool rows
+  with each clock and measured duration, and the last turn points at the report
+  with `→ the report, shown under result`.
+- step: the result card reads the report itself — its first lines, the diff's
+  changed paths, the step's `Shared-file requests` when its report has that
+  heading, and only the artifacts it left (`files` names the run directory once,
+  then `task · out · stream (N events) · diff`); the task card shows the
+  author's own prompt with `owns`/`after`/`affects` and the kernel wrapper's
+  size (`Enter on task: full text 2.4 KB · kernel wrapper 5.1 KB`); cost is two
+  plain-word rows (API rate and `<pool> plan`) with token classes under the
+  amount, `≈` for estimates, `—` with its reason for unknowns, and a closing
+  `measured from the … transcript` line.
+- step: at 160 columns the activity takes the left column and result, task and
+  cost stack on the right so a finished step fits one screen; 120 narrows the
+  right column to 40; below that the page stacks result → activity → task →
+  cost, with `now` leading while the step runs. The footer carries the keys
+  once (`v detail (every event)`, `t filter`), and a live attempt says when its
+  cost will be measured instead of printing a guess.
+- tasks: a single `bullswarm run` task uses the same Step model and view through
+  an adapter, preserving recorded fields and leaving unavailable effort,
+  verification, usage, money, and activity unavailable.
+- step: an expanded turn shows its newest three tool rows with a
+  `↑ N earlier commands · Space page up` fold; `Space`, `PageUp` and `PageDown`
+  walk that window back through the older rows, and opening, collapsing or
+  changing the turn resets it.
+- step: a tool that is still running keeps a spinner and its elapsed time, stays
+  the last expanded row and is counted in the collapsed turn's counts; a
+  sub-second tool prints no duration rather than `0s`, and a capture with no
+  summary falls back to its event kind instead of `summary unavailable`.
+- step: the activity reader reads a capture's `.tail` file as well as its head,
+  merges the truncation marker and drops the overlap, so a long attempt's newest
+  events are visible instead of ending at the head cap.
+- step: `t` cycles the activity lens turns → tools → errors → all and `f`
+  follows the tail on this page; Fleet keeps `f` everywhere else.
+- codex: a `file_change` item keeps its path and its raw `changes` array, so the
+  Step page can name the kind and path of each change (capped at three) instead
+  of printing an empty summary.
+- durations: every clock is h/m/s — a step or phase past an hour reads `2h04m`,
+  not `124m09s`, on the Run page, the Step page and the timeline alike.
+- run: the `live` and `spend` columns are one aligned band at 120 columns and
+  wider; the running phase is never folded into the `↑ phases a–b` summary; and
+  the page keys and the wheel scroll the page body, so a timeline longer than
+  the terminal can be read.
+- run: a paused run's live block still says `bullswarm workflow resume <id>
+  continues it` rather than leaving `last finished` to read as "any moment now".
+- mod: `workflow tui --overview` keeps the goal preview and draws its milestone
+  rows flush to the pane border, the two shapes the Claude mod's pane parses.
+- colour: the Step page, the Run page and the single-task page paint one meaning
+  per colour — green for work that went well (`✓`, `succeeded`, `verified`),
+  amber for work running now (`▶`, `●`, the spinner, `following ●`), red for
+  failures (`✗`, `failed`, an error count above zero), dim for the supporting
+  detail (clocks, counts, row labels, basis phrases, block rule dashes, footer
+  hints, pending marks), bold for identity and every money amount, and each pool
+  in the colour its bar has on Home. Response, task, report and command text
+  stay plain, the selected row is inverse, and in ASCII mode only bold, dim and
+  inverse remain.
+- colour: the frames the records are reviewed against are rendered twice —
+  `docs/design/tidy-0.35.1/frames/real-*.txt` as text and
+  `docs/design/tidy-0.35.1/frames/colour/` with the escape codes kept, from the
+  one snapshot render (`scripts/render-tidy-0.35.1-frames.mjs --colour`), so a
+  reviewer can grep for a colour instead of trusting a screenshot.
+- tasks: the single-task page names the task the way the Runs list does —
+  `<lane> task · <8-char id>` (`analyze task · 3155fb3c`) — instead of the full
+  UUID or a six-character prefix.
+- home: a card's durations use the same h/m/s clock as the Step and Run pages
+  (`58m37s active of 58m38s`, `1h38m active of 1h39m`), never decimal minutes
+  like `active 725.95m`.
+- runs: the page opens with the cursor on its first row — the first active run
+  when one is running — drawn inverse, so `Enter` opens the highlighted row, and
+  `Up` on the first row stays there.
+- tests: the real-data tests and the frame script now run from a scrubbed
+  in-repo fixture, `tests/fixtures/home-351` (2.8 MB), built by
+  `scripts/build-test-home.mjs`: every id, time, status, pool, model, token
+  count, cost and event kind is as recorded, while goals, prompts, reports,
+  responses, commands and paths are marked placeholder text and project names
+  are aliases, so the suite needs no copy of anyone's home.
+
+## 0.35.0 — the Step page tells the whole story
+
+- step: the Step page leads with identity and verdict, the selected attempt,
+  retry history, route, money pair, activity, outcome, prompt, and artifacts.
+- verification: execution success stays separate from the workflow's durable
+  `verified` result, so a successful action is not mistaken for accepted work.
+- activity: the page follows a bounded per-attempt stream with capture-order
+  minimap, selection, filters, and explicit unavailable states instead of
+  inferring turns, tools, timing, usage, or subagents from prose.
+- usage: API-rate and subscription figures remain a labeled pair; token source,
+  unknown values, pending live usage, and estimated bases stay visible across
+  retries rather than becoming zero or a bare dollar amount.
+- providers: the guide and provider reference now list the optional normalized
+  stream fields each shipped capture can actually supply.
+- watch: a truncated delegate response now gets one connector-declared recovery turn or a derived workspace/test report, with the recovery source persisted on the attempt.
+- meters: a quota refusal forces a fresh meter read and marks the pool blocked until it clears, with the refusal age shown in Pools, Budget, and Usage.
+- stats: single `bullswarm run` records retain their working directory so Stats and history derive the project while truly legacy records remain unknown.
+- dashboard: the navigation footer keeps active run names visible and adds `+N more` when the terminal is too narrow.
+- stats: model labels preserve provider/model identity at narrow widths instead of collapsing to a bare version.
+- reprice: transcript matches can back-fill missing cwd and project fields for workflow attempts and single tasks, reporting the project changes.
+- money: sub-cent API, subscription, budget, and strategy amounts keep three significant digits instead of rounding to `$0.00`.
+- meters: a continuous, window-specific ledger records resolution and source, names each interval, attributes positive quota deltas to each attempt, shares overlaps by API cost, and reconciles same-pool totals at run finish.
+- home: `home snapshot` creates a selective dashboard-readable copy of routing, meters, providers, task records, and chosen workflow runs without modifying the source.
+- dashboard: the Home, Runs, Run and Step pages now live in their own model and
+  view modules; dashboard.js shrinks from 5,996 to 3,494 lines with every saved
+  frame rendering identically.
+
 ## 0.34.0 — every dollar says how it was measured
 
 - usage: Claude, Codex, and Grok attempts now retain provider-reported or transcript-summed token classes, with the byte estimate and unknown kept as explicit fallbacks.