Oliver Kieselbach 5029bdd4c3 v2 codex-01 phase 3: re-arm persisted deadlines after recovery replay
Wires IDeadlineScheduler.RehydrateFromSnapshot (long-present, zero
production callers) into EnrollmentOrchestrator.Start so deadlines
persisted inside DecisionState survive a restart. Without this any
safety-net armed pre-crash (HelloSafety, Part2Safety, FinalizingGrace,
ClassifierTick) silently vanishes and a resumed session can hang until
the max-lifetime watchdog trips.

Placement matters: the rehydrate call MUST run after the Fired event
is subscribed (step 12 in Start) AND after _ingress.Start (step 13)
because (a) past-due deadlines fire immediately via ThreadPool and
would otherwise fall into the void without a subscriber, (b)
OnDeadlineFired returns early when _ingress is null and would drop
the synthesised DeadlineFired signal. Put at step 13.5 just before
the WG Part-2 bridge so rehydrated fires precede fresh collector
signals.

Rehydrate failures are logged at error but do NOT throw — this path
will get a synthetic EffectInfrastructureFailure transition once
Codex follow-up #2 lands, at which point the session can terminate
cleanly instead of relying on the max-lifetime watchdog.

Tests (2 new in RecoveryPathTests):
  - Snapshot_with_past_due_deadline_fires_DeadlineFired_signal_on_start
    — end-to-end: scheduler fires via ThreadPool, bridge posts signal,
      signal reaches the SignalLog within 3s.
  - Snapshot_with_future_deadline_is_scheduled_but_not_yet_fired
    — future-due deadline reports IsScheduled=true, no premature fire.

All suites green: DecisionCore 146/146, Agent.V2.Core 640/640 (+2),
Functions 727/727. Build 0 warnings.

Plan: .claude/plans/codex-01-recovery-signallog-replay.md §3 Phase 3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-24 11:16:31 +02:00
2026-04-22 19:36:19 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-04-04 19:17:01 +02:00

Autopilot Monitor

Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.

Private Preview

Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.

Overview

Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:

  • Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
  • Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
  • Backend API — Azure Functions-based ingestion and processing pipeline
  • Web Dashboard — Next.js application for real-time monitoring and fleet analytics

Architecture

For detailed information about the system architecture, components, and data flow, see Architecture Documentation.

Documentation

Full documentation is available at autopilotmonitor.com/docs

License

This project uses a split licensing model:

  • MIT License — Agent (src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices
  • AGPL-3.0 — Backend (src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source

See LICENSE for full details.

S
Description
Windows Autopilot & Intune enrollment monitoring: live session timelines, fleet health, diagnostics, and an MCP server for AI-assisted troubleshooting.
Readme AGPL-3.0 60 MiB
Languages
C# 72.7%
TypeScript 25.7%
PowerShell 1%
JavaScript 0.5%