| name | verify |
| description | Runtime verification recipe for glow-pay — launch the app, restore the test wallet, observe SDK connect/balance sync, and exercise the payment flow. |
Verifying glow-pay changes at runtime
Launch
source /home/roys/.nvm/nvm.sh
npm run dev
If the flow needs /api (merchant restore, payment create), either run
npx vercel dev --yes --listen 3000 plus a /api proxy in vite.config.ts,
or temporarily proxy straight to production:
proxy: { '/api': { target: 'https://glow-pay.co', changeOrigin: true } },
Production proxy is safe for the test merchant; writes go to real Redis.
Drive (Playwright MCP)
- Navigate to
http://localhost:5173/setup (use domcontentloaded, never
networkidle — SDK WASM does background calls that prevent idle).
- Click "Restore Existing Account", paste the test mnemonic from CLAUDE.md /
memory (current:
situate business peasant filter whisper glance candy belt surprise chaos head bar), click "Restore Account".
- Wait for "You're all set" → "Open Dashboard".
- Wallet-connect evidence is in the browser console (Playwright saves logs to
~/.playwright-mcp/console-*.log): look for Wallet connected (<addr>),
Received event: Synced, Balance updated successfully.
- Balance sync: the "Syncing" badge on the dashboard disappears on the first
fresh
synced event.
- Payment flow: Dashboard → New Payment → amount in sats → open the
/pay/:merchantId/:paymentId link → QR + "Expires in 9:xx" countdown means
the LNURL invoice was fetched from breez.cash successfully.
Gotchas
- Sweep (Settings → Wallet) is disabled at 0 balance and moves real funds —
don't drive it live.
- The only expected console error is a fonts.gstatic.com 404 (external font).
- Screenshots from Playwright MCP land in
~ or ~/.playwright-mcp/.
