refactor(integrations): rename vercel-world to workflow-world and align docs with Workflow SDK

[jog1t]

No description provided.

[jog1t]

Stack for rivet-dev/actors

• refactor(integrations): rename vercel-world to workflow-world and align docs with Workflow SDK #5571 yoqozxqo · 2026-08-18 12:12:01 👈
• main

Get stack: forklift get 5571
Push local edits: forklift submit
Merge when ready: forklift merge 5571

[railway-app]

🚅 Deployed to the actors-pr-5571 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
kitchen-sink	❌ Build Failed (View Logs)	Web	Aug 18, 2026 at 9:58 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Aug 18, 2026 at 9:58 pm
ladle	❌ Build Failed (View Logs)	Web	Aug 18, 2026 at 9:58 pm
frontend-inspector	❌ Build Failed (View Logs)	Web	Aug 18, 2026 at 9:58 pm
website	❌ Build Failed (View Logs)	Web	Aug 18, 2026 at 9:51 pm
mcp-hub	✅ Success (View Logs)	Web	Aug 18, 2026 at 12:12 pm

[claude]

Review

PR renames @rivet-dev/vercel-world to @rivet-dev/workflow-world (and the vercel-workflow example to workflow-sdk), plus reworded associated docs. This is a clean, mechanical rename.

Verified:

• No stale vercel-world / vercelWorldActors / old example-path references remain anywhere in the tracked repo (integrations/, examples/, docs/, .github/workflows/, pnpm-lock.yaml, scripts/publish/).
• Durable on-disk identifiers were correctly left unchanged with new explanatory comments, since renaming them would reset migration/cron state for existing deployments:
  • SQLite migration table names in integrations/workflow-world/src/actors/db.ts:280,284,288 (vercel_world_*_schema_version)
  • Cron job name in integrations/workflow-world/src/actors/workflow-run.ts:149 (vercel-world-recovery)
• Doc route changes (docs/sidebar.json, docs/content/integrations/vercel-eve.mdx, new docs/content/integrations/workflow-sdk.mdx) are internally consistent and match the existing /actors/integrations/{slug} routing convention.
• CI/publish wiring (docs-sync.yml, publish.yaml, scripts/publish/src/lib/packages.ts) updated consistently with the package/directory rename.
• No CLAUDE.md terminology violations introduced (rivet.dev vs rivet.gg, etc.).

No issues found. No bugs, no test coverage gaps introduced by the rename, no security or performance concerns.

---

🤖 Generated with automated code review