Migrations

.github/workflows/opencode-review.yml

@@ -0,0 +1,30 @@
+name: opencode-review
+
+on:
+  pull_request:
+    types: [opened, synchronize, reopened, ready_for_review]
+
+jobs:
+  review:
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write
+      contents: read
+      pull-requests: read
+      issues: read
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          persist-credentials: false
+      - uses: anomalyco/opencode/github@latest
+        env:
+          ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          model: anthropic/claude-sonnet-4-20250514
+          use_github_token: true
+          prompt: |
+            Review this pull request:
+            - Check for code quality issues
+            - Look for potential bugs
+            - Suggest improvements

.github/workflows/opencode.yml

@@ -29,5 +29,3 @@ jobs:
         uses: anomalyco/opencode/github@latest
         env:
           OPENCODE_API_KEY: ${{ secrets.OPENCODE_API_KEY }}
-        with:
-          model: "opencode/MiniMax-M2.5-Free"

.planning/debug/dashboard-internal-server-error-user-id-column.md

@@ -0,0 +1,87 @@
+---
+status: awaiting_human_verify
+trigger: "Investigate issue: dashboard-internal-server-error-user-id-column"
+created: 2026-04-01T21:15:34.683690+05:30
+updated: 2026-04-01T22:11:00.000000+05:30
+---
+
+## Current Focus
+<!-- OVERWRITE on each update - reflects NOW -->
+
+hypothesis: DatabasesPage auth guard should prevent "Authentication is still loading" during initial database fetch
+test: manual verification in real workflow after local lint/build confirmation
+expecting: opening dashboard/databases no longer shows auth-loading error; upload/databases flow proceeds normally
+next_action: ask user to verify databases page and upload flow end-to-end
+
+## Symptoms
+<!-- Written during gathering, then IMMUTABLE -->
+
+expected: After login, dashboard loads databases list successfully.
+actual: Frontend shows "Error loading databases: Internal Server Error".
+errors: sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedColumn) column databases.user_id does not exist while querying /api/v1/databases with WHERE databases.user_id = :user_id.
+reproduction: Login with Firebase -> open dashboard -> frontend requests GET /api/v1/databases -> backend 500.
+started: Started after auth/user-isolation changes that introduced user_id filtering in backend queries.
+
+## Eliminated
+<!-- APPEND only - prevents re-investigating -->
+
+## Evidence
+<!-- APPEND only - facts discovered -->
+
+- timestamp: 2026-04-01T21:17:00+05:30
+  checked: backend API and model references for user_id
+  found: /api/v1/databases router filters with DatabaseModel.user_id == user_id in multiple endpoints; Database model defines user_id field
+  implication: runtime SQL will reference databases.user_id whenever user-scoped queries execute
+
+- timestamp: 2026-04-01T21:17:30+05:30
+  checked: SQL initialization and migration files
+  found: backend/migrations/001_add_user_id.sql adds user_id to databases and query_history; backend/init.sql currently includes user_id columns and indexes
+  implication: codebase expects user_id column, but environments created before migration may still miss the column if migration wasn’t executed
+
+- timestamp: 2026-04-01T21:21:30+05:30
+  checked: backend startup/initialization flow
+  found: main.py calls init_db(); init_db() only does Base.metadata.create_all(bind=engine), which does not alter existing tables to add new columns
+  implication: pre-existing databases table can remain without user_id despite model expecting it
+
+- timestamp: 2026-04-01T21:22:00+05:30
+  checked: migration execution wiring
+  found: backend/migrations SQL files are not referenced by runtime code; docker-compose mounts init.sql into docker-entrypoint-initdb.d, which runs only when postgres volume is first initialized
+  implication: environments with persistent postgres_data created before user_id addition will hit UndefinedColumn at query time
+
+- timestamp: 2026-04-01T21:26:00+05:30
+  checked: backend verification commands
+  found: python -m compileall database/session.py succeeds; python -m pytest unavailable in local environment (pytest module missing)
+  implication: code is syntactically valid, but end-to-end verification requires runtime check in user environment
+
+- timestamp: 2026-04-01T22:02:00+05:30
+  checked: human verification checkpoint response
+  found: original UndefinedColumn issue is fixed after restart, but DatabasesPage now fails initial fetch with frontend error "Authentication is still loading" from useApi.getAuthToken
+  implication: backend schema fix worked; new frontend timing/auth readiness issue blocks dashboard databases flow
+
+- timestamp: 2026-04-01T22:04:00+05:30
+  checked: frontend/src/hooks/use-api.ts getAuthToken implementation
+  found: getAuthToken throws explicit error when auth context loading=true before requesting token
+  implication: any page fetching via useApi during auth bootstrap will deterministically fail with "Authentication is still loading"
+
+- timestamp: 2026-04-01T22:05:00+05:30
+  checked: dashboard page comparison (frontend/src/app/dashboard/page.tsx vs frontend/src/app/dashboard/databases/page.tsx)
+  found: dashboard home waits for useAuth().isLoading to clear and checks isAuthenticated before api.getDatabases(); databases page calls api.getDatabases() immediately on mount without auth guard
+  implication: missing auth guard in databases page is the direct mechanism causing premature token request and frontend error
+
+- timestamp: 2026-04-01T22:08:00+05:30
+  checked: frontend/src/app/dashboard/databases/page.tsx
+  found: added useAuth-based guard (authLoading/isAuthenticated) before fetch, with dependencies updated accordingly
+  implication: DatabasesPage no longer issues token-bound API request during auth bootstrap window
+
+- timestamp: 2026-04-01T22:10:00+05:30
+  checked: frontend verification commands
+  found: pnpm lint passed; pnpm build passed with successful Next.js production build
+  implication: fix compiles cleanly and passes frontend static checks
+
+## Resolution
+<!-- OVERWRITE as understanding evolves -->
+
+root_cause: DatabasesPage triggers api.getDatabases() on mount before auth-provider finishes loading, and useApi.getAuthToken intentionally throws while loading=true.
+fix: Added useAuth guard in frontend/src/app/dashboard/databases/page.tsx to defer api.getDatabases() until auth loading completes and user is authenticated.
+verification: Self-verified with frontend lint/build pass; pending user confirmation in live login + databases/upload workflow.
+files_changed: [backend/database/session.py, frontend/src/app/dashboard/databases/page.tsx]