Cue dashboard: show pipeline count when an agent has more than one pipeline

[scriptease]

Summary

In the Cue modal's Sessions With Cue table, the Pipelines column shows colored dots for each pipeline on an agent but never surfaces a numeric count. When an agent has more than one pipeline this is hard to read at a glance — and when several agents are listed it becomes very easy to miss that an agent has additional pipelines beyond the first one or two visible dots. Adding an explicit count (e.g. ●●● 3 or 3 pipelines) when pipelineCount > 1 would make the surface honest about how much is configured.

Repro / observed behavior

Shows that the agent does in fact have multiple pipelines configured, visible only after clicking into the dropdown.

Several agents are present but the column doesn't communicate which ones own multiple pipelines and the red and orange are missing. Without a count, the user assumes one pipeline per agent and is confused where their pipeline is.

Expected

The Pipelines column should show a numeric count alongside the dots whenever an agent has > 1 pipeline. Examples of acceptable presentations:

• ●●● ×3
• 3 ●●●
• ● ● ● (3)
• A small badge 3 overlaid on the dot cluster

Single-pipeline rows can keep the bare dot — adding ×1 everywhere would be noise.

Why this matters

• Discoverability — users need to know multiple pipelines exist before they think to click into them.
• Pairs with Cue dashboard 'View in Pipeline' always opens the first pipeline regardless of which row was clicked #869 — the broken "View in Pipeline" routing already makes the multi-pipeline case painful; a missing count makes the same case invisible.
• Pairs with Cue dashboard Run Now only fires the first subscription when an agent has multiple #868 — Run Now fires only the first subscription, so users need to know how many subscriptions exist to even understand what they're missing.

Suggested fix

In the Sessions table cell renderer for the Pipelines column, append a count whenever the pipeline list has more than one entry. The count is already known at render time (it's the source of the dots).

Related

• task.pending: first-scan seeding never fires, even when tasks already exist #865 — task.pending first-scan seeding
• Cue dashboard ignores agents with valid cue.yaml until they're opened in the UI #866 — dormant agents not visible in dashboard
• Multiple agents sharing a project root run every Cue subscription N times — no way to designate an owner #867 — multiple agents sharing a project root run every subscription N times
• Cue dashboard Run Now only fires the first subscription when an agent has multiple #868 — Run Now only fires the first subscription
• Cue dashboard 'View in Pipeline' always opens the first pipeline regardless of which row was clicked #869 — View in Pipeline always opens the first pipeline