Local dev Mongo config still points at the retired zmpox Atlas cluster

[JoshuaVSherman]

The webjamllc-zmpox Atlas cluster (old wj-prod / wj-socket-dev) was TERMINATED on 2026-07-08 (web-jam-back#897 finalization — its org "Joshua's Org" was deleted too). Prod was repointed to web-jam-data back on 7/5 (v151), but local dev configs still reference the dead cluster:

• WebJamSocketCluster's local dotenv file — Josh, manual (1 min): edit MONGO_DB_URI to point at the DEV Atlas cluster (same host as web-jam-back's local dotenv MONGO_DB_URI, per the local-dev-uses-dev-atlas convention), database web-jam-dev (the DB the Re-point at web-jam-data + artist-scope gig messages: serve Josh AND Tim (Part of web-jam-back#897) #238 dev drill used; jamPics dev-seed lives there). Agents are hook-blocked from reading credential files, so this edit is yours.
• The example env file in the repo — agent-fixable: replace the zmpox example URI with a dev-cluster-shaped placeholder. Tiny change — fold into the next WJSC PR (per the avoid-tiny-PRs rule) rather than opening a dedicated one; closing this issue rides that PR.

Symptom if skipped: next local npm run dev of the socket app fails to connect (DNS for the zmpox host no longer exists).

🤖 Work by Claude Code — Fable 5

[JoshuaVSherman]

✅ Manual half done (Josh, 2026-07-08): local WJSC dev MONGO_DB_URI replaced with the web-jam-back dev URI (DEV cluster, web-jam-dev DB — same one the #238 dev drill used). Quick smoke check when convenient: npm run dev in WJSC should boot and connect cleanly.

Remaining (keeps this open): the example-env file still shows a zmpox-shaped URI — fold that one-line fix into the next WJSC PR, which closes this.

[JoshuaVSherman]

✅ Smoke-tested by Josh: local npm run dev boots and connects to the DEV cluster. Only the example-env one-liner remains (rides the next WJSC PR).