fix(web): ask Safari users for Mac type

[baxen]

Why

Safari does not expose whether a Mac is Apple Silicon or Intel, so invite landing pages silently selected the Intel DMG.

What

• ask unknown-architecture Mac users to choose a newer or older Mac
• resolve the selected architecture to the matching release asset
• keep automatic downloads for platforms whose architecture is known
• open selected Mac downloads in a new tab, close the chooser immediately, and guard duplicate choices
• preserve the invite page when release lookup falls back to GitHub Releases
• cover the Safari chooser, selected-download fallback, Escape/focus behavior, and unsupported-device fallback in Playwright

Validation

• pnpm typecheck
• pnpm check
• pnpm exec playwright test --project=smoke --grep 'invite asks Safari users|invite download falls back|invite requires age'\n\nPre-push also passed repository Rust tests; the unrelated desktop Tauri suite had 3 existing Codex adapter discovery failures under the hook environment.\n\nGenerated with mini

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 591ffcf903

ℹ️ 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]

Fall back when the chooser popup is blocked

In browsers or managed environments that block window.open, selecting either Mac option still calls event.preventDefault() and then this optional call becomes a no-op because downloadWindow is null; the dialog closes but no download or releases page opens. Since the anchors already have href={BUZZ_RELEASES_URL}, fall back to same-tab navigation (or avoid preventing default) when the popup can't be created.

Useful? React with 👍 / 👎.

[wesbillman]

The implementation looks sound, and current-head CI is green. Before approval, please rebase onto current main and let CI rerun: this head is 8 commits behind (main at c81806d; merge base 5a656c9), so the existing checks do not validate the merged result.