`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.
ca171502f7