Enable Android APK build with Capacitor and add multi-platform CI/CD

[TechnologyStar]

Summary

This PR enables Android APK build support via Capacitor and introduces multi-platform CI/CD to automatically build and release desktop and Android artifacts.

Details

• Initialize Capacitor Android project and sync web assets from dist/renderer
• Update capacitor.config.ts for Android web integration and build options
• Add Android Gradle files and placeholder resources in android/ (Gradle wrapper, manifests, resources)
• Extend package.json with scripts: build:android, package:android, package:android:debug
• Add GitHub Actions workflow to build Windows/macOS/Linux/Android in parallel and publish artifacts
• Add documentation scaffolding: BUILD_ANDROID.md, QUICK_START_ANDROID.md, CHANGELOG_ANDROID.md, MULTI_PLATFORM_RELEASE_NOTES.md
• Introduce platformAdapter.ts for mobile compatibility and graceful degradation
• Update README and README_CN to reflect Android support
• Update .gitignore to exclude Android build outputs

No breaking changes introduced.

Warning: Task VM test is not passing, cto.new will perform much better if you fix the setup

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Auto-release publishes during pull_request builds

The auto-release job is gated only by if: "!startsWith(github.ref, 'refs/tags/')", so it runs for pull_request events as well as pushes, yet the steps later in the job call softprops/action-gh-release with GITHUB_TOKEN. On pull_request workflows—especially those from forks—GitHub supplies a read-only token that cannot create releases, so this job will fail and block PR CI even though no release should be published. Restrict the job to push/tag events or skip it for pull_request to avoid PR build failures.

Useful? React with 👍 / 👎.