orchestrator: Compose boot-walk supervision from the board's BootWatch capability ReleaseReset arms the component's walk, AssertReset stops it, and the new PlatformDriver::poll_boot_walks maps terminal verdicts to events: Complete becomes ComponentReady (Active) or Booted (Passive), Failed becomes Timeout regardless of cause — retry budgeting is the SM's. A finished walk stops being watched, so each verdict is delivered once; while everything waits, the poll carries the earliest walk deadline as the run loop's next wake-up. BootWatch gains arm(): a retry re-release starts a fresh walk, and since reset actuation has no clock, the attempt starts at the next poll's now_millis. The Board supplies one walk and one ComponentKind per component, from the same table as the SM's chain. The driver README still described take_event and NotImplemented, both gone; rewritten to the current execute/fail-closed shape. Signed-off-by: Christina Quast <christina.quast@9elements.com>
The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md
NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.
You can run tasks using the Pigweed workflow launcher pw or bazel.
./pw presubmit - Run presubmit checks: formatting, license checks, C/C++ header checks and clippy../pw format - Run the code formatters.bazel test //... - Run all tests.bazel build //docs - Build documentation.The project is structured as a bazel module.
No additional tools are required - all dependencies are managed by bazel.