bytelyst/learning_ai_invt_trdg
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ui): add platform migration handoff

Browse Source
This commit is contained in:
Saravana Achu Mac 2026-05-06 20:32:12 -07:00
parent 6091f241d6
commit af74867fc0
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/UI_UX_PLATFORM_CORE_MIGRATION_ROADMAP.md
View File

@ -97,3 +97,21 @@ Note: common platform had a pre-existing local modification in `packages/ui/src/
- Do not move trading-domain behavior into common platform.
- Keep Gitea and vendor support available; use local common platform for implementation and verification.
- Commit and push each implementation step, then update this roadmap with commit hash and verification notes in a separate commit.
## Next Agent Handoff
Use this document as the live source of truth for the remaining UI/UX platform-core migration. Before continuing, pull the latest repo state and rebase any local branch on top of the pushed roadmap updates:
```bash
git fetch origin
git pull --rebase origin main
```
Then read this file end-to-end and continue phase 12 from the current baseline:
- **Current phase**: 12. Legacy global cleanup and strict audit.
- **Current audit baseline**: 0 direct `@bytelyst/ui` imports outside the adapter, 0 raw production controls outside approved primitives, 0 legacy global surface classes, and 447 hardcoded color literals.
- **Next focus**: classify the remaining hardcoded color literals, move reusable surface/status/list/table colors to `web/src/index.css` token aliases, keep legitimate chart/trading semantic colors product-owned, and enable or enforce `pnpm run audit:ui:strict` with explicit allowlisting where needed.
- **Verification after each slice**: run `pnpm run audit:ui`, targeted DOM tests for touched files, `pnpm --filter @bytelyst/trading-web typecheck`, and `git diff --check`; add `pnpm --filter @bytelyst/trading-web lint` and broader tests before major commits.
- **Roadmap update requirement**: after every implementation commit, update the roadmap row/checkboxes with the new status, final audit counts, exact verification commands, commit hash, and any deferrals or environment blockers.
- **Commit/push rule**: keep commits small and scoped, push each completed slice, then update this document in a follow-up docs commit so the next agent can resume without reconstructing context.