feat: HSAP platform v2 — modular navigation, quality review, audit log, world model simulation

Major changes:
- New frontend (platform/web/): Vite + React 18 + TypeScript + Tailwind
- 4-module navigation: 数据送标 / 模型管理 / 车队管理 / 系统管理
- Data catalog with charts (DMS/ADAS/Lane 3-tab view)
- Quality review workflow (标注质检): Good/Fine/Bad scoring with auto-advance
- Audit enhancements: batch operations, rejection categories, Feishu notifications
- Operation audit log (操作日志)
- World model simulation studio (仿真工坊)
- Dataset version management with snapshots and diff
- ADAS 7-class dataset integration (138K images organized + compressed)
- User management with Feishu integration and pagination
- CRUD/search/filter on all pages, card layout redesign
- PIL-optimized image overlay rendering
- Auto-snapshot on build, in_review workflow stage
- Removed embedded algorithm code (now in workspace)
This commit is contained in:
2026-06-03 11:40:21 +08:00
parent 7c43b44c57
commit e72bc061c5
5487 changed files with 979207 additions and 6197 deletions

26
platform/web/node_modules/resolve/.claude/notes.md generated vendored Normal file
View File

@@ -0,0 +1,26 @@
# resolve package - session notes
## Versioning
- Manual versioning only - do NOT use `npm version`
- Edit package.json version directly, commit with message `v{version}`, then create annotated tag
- Changelog lives in git tag annotations, not a separate file
- Tag format: `git tag -a v{version} -m "{changelog}"`
## Code style
- `__proto__: null` on ALL object literals (prototype pollution protection)
- `.slice()` not `.substring()`
- One exported function per file
- Move nested/inner functions to module level when feasible
- Prefer non-hoisted declarations (function declarations at module level, not expressions)
- No mutation - copy objects instead of modifying inputs
## Testing
- `test/list-exports` is a git submodule with sparse checkout
- Tests should cover ALL entrypoints from fixtures, not just `'.'` subpaths
- Use `extensions: ['.js', '.json']` when testing exports resolution
## exports field implementation
- Uses `node-exports-info` for category semantics
- Categories: pre-exports, broken, conditions, patterns, pattern-trailers, current
- `exportsCategory` option or `engines: true` to auto-detect from consumer's engines.node
- Self-reference resolution respects node_modules boundaries