myco:debug-daemon-errors

Debug Myco daemon crashes by running the daemon in a failing scenario and following the playbook for log analysis and subsystem mapping. This process identifies the implicated area among PowerManager, SQLite, Outbox, Session lifecycle, and Executor subsystems to isolate the failure.

Outbox drain loops and scheduler starvation occur when daemon subsystems fail to process tasks efficiently. The playbook traces these root causes by mapping the Outbox and Executor subsystems, analyzing structured diagnostics, and applying surgical fixes to restore normal startup and shutdown behavior.

Trace phantom sessions and FK violations by applying the playbook's structured diagnostics and logging enhancements. This distinguishes timeout-related failures across the Session lifecycle and SQLite subsystems, enabling you to write regression tests and apply minimal surgical fixes for safe recovery.

Yes, this daemon debugging approach supports regression testing and safe recovery. It guides you to write regression tests for the identified root cause, apply surgical fixes, and verify startup resilience with clear failure signals to ensure stable daemon operation.

Use a structured playbook for daemon error diagnosis when you need to reduce mean time to recovery across complex subsystems. It is essential when facing daemon crashes, FK violations, scheduler starvation, or outbox drain loops that require systematic root-cause tracing and logging enhancements.