Part of #3201 (shadcn/ui migration epic).
Phase 4 — end-of-ride design decisions (ALL decisions, made fresh on the working app)
Per user directive: no carried decisions. With shadcn stock + original palette ported (i.e. a working, look-preserving app), the user decides — unbound by earlier lane-A/B/C mock work (those remain reference material only):
- Palette: keep the original 9-palette look, or restyle? If restyle: which direction (the old minimalist/soft/brutalist mocks may be re-viewed as references)?
- Specials: keep+restyle (current state) vs replace any of echarts/xterm/novnc/cytoscape/leaflet?
- Density/layout: any layout changes wanted now that components are shadcn?
- Anything else the user wants adjusted "when needed".
Process: agent writes one DECISION--.md per topic to /home/xore/desktop/ (STATUS: WAITING, options + recommendation first); user answers; agent applies answers in #shadcn-9. Multiple topics can be asked in one batch to minimize round-trips.
Gate: all decision files answered (STATUS: DECIDED) before #shadcn-9 starts.
Part of #3201 (shadcn/ui migration epic).
Phase 4 — end-of-ride design decisions (ALL decisions, made fresh on the working app)
Per user directive: no carried decisions. With shadcn stock + original palette ported (i.e. a working, look-preserving app), the user decides — unbound by earlier lane-A/B/C mock work (those remain reference material only):
Process: agent writes one DECISION--.md per topic to /home/xore/desktop/ (STATUS: WAITING, options + recommendation first); user answers; agent applies answers in #shadcn-9. Multiple topics can be asked in one batch to minimize round-trips.
Gate: all decision files answered (STATUS: DECIDED) before #shadcn-9 starts.