Premium client speed, tighter admin control and a deliberate path to zero legacy runtime.
The migration target is no longer a basic parity layer. It is a faster, safer and more premium product that absorbs the useful business logic, removes legacy drag and leaves one clean operational stack.
Fast client flows
Core order, wallet and dashboard paths are already migrated into typed, faster interfaces built for low-friction repeat use.
Operational control
Catalog sync, provider routing, audit visibility and admin workspaces now live in one clearer control surface.
Safer provider runtime
Webhook auth, signed callbacks, retry policy, failover routing and provider diagnostics are handled as first-class runtime concerns.
Legacy retirement
The target is one modern product, not permanent dual maintenance. Migrated slices become the system of record and legacy gets trimmed away.
Live tabs
Test the migrated product in local UI now
These routes are already useful smoke surfaces for the new stack. They are the tabs worth using while legacy gets retired slice by slice.
Public pages
Client tabs
Admin tabs
/admin/dashboardAdmin menupublic info link visibility/admin/menuAdmin pagesfaq and terms content/admin/pagesAdmin ordersprovider lifecycle/admin/ordersAdmin catalogsync, routing, presets/admin/catalogAdmin settingsruntime and providers/admin/settingsAdmin paymentsmanual top-ups/admin/paymentsSupport
Public runtime and trust signals
- Support emailNot configured yet
- Support TelegramNot configured yet
- Session modelCookie-backed auth with secure server validation
- Provider postureRetry-aware transport, signed webhook support, admin diagnostics
Direction
What this migration is optimizing for
- Lower client overhead on high-frequency screens.
- Sharper admin visibility for provider and payment operations.
- Cleaner slice ownership so legacy code can be deleted, not preserved indefinitely.
- More premium visual quality without slowing down the panel.