Session Lifecycle
Represent the charging journey as a single flow with clear transitions from connect to settle.
Pending to completed state shape
Clear customer and operator checkpoints
UI built around chronology, not menu sprawl
The platform page explains the system the rest of the site points to: a charging control plane where session lifecycle, operator action, payment checkpoints, and structured logs stay attached.
Session narrative from payment to stop
Operator pillars in the current frontend map
Backend changes in this UI phase
Instead of separating charging, payments, and support into disconnected surfaces, the frontend follows the same operational spine the backend already models.
Represent the charging journey as a single flow with clear transitions from connect to settle.
Pending to completed state shape
Clear customer and operator checkpoints
UI built around chronology, not menu sprawl
Keep authorization and settlement inside the session story so charging decisions and payment evidence remain legible.
Pre-auth context beside the session
Refund and stop reasoning together
Reduced finance-operation mismatch
Make remote actions explicit and contextual so support teams know what can be done and why.
Remote start and stop clarity
Charger readiness surface
Less hesitation during intervention
Logs, events, and charger-linked facts are first-class UI material, not hidden exhaust.
Session-related filtering
Machine-specific visibility
Proof-first support and QA flow
This page set is intentionally UI-only. It gives the product a coherent public surface now, while keeping the current FastAPI and simulator architecture untouched.