Draw 「Pipeline by Stage」 as a ranked bar, not a funnel

[zhuangjianguo]

Fixes #48

Pipeline by Stage on 法务工作台 was authored as a funnel. A funnel encodes monotonic decline — each stage narrower than the last, because contracts drop out between them. This book does not decline, so the mark was asserting something the numbers do not say. It is now a ranked bar over the same dimension and the same measure.

What the data actually is (measured, not assumed)

Counted out of the running database, POST /api/v1/analytics/dataset/query on contract_metrics with dimension status and no filter — all ten statuses, 120 contracts:

stage	contracts		stage	contracts
draft	10		active	60
submitted	6		expired	8
in_review	12		terminated	4
in_approval	8		cancelled	2
approved	4
signing	6

The card's premise holds: the late stages outnumber the thin draft/submitted head, by 60 to 10. (The card says "active / signed"; there is no signed status — signing is 6 and active is 60.) This is DESIGN.md §10's spread, pinned by assertSpread in src/data/plan-contracts.ts, and it is unchanged on origin/main @ d34b225 after #47/#55 landed — that card re-dealt which types carry in_review, not how many contracts sit in each status.

Rendered as a funnel that shape is a bowtie. Measured band widths in Chromium, before the change: 115 · 138 · 138 · 92 · 69 · 692 · 692 px — narrow, wide, narrow, then eleven times wider at the end.

The fix, and why it is correct at any distribution

• type: 'funnel' → type: 'horizontal-bar'. A bar over the stage dimension says exactly what the data says and cannot bowtie at any distribution — which is the requirement, not a preference: the corpus is dealt by a fixture and re-dealt by other cards, so a mark that merely suited today's counts would break again quietly.
• options.stageOrder → options: { sortBy: 'contract_count', sortOrder: 'desc' }. See below — this is the ordering half of the card, and the answer turned out to be measurable rather than assumable.
• The widget's description changes with the mark ("intake through activation" described an order the chart no longer has), so both translation bundles change with it. No other string moves; the title is untouched in both locales.

No data was reshaped. src/data/, README.md and DESIGN.md are untouched.

The ordering question — answered, and it is not ours to fix

options.stageOrder is lowered by the dashboard renderer onto every chart type as categoryOrder, and only the funnel branch reads it. Measured twice on @objectstack/console 17.4.0:

1. In its code: categoryOrder is consumed inside the chartType === 'funnel' branch and nowhere else; the bar branch passes the rows through untouched.
2. In the browser: this widget as horizontal-bar with stageOrder still authored rendered Active · Approved · Draft · In Approval · In Review · Signing · Submitted — alphabetical.

So an explicit lifecycle order is not authorable for a bar on this platform version, and keeping stageOrder would have been metadata that does nothing. It is removed rather than left inert, and reported upstream rather than patched.

What is authorable is an order that cannot depend on a label, and that is the robustness the card was after. The zh-CN measurement before the change is the reason it matters:

zh-CN console, funnel, stageOrder authored: labels fell back to English and stage order was lost entirely — Active · Approved · Draft · In Approval · In Review · Signing · Submitted, i.e. alphabetical by the English label.

The mechanism: the query rows carry the API's English labels while the client's order map carries the bundle's Chinese ones, so nothing matches and every row falls to the same sort sentinel. The label bug was silently reordering the chart, exactly as the card suspected.

sortBy on the measure cannot be reordered by any label in any locale. It lowers to order: { contract_count: 'desc' } on the dataset query (verified in the request body), and the rendered order is now byte-identical in both locales:

	en console	zh-CN console
category order	Active · In Review · Draft · In Approval · Submitted · Signing · Approved	Active · In Review · Draft · In Approval · Submitted · Signing · Approved
bar widths (px)	615 · 123 · 103 · 82 · 62 · 62 · 41	615 · 123 · 103 · 82 · 62 · 62 · 41

Including the 6–6 tie between Submitted and Signing, which lands the same way both times.

The "spills outside its card" half does not reproduce

That claim came from a screenshot in the #45 dogfood pass, and it was re-checked rather than inherited. On main @ 2807b3b with console 17.4.0, the funnel's ink sits 25px inside the card on every side at 1440 / 1280 / 1024 / 820 px viewport widths, with scrollWidth === clientWidth (no horizontal scroll) at each. The mark was wrong-shaped, not overflowing. Nothing about the fix changes; the card should just not carry a claim nobody re-checked. The bar measures the same 25px inset at all four widths.

Browser verification

pnpm demo on a clean database (port 3048), signed in as admin@objectos.ai, navigated to Dashboards → Legal Workbench, in an en and then a zh-CN console, before and after the change; the widget was screenshotted in all four states.

• Before, en: a bowtie — a narrow hourglass over two full-width triangles for Signing and Active.
• After, en: seven ranked bars, Contracts axis 0–60, every stage label legible.
• Before, zh-CN: the same funnel with a giant Active band at the top — English labels, alphabetical order.
• After, zh-CN: Chinese title, Chinese description, Chinese measure axis (合同数), same order as en. The category labels are still English — that is the platform gap the card routes upstream, unchanged and untouched here.

Console during both passes: two lines, identical before and after and therefore pre-existing — a 404 on a resource fetch and [AuthProvider] Failed to load organizations: TypeError: Failed to fetch. Boot carried only the two known platform ERROR lines (objectstack#17175, #17176) and the background seed continuation (objectstack#17329).

Gates

Exit codes captured before any pipe (cmd > file 2>&1; EXIT=$?).

pnpm validate        → 0
pnpm lint            → 0     21 warning(s), 5 suggestion(s)  (unchanged from base)
pnpm typecheck       → 0
pnpm lint:i18n-gate  → 0     LOCALES "en","zh-CN" · REACH 12 surface classes (widget=38)
                             COVERAGE 0 missing keys across 2 locale(s)

Acceptance notes

• PR title deviates from the issue title deliberately: the issue title asserts the widget "renders as a bowtie spilling outside its card", and the spilling half did not reproduce (above). The bowtie half did.
• The widget id stays stage_funnel. It is the key both bundles address this widget by, it is not user-visible, and type one line below is what states the mark; renaming it would move three files for no user-visible gain.
• suppressWarnings: ['chart-config-missing'] is kept and is inert on this lint version — measured in both directions: removing it produces the same 21 warning(s), 5 suggestion(s) on this branch and on base 2807b3b with the funnel. It is pre-existing, unaffected by this change, and left alone rather than tidied under this card.
• Platform gap for the upstream tracker: dashboard.widgets[].options.stageOrder is forwarded to every chart type as categoryOrder and honoured only by the funnel branch, so an authored stage order is silently dropped on a bar/column widget. Noted, not filed here — it belongs in objectstack-ai/objectstack, and this card owns no issue-filing on that repo.

🤖 Generated with Claude Code

https://claude.ai/code/session_01R3n3GGzobdegM4HUzah1iR

---

Generated by Claude Code