🧭 fix deploy target in CLAUDE.md + track dev launch configs

Verified live: godstrument.pro is served from the botchat VPS
(humanjing@100.71.119.27) via Cloudflare Tunnel, NOT dealgod — corrected the
canon note and recorded the rsync+restart deploy recipe. Also track the
godstrument-verify / -test launch configs.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.claude/launch.json

@@ -25,6 +25,12 @@
       "runtimeArgs": ["-m", "http.server", "8899", "--directory", "viz"],
       "port": 8899
     },
+    {
+      "name": "godstrument-verify",
+      "runtimeExecutable": "sh",
+      "runtimeArgs": ["-c", "python3 -c \"import json; c=json.load(open('config.json')); c['ws_port']=8791; c['http_port']=8891; c['osc_in_port']=9010; json.dump(c, open('/tmp/gs_verify_config.json','w'))\" && .venv/bin/python run.py --no-browser --profile minimal --config /tmp/gs_verify_config.json"],
+      "port": 8891
+    },
     {
       "name": "godstrument-test",
       "runtimeExecutable": "sh",

CLAUDE.md

@@ -0,0 +1,7 @@
+# Godstrument — Claude context
+
+Music-instrument web app; hosted at godstrument.pro on the **botchat** VPS (`humanjing@100.71.119.27`, exposed via Cloudflare Tunnel — NOT dealgod, despite earlier notes). App dir `/home/humanjing/godstrument` (not a git checkout). Deploy = rsync git-tracked files only (`--files-from=<(git ls-files)`, never `--delete`, never push `godstrument_users.db`/`auth_secret`/`patches/`) then `sudo -n systemctl restart godstrument`. Origin is Gitea `ssh://git@100.71.119.27:222/monster/Godstrument.git`. See [[godstrument-pro-deploy]].
+
+- **Canon gotcha:** the real spec prose lives in `viz/index.html` (grimoire text around line ~950); `GODSTRUMENT_MANUAL_SOURCE.md` claims to be exhaustive but has drifted before (Earth Echo / Schumann layer was missing). When they disagree, **viz/index.html is truth** — update the manual to match, not the other way.
+- Secrets (Cloudflare token etc.): read from `.env`/local files, never from chat. A CF token was pasted in chat once and rolled — don't repeat that.
+- First page load after a deploy is slow (cold start) — wait before declaring it broken.