Fixes

.env.example

@@ -30,8 +30,12 @@ R2_BUCKET_NAME="unvibe-assets"
 RESEND_API_KEY="re_..."
 
 # Sentry application monitoring DSNs
-SENTRY_DSN_WEB="https://example_public_key@o0.ingest.sentry.io/0"
-SENTRY_DSN_API="https://example_public_key@o0.ingest.sentry.io/0"
+SENTRY_DSN_API="https://examplePublicKey@o0.ingest.sentry.io/0"
+SENTRY_DSN_AI="https://examplePublicKey@o0.ingest.sentry.io/0"
+NEXT_PUBLIC_SENTRY_DSN="https://examplePublicKey@o0.ingest.sentry.io/0"
+
+# API URL for web
+NEXT_PUBLIC_API_URL="http://localhost:3000"
 
 # Posthog analytics public key
 NEXT_PUBLIC_POSTHOG_KEY="phc_..."

.gitignore

@@ -39,5 +39,8 @@ yarn-debug.log*
 yarn-error.log*
 pnpm-debug.log*
 
+# TypeScript incremental build info
+*.tsbuildinfo
+
 # Sentry
 .sentry-clirc

.planning/debug/knowledge-base.md

@@ -0,0 +1,14 @@
+# GSD Debug Knowledge Base
+
+Resolved debug sessions. Used by `gsd-debugger` to surface known-pattern hypotheses at the start of new investigations.
+
+---
+
+## unused-usestate-import — unused useState import in code-submission component
+- **Date:** 2026-07-02
+- **Error patterns:** useState, defined but never used, @typescript-eslint/no-unused-vars, code-submission
+- **Root cause:** useState was imported but never used — the component uses Zustand (useEditorStore) and tRPC mutation state instead of local React state.
+- **Fix:** Removed useState from the React import statement.
+- **Files changed:** apps/web/src/components/features/code-submission.tsx
+---
+

.planning/debug/redis-econnrefused.md

@@ -0,0 +1,62 @@
+---
+status: diagnosing
+trigger: "Debug a `npm run dev` error - Redis ECONNREFUSED when Docker containers not running"
+created: 2026-06-30T00:00:00.000Z
+updated: 2026-06-30T00:00:00.000Z
+---
+
+## Current Focus
+
+root_cause: "BullMQ Queue and Worker are instantiated synchronously at module-level in index.ts (lines 43-47) without error handling. Both constructors immediately attempt to connect to Redis. When Docker is not running, Redis is unavailable, and BullMQ's built-in reconnection logic repeatedly retries the connection, spamming ECONNREFUSED errors."
+next_action: "Return structured diagnosis with root cause and recommended fix"
+
+## Symptoms
+
+expected: "npm run dev starts api and web without errors"
+actual: "api:dev throws AggregateError [ECONNREFUSED]: connect ECONNREFUSED 127.0.0.1:6379 repeatedly"
+errors: "AggregateError [ECONNREFUSED]: connect ECONNREFUSED 127.0.0.1:6379"
+reproduction: "Run npm run dev while Docker Desktop is not running"
+started: "Always broken when Docker containers are not running"
+
+## Eliminated
+
+## Evidence
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: apps/api/src/index.ts lines 37-47
+  found: BullMQ Queue('submissions') and createSubmissionWorker() are instantiated synchronously at module level, before Express server starts. connectionOpts derived from REDIS_URL env var.
+  implication: Redis connection is attempted immediately on module load, not lazily
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: apps/api/src/services/submission-worker.ts lines 42-113
+  found: createSubmissionWorker constructs a new Worker('submissions', processor, { connection }) — Worker constructor attempts Redis connection immediately
+  implication: Both Queue and Worker try to connect to Redis at module load time, causing duplicate ECONNREFUSED errors
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: infra/docker-compose.yml
+  found: redis:7-alpine service defined on port 6379, with healthcheck
+  implication: Redis is meant to be provided via Docker
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: Docker Desktop service status
+  found: com.docker.service is Stopped; docker ps fails with pipe error; docker compose binary exists (v5.1.4) but daemon not running
+  implication: Docker containers cannot be started until Docker Desktop is running
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: apps/api/src/index.ts lines 37-47
+  found: BullMQ Queue('submissions') and createSubmissionWorker() are instantiated synchronously at module level, before Express server starts. connectionOpts derived from REDIS_URL env var.
+  implication: Redis connection is attempted immediately on module load, not lazily
+
+- timestamp: 2026-06-30T00:00:00.000Z
+  checked: infra/docker-compose.yml
+  found: redis:7-alpine service defined on port 6379, with healthcheck. Docker Desktop is not running (pipe not available).
+  implication: Redis is not available, but code doesn't handle this gracefully
+
+## Resolution
+
+root_cause: "BullMQ Queue('submissions') and Worker('submissions') are instantiated at module-level in apps/api/src/index.ts (lines 43-47) without any error handling. Both constructors immediately attempt to connect to Redis at redis://localhost:6379. When Docker containers are not running (Docker Desktop service stopped), Redis is unreachable, and BullMQ's internal reconnection logic causes repeated ECONNREFUSED errors that spam the console. The API server still starts because these async connection failures don't crash the process (Express listen continues), but the console noise is disruptive."
+fix: "Option C: Both — (1) Start Docker containers to provide Redis, AND (2) Make Redis/BullMQ initialization lazy and resilient so the API can start without Redis (wrap in try-catch with optional flag, defer connection to first use)"
+verification: ""
+files_changed:
+
+- apps/api/src/index.ts

