fix(frontend/rivet-agent-prompt): add workflow_dispatch hook to prompt

[abcxff]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[abcxff]

• fix(frontend/rivet-agent-prompt): add workflow_dispatch hook to prompt #4440 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[railway-app]

🚅 Deployed to the rivet-pr-4440 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
ladle	❌ Build Failed (View Logs)	Web	Mar 17, 2026 at 3:00 am
mcp-hub	🕒 Building (View Logs)	Web	Mar 17, 2026 at 3:00 am
frontend-cloud	🕒 Building (View Logs)	Web	Mar 17, 2026 at 3:00 am
website	🕒 Building (View Logs)	Web	Mar 17, 2026 at 3:00 am
frontend-inspector	🕒 Building (View Logs)	Web	Mar 17, 2026 at 3:00 am

[jog1t]

Merge activity

• Mar 17, 3:00 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Mar 17, 3:01 AM UTC: @jog1t merged this pull request with Graphite.

[claude]

PR Review: fix(frontend/rivet-agent-prompt): add workflow_dispatch hook to prompt. This minimal PR adds workflow_dispatch to two GitHub Actions YAML snippets in getting-started.tsx. The change is correct and idiomatic - both instances updated consistently, no security concerns (write-access users can already deploy), no tests needed for static string content. LGTM.