Fix: Use Next.js API proxy to avoid mixed-content/CORS errors

HTTPS pages cannot fetch from HTTP backend ports. Added Next.js
API route proxies for /api/vocabulary, /api/learning-units, /api/progress
that forward to backend-lehrer internally (same Docker network, HTTP).

All frontend pages now use same-origin requests (getApiBase = '')
instead of direct port:8001 connections.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

studio-v2/app/learn/[unitId]/quiz/page.tsx

@@ -13,11 +13,11 @@ interface MCQuestion {
   explanation?: string
 }
 
-function getBackendUrl() {
-  if (typeof window === 'undefined') return 'http://localhost:8001'
-  const { hostname, protocol } = window.location
-  if (hostname === 'localhost') return 'http://localhost:8001'
-  return `${protocol}//${hostname}:8001`
+function getApiBase() {
+  return ''  // Same-origin proxy
+  
+  
+  
 }
 
 export default function QuizPage() {
@@ -43,7 +43,7 @@ export default function QuizPage() {
   const loadMC = async () => {
     setIsLoading(true)
     try {
-      const resp = await fetch(`${getBackendUrl()}/api/learning-units/${unitId}/mc`)
+      const resp = await fetch(`${getApiBase()}/api/learning-units/${unitId}/mc`)
       if (!resp.ok) throw new Error(`HTTP ${resp.status}`)
       const data = await resp.json()
       setQuestions(data.questions || [])