Add M-1 LED matrix with WLED firmware toggle

[bharvey88]

Adds the Apollo M-1 LED matrix to the installer with a three-way firmware toggle, reusing the same variant control R_PRO-1 uses for WiFi/Ethernet (no JS changes):

• WLED-MM 14.5.1 (Rev6), the default: the hardware being sold and the firmware it ships with
• WLED-MM 14.5.1 (Rev4) for the earlier hardware revision
• WLED 16.0.1 (Rev6 only), the new firmware option built from ApolloAutomation/WLED-M1

Also fetches the M-1 product image via scripts/fetch_images.py and rewrites docs/m1-wled-migration.md to describe the shipped toggle plus the hosting layout.

Verified: Playwright 21/21 from tests/, three-way toggle renders with Rev6 preselected at desktop and 390px widths, and the registry validator passes on every URL except the expected one below.

Note on CI: the WLED 16.0.1 manifest URL (apolloautomation.github.io/WLED-M1/manifest.json) goes live when ApolloAutomation/WLED-M1 PR #1 merges and its Pages workflow deploys. Until then the validate job fails on exactly that one URL. Re-run the check after that lands and it goes green. This PR should merge only once that happens, so the 16.0.1 button never 404s for a real user.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@bharvey88, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 288f68ec-b49d-4694-96e1-a8b8ba604ffc

📥 Commits

Reviewing files that changed from the base of the PR and between 754ba1a and 2ddc562.

⛔ Files ignored due to path filters (1)

• images/m-1.jpg is excluded by !**/*.jpg

📒 Files selected for processing (2)

• devices.json
• docs/m1-wled-migration.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/m1-wled-entry

---

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.}