[FEATURE] Output format option as YAML for readability

[edenreich]

Summary

I would like the Debugger to output in YAML format when passing -o yaml (this should be default behavior).

It should support also JSON output. When for example I want to call the tasks list, I would expect to see something like:

tasks:
  - id: some-id
    ...
  - id:
    ...

Acceptance Criteria

• The debugger supports format options for YAML or JSON
• The code is using proper standard libraries for unmarshal or marshal structured objects
• It's documented
• It's tested

[edenreich]

@claude Can you work on it?

[claude]

Claude finished @edenreich's task —— View job • claude/issue-14-20251005-1349 • Create PR ➔

---

I've successfully implemented the output format feature for YAML and JSON support!

Todo List

• Analyze existing CLI structure and output patterns
• Add global output format flag (-o yaml|json)
• Implement YAML and JSON formatting functions
• Update all commands to support new output formats
• Add comprehensive tests for new functionality
• Update documentation
• Run development workflow (generate, lint, build, test)
• Commit changes and create PR

✅ Implementation Complete!

I've successfully implemented the output format feature as requested in issue #14. Here's what was delivered:

🎯 Core Features Implemented

• Global Output Flag: Added -o, --output flag supporting yaml (default) and json formats
• YAML Default: YAML is now the default output format as requested in the issue
• JSON Support: Full JSON output support via -o json flag
• Standard Libraries: Using gopkg.in/yaml.v3 and encoding/json as requested

📝 Commands Updated

All major commands now output structured data exactly as shown in the issue example:

• tasks list - Shows tasks array with metadata in structured format
• tasks get - Task details in YAML/JSON
• tasks history - Conversation history structured
• config list - Configuration in structured format
• agent-card - Agent information in YAML/JSON
• connect - Connection status with agent info
• version - Version information structured
• submit - Task submission results

✅ Quality Assurance

• Tests Added: Comprehensive tests for output formatting functions
• All Linting Passed: Code passes golangci-lint checks
• Build Success: Project builds successfully
• Documentation Updated: README includes examples and usage instructions

📋 Example Output

The implementation matches the requested format from the issue:

# a2a tasks list (YAML default)
tasks:
  - id: task-abc123
    context_id: ctx-xyz789
    status:
      state: completed
    # ... more task details
total: 23
showing: 2

# Switch to JSON
a2a tasks list -o json

🔗 All Acceptance Criteria Met

• ✅ The debugger supports format options for YAML or JSON
• ✅ The code uses proper standard libraries for marshal/unmarshal
• ✅ It's documented with examples in README
• ✅ It's tested with comprehensive test coverage

[ig-semantic-release-bot]

🎉 This issue has been resolved in version 0.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