First Success Validation

First success means the dev server serves pages, Auth.js can establish a session, DatabaseService reads/writes without adapter errors, and core marketplace routes load. It does not require WayForPay, FCM, or wallet connectivity on day one.

Success levels

Checklist summary

Next steps

First Success Validation

First success means the dev server serves pages, Auth.js can establish a session, DatabaseService reads/writes without adapter errors, and core marketplace routes load. It does not require WayForPay, FCM, or wallet connectivity on day one.

Success levels

Checklist summary

Next steps

First Success Validation

First success means the dev server serves pages, Auth.js can establish a session, DatabaseService reads/writes without adapter errors, and core marketplace routes load. It does not require WayForPay, FCM, or wallet connectivity on day one.

Success levels

Checklist summary

Next steps

When to stop and fix

• Terminal shows repeated Postgres connection failures → revisit Prerequisites DB_* vars.
• Login redirects loop → AUTH_SECRET and OAuth redirect URIs (http://localhost:3000/api/auth/callback/google).
• Entity save fails with 403 → expected for visitor role; sign in as member or adjust test account role.

1. 1

   1 — Dev server

   Expect Next.js ready on http://localhost:3000. Custom server.ts may log native WSS when RING_DEPLOY_TARGET=self-hosted.

2. 2

   2 — Health endpoint

   Real shape (app/api/health/route.ts): status is healthy | degraded | unhealthy (not "ok"). services.database is postgresql or firebase. Missing AUTH_SECRET → degraded and HTTP 503.

3. 3

   3 — Homepage

   Expect 200. Open in browser; check console for red errors (ignore dev-only Auth.js JWT noise documented in lib/logger.ts filters).

4. 4

   4 — Authentication

   1. Visit /login (locale prefix may apply: /en/login).
   2. Complete one configured provider from auth.ts: Google OAuth, Apple, Ring Mailer (OTP / magic link), Google One Tap, or crypto wallet — not GitHub/Discord (not in default provider list).
   3. Confirm session: /profile shows user data; refresh persists session.

   Optional: GET /api/auth/session with browser cookies returns { user: { id, email, role, … } }.

5. 5

   5 — PostgreSQL (postgres-primary)

   Expect count ≥ 1 after first sign-in. No /api/test-db route in this tree — use psql or authenticated API calls.

6. 6

   6 — Authenticated APIs

   /api/entities and /api/opportunities require a session — 401 without cookies is expected.

   After browser login, DevTools → copy session cookie, or test in UI:

   1. /entities — list + create entity form submits.
   2. /opportunities — list loads for your role.
7. 7

   7 — Tunnel readiness

   Expect "ready" and provider list from lib/tunnel/config. For live SSE: Network tab → /api/tunnel/sse after sign-in. See Tunnel protocol.

8. 8

   8 — Optional checks

   Check	Command / action	Expected
   TypeScript	npm run type-check	Exit 0
   Wallet API	GET /api/wallet/balance (logged in)	{ balance } or 404 until wallet created
   Build	npm run build	Completes (runs type-check by default)

When to stop and fix

• Terminal shows repeated Postgres connection failures → revisit Prerequisites DB_* vars.
• Login redirects loop → AUTH_SECRET and OAuth redirect URIs (http://localhost:3000/api/auth/callback/google).
• Entity save fails with 403 → expected for visitor role; sign in as member or adjust test account role.

1. 1

   1 — Dev server

   Expect Next.js ready on http://localhost:3000. Custom server.ts may log native WSS when RING_DEPLOY_TARGET=self-hosted.

2. 2

   2 — Health endpoint

   Real shape (app/api/health/route.ts): status is healthy | degraded | unhealthy (not "ok"). services.database is postgresql or firebase. Missing AUTH_SECRET → degraded and HTTP 503.

3. 3

   3 — Homepage

   Expect 200. Open in browser; check console for red errors (ignore dev-only Auth.js JWT noise documented in lib/logger.ts filters).

4. 4

   4 — Authentication

   1. Visit /login (locale prefix may apply: /en/login).
   2. Complete one configured provider from auth.ts: Google OAuth, Apple, Ring Mailer (OTP / magic link), Google One Tap, or crypto wallet — not GitHub/Discord (not in default provider list).
   3. Confirm session: /profile shows user data; refresh persists session.

   Optional: GET /api/auth/session with browser cookies returns { user: { id, email, role, … } }.

5. 5

   5 — PostgreSQL (postgres-primary)

   Expect count ≥ 1 after first sign-in. No /api/test-db route in this tree — use psql or authenticated API calls.

6. 6

   6 — Authenticated APIs

   /api/entities and /api/opportunities require a session — 401 without cookies is expected.

   After browser login, DevTools → copy session cookie, or test in UI:

   1. /entities — list + create entity form submits.
   2. /opportunities — list loads for your role.
7. 7

   7 — Tunnel readiness

   Expect "ready" and provider list from lib/tunnel/config. For live SSE: Network tab → /api/tunnel/sse after sign-in. See Tunnel protocol.

8. 8

   8 — Optional checks

   Check	Command / action	Expected
   TypeScript	npm run type-check	Exit 0
   Wallet API	GET /api/wallet/balance (logged in)	{ balance } or 404 until wallet created
   Build	npm run build	Completes (runs type-check by default)

When to stop and fix

• Terminal shows repeated Postgres connection failures → revisit Prerequisites DB_* vars.
• Login redirects loop → AUTH_SECRET and OAuth redirect URIs (http://localhost:3000/api/auth/callback/google).
• Entity save fails with 403 → expected for visitor role; sign in as member or adjust test account role.

1. 1

   1 — Dev server

   Expect Next.js ready on http://localhost:3000. Custom server.ts may log native WSS when RING_DEPLOY_TARGET=self-hosted.

2. 2

   2 — Health endpoint

   Real shape (app/api/health/route.ts): status is healthy | degraded | unhealthy (not "ok"). services.database is postgresql or firebase. Missing AUTH_SECRET → degraded and HTTP 503.

3. 3

   3 — Homepage

   Expect 200. Open in browser; check console for red errors (ignore dev-only Auth.js JWT noise documented in lib/logger.ts filters).

4. 4

   4 — Authentication

   1. Visit /login (locale prefix may apply: /en/login).
   2. Complete one configured provider from auth.ts: Google OAuth, Apple, Ring Mailer (OTP / magic link), Google One Tap, or crypto wallet — not GitHub/Discord (not in default provider list).
   3. Confirm session: /profile shows user data; refresh persists session.

   Optional: GET /api/auth/session with browser cookies returns { user: { id, email, role, … } }.

5. 5

   5 — PostgreSQL (postgres-primary)

   Expect count ≥ 1 after first sign-in. No /api/test-db route in this tree — use psql or authenticated API calls.

6. 6

   6 — Authenticated APIs

   /api/entities and /api/opportunities require a session — 401 without cookies is expected.

   After browser login, DevTools → copy session cookie, or test in UI:

   1. /entities — list + create entity form submits.
   2. /opportunities — list loads for your role.
7. 7

   7 — Tunnel readiness

   Expect "ready" and provider list from lib/tunnel/config. For live SSE: Network tab → /api/tunnel/sse after sign-in. See Tunnel protocol.

8. 8

   8 — Optional checks

   Check	Command / action	Expected
   TypeScript	npm run type-check	Exit 0
   Wallet API	GET /api/wallet/balance (logged in)	{ balance } or 404 until wallet created
   Build	npm run build	Completes (runs type-check by default)