Problem

When API calls fail (quota exceeded, permission denied, locked server, etc.), the error modal shows raw error text that can be opaque. Users need to understand why something failed and what to do about it.

Proposed Solution

• Parse common OpenStack error patterns and provide human-readable explanations
• Include suggested next steps where possible (e.g., "Quota exceeded — free up resources or contact your cloud admin")
• Preserve the raw API error for advanced users (e.g., expandable detail section)
• Ensure error text is not truncated for long messages

Priority

High — clear error handling is critical for user confidence, especially for operators new to lazystack.

Context

Identified during features & usability review.