Analyze Logs

This is for debugging with evlog's structured logging system. It reads NDJSON files from `.evlog/logs/` where each line is a complete wide event with all request context in one place. No correlating multiple log lines to understand what happened. When errors occur, you get `error.data.why` and `error.data.fix` fields that actually explain the problem and suggest remediation. The skill knows to check for both compact and pretty-printed formats, hunt through monorepo structures, and walk you through setup if the file system drain isn't configured yet. Most useful when you're staring at a 500 error or mysterious slowdown and need to see exactly what the application saw, including business context like user data or payment details that got logged alongside the technical failure.