Two prerequisites for deploying ab2299c. VERSION. ab2299c shipped the new endpoint without a bump, leaving package.json at 0.9.33 — identical to what is deployed, so the new code would have been indistinguishable from the old on the target. DEPLOY TARGET. scripts/deploy.sh hardcoded APP=atproto-pds, a name left over from before the rename (cf. the "atproto-pds 0.9.25" commits). The app actually running on stortron is atproto-bridge: pid 86967 up 23:28 apps/atproto-bridge/index.js -> LISTEN 0.0.0.0:3399 which is why `deploy.sh stortron --check` reported `running:false version:0.1.0 tree=` while the health probe on 3399 passed — pgh was answering about a different, nonexistent app. Running the deploy unchanged would have stopped nothing, started a second process racing for 3399, and left the real membrane on old code: precisely the 2026-07-03 stranding the script was written to prevent, reintroduced by a stale constant. Corroboration: stortron still carries a 2-day-old orphan shell spinning in `until [ -S ~/.config/atproto-pds/svc.sock ]` — someone hit this before. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>