What problem does it solve? When a music generation fails, the ace-server engine crashes, or the HOT-Step CPP app hangs with no progress, the cause is buried across three interleaved log files. This Skill provides a log-driven playbook that maps each symptom to the exact log file to open first, decodes real failure strings, and correlates a gen_<uuid> log back to engine output. ## Core Features & Use Cases - Symptom-to-log triage tables: Match failures like "Generation stalled", HTTP 503 "Engine not ready", or exit code 3221226505 to their root causes in node_console.log, ace_engine.log, or per-generation gen logs. - Safe operational rules: Enforces critical constraints such as never killing ace-server.exe externally (it triggers a respawn/file-lock loop) and rebuilding only via dev-rebuild.bat. - Copy-paste PowerShell command pack: The bundled reference.md provides ready triage commands, API response shapes for /api/health and /api/generate/queue, watchdog timing constants, and Windows exit-code meanings. - Use Case: A user's generation failed with a generic "Generation failed on ace-server" message. Use this Skill to locate the newest logs/ session folder, read the gen log's failure line, then grep node_console.log for FATAL or CUDA error lines to find the real engine-side cause. ## Quick Start Diagnose why my last HOT-Step music generation failed by reading the newest session folder under logs/ and tracing the gen log back to the engine output.
