feat(workspace): add microsandbox worker option

[benjaminshafii]

Summary

• add a second local worker action in the create-workspace flow so desktop users can start MicroSandbox-backed workers alongside the existing Docker sandbox path
• route the MicroSandbox worker path through the OpenWork orchestrator using the microsandbox SDK, including automatic runtime provisioning, instead of requiring users to preinstall msb
• keep Docker-specific readiness checks on the Docker path while letting the MicroSandbox flow provision its own runtime on demand

Testing

• pnpm typecheck && pnpm build in apps/app
• pnpm typecheck && pnpm build && pnpm build:bin in apps/orchestrator
• pnpm build:bin in apps/server
• cargo check in apps/desktop/src-tauri

Validation limits

• I did not run the full desktop/Tauri create-worker flow end to end in this environment.
• I did not force a real MicroSandbox runtime install here, so first-run download behavior still needs live desktop validation.
• Chrome MCP evidence was not captured because this feature is in the desktop-only local worker flow rather than a browser-only surface.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
openwork-app	Ready	Preview, Comment	Apr 1, 2026 3:10pm
openwork-den	Ready	Preview, Comment	Apr 1, 2026 3:10pm
openwork-den-worker-proxy	Ready	Preview, Comment	Apr 1, 2026 3:10pm
openwork-landing	Ready	Preview, Comment, Open in v0	Apr 1, 2026 3:10pm
openwork-share	Ready	Preview, Comment	Apr 1, 2026 3:10pm

[github-actions]

The following comment was made by an LLM, it may be inaccurate: