Panels: per-device dashboard sets, paired by code

A panel is one screen and the ordered set of whole dashboards it shows, so a
hallway tablet and a workshop tablet carry different sets without either
dashboard knowing about the other. More than one and the device draws a rail
to switch between them — the same rail the editor puts on screen, because the
wall has it and it takes room off the canvas.

A screen has no keyboard, so it pairs rather than logs in: it shows a
six-character code, somebody approves it against a panel from the dashboards
overview, and the credential that mints reaches that panel's published
dashboards and the message endpoints its widgets speak, and nothing else.
Deleting the panel revokes it.

Closes the per-device view and the kiosk credential; supersedes the
multi-page/multi-section UI, since a page is now a dashboard of its own.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AHpLJHozysQXjsxAyU1WHj

frontend/src/main.tsx

@@ -39,6 +39,17 @@ const handleApiError = (error: Error) => {
     return
   }
   if (isAuthFailure(error)) {
+    // A paired wall panel has no login screen to go back to — it asks for a
+    // new code instead. Only a 401 is worth throwing its credential away for:
+    // a 403 there is a dashboard it was just unassigned from, which the next
+    // read of the panel corrects on its own.
+    if (window.location.pathname.startsWith("/panel")) {
+      if (error instanceof ApiError && error.status === 401) {
+        localStorage.removeItem("access_token")
+        window.location.href = "/panel"
+      }
+      return
+    }
     if (portal) {
       // The portal knows whether they are still signed in; it can mint a fresh
       // handoff or send them to the login screen.