Dashboard storyboard list not filtered by agent's declared capabilities

[EvgenyAndroid]

Bug

The dashboard "Test" view for a registered agent shows the full storyboard catalog rather than filtering to storyboards applicable to that agent's declared capabilities.

Affected agent: https://adcp-signals-adaptor.evgeny-193.workers.dev/mcp
Declared: supported_protocols: [signals], specialisms: [signal-owned]

Observed behavior:

• Dashboard shows ~20+ storyboards including pagination-integrity (list_creatives), get-media-buys-pagination-integrity, collection-lists-pagination-integrity, pagination-integrity-creative-formats, etc.
• None of these are applicable to a signals-only agent

Expected behavior:

• Dashboard should filter storyboards the same way recommend_storyboards does: universal baseline (17) + signals baseline (1) + signal-owned specialism (1) = 19 total
• Storyboards for protocols/specialisms the agent has not declared should be hidden

Impact:

• Confusing UX — members see dozens of irrelevant storyboards
• No clear signal of what they actually need to pass
• Makes the "AAO Verified" path harder to understand

Suggested fix:

• Pull get_adcp_capabilities for the agent when rendering the Test view
• Apply the same filtering logic as recommend_storyboards to scope the displayed list

[bokelley]

Thanks for filing!

Triage

Classification: Bug
Bucket(s): admin / ops tools, compliance-suite
Status: drafting-pr

What the experts said:

• internal-tools-strategist: remove the fallback entirely; the existing reason enum returned by the server already has actionable signal; the "Showing all available storyboards" subheading is not sufficient to prevent confusion — the fallback actively misleads (blocker verdict)
• dx-expert: right call; probe failure means fix-your-agent-first, not browse-storyboards; no blockers; nits on copy register consistency and branch ordering

My take: The renderStoryboardPicker function in dashboard-agents.html was calling GET /api/storyboards (the unfiltered catalog) as a fallback whenever the capability probe returned any non-classified error (500/504). A signals-only agent would see media-buy storyboards because the probe failed, not because those storyboards apply. Drafted a fix that removes the fallback entirely and routes each error class (network, tls, timeout, protocol, unknown, specialism_parent_protocol_missing, HTTP 504) to a one-line actionable hint. Draft PR: #4262 — removes unfiltered fallback, adds per-reason guidance.

---

Triaged by Claude Code. Session: https://claude.ai/code/session_011RjJrMxXuaEQXgg6HJMWqA

---

Generated by Claude Code