Task: Add horizontal bars to dashboard rankings

Identity

Add horizontal bar visualization to both the task-type ranking and employee-operation ranking on /operations-dashboard.
Preserve the compact fixed-height ranking panels, operation/success count labels, ordering, scrolling, and click-through filters.
Keep completion rate and all percentage labels out of the leadership presentation.
Update browser cache versions and focused dashboard regression assertions.

Use the existing vanilla HTML/CSS/JavaScript stack and dashboard response; do not introduce a chart library or change the operations API.
Scale bars independently within each ranking so the leading operation count occupies the available width and the remaining rows are immediately comparable.
Encode total operations as a muted outer bar and successful operations as a darker inner bar on the same scale; keep the exact counts visible as text.
Preserve leadership-only read access, business-safe copy, task drill-through, employee filtering, and all task/ERP authorization boundaries.
Do not restart, deploy, mutate runtime tasks, access ERP, or add an organization concept.

Added one reusable ranking-bar renderer that clamps numeric inputs and normalizes total/success widths against the largest operation count in the current ranking.
Added the same two-layer horizontal bar to every task-type and employee row: the light fill shows operation volume and the dark-green inner fill shows successful volume.
Retained explicit “操作 N / 成功 N” labels and accessible button names; no percentage or completion-rate text was reintroduced.
Expanded the compact row grid to include the bar without changing the fixed 304px panel height or internal scrolling. On narrow screens, the bar moves to a second row beneath the identity and counts.
Preserved task-type and employee click-through behavior, filters, task detail, ranking order, and business-safe dashboard language.
Updated static asset cache versions and regression assertions for the ranking-bar renderer.
The running 8786 service serves the static change directly. No restart, deployment, database/task mutation, ERP access, or external send was performed.

node --check LianSyn-platform/app.js: passed with the bundled Node runtime.
Focused account/dashboard regression: 8/8 passed.
node --run check:repo: 10/10 passed.
node --run check: passed.
node --run test:control-plane: 153/153 passed.
node --run test:legacy: 256/256 passed.
node --run build: passed.
git diff --check: passed.
Authenticated browser verification on http://127.0.0.1:8786/operations-dashboard?bars=1 loaded 359 operations, 251 successes, 23 task types, and 1 participating employee.
Visual verification confirmed that the task-type ranking visibly compares 43/27/26/24 operation counts, the success layer remains readable inside each total bar, and the employee row shows 359 total operations against 251 successes.
Interaction verification confirmed that task-type click-through selected “删除订单”, narrowed the table to 43 operations, and kept completion-rate language absent.

The current standard data contains one employee, so employee-to-employee bar comparison will become visible once additional accounts have task activity; the same normalization is already applied.

None. This is a focused visual encoding of the already accepted count-based leadership rankings and does not change product, authorization, data, or API semantics.