bento/dash: the release blockers, two kinds of sheet, and an Excel bounce test

.claude/launch.json

@@ -1,21 +1,41 @@
 {
   "version": "0.0.1",
   "configurations": [
+    {
+      "name": "dash-dev",
+      "cwd": "dash",
+      "runtimeExecutable": "npm",
+      "comment": "LOOPBACK ONLY, see spaces-dev.",
+      "runtimeArgs": [
+        "run",
+        "dev",
+        "--",
+        "--host",
+        "127.0.0.1",
+        "--port",
+        "5188",
+        "--strictPort"
+      ],
+      "port": 5188
+    },
     {
       "name": "serve-dash-wt",
       "runtimeExecutable": "python3",
+      "comment": "LOOPBACK ONLY, see serve-spaces-built.",
       "runtimeArgs": [
         "-m",
         "http.server",
         "5188",
+        "--bind",
+        "127.0.0.1",
         "--directory",
-        "/Users/andy/devel/bento/.claude/worktrees/bento-dash/dash/dist-single"
+        "dash/dist-single"
       ],
       "port": 5188
     },
     {
       "name": "spaces-dev",
-      "comment": "LOOPBACK ONLY. Vite already defaults to loopback, but the flag is written out so every entry in this file states its interface \u2014 the one entry that stayed silent is the one that kept binding the wildcard.",
+      "comment": "LOOPBACK ONLY. Vite already defaults to loopback, but the flag is written out so every entry in this file states its interface — the one entry that stayed silent is the one that kept binding the wildcard.",
       "cwd": "spaces",
       "runtimeExecutable": "npm",
       "runtimeArgs": [
@@ -32,7 +52,7 @@
     },
     {
       "name": "serve-spaces-built",
-      "comment": "LOOPBACK ONLY. http.server defaults to 0.0.0.0 (measured: TCP *:<port> LISTEN, reachable from the LAN), so every entry here pins the interface \u2014 a preview server has no reason to be a LAN service, whatever it happens to be serving today.",
+      "comment": "LOOPBACK ONLY. http.server defaults to 0.0.0.0 (measured: TCP *:<port> LISTEN, reachable from the LAN), so every entry here pins the interface — a preview server has no reason to be a LAN service, whatever it happens to be serving today.",
       "runtimeExecutable": "python3",
       "runtimeArgs": [
         "-m",
@@ -80,7 +100,7 @@
     },
     {
       "name": "serve-testing",
-      "comment": "LOOPBACK ONLY, and the highest-value of the http.server entries after working/: .gitignore describes testing/ as 'local test decks \u2014 never committed (may contain confidential content)'. It bound the wildcard until now (measured: TCP *:5197 LISTEN, LAN curl 200).",
+      "comment": "LOOPBACK ONLY, and the highest-value of the http.server entries after working/: .gitignore describes testing/ as 'local test decks — never committed (may contain confidential content)'. It bound the wildcard until now (measured: TCP *:5197 LISTEN, LAN curl 200).",
       "runtimeExecutable": "python3",
       "runtimeArgs": [
         "-m",
@@ -125,7 +145,7 @@
     },
     {
       "name": "serve-working",
-      "comment": "LOOPBACK ONLY. working/ is the gitignored secrets drawer \u2014 the live guestbook ADMIN_KEY bearer token and the room's owner ECDSA private key sit in it, and http.server serves a directory listing. http.server defaults to 0.0.0.0, so without --bind anyone on the same cafe/office LAN could walk the listing and take both while this entry runs.",
+      "comment": "LOOPBACK ONLY. working/ is the gitignored secrets drawer — the live guestbook ADMIN_KEY bearer token and the room's owner ECDSA private key sit in it, and http.server serves a directory listing. http.server defaults to 0.0.0.0, so without --bind anyone on the same cafe/office LAN could walk the listing and take both while this entry runs.",
       "runtimeExecutable": "python3",
       "runtimeArgs": [
         "-m",
@@ -140,7 +160,7 @@
     },
     {
       "name": "serve-working2",
-      "comment": "LOOPBACK ONLY, same secrets as serve-working. `serve -l 5193` listens on the WILDCARD (measured: `*:5193`) while logging 'Accepting connections at http://localhost:5193' \u2014 the line reads as loopback and is not, so the misconfiguration is invisible. The tcp://host:port form is the only way to pin the interface.",
+      "comment": "LOOPBACK ONLY, same secrets as serve-working. `serve -l 5193` listens on the WILDCARD (measured: `*:5193`) while logging 'Accepting connections at http://localhost:5193' — the line reads as loopback and is not, so the misconfiguration is invisible. The tcp://host:port form is the only way to pin the interface.",
       "runtimeExecutable": "npx",
       "runtimeArgs": [
         "--yes",