Update market, account, and onion operations

Capture the current CyberLux UI, commerce, messaging, and Tor ops updates so local main can be pushed to the remote.

Made-with: Cursor

DEPLOY.md

@@ -74,6 +74,34 @@ sudo node scripts/onion-status.cjs
 3. `sudo bash scripts/install-tor-onion.sh`
 4. Rebuild/restart the app: `npm run build` and `sudo systemctl restart cyberlux.service`
 
+## 502 Bad Gateway on `.onion` sites
+
+Tor and nginx are working, but **nginx proxies to Next.js on `127.0.0.1:3000`**. A **502** means **nothing is listening there** (Next is stopped, crashed, or never started after reboot).
+
+1. **Confirm** (from the repo):
+
+   ```bash
+   curl -sS -o /dev/null -w "%{http_code}\n" http://127.0.0.1:3000/
+   ```
+
+   `000` = connection refused → Next is down.
+
+2. **Start Next** (pick one):
+
+   - **Foreground (dev / quick test):** `cd /path/to/cyberlux && npm run start:onion` — leave the terminal open.
+   - **systemd (production):** `sudo systemctl start cyberlux.service` — ensure the unit is installed (`scripts/install-systemd.sh`) and enabled.
+   - **Full stack script:** `./start.sh` (builds, configures Tor/nginx if needed, then starts Next).
+
+3. **Verify again:**
+
+   ```bash
+   npm run health:stack
+   ```
+
+   You want `Next.js: OK` and `hub vhost: OK` (HTTP 200/301/302/304).
+
+4. **If it still fails:** `journalctl -u cyberlux.service -n 80 --no-pager` — look for crash loops, missing `.next` (run `npm run build`), or wrong `WorkingDirectory` in the unit.
+
 ## Verification
 
 ```bash