mirror of
https://github.com/okieselbach/AutopilotMonitor.git
synced 2026-10-24 04:32:32 +00:00
Oliver Kieselbach
46058ffb90
Field measurement 3: a first-run agent that started after the update page (6a7d241d) left the whole update in Apps (ESP), failed and skipped updates were reported by nothing, and the lane listed a failed update's staged servicing stack as an installed KB. - Time attribution v5: update names before the first observed OobeNDUP start begin the update at the earlier of the first name and the update's first servicing step (after the window's ESP exit when one was seen before the name, else the first step of a package the update also serviced later). The fallback's ESP exit is per window, so a WhiteGlove part-1 exit no longer begins an update in part 2. OsUpdateSpan carries Outcome (installed/failed/skipped/unknown, the latest evidence wins) and NotInstalledKbs; Kbs lists only packages that reached Installed. The 2-h sweep recomputes the last 30 days. - ANALYZE-DEV-013 (update failed), DEV-014 (not offered after an earlier failure), DEV-015 (update check ended without a result): warning, never KO; a failure only from explicit names, every absence condition gated on the agent's names_capped marker; never two at once. - ShellCoreTracker rows never set the session start (D-315 list), ahead of the agent's first-run update page backfill. - The web lane names the outcome and the KBs not installed; MCP get_time_attribution mentions both. Real-event replay: 6a7d241d os_update 2358 s installed (was 55 min in esp_apps), e7551b82 failed with KB5124007 not installed. Rule dry runs and a sweep over all 97 update-page sessions since 2026-10-02 hit exactly the five field sessions. Functions 6,918, web 1,701, MCP 997 green. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>