docs(release): prepare Alpha 7

[HsiangNianian]

Summary

• publish bilingual Alpha 7 UX Foundation release notes and link them from the manuals
• align installation assets, navigation, configuration, and migration guidance with shipped behavior
• add Semifold changesets for the launcher fixtures, readiness command center, instance library, Monaco editor, and documentation corrections

Expected version plan

• dropout: 0.2.0-alpha.7
• @dropout/ui: 0.1.0-alpha.5
• @dropout/docs: 0.1.0-alpha.3

Validation

• pnpm -C packages/docs types:check
• pnpm deploy:docs:dry-run
• local route smoke: 18 English/Chinese manual and development routes returned 200
• pnpm exec prek run --all-files
• git diff --check

Release gate

Merging this PR lets the existing Semifold workflow generate the version/changelog PR. The final version PR and public prerelease remain gated on explicit release confirmation.

[sourcery-ai]

Reviewer's Guide

Docs for Alpha 7 release align installation, navigation, features, and migration guidance with the new launcher UX, instance library, Monaco editor, and UI validation work, and add bilingual release notes plus changeset metadata for the release.

File-Level Changes

Change	Details	Files
Update getting-started docs in English and Chinese to reflect Alpha prerelease status, new installer assets, and correct URLs/paths.	Point download links to the HydroRoll Team releases and describe Alpha builds as prerelease with backup guidance. Refresh platform/asset tables with macOS x86_64 entries and NSIS setup.exe installers for Windows. Adjust Linux install commands to match Dropout_* naming and update AppImage usage examples. Simplify Windows installation steps to focus on architecture-specific NSIS installers. Update navigation card links and troubleshooting URLs to language-scoped/manual paths and add Alpha 7 release notes cards. Switch GitHub Issues links to the HydroRoll-Team organization.	packages/docs/content/zh/manual/getting-started.mdx packages/docs/content/en/manual/getting-started.mdx
Revise feature index docs to highlight the configuration editor, updated migration capabilities, UI themes, and migration workflow semantics in both languages.	Replace Downloads and AI Assistant feature cards with a Configuration Editor card in EN/ZH manuals. Update the launcher migration roadmap row from a generic import profiles entry to a preview migration capability description. Change UI design copy from dark-mode-only to light/dark themes with better contrast in EN/ZH. Retitle and rewrite profile import sections as migration compatibility, detailing preview, metadata preservation, cancellation/rollback, and non-destructive behavior.	packages/docs/content/en/manual/features/index.mdx packages/docs/content/zh/manual/features/index.mdx
Expand README feature lists to describe the launch command center, instance library, Monaco-based configuration editor, and clarify migration roadmap status.	Add launch command center and instance library bullets describing state-driven launch workflow and scalable instance views. Enhance the instance system bullet to include mods, saves, and migration entry points. Update configuration editor bullets to mention bundled Monaco, schema diagnostics, formatting, keyboard save, and discard protection. Refine migration checklist items to distinguish shipped basic discovery/copy import from planned conflict preview, cancellation, rollback, and structured compatibility reports in EN/ZH.	README.md README.CN.md
Adjust manual index pages to route architecture and development docs through the /docs/development paths and better describe UI and configuration capabilities.	Update Architecture and Development card hrefs to absolute /docs/development and localized /zh/docs/development/architecture paths. Rewrite Modern UI sections to mention launch command center, instance library, themes, and responsive layouts. Add Safe Configuration sections describing the Monaco JSON editor’s diagnostics, formatting, keyboard save, and unsaved-change protection in EN/ZH manuals.	packages/docs/content/en/manual/index.mdx packages/docs/content/zh/manual/index.mdx
Add bilingual Alpha 7 release notes pages and releases metadata, detailing UX, instance library, Monaco editor, and migration behavior.	Create en/zh Alpha 7 release notes pages under manual/releases with highlights for launch readiness, instance library, Monaco editor, and UI fixtures. Document upgrade and migration notes, release assets per platform/architecture, and known limitations for the Alpha 7 prerelease. Add meta.json stubs for manual releases sections in both languages.	packages/docs/content/en/manual/releases/alpha-7.mdx packages/docs/content/zh/manual/releases/alpha-7.mdx packages/docs/content/en/manual/releases/meta.json packages/docs/content/zh/manual/releases/meta.json
Register changesets describing Alpha 7 UX, instance library, Monaco editor, fixtures, and docs alignment for versioning.	Add changeset for deterministic browser fixtures, route code splitting, accessibility checks, and visual regression baselines. Add changeset for the searchable/sortable instance library with scalable views and guarded actions. Add changeset for the launch readiness command center redesign. Add changeset for the Monaco-based configuration editor replacement. Add changeset for the Alpha 7 docs and release-notes alignment.	.changes/alpha7-fixtures.md .changes/alpha7-instance-library.md .changes/alpha7-launch-readiness.md .changes/alpha7-monaco.md .changes/alpha7-docs.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Please double-check that the updated asset names and patterns (Dropout_*.deb, Dropout_*.AppImage, -setup.exe) in the getting-started guides match the actual build output, to avoid installation instructions drifting from the real filenames.
• The updated documentation paths (e.g. /zh/docs/manual/..., /docs/development/...) introduce more explicit routing; verify that all affected links resolve correctly in both locales and that there aren’t any remaining mixed old/new path variants.
• The migration feature is now described as a preview with more detailed behavior; consider checking that this wording aligns with the current UI labels and flows (Library actions, migration entry points) so users don’t see terminology discrepancies between the app and docs.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Please double-check that the updated asset names and patterns (`Dropout_*.deb`, `Dropout_*.AppImage`, `-setup.exe`) in the getting-started guides match the actual build output, to avoid installation instructions drifting from the real filenames.
- The updated documentation paths (e.g. `/zh/docs/manual/...`, `/docs/development/...`) introduce more explicit routing; verify that all affected links resolve correctly in both locales and that there aren’t any remaining mixed old/new path variants.
- The migration feature is now described as a preview with more detailed behavior; consider checking that this wording aligns with the current UI labels and flows (Library actions, migration entry points) so users don’t see terminology discrepancies between the app and docs.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Workspace change through: 936a72e

5 changesets found

Planned changes to release

Package	Bump Level	Current Version	Next Version
@dropout/ui	patch	0.1.0-alpha.4	0.1.0-alpha.5
dropout	patch	0.2.0-alpha.6	0.2.0-alpha.7
@dropout/docs	patch	0.1.0-alpha.2	0.1.0-alpha.3