Add USB/Battery Power variants for TEMP-1 and PLT-1

[bharvey88]

What does this change?

Gives TEMP-1 and PLT-1 a USB Power / Battery Power variant toggle (like R_PRO-1's WiFi/Ethernet), and fixes TEMP-1 to flash the current R2 firmware.

TEMP-1 — its firmware pointed at firmware/ (the pre-R2 build); the current board is R2, so:

• USB Power → firmware2/ (TEMP-1_R2) — this corrects the firmware TEMP-1 owners get
• Battery Power → firmware-b2/ (TEMP-1B_R2) — new

PLT-1 — USB Power firmware unchanged; adds the battery build:

• USB Power → firmware/ (PLT-1)
• Battery Power → firmware-b/ (PLT-1B)

Each variant rewires both the flashed firmware and the config viewer (#3). The existing data-driven Playwright tests now also exercise temp-1/plt-1 as multi-variant devices.

Note: the battery firmware folder names (firmware-b, firmware-b2) are the product repos' existing build output paths, referenced as-is — not renamed.

Checklist

• Playwright tests pass locally (cd tests && npx playwright test) (18 passed, 1 intentional skip)
• Any new runtime file/dir is added to the cp list in .github/workflows/pages.yml (n/a: devices.json data only)
• No new build step, framework, or runtime CDN dependency
• If devices.json changed: python scripts/validate_registry.py passes (Registry OK — all manifests + config URLs return 200)

🤖 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: 23 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: e7390fc6-8059-4f90-b78c-1fd45de6648a

📥 Commits

Reviewing files that changed from the base of the PR and between 2af5615 and 71d6b01.

📒 Files selected for processing (1)

• devices.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/battery-power-variants

---

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