[codex] publish fbuild usb vidpid overlay

[zackees]

What changed

• Add online-data-tools/build_usb_vid_proto.py to encode merged usb-vid.json into the usb-vids.proto.zstd protobuf/zstd runtime artifact that fbuild_core::usb already knows how to read.
• Wire Update data to publish data/usb-vids.proto.zstd on the online-data branch whenever the USB merge succeeds.
• Move USB_VIDS_PROTO_ZSTD_URL from fastled.github.io/boards to the fbuild online-data branch.
• Surface CDC classification through fbuild port scan, daemon DeviceState, device list/status API responses, and CLI fbuild device output.
• Document source precedence: third-party SDK/package rows are weak supplemental inputs that fill gaps only; local FastLED board data and first-party/vendor sources remain stronger.

Why

The runtime scan path was fetching a compact VID/PID overlay from fastled.github.io/boards, while this repo's online-data workflow only published JSON/SQLite/vendor artifacts. That left fbuild dependent on an external board artifact for product-level VID/PID resolution. This makes fbuild publish and consume its own compact artifact.

The device surfaces also exposed vendor/product but not the requested CDC-vs-bridge signal. The new nullable is_cdc field reports true for CDC ACM, false for USB serial bridge, and null when the host cannot classify the port.

Follow-up note

First-party repo board data remains the support boundary: if a board is not present under crates/fbuild-config/assets/boards, it may not exist as an fbuild-supported board. Remaining product-PID gaps should be researched from internet/vendor sources only for boards that are present in that repo board set; third-party SDK/package findings can weakly fill missing VID/PID names but must not override first-party, vendor-owned, or generic USB-ID winners.

Validation

• uv run --no-project --with pytest --with zstandard pytest online-data-tools/test_usb_vid_proto.py -q
• soldr cargo test -p fbuild-core usb::data --lib
• soldr cargo test -p fbuild-cli port_scan --lib
• soldr cargo test -p fbuild-cli cdc_suffix --lib
• soldr cargo test -p fbuild-daemon device_manager --lib
• soldr cargo test -p fbuild-daemon deploy_port --lib
• soldr cargo test -p fbuild-cli --lib
• soldr cargo test -p fbuild-daemon --lib
• soldr cargo test -p fbuild-serial --lib
• soldr cargo test -p fbuild-packages --lib
• soldr cargo clippy -p fbuild-serial --all-targets -- -D warnings
• soldr cargo clippy -p fbuild-build --tests -- -D warnings
• soldr cargo doc -p fbuild-build --no-deps with RUSTDOCFLAGS=-D warnings
• soldr cargo doc -p fbuild-cli --no-deps with RUSTDOCFLAGS=-D warnings
• docker run --rm -v "${PWD}:/work" -w /work rust:1.94.1 bash -lc "export PATH=/usr/local/cargo/bin:$PATH; cargo fmt --all -- --check"
• uv run --no-project python ci/render_workflows.py --check
• uv run --no-project python -m py_compile ci/validate_boards.py
• git diff --check

Also generated the artifact from the current published usb-vid.json: 1,946 vendors, 22,258 products, 260,305-byte usb-vids.proto.zstd.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: bda33d1e-50a4-48d1-a1ab-1ead8fa7005f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/usb-vid-proto-online-data

---

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