feat: 添加 Analytics 分析功能(行为追踪、错误码、协议更新)
This commit is contained in:
@@ -84,6 +84,16 @@ When creating/modifying/deprecating any code, this table must be updated in the
|
||||
| `AUTH_REFRESH_TOKEN_MISSING` | auth | 401 | Refresh token is missing for logout/refresh |
|
||||
| `AUTH_USER_NOT_FOUND` | auth | 404 | User lookup by phone returns no match |
|
||||
| `AUTH_UNAUTHORIZED` | auth | 401 | Authorization header or token is invalid |
|
||||
| `ANALYTICS_LOGIN_PASSWORD_INVALID` | analytics | 401 | Analytics dashboard password is invalid |
|
||||
| `ANALYTICS_AUTH_HEADER_MISSING` | analytics | 401 | Authorization header is missing when reading analytics data |
|
||||
| `ANALYTICS_AUTH_SCHEME_INVALID` | analytics | 401 | Authorization scheme is invalid; Bearer token required |
|
||||
| `ANALYTICS_AUTH_TOKEN_MISSING` | analytics | 401 | Bearer token is missing |
|
||||
| `ANALYTICS_TOKEN_MALFORMED` | analytics | 401 | Analytics token format is malformed |
|
||||
| `ANALYTICS_TOKEN_SIGNATURE_INVALID` | analytics | 401 | Analytics token signature verification failed |
|
||||
| `ANALYTICS_TOKEN_PAYLOAD_INVALID` | analytics | 401 | Analytics token payload cannot be parsed |
|
||||
| `ANALYTICS_TOKEN_EXPIRED` | analytics | 401 | Analytics token is expired |
|
||||
| `ANALYTICS_DATE_FORMAT_INVALID` | analytics | 400 | Analytics date must use YYYY-MM-DD format |
|
||||
| `ANALYTICS_FILE_NOT_FOUND` | analytics | 404 | Analytics day file does not exist |
|
||||
| `JWT_VERIFIER_NOT_CONFIGURED` | auth | 503 | JWT verifier configuration is missing |
|
||||
| `AUTOMATION_JOB_LIMIT_EXCEEDED` | automation_jobs | 400 | User-created automation jobs exceed allowed limit |
|
||||
| `AUTOMATION_SYSTEM_JOB_MODIFICATION_FORBIDDEN` | automation_jobs | 403 | System bootstrap job cannot be modified |
|
||||
@@ -150,29 +160,13 @@ When creating/modifying/deprecating any code, this table must be updated in the
|
||||
| `FRIENDSHIP_NOT_FOUND` | friendships | 404 | Friendship record not found |
|
||||
| `FRIENDSHIP_REMOVE_REQUIRES_ACCEPTED` | friendships | 400 | Only accepted friendships can be removed |
|
||||
|
||||
## Registry Coverage Check Script
|
||||
## Registry Coverage Check
|
||||
|
||||
Use the checker script to ensure this registry and frontend code mapping stay aligned:
|
||||
当前仓库未内置自动校验脚本,维护流程按以下约束执行:
|
||||
|
||||
```bash
|
||||
python3 scripts/check_error_code_registry.py
|
||||
```
|
||||
|
||||
Optional arguments:
|
||||
|
||||
- `--doc`: custom registry markdown path
|
||||
- `--mapper`: custom frontend mapper path (default: `apps/lib/core/network/error_code_mapper.dart`)
|
||||
|
||||
Output always includes three result groups:
|
||||
|
||||
- doc has code but frontend has no mapping
|
||||
- frontend maps code but doc has no such code
|
||||
- duplicate codes
|
||||
|
||||
Exit code policy:
|
||||
|
||||
- `0`: no inconsistency found
|
||||
- non-`0`: at least one inconsistency found or input path invalid
|
||||
- 更新本文件错误码时,同步检查前端映射文件:`apps/lib/data/network/error_code_mapper.dart`
|
||||
- 任何新增/变更/废弃错误码必须在同一 PR 中完成「协议文档 + 前端映射 + 后端返回码」三方对齐
|
||||
- 若后续补充自动校验脚本,需在本节追加命令与输出约定
|
||||
|
||||
## Agent Error Code Set
|
||||
|
||||
|
||||
Reference in New Issue
Block a user