mirror of
https://github.com/okieselbach/AutopilotMonitor.git
synced 2026-10-24 04:32:32 +00:00
44203423ec
Devices that hit the ESP terminal timeout in DeviceSetup on a profile that allows "Continue anyway" are recorded as Failed even though the user most likely dismissed the error and reached the desktop. The existing advisory- defang only covers AccountSetup failures, so DeviceSetup timeouts (e.g. a slow blocking app missing the 30-min wall) show up as hard failures. Add a built-in, enabled-by-default analyze rule (severity: warning) keyed on enrollment_failed.mayHaveContinuedAnyway==true. It surfaces the soft failure and points at the root cause (slow blocking app / ESP timeout / detection mismatch / masked certificate failure) without changing session lifetime or the terminal status. No agent change required; ships via EmbeddedResource or ReseedFromGitHub. Tests: RuleEngineEspSoftFailureTests (fires on the continue-anyway shape, stays silent on hard failures and when the flag is absent). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>