[Blazehue]

What does this PR do?

Stops tracking TypeScript incremental build caches, so git status stays clean after a build.

• Untracks apps/http-server/tsconfig.tsbuildinfo and apps/ws-server/tsconfig.tsbuildinfo with git rm --cached. The files stay on disk.
• Adds *.tsbuildinfo under # Build Outputs in the root .gitignore. That covers every app that builds with tsc -b: ws-server and streaming, which had no rule before, admin-server, and any future app.

An ignore rule on its own doesn't untrack files that are already committed, so both changes are needed. I left the existing /tsconfig.tsbuildinfo rule in apps/http-server/.gitignore alone to keep the diff small.

Related issue

Closes #187

Type of change

• Bug fix
• New feature
• Documentation
• Refactoring
• Performance
• Tests
• Build / CI / deployment

Which services does this touch?

• apps/frontend
• apps/http-server
• apps/ws-server
• apps/genAI
• packages/db (schema or Prisma changes)
• Docker / CI

How did you test this?

• Ran the same build as CI (pnpm run build --filter='!admin' --filter='!admin-server'). It passes, and afterwards git status --short prints nothing, even though the build regenerates tsconfig.tsbuildinfo files.
• git ls-files | grep tsbuildinfo prints nothing.
• git check-ignore -v shows that the root rule ignores apps/ws-server/tsconfig.tsbuildinfo.
• pnpm run check-types passes.
• pnpm run lint fails with existing apps/frontend ESLint errors (no-explicit-any, setState in an effect). These happen on main too and are unrelated to this change.

Checklist

• I ran pnpm run lint (existing frontend errors only, see above)
• I ran pnpm run check-types
• I ran pnpm run build (the CI-filtered build)
• The app still starts with docker-compose up (not run; this change has no runtime effect)
• I updated documentation if this changes behaviour or setup (not applicable)
• I did not commit any .env file, API key or other secret

---

AI assistance: this change was drafted with an AI coding assistant (Claude Code). I reviewed the diff, and the checks listed above were actually run locally.