♿ fix(api): improve accessibility of error responses

[claude]

Summary

This PR improves developer accessibility by replacing raw exception strings with user-friendly, actionable messages in API error responses, while logging detailed errors server-side for debugging.

Changes

• users.py: Add logging and user-friendly messages for user management errors
• file.py: Add logging and user-friendly messages for file operation errors
• openai.py: Add logging and user-friendly messages for OpenAI-compatible endpoints
• workflow.py: Add logging and user-friendly messages for workflow operation errors
• collection.py: Add logging and user-friendly messages for collection operation errors
• Memory: Add accessibility issue and insight files documenting the pattern

Benefits

• ✅ Provides clear, actionable error messages to users
• ✅ Logs detailed errors server-side for debugging
• ✅ Avoids exposure of internal implementation details
• ✅ Maintains consistent error response format across all endpoints
• ✅ Enhanced security by not exposing internals in production

Testing

• All typecheck and lint checks pass
• All API tests pass (file API, workflow API)
• Full test suite: 4112 passed, 8 failed (pre-existing SERP provider issues unrelated to this change)

Example

# Before:
except Exception as e:
    raise HTTPException(status_code=500, detail=str(e)) from e

# After:
except Exception as e:
    log.error("Error listing files in %s: %s", path, e)
    raise HTTPException(
        status_code=500,
        detail="Failed to list files. Please check the path and try again.",
    ) from e

🤖 Generated with Claude Code