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

src/components/ScheduleGenerator.tsx

@@ -1,6 +1,7 @@
 "use client"
 
 import { useState } from "react"
+import { useRouter } from "next/navigation"
 
 interface ScheduleGeneratorProps {
   tournamentId: number
@@ -9,6 +10,7 @@ interface ScheduleGeneratorProps {
 }
 
 export function ScheduleGenerator({ tournamentId, teamCount, existingRounds }: ScheduleGeneratorProps) {
+  const router = useRouter()
   const [isGenerating, setIsGenerating] = useState(false)
   const [error, setError] = useState("")
   const [result, setResult] = useState<{
@@ -47,6 +49,9 @@ export function ScheduleGenerator({ tournamentId, teamCount, existingRounds }: S
         matchupsCreated: data.matchupsCreated,
       })
       setIsGenerating(false)
+      
+      // Re-fetch the schedule data from the server
+      router.refresh()
     } catch {
       setError("An error occurred. Please try again.")
       setIsGenerating(false)
@@ -81,7 +86,7 @@ export function ScheduleGenerator({ tournamentId, teamCount, existingRounds }: S
         return
       }
 
-      window.location.reload()
+      router.refresh()
     } catch {
       setError("An error occurred. Please try again.")
       setIsGenerating(false)