Fix Ambiq Apollo3 VID seed

[zackees]

Summary

• correct the Apollo3 MCU-to-VID seed from Luminary/TI 1cbe to the CH340 bridge VID used by SparkFun Artemis boards in this repo
• add a narrow online-data migration so the already-published stale AM_APOLLO3 -> 1cbe row is removed on the next refresh and replaced from the current seed
• document the Ambiq investigation caveat: generic USB IDs already cover 2aec:6011, SparkFun Arduino_Apollo3 has no vid.N/pid.N rows, and third-party/package data must merge only as weak supplemental data

Source notes

• linux-usb.org lists 1cbe as Luminary Micro Inc., 2aec:6011 as Ambiq Micro Converter, and 1a86:7523 as CH340 serial converter.
• SparkFun Arduino_Apollo3 boards.txt contains no VID/PID declarations, so there is no board-package PID table to ingest for Apollo3.
• The FastLED board repo entries for Apollo3 are SparkFun Artemis boards under crates/fbuild-config/assets/boards, uploaded with the serial loader path.

Closes #732

Validation

• uv run --no-project --with pytest pytest online-data-tools/test_orchestrators.py -q
• ruff check online-data-tools/update_www.py online-data-tools/test_orchestrators.py
• git diff --check
• live sanity checks against linux-usb.org and SparkFun Arduino_Apollo3

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 51 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 43c6c0e9-86a7-40a6-a873-f38e2416dd42

📥 Commits

Reviewing files that changed from the base of the PR and between 1a9e912 and 4e7f07e.

📒 Files selected for processing (4)

• online-data-tools/README.md
• online-data-tools/seed_mcu_to_vid.json
• online-data-tools/test_orchestrators.py
• online-data-tools/update_www.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/ambiq-vid-correction

---

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