Homepage Launch Readiness Checklist

Use this checklist before treating the public homepage download surface as launch-ready. The current page intentionally supports a development fallback when generated release metadata is unavailable: desktop cards open the GitHub releases page with "pending" labels, store cards stay disabled, and no generated From <release> labels appear. That fallback is acceptable for local builds, but it is not enough for launch.

Required Release Data

• packages/homepage/src/generated/release-data.ts was regenerated by packages/app-core/scripts/write-homepage-release-data.mjs during the build.
• releaseData.release.tagName is not unavailable.
• releaseData.release.downloads includes current macOS Apple Silicon, macOS Intel, Windows, Linux archive/AppImage, Linux .deb, and Linux .rpm artifacts for the release being announced.
• Android release jobs have produced both the Play .aab and signed QA .apk artifacts when mobile release is part of the launch.
• Every generated download URL contains /releases/download/<releaseData.release.tagName>/.
• Every generated download shown on the homepage comes from the same release tag as releaseData.release.tagName.
• releaseData.release.url points at the matching GitHub release tag page.
• releaseData.release.checksum is present when checksums are published for the release artifacts.

Homepage Download Surface

• The primary "Download the app" CTA scrolls to #download.
• macOS, Windows, and Linux download cards resolve to generated release assets, not only the generic latest-download fallback.
• The page renders the generated From <tag> label for each generated download shown to users.
• App Store, Play Store, Mac App Store, and Microsoft Store cards remain marked "Coming soon" until approved store URLs exist.
• Store targets are generated release data, not hard-coded placeholder links.
• No package-manager or stale install command is presented as the primary install path.

Verification Commands

Run these from the repository root:

bun run --cwd packages/homepage typecheck
bun run --cwd packages/homepage check:release-data
bun run --cwd packages/homepage test:e2e
bun run --cwd packages/homepage build

If the e2e test passes while releaseData.release.tagName is still unavailable, the homepage is only verified for fallback behavior. Block public launch until check:release-data passes with real release metadata.

Release Notes

Record the following in the launch notes:

• Release tag and GitHub release URL.
• macOS, Windows, and Linux artifact names.
• Checksum file name or reason checksums are not published.
• Android AAB/APK checksum file name when mobile artifacts are published.
• Store card state for iOS, Android, macOS, and Windows.
• Known degraded install paths and the owner for each follow-up.