david caefb0dcc0 fix: resolve schedule data staleness in production builds ...

- Replace window.location.reload() with router.refresh() in ScheduleGenerator, MatchEditor, RecalculateEloButton for proper Next.js cache invalidation
- Add revalidatePath() call after schedule generation in POST handler
- Add ownerId to tournament creation in cucumber tests for proper permission checks
- Assign tournament_admin role via Prisma after user creation in cucumber tests
- Fix TypeScript type annotations in hooks.ts (tournament id map)
- Update page reload to use networkidle in common-steps.ts
- Clear .next/ cache before cucumber tests in justfile
- Add .turbo to clean target
- Add comprehensive debug logging to schedule API route
- Document findings in docs/TROUBLESHOOTING_SCHEDULE_GENERATION.md

2026-05-01 16:39:50 -07:00

..

auth-steps.ts

fix: resolve schedule data staleness in production builds

2026-05-01 16:39:50 -07:00

common-steps.ts

fix: resolve schedule data staleness in production builds

2026-05-01 16:39:50 -07:00