orchestrator: Cascade past a component that is already isolated cascade_hold only queued a dependent it had just gated, so the walk stopped at a component isolated earlier and never reached what depends on it. Gate a middle node on its own, then corrupt its Cascading parent, and the component behind it comes out of reset with its whole dependency chain isolated. The frontier is the visited set now, so traversal continues through a gated component. gate_one is idempotent, so re-visiting one emits nothing. property_cascading_isolation_reaches_the_whole_subtree guards it. Assisted-by: Claude:claude-opus-5 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.