Install picker: platform buttons + Linux/Windows install methods

[bschellenberger2600]

Summary

Replaces the platform <select> with OS button radiogroups (same pattern as the earlier platform PR) and adds a second “Install via” row when Linux or Windows is selected, so visitors can pick among documented install paths instead of a single combined block.

Linux

• git-fire: .deb, .rpm, curl install script, Homebrew (Linux) — commands/notes aligned with the upstream README.
• git-rain: .deb, .rpm, binary archive (manual) — aligned with README.
• Ordering: best-effort DEB vs RPM detection from navigator.userAgent (many browsers omit distro → falls back to a neutral order: script-first for git-fire; deb-first for git-rain). When DEB or RPM is inferred, that method is listed first; others follow in the neutral sequence.
• A short hint appears under the platform row when detection is not unknown (explains that it is UA-based and best-effort).

Windows

• winget (existing) plus manual install using the PowerShell + user PATH snippets from each README.

Persistence

• sessionStorage: git-fire-site-install-linux-method and git-fire-site-install-windows-method store the last chosen method; per-picker coercion applies when a stored method does not exist for the current product (e.g. brew stored from git-fire still applies when you view git-rain, which shows its first valid option without overwriting the stored value for git-fire).

Verify

1. npm run build
2. Choose Linux on both hero pickers; confirm method buttons and commands update, and Copy matches the visible block.
3. Toggle Windows → winget vs Binary (manual) and confirm commands.

Branch: feature/install-or-methods

[coderabbitai]

Warning

Rate limit exceeded

@bschellenberger2600 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 54 minutes and 5 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 54 minutes and 5 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 04c8b81e-ca19-49d3-a75d-c5c3120f3671

📥 Commits

Reviewing files that changed from the base of the PR and between 37c80d4 and 9358b24.

📒 Files selected for processing (3)

• src/components/InstallPicker.astro
• src/scripts/install-pickers.ts
• src/styles/global.css

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/install-or-methods

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}