Rollback frontend and config changes to commit a9a7e98 state.

Restore project files to match the requested baseline before subsequent updates. Made-with: Cursor
2026-04-26 14:05:50 +07:00
parent d86434e9c9
commit fe7acd655e
57 changed files with 1805 additions and 7665 deletions
@@ -1,28 +0,0 @@
-# Tabler to shadcn/ui baseline
-
-## Purpose
-This file freezes the legacy UI baseline before migration to native-first shadcn/ui.
-All new UI work should follow these constraints.
-
-## Confirmed legacy entry points
- `frontend/src/main.jsx` imports Tabler CSS and Tabler JS runtime.
- `frontend/src/App.jsx` and `frontend/src/App.css` contain the primary legacy shell and Tabler-oriented layout classes.
-
-## Legacy patterns to block in new code
- `window.Tabler.*`
- `data-bs-*` attributes for interactive behavior
- Bootstrap/Tabler JS-driven collapse, dropdown, modal, offcanvas behavior
- New custom wrappers for components that already exist in shadcn/ui primitives
-
-## Migration-first rules
- Use shadcn/ui primitives directly for new UI: `Button`, `Input`, `Dialog`, `AlertDialog`, `DropdownMenu`, `Table`, `Tooltip`, `Sheet`, `Select`, `Checkbox`, `Sonner`.
- Use shadcn sidebar primitives for application shell work:
-  - `SidebarProvider`
-  - `Sidebar`
-  - `SidebarInset`
-  - `SidebarTrigger`
- Keep custom abstractions thin and only where there is repeated business logic.
- Do not introduce new Tabler classes in migrated files.
-
-## Current impact snapshot
-Tabler-related usage appears across most frontend screens and shared components. The migration must proceed by shared primitives first, then screen waves.