docs: publish the Daytona migration guide (fix README dead link)

[stubbi]

What

Publish the Daytona migration guide on the docs site by adding migrating-from-daytona to the docs allowlist.

Why

The mitos README links https://mitos.run/docs/migrating-from-daytona (next to the E2B one) in its integrations paragraph, but that slug was missing from scripts/lib/docs-manifest.mjs, so the page 404s while migrating-from-e2b resolves. That is a dead link on a competitor-migration path we actively promote.

The doc already exists in mitos-run/mitos at docs/migrating-from-daytona.md (shipped in mitos#592, the Daytona runtime went private so the migration story is a live GTM lever). This one-line allowlist add makes the sync publish it so the README link resolves and the Migrating group lists both E2B and Daytona.

Verification

• Before: curl -sL https://mitos.run/docs/migrating-from-daytona -> 404; .../migrating-from-e2b -> 200.
• The slug maps to an existing source file (docs/migrating-from-daytona.md on mitos@main), so the loud-fail sync check passes.
• After deploy, confirm https://mitos.run/docs/migrating-from-daytona returns 200 and appears under Migrating in the docs nav.

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features
  • Added support for an additional migration guide slug, making the new migration documentation available alongside the existing one.
• Bug Fixes
  • Updated the docs listing so the new migration page is now included in the allowed set and can be surfaced correctly.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: b9591577-635a-490a-b932-27ea3e91a95c

📥 Commits

Reviewing files that changed from the base of the PR and between b4a9473 and e5287fb.

📒 Files selected for processing (1)

• scripts/lib/docs-manifest.mjs

---

📝 Walkthrough

Walkthrough

The migrating group's slugs array in scripts/lib/docs-manifest.mjs is updated to add migrating-from-daytona, which is subsequently included in the derived ALLOWLIST and ALLOW_SLUGS exports.

Changes

Docs Manifest Update

Layer / File(s)	Summary
Add migrating-from-daytona slug scripts/lib/docs-manifest.mjs	The migrating group's slugs array is extended to include migrating-from-daytona, flowing through to the derived ALLOWLIST and ALLOW_SLUGS exports.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Related PRs: None found.

Suggested labels: None

Suggested reviewers: None

Poem:
A rabbit hops through docs so neat,
Adding Daytona's slug complete,
One line changed, allowlist grows,
Migration paths where each one goes,
Hop, hop, hooray — the manifest glows! 🐰📄

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes publishing the Daytona migration guide and fixing the broken README link.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/publish-daytona-migration

---

_{Comment @coderabbitai help to get the list of available commands.}