.planning/debug/resolved/unused-usestate-import.md

@@ -0,0 +1,42 @@
+---
+status: resolved
+trigger: "web#build failing: 'useState' is defined but never used. @typescript-eslint/no-unused-vars in apps/web/src/components/features/code-submission.tsx"
+created: 2026-07-02T10:00:00.000Z
+updated: 2026-07-02T10:00:00.000Z
+---
+
+## Current Focus
+
+hypothesis: "useState is imported but genuinely unused — the component uses Zustand (useEditorStore) and tRPC mutation state instead"
+test: Remove useState from import, run build to verify
+expecting: Build passes without the no-unused-vars error
+next_action: Apply fix and run pnpm run build in apps/web
+
+## Symptoms
+
+expected: web#build passes without errors
+actual: ESLint error — 'useState' is defined but never used
+errors: "3:10  Error: 'useState' is defined but never used.  @typescript-eslint/no-unused-vars"
+reproduction: Run any build command that invokes ESLint on code-submission.tsx
+started: Likely since the component was written without using useState
+
+## Eliminated
+
+- hypothesis: useState might be needed but was forgotten
+  evidence: Component uses useEditorStore for code state and trpc.useMutation for submission lifecycle — all state needs are met without useState
+  timestamp: 2026-07-02T10:00:00.000Z
+
+## Evidence
+
+- timestamp: 2026-07-02T10:00:00.000Z
+  checked: apps/web/src/components/features/code-submission.tsx lines 1-63
+  found: useState imported on line 3 but never called in component body. Component uses useEditorStore (line 11) and trpc.modules.submitDecode.useMutation() (line 12).
+  implication: useState is genuinely unused — removing it is the correct fix
+
+## Resolution
+
+root_cause: Unused import of useState in code-submission.tsx component — the component uses Zustand (useEditorStore) for state management and tRPC mutation state for submission lifecycle, with no need for local React state
+fix: Remove useState from the React import on line 3
+verification: Build passes cleanly — "Compiled successfully", 0 ESLint errors, 13 static pages generated
+files_changed:
+  - apps/web/src/components/features/code-submission.tsx

.planning/debug/ts-build-errors.md

