fix(v2): scope the tools typecheck to the two src/lib files it imports

tools/tsconfig.json included ../src/lib/**/*.ts, which drags in prisma.ts,
redis.ts and mqtt.ts -- the tinyhttp server's infrastructure. prisma.ts needs
types that exist only after `prisma generate`, so typecheck:v2 still failed on
the legacy server's codegen even after CI stopped running the root tsc. Same
coupling, one layer down.

The tooling imports exactly two files from src/lib: resource.ts (the hardware
list) and deviceLinks.ts. The include now names them.

Verified by moving the generated Prisma client aside and re-running: typecheck:v2
passes without it.

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

Author: thebentern

tools/tsconfig.json

@@ -10,5 +10,10 @@
     "skipLibCheck": true,
     "allowImportingTsExtensions": true
   },
-  "include": ["*.ts", "../src/lib/**/*.ts"]
+  // Only the two src/lib files the build tooling actually imports. A `src/lib/**/*.ts` glob also
+  // pulls in prisma.ts, redis.ts and mqtt.ts -- the tinyhttp server's infrastructure -- and
+  // prisma.ts needs types that only exist after `prisma generate`. That made the v2 typecheck
+  // depend on the legacy server's codegen, which is precisely the coupling this split removed
+  // from CI a commit earlier.
+  "include": ["*.ts", "../src/lib/resource.ts", "../src/lib/deviceLinks.ts"]
 }