refactor: refactor error code definitions

- Consolidate error code definitions into error_code.go
- Optimize error code structure with functional categorization
- Improve error code documentation and comments

Author: RanchoCooper

README.md

@@ -383,110 +383,65 @@ The project has recently undergone the following improvements:
 ### 3. Eliminated Global Variables
 - **Problem**: The project used global variables to store service instances, violating dependency injection principles
 - **Solution**:
-  - Removed the use of global variables `service.ExampleSvc` and `service.EventBus`
-  - Passed service instances through dependency injection
-  - Initialized services using dependency injection when starting the HTTP server
+  - Removed global service variables
+  - Properly injected services via the Factory pattern
+  - Improved testability by making dependencies explicit
 
-### 4. Improved Application Layer Integration
-- **Problem**: Application layer use cases were not fully utilized, with the HTTP server not enabling the application layer by default
+### 4. Enhanced Architecture Validation
+- **Problem**: Architecture validation was manual and prone to errors
 - **Solution**:
-  - Enabled application layer use cases by default
-  - Used the use case factory to create and manage use cases
-  - Implemented clearer error handling and response mapping
+  - Implemented automated layer dependency checking
+  - Enforced strict architectural boundaries through code scanning
+  - Added validation to CI pipeline
 
-## Recent Optimizations
-
-The project has recently undergone the following optimizations:
-
-1. **Environment Variable Support**:
-   - Added functionality for environment variable overrides for configuration files, making the application more flexible in containerized deployments
-   - Used a unified prefix (APP_) and hierarchical structure (e.g., APP_MYSQL_HOST) to organize environment variables
-
-2. **Unified Error Handling**:
-   - Implemented an application-level error type system, supporting different types of errors (validation, not found, unauthorized, etc.)
-   - Added unified error response handling, mapping internal errors to appropriate HTTP status codes
-   - Improved error logging to ensure all unexpected errors are properly recorded
+### 5. Graceful Shutdown
+- **Problem**: Application didn't handle shutdown gracefully, potentially causing data loss
+- **Solution**:
+  - Implemented a graceful shutdown mechanism for the server, ensuring all in-flight requests are completed before shutting down
+  - Added shutdown timeout settings to prevent the shutdown process from hanging indefinitely
+  - Improved signal handling, supporting SIGINT and SIGTERM signals
 
-3. **Request Logging Middleware**:
-   - Added detailed request logging middleware to record request methods, paths, status codes, latency, and other information
-   - In debug mode, request and response bodies can be logged to help developers troubleshoot issues
-   - Intelligently identifies content types to avoid logging binary content
+### 6. Internationalization Support
+- **Problem**: The application lacked proper internationalization support
+- **Solution**:
+  - Added translation middleware for multi-language validation error messages
+  - Automatically selected appropriate language based on the Accept-Language header
 
-4. **Request ID Tracking**:
-   - Generated unique request IDs for each request, facilitating tracking in distributed systems
-   - Returned request IDs in response headers for client reference
-   - Included request IDs in logs to correlate multiple log entries for the same request
+### 7. CORS Support
+- **Problem**: Cross-origin requests were not properly handled
+- **Solution**:
+  - Added CORS middleware to handle cross-origin requests
+  - Configured allowed origins, methods, headers, and credentials
 
-5. **Graceful Shutdown**:
-   - Implemented a graceful shutdown mechanism for the server, ensuring all in-flight requests are completed before shutting down
-   - Added shutdown timeout settings to prevent the shutdown process from hanging indefinitely
-   - Improved signal handling, supporting SIGINT and SIGTERM signals
+### 8. Debugging Tools
+- **Problem**: Diagnosis of performance issues in production was difficult
+- **Solution**:
+  - Integrated pprof performance analysis tools for diagnosing performance issues in production environments
+  - Can be enabled or disabled via configuration file
 
-6. **Internationalization Support**:
-   - Added translation middleware for multi-language validation error messages
-   - Automatically selected appropriate language based on the Accept-Language header
+### 9. Advanced Redis Integration
+- **Problem**: Redis implementation was limited and lacked proper connection management
+- **Solution**:
+  - Enhanced Redis client with proper connection pooling
+  - Added comprehensive health checks and monitoring
+  - Improved error handling and connection lifecycle management
 
-7. **CORS Support**:
-   - Added CORS middleware to handle cross-origin requests
-   - Configured allowed origins, methods, headers, and credentials
+### 10. Structured Request Logging
+- **Problem**: API requests lacked proper logging, making debugging difficult
+- **Solution**:
+  - Implemented comprehensive request logging middleware
+  - Added request ID tracking for correlating logs
+  - Configured log levels based on status codes
 
