Ingest live 3proxy traffic from access logs

README.md

@@ -9,6 +9,7 @@ The project now includes both the UI and the first backend/runtime slice:
 - Express-based control plane API
 - generated `3proxy.cfg` from persisted panel state
 - runtime manager for start/restart/reload
+- access-log-backed traffic ingestion from a real 3proxy process
 - Docker image that builds the panel and compiles 3proxy in-container
 - panel views for dashboard, users, and system
 - edge-case-focused frontend and backend tests
@@ -35,6 +36,7 @@ For Docker runs these values come from `compose.yaml`:
 - `PANEL_SESSION_TTL_HOURS` with a default of `24`
 
 The panel stores the issued session token in `sessionStorage`, so a browser refresh keeps the operator signed in until the token expires.
+Once the API is available, dashboard/user traffic values are refreshed from live 3proxy access logs instead of the seeded fallback snapshot.
 
 ## Docker run