docs(migrations): add Daytona v2 migration workflows
This repository has no entry point for competitor sandbox migrations. Add a Daytona v2 migration overview and pages for Vercel, Fly Machines, Blaxel, Modal, Cloudflare and E2B, including human/agent linter commands, JSON interpretation, behavior-preservation checks and known gaps.
The toolkit is verified in a local checkout but has no confirmed publication destination. The pages explicitly require a reviewed local checkout and mark permanent toolkit/provider links as pending. This draft should stay unmerged until that destination and access model are established. Existing SDK 0.x examples retain their own target versions.
Validation:
- Local Markdown links, anchors and fences checked across all 8 changed pages.
- Documented CLI flags/JSON exercised for all 6 providers in TS and Python.
- Toolkit: 202 tests, syntax/link/source/generator/format checks, preserved Vercel package installation tests, and source-pinned SDK gate (26 TS examples, 52 Python examples) pass.
- No live cloud migration or application acceptance run is claimed. The documented target is source-audited v2 alpha, not a deployment-availability guarantee.
The toolkit flags hidden/unreleased target features as unavailable, makes no automatic API rewrites, and keeps unresolved storage/auth/lifecycle work explicit. Only the small static CI wrapper was built; larger converters, smoke execution and cost estimation remain proposals.
Summary by cubic
Adds Daytona v2 migration documentation: a high-level overview plus per-provider guides for Vercel, Fly Machines, Blaxel, Modal, Cloudflare, and E2B, linked from the repo README.
- Documents the human and agent linter workflows, JSON output format, exit codes, and per-provider CLI flags.
- Flags v2 gaps such as volumes, persistent Linux creation, Functions, and GPU/Windows support as blockers instead of silent fallbacks.
- Requires a reviewed local toolkit checkout because the toolkit's publication destination is pending; permanent links are marked as such, and this draft should stay unmerged until that is settled.
- Keeps existing SDK 0.x examples intact; only a small static CI wrapper was added, while larger converters, smoke execution, and cost estimation remain proposals.