feat(dashboard): complete React cutover

docs/architecture.md

@@ -167,8 +167,6 @@ RedditBot/
 │       └── dist/          # Generated production assets (not committed)
 ├── packages/
 │   └── api-contracts/     # Shared Zod HTTP and realtime schemas
-├── public/
-│   └── index.html         # Temporary legacy dashboard fallback
 ├── scripts/
 │   ├── inspect-chat-dom.ts  # Debug: inspect chat DOM structure
 │   └── login.ts           # Manual browser login helper
@@ -203,7 +201,7 @@ RedditBot/
     │   └── image.ts       # Image download + base64 + MIME validation (34 lines)
     └── web/
         ├── server.ts      # Express API, SSE, and dashboard host
-        ├── dashboard-assets.ts # React-build selection with legacy fallback
+        ├── dashboard-assets.ts # Required production React-build resolver
         └── events/        # Typed event hub and Express SSE adapter
 ```
 
@@ -412,10 +410,8 @@ Express server with API route modules and SSE transport.
   keys; cached content remains visible if the stream reconnects.
 - Vite writes production assets to `apps/dashboard/dist`.
 
-The asset resolver prefers the React build and can fall back to
-`public/index.html`. Wiring that resolver into authenticated Express static and
-private-media hosting is still a migration gate; the legacy file has not been
-removed.
+The asset resolver requires the production React build. Express serves those
+assets, API/SSE routes, and private media behind one authentication boundary.
 
 ---
 
@@ -922,15 +918,9 @@ Deployment documentation is provided in `DOKPLOY_DEPLOY.md`.
 
 ### Medium Priority
 
-7. **Legacy dashboard fallback** - `public/index.html` remains during migration.
-   Remove it only after authenticated React hosting and feature-parity gates pass.
+7. **Config Mutability** - Runtime config updates via `PUT /api/config` modify the in-memory config object. Consider a proper config service with validation on updates.
 
-8. **Settings route** - The React route is still a placeholder; runtime and
-   access settings have not yet moved into validated route-backed forms.
-
-9. **Config Mutability** - Runtime config updates via `PUT /api/config` modify the in-memory config object. Consider a proper config service with validation on updates.
-
-10. **Error Handling** - Some services have basic try/catch. Consider structured error types with retry logic.
+8. **Error Handling** - Some services have basic try/catch. Consider structured error types with retry logic.
 
 ### Low Priority