Publish Mihoro migration and rollback guide

[Pectics]

Context

Roadmap item imported from PLAN_REQUEST.md and PLAN_RESPONSE.md for v1.0.0 — Stabilization.

Upstream references

• spencerwooo/mihoro
• feat: add system-level service option and update related logic spencerwooo/mihoro#200

Upstream decision

• Ported
• Reimplemented
• Deferred
• Rejected

Reason: Reimplemented as Mihoto migration documentation tied to import and backend migration commands.

Scope

• Document Mihoro-to-Mihoto user-backend migration, user-to-system migration for TUN, verification, dry-run, and rollback.
• State that original Mihoro files are preserved unless cleanup is explicit.

Acceptance criteria

• The scope above is implemented or documented in issue-linked PRs.
• Relevant upstream references are reviewed before implementation starts.
• Tests are added, or the PR explicitly explains why this is documentation-only.
• Documentation is updated, or the PR explicitly explains why no docs changed.
• Migration impact, security impact, and rollback behavior are evaluated.

Out of scope

• Work explicitly listed outside v1.0 in the roadmap remains deferred unless this issue is in v1.1+ — Post-v1 Backlog.
• No GitHub Project board, branch protection change, local commit, or repository file edit is part of this import pass.

Dependencies

• Depends on Add reversible Mihoro-to-Mihoto import and migration #14
• Depends on Add reversible user-to-system deployment migration #15
• Depends on Implement recover-network emergency recovery command #21
• Blocks Complete release-candidate migration testing #30

Security and rollback considerations

Apply Mihoto's safety rule for this issue: updates, migrations, service changes, TUN/DNS changes, and credential handling must be explicit, validated, auditable, and recoverable. Secrets and subscription URLs must be redacted from logs and issue artifacts.