CyberMind-FR dc08a8c139 feat(profiles): boot reconciliation + watchdog exclusion for on-demand (ref #896) ... boot_should_start(m) is the pure boot policy (always-on/eager start immediately, on-demand/manual wait for a real wake) and watchdog_should_manage(m) documents/tests that no sleepable module is ever force-revived by secubox-watchdog. Investigation found: HEAD's secubox-watchdog has no auto-revive logic at all today (monitor_loop only logs up/down, restarts are manual-only); the unmerged feat/watchdog-auto-revive branch adds one gated purely on lxc.start.auto, which actuate.py::runtime_stop already clears before lxc-stop specifically to avoid this race — the same flag streamlit sleepers rely on for exclusion today. No separate exclusion file exists to reuse, so none was invented; once that branch merges it is already #896-safe with zero further wiring. The real, closeable gap was secubox-hub's own sidebar health-batch, which reported a sleeping on-demand module's inactive systemd unit as "warn". Added a profiles-side export (secubox-wakectl health-sync -> sleepable-modules.json, mirrors waf-sync/nginx-sync) and wired it into secubox-hub so a sleepable module shows "Asleep (on-demand)" instead of an alarm; a failed unit still alarms regardless. The full admin /health/ page reads module_prober.py/prober.py, which aren't sourced in this repo yet (TODO #393) -- documented as a precise cross-package follow-up. Co-Authored-By: Gerald KERMA <devel@cybermind.fr>		2026-07-20 16:51:56 +02:00
..
brainstorm/1465198-1777214258	fix(eye-remote): Fix route parameter naming and logic issues	2026-04-26 17:39:56 +02:00
sdd	feat(profiles): boot reconciliation + watchdog exclusion for on-demand (ref #896)	2026-07-20 16:51:56 +02:00