Enrich JSON/YAML Output with Metadata

[jtdub]

Problem

Current JSON/YAML output is minimal - just {"config": [...]}. It lacks context about what operation was performed, platform used, and when generated.

Proposed Solution

Include metadata in structured output:

• tool name and version
• platform
• operation type
• timestamp
• input file paths
• line count

Benefits

• Traceability
• Reproducibility
• Easier automation pipeline processing
• Better debugging

Acceptance Criteria

• JSON output includes metadata object
• YAML output includes metadata
• Option to exclude metadata for minimal output
• Documentation updated
• Tests updated