An in-review card now renders its stage through the running-gate badge alone —
Code Review, then Documentation, then Merging — with no progress bar, no counter,
and no expandable step list.
This reverts the review-lane progress section added earlier in this series. That
change was a correct fix for the complaint at the time (the review lane showed
nothing at all), but with the lane reduced to two milestones in a fixed order the
badge already answers "where is this card", and a list of two rows plus every
finished implementation step is noise on a board.
It also removes a defect for free rather than by repair. The list is built from
`task.enabledWorkflowSteps`, which is FROZEN on the card at planning time, so a card
planned before its workflow changed rendered a milestone that no longer exists as
permanently `pending` — a ghost row that could never resolve. Removing the deleted
`verification` group created exactly that on in-flight cards. No list, no ghost, and
no reconciliation pass to write and maintain.
Cost, stated rather than hidden: a NON-BLOCKING gate that failed is no longer
visible from the board — Documentation cannot hold a card, so a failed delivery note
now merges silently and must be read on the card itself. Blocking failures are
unaffected: a Code Review REVISE moves the card back to in-progress, which is the
most visible signal the board has.
Tests updated to the new truth, not around it: the review-lane assertions now expect
`.card-progress` and `.card-steps-list` to be absent.
pnpm lint 0 errors, typecheck, test:gate, and 738 tests across every suite that
touches card progress (TaskCard, ListView, taskProgress, board-mobile, live-ticker).
The full dashboard suite's 22 failures are pre-existing and unrelated — ChatView,
voice dictation, model menus, process supervision — with no card or progress test
among them.
Each changeset file in this directory describes one user-facing change for release notes.
Required body format
---
"@runfusion/fusion": minor
---
summary: Add a Command Center productivity control for LOC backfills.
category: feature
dev: Uses the new `fn_backfill_loc` tool; settings key `commandCenter.locBackfill`.
Fields
Field
Required
Description
summary
Yes
One line, user-facing, max 120 chars. Describe what changed for the operator.
category
Yes
One of: feature, fix, breaking, security, performance, internal.
dev
No
Developer or migration detail. Preserved in per-package CHANGELOGs but excluded from distilled release notes.
Audience
The summary is the only content that appears in end-user release notes by default. Write for Fusion operators — describe behavior, fixes, and what changed. Avoid internal class names, file paths, and implementation detail.
Bump types
patch — bug fixes, internal changes
minor — new features, CLI additions, tools
major — breaking changes
Validation
Run pnpm check:changesets to validate. The linter runs in the PR-check gate and test:gate. Legacy freeform changesets pass with a warning during the transition period.
e71ccb9d70