`TaskCard` already switches to the full pipeline once a card reaches its review
lane, but `ListView` resolved progress with `scope: "implementation"`
unconditionally — and `shouldShowTaskProgress` suppressed the review column
outright. Implementation scope hides exactly `verification`,
`documentation-delivery` and `code-review`, so a list row showed "-" or a stale
count for the stage the operator was watching.
That default was written when those steps existed only as invisible gates.
builtin:coding-ideas-v2 promotes them into first-class review-lane work, so the
rule now hides the very thing it was asked to surface. Both call sites resolve the
lane through `isReviewColumnRole` — by trait, not by the hardcoded `in-review` id,
so a renamed board behaves the same.
Regression coverage asserts both directions: implementation scope still hides the
gates, and the full pipeline surfaces Verification, Documentation & Delivery and
Code Review.
Dashboard 250 tests, smoke lane 6 files / 81 tests / 19/19 scenarios, test:gate and
verify:fast green.
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.
ca171502f7