Product: Studio deploy + Act on findings + unified action surface (F5/F12/F3)

[groupthinking]

Problem

Studio deploy, dashboard “act on findings,” and project scaffold packaging were incomplete or fragmented:

• Studio Deploy was a static handoff message, not a real /api/pipeline kickoff + job poll.
• Dashboard Actions did not expose POST /api/agents/actions.
• Backend project_scaffold from TranscriptActionAgent was dropped before UI; workbench /api/scaffold was a parallel non-canonical surface.

SSOT follow-ups: F5, F12, F3 (UVAI-EventRelay-SSOT).

Acceptance criteria

• Studio Deploy calls POST /api/pipeline with deployment_target=vercel, reuses last Run job id when present, polls /api/jobs/{id} for live_url / github_repo, and degrades cleanly without BACKEND_URL.
• Dashboard ActionsPanel runs action agent via useActionAgentStore → /api/agents/actions with phase UI.
• project_scaffold is preserved through pipeline stream + dashboard insights.
• Deterministic scaffold package (README, tasks.json, stub) lives in EventRelay lib/action-surface.ts with Export package UI; workbench marked retired.
• Unit tests for studio-deploy and action-surface pass.
• PR governance + required CI green on the implementation PR.

Implementation PR

#1343

[linear-code]

GRV-301

[github-actions]

👋 Thanks for opening this issue! It has been automatically labeled for triage.

[coderabbitai]

🔗 Related PRs

#277 - Vercel remediation complete: waitUntil adoption + active middleware + @vercel/functions package (resolves three user-defined outcomes; 16-agent verification-gate consolidated PASS on full matrix) [closed]
#301 - chore: remove dead Railway / stale Vercel references [merged]
#313 - fix(pipeline): stream API key on job poll, async jobs, smoke SSE path [merged]
#404 - fix(web): sync package-lock with @vercel/functions (unblocks #277 auto-merge) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!