koan-debugging

Diagnose Koan app startup failures by analyzing boot logs using `docker logs koan-app --tail 20 --follow | grep "Koan:"` to identify module loading errors, provider election problems, and configuration warnings. In development, call `KoanEnv.DumpSnapshot(logger)` to capture a full initialization snapshot for detailed inspection.

These errors typically stem from missing service registrations, incorrect module discovery, or DI wiring failures. Use boot report analysis to verify registrar visibility, confirm module discovery completed, validate provider capabilities match service requirements, and check configuration correctness across Bootstrap and Initialization phases.

Resolve N+1 query problems and out-of-memory errors by implementing batch operations and streaming patterns. Review boot reports to identify provider election and configuration issues, then apply targeted performance diagnostics to validate query execution and resource allocation.

Yes, the Skill provides container debugging guidance for troubleshooting startup failures, networking connectivity, and health check configuration in containerized Koan deployments. Analyze boot logs and provider election decisions to resolve multi-provider scenarios and cross-container service discovery problems.

When wrong provider election occurs, examine boot logs for provider registration order, configuration overrides, and capability mismatches. Verify each provider's visibility in the registrar, confirm module discovery sequence, and validate DI wiring to ensure the highest-priority provider matching service requirements gets selected.

Validate module registration by reviewing boot reports to confirm all modules were discovered and registered correctly. Check registrar visibility for each module, verify provider election results, confirm DI wiring is complete, and inspect configuration for misconfigurations that prevent auto-discovery or affect provider selection.