[plan] Validate terminal output after lipgloss upgrade

[github-actions]

Objective

Perform comprehensive manual validation of all terminal output rendering after upgrading lipgloss to ensure no visual regressions.

Context

After upgrading lipgloss (either to v1.1.0 or latest commit), we need to manually test all terminal output scenarios to ensure consistent rendering across different terminal types and color modes.

Testing Scenarios

1. Console Output (pkg/console/console.go)

# Test error messages
./gh-aw compile nonexistent.md

# Test success messages
./gh-aw compile examples/hello-world.md

# Test table rendering
./gh-aw audit --json | jq

2. MCP Commands (pkg/mcp/)

# Test MCP list output
./gh-aw mcp list

# Test MCP inspect output
./gh-aw mcp inspect --help

3. Banner Rendering (pkg/console/banner.go)

# Test ASCII logo
./gh-aw --help

4. CLI Inspection (pkg/cli/inspect.go)

# Test inspection output
./gh-aw inspect examples/hello-world.md

5. Light/Dark Theme Support

Test in both light and dark terminal backgrounds using adaptive colors:

• Set terminal to light background and run commands
• Set terminal to dark background and run commands
• Verify colors are readable in both modes

Acceptance Criteria

• Error messages render correctly with proper colors
• Success/info/warning messages display as expected
• Tables render with proper borders and alignment
• ASCII banner displays correctly
• MCP output formatting is consistent
• Adaptive colors work in both light and dark terminals
• No visual regressions compared to current version
• All test scenarios documented with screenshots/examples

Files Affected

All files using lipgloss (6 total):

1. pkg/styles/theme.go
2. pkg/console/console.go
3. pkg/console/banner.go
4. pkg/mcp/server.go
5. pkg/mcp/inspect.go
6. pkg/cli/inspect.go
   Related to [plan] Upgrade lipgloss to stable v1.1.0 release #6473

AI generated by Plan Command for discussion #6470