-8. **Debugging Tools**:
-   - Integrated pprof performance analysis tools for diagnosing performance issues in production environments
-   - Can be enabled or disabled via configuration file
+### 11. Unified Error Response Format
+- **Problem**: Error responses had inconsistent formats across the API
+- **Solution**:
+  - Standardized error response structure with code, message, and details
+  - Added documentation references to errors
+  - Implemented consistent HTTP status code mapping
 
 These optimizations make the project more robust, maintainable, and provide a better development experience.
 
-## Usage Guide
-
-### Environment Preparation
-
-Start MySQL using Docker:
-```bash
-docker run --name mysql-local \
-  -e MYSQL_ROOT_PASSWORD=mysqlroot \
-  -e MYSQL_DATABASE=go-hexagonal \
-  -e MYSQL_USER=user \
-  -e MYSQL_PASSWORD=mysqlroot \
-  -p 3306:3306 \
-  -d mysql:latest
-```
-
-### Development Tool Installation
-
-```bash
-# Install development tools
-make init && make precommit.rehook
-```
-
-Or install manually:
-
-```bash
-# Install pre-commit
-brew install pre-commit
-# Install golangci-lint
-brew install golangci-lint
-# Install commitlint
-npm install -g @commitlint/cli @commitlint/config-conventional
-# Add commitlint configuration
-echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js
-# Add pre-commit hook
-make precommit.rehook
-```
-
-### Running the Project
-
-```bash
-# Run the project
-go run cmd/main.go
-```
-
-### Testing
-
-```bash
-# Run tests
-go test ./...
-```
-
 ## Extension Plans
 
 - **gRPC Support** - Add gRPC service implementation

README.zh.md

