Found 2026-07-16 while investigating two running scan rows a second apart. Facts: (1) one real scan, one process chain — but Hermione's scheduler launches the scanner through the\u2026

RSI diagnosis (CAROL-INI-2223b/2246, cookbook 456): Albus root-causes WHY CAROL-INI-2631-02 (row 999901535, 'CAROL-INI-2631-02: Auto-detected stuck process: SST Scanner (sst-scan-\u2026

Inspector detected that Hermione's Daily Process Sweep SAW broken processes but could NOT file the fix-initiatives (action_taken='file-failed') for: Developer Executor (ex-dev-01)\u2026

Hermione (Process Monitor) found 80 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026

Hermione (Process Monitor) found 81 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026

Hermione (Process Monitor) found 82 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026

Hermione (Process Monitor) found 84 registered scheduled/ongoing droids that write no run-audit row, so their liveness cannot be judged (silent observability blind spot). Instrume\u2026

The SST scanner records its run only in the SST scans table, not as a droid_runs row, so the Daily Process Sweep (which reads droid_runs) sees sst-scan-01 as never-ran. Wrap the s\u2026