## Bug Description Logger output should be more user-friendly for debugging. Currently: 1. Logs output only JSON format which is hard to read 2. Missing fix suggestions for WARN/ERROR/FATAL levels 3. JSON errors not displayed as friendly multi-line markdown ## Steps to Reproduce 1. Run CLI with some config errors 2. Observe JSON-only log output 3. Try to understand the error and how to fix it ## Expected Behavior - Log output should support markdown format that can be easily copied - WARN/ERROR/FATAL logs should include actionable fix suggestions via an extra parameter - When errors occur, JSON should display as friendly multi-line markdown with proper indentation - Example expected output: ``` - { $: [11:20:36.990, INFO, defineConfig], _: {...} } - { $: [11:20:36.993, WARN, defineConfig], _: {...} } - { $: [11:20:38.378, ERROR, defineConfig], _: {...} } ``` ## Actual Behavior - Current logger only outputs JSON - No fix suggestions provided - Hard to copy/understand for AI debugging ## Additional Context - Context: CLI (tnmsc) - Related to logger library enhancement
Bug Description
Logger output should be more user-friendly for debugging. Currently:
Steps to Reproduce
Expected Behavior
Actual Behavior
Additional Context