os-health-checklisted

<example> <commentary>User explicitly requested a system diagnostic.</commentary> user: "Run a system monitor check on the OS." assistant: Scans the event bus and state file, compiles liveness metrics, and reports them. </example> ## Dependencies This skill requires **Python 3.8+** and standard library only. No external packages needed. # OS Health Check Scan across the `context/events.jsonl` Event Bus stream, review `os-state.json` liveness, and compile system metrics without mutating user files. ## Execution Flow ### Phase 0: Intent Emission (Event Bus) ```bash python3 scripts/kernel.py emit_event --agent os-health-check --type intent --action scan_metrics ``` ### Phase 1: Context Gathering & OS State Lock ```bash python3 scripts/kernel.py state_update active_agent os-health-check python3 scripts/kernel.py acquire_lock monitor ``` If the lock acquisition fails, abort — the kernel handles stale lock cleanup automatically (see `os-clean-locks` if a stale lock persists). ### Phase 2: Analyze Event Bus Inspect the recent Event Bus (`tail -n 100 context/events.jsonl`) and calculate metrics: total intent vs. result events, hook error count (also check `context/memory/hook-errors.log`), and any agent that emitted `intent` without a matching `result` (crash signal). ### Phase 3: Inspect Memory & File Health Check `context/memory.md` length (`wc -l`), scan `context/.locks/` for leaked stale locks, and determine whether `memory_gc_due` should be flagged. ### Phase 3.5: