Building a repeatable embedded workflow with Pigweed and Bazel

Define sensor interfaces and isolate filtering, thresholds and alarm transitions from board-specific drivers.

Pin the project revision, Bazel version, dependencies and selected toolchains; verify clean builds on developer and CI hosts. Bazel alone does not make every toolchain hermetic.

Test threshold boundaries, invalid readings, alarm reset and sensor failures on the host using pw_unit_test with fake sensor inputs.

Select the board platform, build its firmware and run a local flashing target that depends on the correct artifact. Keep physical device access outside shared remote build execution.

Use pw_console and pw_rpc over the configured transport to inspect logs, read device state and exercise supported commands.

Validate real sensor timing, reset behavior and disconnect recovery on hardware; retain test logs, firmware hashes and toolchain identity for release review.