Motivation

• Provide a complete Operator Dashboard (routing tails, failover sim, anomaly view, handoff generator, dependency graph) as an actionable operator surface.
• Eliminate the stuck-looking Suspense fallback when landing directly on the Operator Dashboard in preview / screenshot tooling.
• Surface runtime guardrails and small UI/TS fixes discovered while integrating the new view.

Description

• Add a new OperatorDashboard view at apps/web-next/src/views/OperatorDashboard.tsx implementing tail views, incident drilldown modal, provider failover simulator, cost anomaly mini-view, operator handoff generator, and a compact routing dependency list.
• Prevent the loading-fallback stall by importing OperatorDashboard statically in apps/web-next/src/App.tsx and wiring it into navItems and the view render switch.
• Add runtime chart dependency recharts to apps/web-next/package.json and update pnpm-lock.yaml accordingly.
• Apply a set of targeted TypeScript/JSX fixes across multiple views (examples: replace mutable sort with toSorted for immutability, tighten implicit any types, small JSX/conditional fixes, icon swaps, and minor UI text tweaks).

Testing

• Built the web app with pnpm -C apps/web-next build and the build completed successfully.
• Started the dev server with pnpm -C apps/web-next dev --host 0.0.0.0 --port 4173 and validated the running app.
• Automated Playwright verification navigated to / and waited for h1:has-text("Operator Dashboard"), confirming loading_count=0 and producing a verification screenshot (artifacts/operator-dashboard-no-loading.png).
• The combined checks (build + Playwright) passed and show the Operator Dashboard renders without the previous top-level "Loading..." fallback.

Codex Task