Phase 3.7: paid pairing flow + returning chat + extension flip

- Backend: payment_sessions + pairing_failures tables; payment.service.js
  and pairing-failure.service.js (new); rewritten pairing.service.js
  (payment-gated blast + targeted "Curhat lagi" + cancel + fallback);
  rewritten extension.service.js (data-driven auto-approve with offline
  safeguard, charge-at-approval); pricing.service.js (extension tiers
  without free trial); mitra-status.service.js (countAvailableMitras
  cached path); 60s sweeper for stale payment sessions
- Backend routes: client.payment.routes, client.mitra-availability.routes,
  internal/failed-pairings.routes; client.chat.routes rewritten for
  payment-gated start + /returning + /cancel + /fallback-to-blast;
  internal/config.routes adds 4 new keys with Valkey invalidate publish
- client_app: mitra-availability poll, payment screen + notifier, pairing
  notifier rewrite (PairingTargetedWaiting + PairingFailed states),
  targeted-waiting overlay + bestie-unavailable dialog, "Curhat lagi"
  CTA, failed-pairing terminal, extension via payment-session
- mitra_app: PairingRequestType enum, returning-chat 20s countdown
  auto-dismiss, extension card "otomatis disetujui" copy
- control_center: 4 new config rows in Settings, Failed Pairings page
  (filter + paginate + action menu), sidebar + route registered
- Test infrastructure: Vitest backend (7/7 pass), Playwright CC (4/4
  pass), Maestro mobile scaffold (CLI install pending)
- Bugs found via Playwright + fixed: LoginPage labels not associated
  with inputs (a11y); backend internal CORS missing PATCH/PUT/DELETE
  in allow-methods (silent settings breakage in browsers since Stage 4)
- Docs: phase3.7.md PRD, phase3.7-plan.md, phase3.7-questions.md (Q&A),
  phase3.7-testing.md (E2E checklist), phase3.7-test-run-2026-05-03.md
  (today's run results)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

backend/.env.test.example

@@ -0,0 +1,26 @@
+# Test environment configuration. Copy to .env.test and adjust if needed.
+#
+# DEFAULT STRATEGY (Option C): same remote Postgres, isolated `halobestie_test` SCHEMA.
+# The dev role on the remote DB cannot CREATE DATABASE, so we use schema isolation
+# instead of a separate database. Tests set search_path so the migration creates all
+# tables inside `halobestie_test`, leaving the dev `public` schema untouched.
+
+# Test Postgres (same instance + same database as dev — schema isolates).
+TEST_DATABASE_URL=postgresql://halobestie_clone:halobestie_clone@omv.sjamsani.id:5432/halobestie_clone
+
+# Schema used to isolate test tables from dev tables. MUST NOT be `public`.
+TEST_DB_SCHEMA=halobestie_test
+
+# Test Valkey (same instance, separate db number 1 to avoid clashing with dev db 0).
+TEST_VALKEY_URL=redis://omv.sjamsani.id:6379/1
+
+# JWT secret for test-minted tokens. Any 32+ char string is fine (does not need to
+# match the dev secret; tests mint and verify in the same process).
+AUTH_JWT_SECRET=test-secret-must-be-at-least-32-characters-long
+
+# Token TTLs (kept short for tests).
+ACCESS_TOKEN_TTL_SECONDS=3600
+REFRESH_TOKEN_TTL_DAYS=30
+
+# CC origin needed by app.internal CORS — anything resolvable.
+CC_ORIGIN=http://localhost:5173