feat(agents): agent display label across operator, monitoring, executions & graph (#1643)

[dolho]

What

Follow-up 5/5 of the #964 display-name track — spread the agent display label to the surfaces the ent#181 foundation (#1676) didn't reach: operator queue, monitoring, executions, the collaboration graph, tab titles, and prose/toasts.

Builds directly on #1676 (merged to dev): agent_ownership.display_label, GET/PUT /label, the utils/agentName.js resolver, and the agent_label_changed WS handler already ship. No backend change here.

The decision (AC #1)

Dense operational surfaces (executions, operator queue, monitoring) read only the slug from their own API payloads. Rather than add a mutable display_name to each of those high-volume endpoints — staleness risk + N sources of truth — the label is resolved on the frontend off the loaded agents, from one place, staying live via the existing agent_label_changed handler:

• agentsStore.displayNameForSlug(slug) → label or slug (prose)
• agentsStore.agentRefForSlug(slug) → agent object or bare slug (feeds agentNameTooltip)

An unloaded slug falls back to itself, so a cold surface never regresses. Recorded as requirements §1.3.1 FR-6.

Render rule by class (#964)

Class	Rule	Surfaces
Dense operational tables	slug primary, label as hover tooltip	ExecutionsPanel · operator QueueCard/QueueList/QueueItemDetail/ResolvedCard/NotificationsPanel · MonitoringPanel (alert + health) · MobileAdmin ops/notif · RoleMatrix (100px, slug-only + tooltip)
Prose / toasts	label alone	Agents.vue toasts · Settings.vue confirm + subscription option · PortalConversation header/switcher/placeholder · PortalFilesPanel headings/toast
Collaboration graph	render label, data.label stays the slug (action key)	network.js node data (agent + system) + live handler · AgentNode
Reviewed case-by-case	label + slug link / tooltip	ExecutionDetail breadcrumb + source-agent · PermissionsPanel · ReplayTimeline · FoldersPanel · AgentWorkspace + AgentBrainOrb headers

Notes:

• AgentAvatar always receives the slug (incl. every touched surface).
• Comma-joined lists (GitHub-PAT propagation failure list) keep the slug — long labels make them unreadable (per the issue's own note).
• Tab titles resolve the label on warm SPA nav; a cold direct load shows the slug (store not fetched yet) and self-heals on the next nav. Explicit tradeoff, not slug-only.
• Terminal header stays slug (machine-facing).

Verification

• All 20 touched SFCs compile via @vue/compiler-sfc; the 3 JS files pass node --check.
• npm run build is blocked by a pre-existing unrelated issue (mermaid declared but not installed, AgentWorkspace.vue) — same as noted on feat(agents): editable display label with an immutable slug (ent#181) #1676; reproduces with this branch stashed.

Scope boundary

#1643 depends on the #964 schema/API decision, which #1676 answered as display_label. #1639/#1640 (schema/API + endpoint) are now largely redundant with #1676 and #1641/#1642 (roomy surfaces / pickers) remain the sibling follow-ups — flagged for reconciliation, not touched here.

Related to #1643

🤖 Generated with Claude Code

[github-actions]

⚠️ Nightly unit-suite check skipped — merge conflict against dev.

Resolve by running git merge dev locally and pushing the result. The next nightly run will re-test once the conflict is gone.

[vybe]

Validated via /validate-pr. Frontend-only spread of the #1676 display-label foundation (#964 track 5/5): single slug→label resolver on the agents store (displayNameForSlug/agentRefForSlug) instead of N mutable presentation fields on operational payloads; graph data.label verified to stay the slug (action key) with display_label render-only; unloaded slug falls back to itself. No v-html introduced anywhere labels render; no secrets/emails in diff. Requirements updated (core-agent §1.3.1 FR-6). Full check suite green including frontend e2e and the pytest matrix. Note: body carries no closing keyword — bumping #1643 to status-in-dev manually after merge.