Improve error messaging & CLI UX

Rationale

Clear, actionable error messages and intuitive CLI interfaces are critical for developer experience. Current error handling may be opaque, making debugging and troubleshooting time-consuming for users.

Suggested Scope

• Audit error messages across SDK and CLI for clarity and actionability
• Implement structured error types with context and suggestions
• Enhance CLI help text, usage examples, and error recovery hints
• Add verbosity levels (quiet/normal/verbose/debug) for graduated output
• Implement color and formatting for readability
• Add error code documentation and troubleshooting guide
• Create developer-friendly error handling patterns

Effort Estimate

Medium (2-3 weeks) depending on scope of CLI surface area.

Success Criteria

• All user-facing errors are descriptive with actionable next steps
• CLI help and examples are clear and discoverable
• Error codes documented with troubleshooting guide
• Verbosity levels working across CLI commands
• User testing validates improved UX

The issue covers error handling across the SDK and CLI but names no files, tests, or specific command entry points. Start by mapping the CLI surface and current user-facing errors, then define a manageable scope before changing anything. Done means the selected errors, help text, verbosity behavior, and documentation meet the stated success criteria.