feat: storyboard UX, inline agent connect, OAuth auth

[bokelley]

Summary

• Short-circuit comply() when product discovery fails — skip dependent tracks instead of running 10+ scenarios to the same error
• Inline agent connection form on dashboard — replace chat bounce with token input, auth type, platform type
• Filter storyboard picker by agent capabilities — recommended vs other grouping
• New generative creative storyboard (creative_generative.yaml) for brief-driven generation (OpenAds pattern)
• OAuth fallback in resolveOwnerAuth() — uses OAuth tokens when no static bearer token exists
• Auto-scroll storyboard results into view

Alignment with #1985

These changes are compatible with #1985 (storyboard coverage and comply() scenario filtering). The overlap is in compliance-testing.ts — #1985 adds extractScenariosFromStoryboard() and scenario filtering in the run endpoint, while this PR adds two-phase comply() execution. They compose cleanly: filtered scenarios still flow through the two-phase comply(). Merge order doesn't matter; the second to merge will need a small conflict resolution in compliance-testing.ts.

Changes

comply() short-circuit (compliance-testing.ts)

• Runs core + products tracks first (phase 1)
• If products track fails, skips all product-dependent tracks (phase 2)
• Adds clear observation: "Product discovery failed — skipped dependent tracks"

Inline agent connect (registry-api.ts + dashboard-agents.html)

• PUT /registry/agents/:encodedUrl/connect — saves auth token + platform type
• Inline form replaces "Connect agent" chat link
• Works for both "not yet checked" and "has data but no auth" states

Storyboard picker filtering (dashboard-agents.html)

• Uses agent track data to sort storyboards into Recommended / Other
• Media buy storyboards for media_buy agents, creative for creative, signal for signal

Generative creative storyboard (creative_generative.yaml)

• 5 phases: format discovery → generate from brief → refine → multi-format → production build
• interaction_model: stateless_generate, capabilities: [supports_generation]

OAuth in resolveOwnerAuth() (compliance-db.ts)

• Falls back to OAuth access tokens when no static token exists
• Respects 5-minute expiration buffer

Test plan

• 607 unit tests pass (pre-commit hook)
• 1329 server unit tests pass
• 43 storyboard tests pass (12 storyboards load)
• TypeScript compiles clean
• Pre-push hooks pass (Mintlify validation, link checking)
• CI passes

🤖 Generated with Claude Code

[bokelley]

Nice work — the two-phase comply() short-circuit is a good optimization, and the inline agent connect + storyboard picker are solid UX improvements.

Merge order with #1985: We're merging #1985 first (storyboard coverage + comply() migration). The main conflict will be in comply() in compliance-testing.ts. Here's how they compose:

#1985 adds a priority chain at the top of comply():

storyboards > scenarios > tracks > default

When storyboards or scenarios are provided, they bypass track-based selection entirely. Your two-phase logic applies to the track-based path (the else branch — when no storyboards or explicit scenarios are given).

When you rebase after #1985 merges, the reconciliation is:

1. Keep the priority chain from #1985 (storyboards → scenarios → tracks)
2. Apply your two-phase logic inside the track-based branch
3. The scenarioList variable from #1985 feeds into your phase 1/phase 2 split

The storyboard path doesn't need two-phase execution because storyboards already select only relevant scenarios — if a storyboard doesn't reference full_sales_flow, products aren't tested.

Other notes:

• creative_generative.yaml fills the gap we noticed — the category existed in schema.yaml but had no storyboard
• #1985 adds creative_generative to the schema.yaml category enum already, so that should merge cleanly
• The SCENARIO_REQUIREMENTS import you add is already available in #1985's version of the file