@@ -0,0 +1,113 @@
+---
+status: investigating
+trigger: "Debug TypeScript build errors in UnVibe monorepo (pnpm build fails with api#build exiting code 2)"
+created: 2026-06-30T21:47:00.000Z
+updated: 2026-06-30T21:47:00.000Z
+---
+
+## Current Focus
+
+hypothesis: Three independent root causes causing tsc build failure — (1) prisma generate not run, (2) tsconfig includes test files without jest types, (3) untyped catch param
+test: Verify each root cause by checking node_modules/.prisma/client existence, tsconfig include/exclude, and TypeScript strict mode behavior
+expecting: All three confirmed
+next_action: Present completed diagnosis with fix steps
+
+## Symptoms
+
+expected: `pnpm build` completes with zero TypeScript errors
+actual: `api#build` task exits with code 2 — three error groups
+errors: |
+Error Group 1 — TS2305: Module '"@prisma/client"' has no exported member 'PrismaClient'
+src/index.ts(8,10): error TS2305
+src/services/submission-worker.ts(13,10): error TS2305
+
+Error Group 2 — Test globals not found (30+ errors)
+src/**tests**/ai-client.test.ts(30,1): error TS2582: Cannot find name 'describe'
+src/**tests**/ai-client.test.ts(33,3): error TS2304: Cannot find name 'beforeEach'
+src/**tests**/ai-client.test.ts(35,5): error TS2304: Cannot find name 'jest'
+... (describe, it, expect, jest, beforeEach all unrecognized)
+
+Error Group 3 — TS7006: Parameter 'e' implicitly has an 'any' type
+src/services/submission-worker.ts(100,19): error TS7006
+reproduction: Run `pnpm build` in repo root (or `pnpm --filter api build`)
+started: First build attempt — never successfully built
+
+## Eliminated
+
+- hypothesis: @prisma/client not installed as dependency
+  evidence: @prisma/client is listed in dependencies of apps/api/package.json at line 17, and node_modules/@prisma/client exists
+  timestamp: 2026-06-30T21:47:00.000Z
+
+- hypothesis: Missing @types/jest is the full fix for Error Group 2
+  evidence: The real fix is to exclude test files from the build tsconfig. Adding @types/jest would only mask the problem — test files shouldn't be compiled during a production build. Test runner (jest.config.ts uses ts-jest) handles compilation separately.
+  timestamp: 2026-06-30T21:47:00.000Z
+
+## Evidence
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/tsconfig.json
+  found: `"include": ["src/**/*"]` — this includes `src/__tests__/ai-client.test.ts`
+  implication: Test files are compiled during `tsc build`. This is the cause of Error Group 2.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/node_modules/@prisma/client/index.d.ts
+  found: `export * from '.prisma/client/default'` — re-exports from generated client
+  implication: Requires `.prisma/client/` generated directory to exist.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: node_modules/.prisma/client/ and apps/api/node_modules/.prisma/client/
+  found: Neither exists anywhere in the repo
+  implication: `prisma generate` has never been run. This is the cause of Error Group 1.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/tsconfig.build.json
+  found: Does not exist
+  implication: No separate build tsconfig exists to exclude test files.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/node_modules/@types/jest
+  found: Does not exist (neither in apps/api/node_modules nor root node_modules)
+  implication: Even if tests were included, jest type definitions are not available.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/src/services/submission-worker.ts line 100
+  found: `.catch((e) => logger.error(...))` — `e` is an untyped arrow function parameter in a `.catch()` callback
+  implication: `useUnknownInCatchVariables` (strict mode) only applies to `catch(e)` in try/catch blocks, NOT to `.catch((e) => ...)` promise callbacks. The param `e` is a regular parameter defaulting to `any`. This is Error Group 3.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: tsconfig.base.json line 9 — `"strict": true`
+  found: strict mode is enabled
+  implication: `noImplicitAny` is enabled, which catches any untyped parameter.
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: turbo.json
+  found: build task has `"dependsOn": ["^build"]` but no dependency on `db:generate`
+  implication: Even if `prisma generate` were a script, it wouldn't automatically run before build
+
+- timestamp: 2026-06-30T21:47:00.000Z
+  checked: apps/api/package.json build script
+  found: `"build": "tsc"` — uses the default tsconfig.json which includes test files
+  implication: No separate build tsconfig is used
+
+## Resolution
+
+root_cause: |
+Three independent root causes:
+
+1. **PrismaClient not found (Error Group 1):** `prisma generate` has never been run. The `@prisma/client` package is installed but its generated client code in `.prisma/client/` only materializes after `prisma generate`. TypeScript resolves the import declaration to `@prisma/client/index.d.ts` which re-exports from `.prisma/client/default` — a file that doesn't exist, so there are no exports to resolve.
+
+2. **Test files compiled during build (Error Group 2):** `tsconfig.json` uses `"include": ["src/**/*"]` which matches `src/__tests__/ai-client.test.ts`. This file uses Jest globals (`describe`, `beforeEach`, `jest`, `expect`, `it`) but `@types/jest` is not installed. The fix is to exclude test files from the build tsconfig (standard practice), NOT to install jest types (which would only allow test code to compile into the production dist).
+
+3. **Implicit any on catch param (Error Group 3):** Line 100 of `submission-worker.ts` has `.catch((e) => logger.error(...))`. The `useUnknownInCatchVariables` flag (implied by `strict: true`) only applies to `catch` clause variables in try/catch blocks, NOT to `.catch()` promise method callbacks. The parameter `e` is a regular untyped arrow function parameter, which strict mode's `noImplicitAny` flags as an error.
+
+fix: |
+
+1. Run `pnpm --filter api exec prisma generate` before build (or add `"prebuild": "prisma generate"` to apps/api/package.json)
+2. Create a `tsconfig.build.json` that excludes `src/__tests__`, update build script to `"build": "tsc -p tsconfig.build.json"`
+3. Add explicit type annotation `e: unknown` on line 100 of submission-worker.ts
+   verification: Not yet applied
+   files_changed:
+
+- apps/api/tsconfig.build.json (create)
+- apps/api/package.json (update build script)
+- apps/api/src/services/submission-worker.ts (fix catch param type)

