What problem does it solve? PolyHost log bundles interleave output from multiple processes (tray, daemon, firmware console), so reading them as a single story leads to wrong diagnoses — mistaking duplicate launches for logging bugs, or normal first-flash states for crashes. This Skill reconstructs what actually happened and separates real faults from states that only look like faults. ## Core Features & Use Cases - Process census and timeline reconstruction: Counts processes via session start/clean exit lines in crash.txt and correlates timestamps across startup.txt, host.txt, daemon.txt, and keyboard-console.txt. - Known-deceptive-line detection: Flags misleading lines such as Connected to PolyKybd. (which does not mean a usable device), 0xE00002C5 exclusive-access errors (not proof of a second process), and stale font-pack bundles (usually a flash in progress). - Settings drift analysis: Compares per-run settings dumps to catch values like telemetry_install_id changing between runs. - Use Case: A user reports "two tray icons" and sends a polyhost-logs-*.zip bundle. The Skill unzips it, reads diagnostics.txt first, counts pids, builds a per-process timeline, and produces a structured report separating the actual bug from non-faults. ## Quick Start Unzip the attached PolyHost log bundle and diagnose what actually happened, separating real faults from states that only look like faults.