@@ -362,131 +362,86 @@ logger.InfoContext(logCtx, "正在创建新实体",
     zap.String("entity_name", entity.Name))
 ```
 
-## 项目优化
+## 项目改进
 
-本项目最近经过以下优化：
+本项目最近进行了以下改进：
 
 ### 1. 统一API版本
-- **问题**：项目同时存在v1和v2 API版本，导致代码重复和维护困难
+- **问题**：项目同时存在v1和v2两个API版本，导致代码重复和维护困难
 - **解决方案**：
-  - 统一API路由，将所有API放在`/api`路径下
+  - 统一API路由，所有API都放在`/api`路径下
   - 保留`/v2`路径以向后兼容
-  - 使用应用层用例处理所有请求，逐步淘汰直接调用领域服务
+  - 使用应用层用例处理所有请求，逐步淘汰直接的领域服务调用
 
 ### 2. 增强依赖注入
 - **问题**：Wire依赖注入配置存在重复绑定问题，导致生成失败
 - **解决方案**：
   - 重构`wire.go`文件，移除重复绑定定义
-  - 使用provider函数替代直接绑定
+  - 使用提供者函数代替直接绑定
   - 添加事件处理器注册逻辑
 
 ### 3. 消除全局变量
 - **问题**：项目使用全局变量存储服务实例，违反依赖注入原则
 - **解决方案**：
-  - 移除全局变量`service.ExampleSvc`和`service.EventBus`的使用
-  - 通过依赖注入传递服务实例
-  - 启动HTTP服务器时使用依赖注入初始化服务
+  - 移除全局服务变量
+  - 通过工厂模式正确注入服务
+  - 通过显式依赖提高可测试性
 
-### 4. 改进应用层集成
-- **问题**：应用层用例未充分利用，HTTP服务器默认不启用应用层
+### 4. 增强架构验证
+- **问题**：架构验证是手动且容易出错的
 - **解决方案**：
-  - 默认启用应用层用例
-  - 使用用例工厂创建和管理用例
-  - 实现更清晰的错误处理和响应映射
+  - 实现自动化层依赖检查
+  - 通过代码扫描强制严格的架构边界
+  - 将验证添加到CI流程
 
-## 最近的优化
-
-本项目最近经过以下优化：
-
-1. **环境变量支持**：
-   - 添加配置文件的环境变量覆盖功能，使应用在容器化部署中更灵活
-   - 使用统一前缀(APP_)和层次结构(如APP_MYSQL_HOST)组织环境变量
-
-2. **统一错误处理**：
-   - 实现应用级错误类型系统，支持不同类型的错误(验证错误、未找到、未授权等)
-   - 添加统一错误响应处理，将内部错误映射到合适的HTTP状态码
-   - 改进错误日志记录，确保所有意外错误被正确记录
+### 5. 优雅关闭
+- **问题**：应用程序没有优雅处理关闭过程，可能导致数据丢失
+- **解决方案**：
+  - 为服务器实现优雅关闭机制，确保所有运行中的请求在关闭前完成
+  - 添加关闭超时设置，防止关闭过程无限期挂起
+  - 改进信号处理，支持SIGINT和SIGTERM信号
 
-3. **请求日志中间件**：
-   - 添加详细的请求日志中间件，记录请求方法、路径、状态码、延迟等信息
-   - 在调试模式下，可以记录请求和响应体，帮助开发者排查问题
-   - 智能识别内容类型，避免记录二进制内容
+### 6. 国际化支持
+- **问题**：应用程序缺乏适当的国际化支持
+- **解决方案**：
+  - 添加翻译中间件，支持多语言验证错误消息
+  - 根据Accept-Language头自动选择适当的语言
 
-4. **请求ID跟踪**：
-   - 为每个请求生成唯一的请求ID，便于在分布式系统中跟踪
-   - 在响应头中返回请求ID，供客户端参考
-   - 在日志中包含请求ID，关联同一请求的多个日志条目
+### 7. CORS支持
+- **问题**：跨源请求没有得到正确处理
+- **解决方案**：
+  - 添加CORS中间件处理跨源请求
+  - 配置允许的来源、方法、头和凭据
 
-5. **优雅关闭**：
-   - 实现服务器的优雅关闭机制，确保所有运行中的请求在关闭前完成
-   - 添加关闭超时设置，防止关闭过程无限期挂起
-   - 改进信号处理，支持SIGINT和SIGTERM信号
+### 8. 调试工具
+- **问题**：在生产环境中诊断性能问题很困难
+- **解决方案**：
+  - 集成pprof性能分析工具，用于诊断生产环境中的性能问题
+  - 可以通过配置文件启用或禁用
 
-6. **国际化支持**：
-   - 添加翻译中间件，支持多语言验证错误消息
-   - 根据Accept-Language头自动选择适当的语言
+### 9. 高级Redis集成
+- **问题**：Redis实现有限，缺乏适当的连接管理
+- **解决方案**：
+  - 使用适当的连接池增强Redis客户端
+  - 添加全面的健康检查和监控
+  - 改进错误处理和连接生命周期管理
 
-7. **CORS支持**：
-   - 添加CORS中间件，处理跨域请求
-   - 配置允许的来源、方法、头和凭据
+### 10. 结构化请求日志
+- **问题**：API请求缺乏适当的日志记录，使调试变得困难
+- **解决方案**：
+  - 实现全面的请求日志中间件
+  - 添加请求ID跟踪，用于关联日志
+  - 根据状态码配置日志级别
 
-8. **调试工具**：
-   - 集成pprof性能分析工具，用于诊断生产环境中的性能问题
-   - 可通过配置文件启用或禁用
+### 11. 统一错误响应格式
+- **问题**：API中的错误响应格式不一致
+- **解决方案**：
+  - 标准化错误响应结构，包含代码、消息和详情
+  - 为错误添加文档引用
+  - 实现一致的HTTP状态码映射
 
 这些优化使项目更加健壮、可维护，并提供更好的开发体验。
 
-## 使用指南
-
-### 环境准备
-
-使用Docker启动MySQL：
-```bash
-docker run --name mysql-local \
-  -e MYSQL_ROOT_PASSWORD=mysqlroot \
-  -e MYSQL_DATABASE=go-hexagonal \
-  -e MYSQL_USER=user \
-  -e MYSQL_PASSWORD=mysqlroot \
-  -p 3306:3306 \
-  -d mysql:latest
-```
-
-### 开发工具安装
-
-```bash
-# 安装开发工具
-make init && make precommit.rehook
-```
-
-或手动安装：
-
-```bash
-# 安装pre-commit
-brew install pre-commit
-# 安装golangci-lint
-brew install golangci-lint
-# 安装commitlint
-npm install -g @commitlint/cli @commitlint/config-conventional
-# 添加commitlint配置
-echo "module.exports = {extends: ['@commitlint/config-conventional']}" > commitlint.config.js
-# 添加pre-commit钩子
-make precommit.rehook
-```
-
-### 运行项目
-
-```bash
-# 运行项目
-go run cmd/main.go
-```
-
-### 测试
-
-```bash
-# 运行测试
-go test ./...
-```
-
 ## 扩展计划
 
 - **gRPC支持** - 添加gRPC服务实现