Repository navigation
Control responsiveness trial: stop redundant dock inspection and isolate RCB diagnostics - #635
Conversation
|
Companion command scheduling PR #638 is now stacked on this PR #635 at exact base |
|
2026-10-20 control audit: follow-up draft PR #640 (stacked #638 -> #635) fixes source-proven Command Dock flicker: |
|
D28 archival on maintainer direction: older experimental IEC 61850 branch superseded by the latest successful, operator-accepted baseline. The operator will not recapture evidence for this historical trial. Closing as NOT MERGED, without modifying runtime or stable release. Historical HEAD |
Based on the installed field build 99d39c7 (P0-E + viewport stack), preserving its report causality and command flight authority.
Opening the Command Dock previously forced inspection of every selected control, including verified status-only targets. Inspection invalidates descriptors and queues MMS work. Reopening now uses existing verified state, while explicit Refresh still requests fresh inspection. Busy targets are excluded; inspection ownership is claimed before local throttle wait and cleaned up on cancellation.
Pins ARIEC61850 PR #183 at c85d4e20db722bd0c2729f2533b323b13d3ef735: non-RCB control InformationReports cannot become BRCB frames via single-monitor fallback. Ordered command evidence now exposes service and post-response wait durations for locating the observed 8–13 second native action latency.
Validation: engine compiled with zero warnings/errors; 64 relevant Fact tests invoked directly passed. Standard local test host fails before execution in the container; Windows CI and physical acceptance remain pending. Added inspection policy regression. No claim that the complete physical command delay is fixed. No timeout/interlock changes and no main merge or release. See docs/CONTROL_LATENCY_TRIAL_2026-10-20.md.