orchestrator: Drop verdicts for a component already isolated A failure verdict or a corruption report can be in flight from before the cascade gated its component. VerificationFailed and CorruptionDetected now return early when the component is gated. Recovering it re-walks the chain for a device that stays held, and on exhaustion a Required one locks the platform down over a cascade that was already contained, which contradicts the rule that a non-Required cascade never reaches lockdown. property_isolation_is_sticky_under_random_sequences guards both: after ReportIsolated(id), nothing in the rest of the run emits ReleaseReset or RecoverComponent for that id. The cursor invariant the walk depends on is written down on the field, since that property is what 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.