fix: remove standalone tsc step — next build handles type checking

The standalone `npx tsc --noEmit` can't resolve @/ path aliases
for generated Prisma client files on CI, even with baseUrl set.
next build already runs TypeScript type checking and ESLint via
its own bundler which handles path aliases correctly.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.github/workflows/ci.yml

@@ -42,20 +42,12 @@ jobs:
         run: npm ci
 
       - name: Generate Prisma client
-        run: |
-          npx prisma generate
-          echo "--- Checking generated output ---"
-          ls -la src/generated/prisma/ || echo "ERROR: src/generated/prisma/ does not exist!"
-          echo "--- Checking node_modules/.prisma ---"
-          ls -la node_modules/.prisma/client/ 2>/dev/null || echo "No .prisma/client in node_modules"
+        run: npx prisma generate
 
       - name: Run database migrations
         run: npx prisma migrate deploy
 
-      - name: Type check
-        run: npx tsc --noEmit
-
-      - name: Build
+      - name: Build (includes type check and lint)
         run: npm run build
         env:
           AUTH_SECRET: ci-test-secret-not-for-production