QA Report: feat: Navigation Surface & Production Cutover (#49) (PR #54)

[sortakool]

QA Report

PR: #54 — feat: Navigation Surface & Production Cutover (#49)
Branch: feat/49-navigation-surface-production-cutover
Date: 2026-02-26
Verdict: ⚠️ PARTIAL

---

Gherkin Scenarios

#	Scenario	AC	Result
1	Sidebar is present on the dashboard overview page	AC #1	⏭️ SKIP
2	Sidebar is present on the tours page	AC #1	⏭️ SKIP
3	Sidebar is present on the riders page	AC #1	⏭️ SKIP
4	Sidebar is present on the settings page	AC #1	⏭️ SKIP
5	Dashboard link shows active state on overview page	AC #2	⏭️ SKIP
6	Tours link shows active state on tours page	AC #2	⏭️ SKIP
7	Riders link shows active state on riders page	AC #2	⏭️ SKIP
8	Settings link shows active state on settings page	AC #2	⏭️ SKIP
9	Tours page renders tour names from Supabase Postgres	AC #3	⏭️ SKIP
10	Tours page shows associated gig information	AC #3	⏭️ SKIP
11	Riders page renders rider hospitality items from Supabase Postgres	AC #4	⏭️ SKIP
12	Settings page displays the authenticated user's email	AC #5	⏭️ SKIP
13	Settings page renders a settings shell	AC #5	⏭️ SKIP
14	Unauthenticated user is redirected from dashboard	AC #8	✅ PASS
15	End-to-end visual verification of navigation and data	Visual	⏭️ SKIP
16	The apps/ directory no longer exists in the repository	AC #9	✅ PASS
17	No source files reference the legacy apps/ directory	AC #9	✅ PASS
18	Legacy monorepo configuration is removed	AC #9	✅ PASS
19	No test file references legacy apps/ paths	AC #10	✅ PASS
20	README project structure matches actual single-app architecture	AC #11	✅ PASS
21	README getting-started steps are accurate for Supabase and Vercel	AC #11	✅ PASS
22	Vercel production URL loads without errors	AC #6	⏭️ SKIP
23	Vercel environment variables are configured	AC #6	⏭️ SKIP
24	User can log in at the Vercel production URL	AC #7	⏭️ SKIP

Summary: 7 passed, 0 failed, 17 skipped (24 total) — 153/153 Bun unit tests passed

---

Failures

None. Zero test failures. All 7 executed Playwright scenarios passed; 17 were skipped due to missing TEST_USER_EMAIL/TEST_USER_PASSWORD env vars or production-only scope.

---

Acceptance Criteria Coverage

AC	Description	Scenarios	Status
AC #1	Sidebar renders on all dashboard routes	1–4	❌ All skipped (need auth)
AC #2	Active page state visible	5–8	❌ All skipped (need auth)
AC #3	Tours page displays data	9–10	❌ All skipped (need auth)
AC #4	Riders page displays data	11	❌ Skipped (need auth)
AC #5	Settings page renders	12–13	❌ All skipped (need auth)
AC #6	Vercel deployment	22–23	⏭️ Out of scope (prod-only)
AC #7	Vercel login	24	⏭️ Out of scope (prod-only)
AC #8	Protected routes work	14	✅ PASS
AC #9	Legacy apps/ directory removed	16–18	✅ All PASS
AC #10	Tests pass (no legacy refs)	19	✅ PASS
AC #11	README is accurate	20–21	✅ All PASS

---

Screenshots

Screenshots from a prior QA run (dated Feb 26) exist in .attractor/qa-report/:

File	Notes
scenario-12-failed.png	Prior run artifact (1280×720)
scenario-13-failed.png	Prior run artifact (1280×720)
scenario-14-failed.png	Prior run artifact (1280×720)
scenario-15-failed.png	Prior run artifact (1280×720)
scenario-27-failed.png	Stale — scenario 27 doesn't exist in current spec

No new screenshots were generated in this run (0 failures, 17 skips).

---

Key Notes

1. ⚠️ 13 of 15 Tier A scenarios untested (HIGH concern): The entire authenticated E2E surface — sidebar rendering, active link highlighting, data page content (Tours, Riders, Settings), and the visual walkthrough — was not exercised. These are the primary acceptance criteria of PR feat: Navigation Surface & Production Cutover (#49) #54. Recommendation: Re-run with valid Supabase credentials.

2. ⚠️ Port conflict during dev server startup: Port 3000 was in use; server fell back to port 3005. Playwright config targets localhost:3000. Scenario 14 still passed, but this setup is fragile.

3. ✅ Bun unit tests provide strong static coverage: All 153 tests pass, including 41 tests validating sidebar structure, active state logic, page file existence, query imports, and force-dynamic exports at the source-code level.

4. ✅ Legacy cleanup thoroughly verified: Tier B (Scenarios 16–21) confirms no apps/ directory, no turbo.json, no workspaces in package.json, and README accurately reflects single-app Next.js + Supabase + Vercel architecture.

---

Raw Output

Full Playwright output

Running 24 tests using 1 worker

1 [chromium] › gherkin.spec.ts:102:7 › AC #1 — Sidebar renders on all dashboard routes › Scenario 1: Sidebar is present on the dashboard overview page
2 [chromium] › gherkin.spec.ts:120:7 › AC #1 — Sidebar renders on all dashboard routes › Scenario 2: Sidebar is present on the tours page
3 [chromium] › gherkin.spec.ts:138:7 › AC #1 — Sidebar renders on all dashboard routes › Scenario 3: Sidebar is present on the riders page
4 [chromium] › gherkin.spec.ts:156:7 › AC #1 — Sidebar renders on all dashboard routes › Scenario 4: Sidebar is present on the settings page
5 [chromium] › gherkin.spec.ts:199:7 › AC #2 — Active page state visible › Scenario 5: Dashboard link shows active state on the dashboard overview page
6 [chromium] › gherkin.spec.ts:217:7 › AC #2 — Active page state visible › Scenario 6: Tours link shows active state on the tours page
7 [chromium] › gherkin.spec.ts:234:7 › AC #2 — Active page state visible › Scenario 7: Riders link shows active state on the riders page
8 [chromium] › gherkin.spec.ts:251:7 › AC #2 — Active page state visible › Scenario 8: Settings link shows active state on the settings page
9 [chromium] › gherkin.spec.ts:274:7 › AC #3 — Tours page displays data › Scenario 9: Tours page renders tour names from Supabase Postgres
10 [chromium] › gherkin.spec.ts:291:7 › AC #3 — Tours page displays data › Scenario 10: Tours page shows associated gig information
11 [chromium] › gherkin.spec.ts:324:7 › AC #4 — Riders page displays data › Scenario 11: Riders page renders rider hospitality items from Supabase Postgres
12 [chromium] › gherkin.spec.ts:351:7 › AC #5 — Settings page renders › Scenario 12: Settings page displays the authenticated user's email
13 [chromium] › gherkin.spec.ts:370:7 › AC #5 — Settings page renders › Scenario 13: Settings page renders a settings shell

✓  14 [chromium] › gherkin.spec.ts:392:7 › AC #8 — Protected routes work › Scenario 14: Unauthenticated user is redirected from dashboard (244ms)
15 [chromium] › gherkin.spec.ts:413:7 › Visual Verification › Scenario 15: End-to-end visual verification of navigation and data

✓  16 [chromium] › gherkin.spec.ts:514:7 › AC #9 — Legacy apps/ directory removed › Scenario 16: The apps/ directory no longer exists in the repository (0ms)

✓  17 [chromium] › gherkin.spec.ts:519:7 › AC #9 — Legacy apps/ directory removed › Scenario 17: No source files reference the legacy apps/ directory (22ms)

✓  18 [chromium] › gherkin.spec.ts:543:7 › AC #9 — Legacy apps/ directory removed › Scenario 18: Legacy monorepo configuration is removed (2ms)

✓  19 [chromium] › gherkin.spec.ts:558:7 › AC #10 — Tests pass › Scenario 19: No test file references legacy apps/ paths (4ms)

✓  20 [chromium] › gherkin.spec.ts:582:7 › AC #11 — README is accurate › Scenario 20: README project structure matches actual single-app architecture (5ms)

✓  21 [chromium] › gherkin.spec.ts:601:7 › AC #11 — README is accurate › Scenario 21: README getting-started steps are accurate for Supabase and Vercel (1ms)
22 [chromium] › gherkin.spec.ts:621:8 › TIER C — Production-only (Vercel) › Scenario 22: Vercel production URL loads without errors
23 [chromium] › gherkin.spec.ts:626:8 › TIER C — Production-only (Vercel) › Scenario 23: Vercel environment variables are configured
24 [chromium] › gherkin.spec.ts:631:8 › TIER C — Production-only (Vercel) › Scenario 24: User can log in at the Vercel production URL

17 skipped

7 passed (4.8s)