orchestrator-sm: test degraded-mode reporting Cover each point a component leaves service: `Isolable` exhaustion, `Cascading` exhaustion (root and transitive dependent both reported), runtime corruption under a non-`Required` policy, and `Required` exhaustion — asserting the recovery-failure report precedes the latch. Two negative cases pin the boundaries: a component that recovers within its budget reports nothing, and an already-gated component is not re-reported. `ECAP` and the one hand-sized `Orchestrator` follow the new `2N + 2` effect-buffer floor. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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.