feat(web): rover ui

[thomasyuill-livekit]

Summary

Adds a second teleop page for the rover alongside the existing pan/tilt arm app, and refactors shared UI/connection plumbing.

Routing

• / is now a landing page that shows a "Connect to Robot" and/or "Connect to Rover" button based on which env vars are set, or an empty state if neither is configured.
• The previous components/app.tsx moved to app/robot/page-client.tsx, and a new app/rover/page-client.tsx mirror was added. Each wraps the SessionProvider in its own app/<robot>/page.tsx.

Rover protocol

• lib/rover.ts — topic helpers (<rover_id>.imu, <rover_id>.control_cmd, <rover_id>.arducam), ImuPayload type, and controlCmdJson(throttle_rps, steering_rps) encoder clamped to ±1 rev/s.
• use-imu subscribes to the rover IMU track (bufferSize: 256 to keep up with ~100 Hz frames).
• use-rover-control-cmd-track publishes the joystick-driven throttle/steering data track and cleans up on mode change.
• The rover's joystick maps (horizontal, vertical) → (steering_rps, throttle_rps) with vertical-up as forward throttle.

Shared components & hooks

• DebugPanel (components/debug-panel.tsx): table-based panel taking {label, value, unit, precision} rows, used by both robot and rover pages.
• Dialog + VideoDialog (components/{dialog,video-dialog}.tsx): a video container that selects the right TrackReference (by participant + track name + source) with a Waiting for <label> placeholder. The rover page targets <rover_id>.arducam explicitly.
• use-video-fit-screen (replaces use-video-fit-container): computes a width/height fit given an inset and the track's aspect ratio.
• use-connection: extracted session.start()/end() lifecycle that surfaces failures via a sonner toast and redirects to /.
• StatusBar accepts an actions prop so each page provides its own disconnect / fullscreen / debug buttons.

Errors & UX

• session.start() failures show a sonner toast (shadcn add sonner) with a stable id to dedupe StrictMode double-mounts, then redirect to /.
• Cleanup-order fix in page-client.tsxs: the connection lifecycle effect is declared first so its cleanup runs last. Subscription hooks (useImu, useGyro, control-cmd track) tear down while the PC manager is still alive — eliminates the "Cannot read properties of undefined (reading 'client')" and "PC manager is closed" crashes during navigation.

Env vars

Split into NEXT_PUBLIC_ROBOT_* and NEXT_PUBLIC_ROVER_* (identity / LiveKit URL / token). .env.example and README updated.

Test plan

• With no env vars set, / shows the "No robots configured" empty state
• With only NEXT_PUBLIC_ROBOT_* set, only the Robot button appears (and vice versa for rover)
• With all six env vars set, both buttons appear
• Connect to robot, acquire control, drive pan/tilt, toggle debug panel, disconnect cleanly (no console errors)
• Connect to rover, acquire control, drive joystick (vertical = throttle, horizontal = steering), verify IMU values update in debug panel, disconnect cleanly
• Set an invalid LIVEKIT_TOKEN and verify an error toast appears and the page redirects back to /
• Verify no "Track name already taken", "readable stream is full", or "PC manager is closed" warnings in the console

🤖 Generated with Claude Code

[stephen-derosa]

skimmed through and tested locally, works as expected!