orchestrator/sm: recovery re-boots; guard out-of-turn verification verdicts

- quiesce_all: assert reset on every live component before a recovery re-walk,
  so recovery is a genuine platform re-boot and no live component is re-verified
  while running (closes the TOCTOU on already-released siblings)
- VerificationPassed: release only the component under verification (chain[cursor]);
  drop stale/out-of-turn verdicts, mirroring the INV9 guard on ComponentReady
- tests: quiesce coverage (multi-sibling, at-rest re-verify), plus a property
  test (INV8) asserting verify-before-release across random event sequences
2 files changed
tree: 43c9bc7f6efff95ba84e0596a3503dffee4cf5b0
  1. .github/
  2. docs/
  3. drivers/
  4. hal/
  5. openprot/
  6. platform/
  7. presubmit/
  8. services/
  9. target/
  10. third_party/
  11. tools/
  12. util/
  13. .bazelignore
  14. .bazelrc
  15. .bazelversion
  16. .clang-format
  17. .gitignore
  18. .semgrepignore
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. pw
  25. README.md
  26. rust-toolchain.toml
  27. workflows.json
README.md

OpenPRoT

Technical Charter

The OpenPRoT Technical Charter can be found at https://github.com/OpenPRoT/.github/blob/main/GOVERNANCE.md

Getting Started

NOTE: We are converting our build system to bazel. We recommend installing bazelisk to automatically manage bazel versions.

Available Tasks

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.

Development

The project is structured as a bazel module.

Requirements

  • Bazel. We recommend installing bazelisk to automatically manage bazel versions.

No additional tools are required - all dependencies are managed by bazel.