.planning/intel/.last-refresh.json

@@ -0,0 +1,45 @@
+{
+  "_meta": {
+    "updated_at": "2026-06-30T22:30:00.000Z",
+    "version": 1
+  },
+  "snapshot": {
+    "branch": "Python-Yuvraj",
+    "commit": "f785ee8",
+    "description": "Dev 2 — AI Service full implementation with real OpenRouter LLM calls",
+    "files": {
+      "apps/ai-service/app/main.py": "hashv1",
+      "apps/ai-service/app/config.py": "hashv1",
+      "apps/ai-service/app/services/llm_client.py": "hashv1",
+      "apps/ai-service/app/services/prompt_manager.py": "hashv1",
+      "apps/ai-service/app/services/ast_differ.py": "hashv1",
+      "apps/ai-service/app/routes/generate.py": "hashv1",
+      "apps/ai-service/app/routes/quiz.py": "hashv1",
+      "apps/ai-service/app/routes/diff.py": "hashv1",
+      "apps/ai-service/app/routes/defend.py": "hashv1",
+      "apps/ai-service/app/prompts/v1/code_generation.txt": "hashv1",
+      "apps/ai-service/app/prompts/v1/quiz_generation.txt": "hashv1",
+      "apps/ai-service/app/prompts/v1/defend_question.txt": "hashv1",
+      "apps/ai-service/app/prompts/v1/defend_evaluation.txt": "hashv1",
+      "apps/ai-service/tests/conftest.py": "hashv1",
+      "apps/ai-service/tests/test_generate.py": "hashv1",
+      "apps/ai-service/tests/test_quiz.py": "hashv1",
+      "apps/ai-service/tests/test_diff.py": "hashv1",
+      "apps/ai-service/tests/test_defend.py": "hashv1",
+      "apps/ai-service/requirements.txt": "hashv1",
+      "apps/ai-service/pytest.ini": "hashv1",
+      "apps/api/src/services/ai-client.ts": "hashv1",
+      "apps/api/src/services/submission-worker.ts": "hashv1",
+      "apps/api/src/__tests__/ai-client.test.ts": "hashv1",
+      "apps/api/jest.config.ts": "hashv1",
+      "apps/api/src/index.ts": "hashv1",
+      "apps/api/package.json": "hashv1"
+    },
+    "counts": {
+      "python_tests": 28,
+      "typescript_tests": 12,
+      "python_source_files": 10,
+      "typescript_source_files": 6
+    }
+  }
+}