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/RecalculateEloButton.tsx

@@ -1,8 +1,10 @@
 "use client"
 
 import { useState } from "react"
+import { useRouter } from "next/navigation"
 
 export function RecalculateEloButton() {
+  const router = useRouter()
   const [isLoading, setIsLoading] = useState(false)
 
   const handleClick = async () => {
@@ -33,7 +35,7 @@ export function RecalculateEloButton() {
       
       if (data.success) {
         alert(`Recalculation completed: ${JSON.stringify(data.data)}`)
-        window.location.reload()
+        router.refresh()
       } else {
         alert(`Error: ${data.error}`)
       }