tsconfig.json included **/*.ts but only excluded worker/**, not bot/**.
This caused next build to type-check bot source files whose dependencies
aren't installed in the root node_modules, breaking CI.
- Add bot/** to tsconfig.json exclude array
- Add bot/** and worker/** to eslint globalIgnores
Adds full Telegram ZIP ingestion pipeline: TDLib worker service scans source
channels for archive files, deduplicates by content hash, extracts metadata,
uploads to archive channel, and indexes in Postgres. Forum supergroups are
scanned per-topic with topic names used as creator. Filename-based creator
extraction (e.g. "Mammoth Factory - 2026-01.zip") serves as fallback.
Includes admin UI for managing accounts/channels, simplified account setup
(API credentials via env vars), auth code/password submission dialog,
package browser with creator column, and live ingestion activity tracking.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The prisma-client generator mandates an output path, which conflicts
with using the standard @prisma/client import. Switch to prisma-client-js
which generates to node_modules by default.
Co-Authored-By: Claude <noreply@anthropic.com>
The custom generator output to src/generated/prisma caused persistent
Turbopack module resolution failures in CI. Switch to the standard
@prisma/client import path which all bundlers resolve correctly.
- Remove custom output from prisma schema generator
- Update all imports from ../generated/prisma to @prisma/client
- Add postinstall script to auto-run prisma generate after npm ci
- Remove generated files from git (no longer needed in source tree)
- Simplify CI workflow (remove verify step and --webpack workaround)
Co-Authored-By: Claude <noreply@anthropic.com>
Turbopack cannot resolve imports from src/generated/prisma even
with relative paths and committed files. Switch to --webpack for
CI build. Also add file verification step for debugging.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Turbopack cannot resolve @/generated/prisma path alias during
next build, even with the files committed and baseUrl set.
Switch to relative imports (../generated/prisma) which Turbopack
resolves without issues.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Turbopack skips gitignored directories during module resolution in
next build. Since src/generated/prisma was in .gitignore, the build
on CI failed with "Module not found: Can't resolve '@/generated/prisma'"
even though prisma generate created the files.
Fix: commit the generated client and remove it from .gitignore.
Run `npx prisma generate` after schema changes to update.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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>
Add ls output after prisma generate to verify files exist
before tsc runs. This will show whether the generated client
is in src/generated/prisma/ or elsewhere.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tsc requires baseUrl to be set for paths mapping to work.
Without it, @/* path aliases are silently ignored during
standalone tsc --noEmit, causing TS2307 errors for
@/generated/prisma imports in CI.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Move DATABASE_URL to workflow-level env so all steps can access it
- Add verification step to confirm prisma generate creates output files
- This should fix TS2307 'Cannot find module @/generated/prisma' in CI
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The migration_lock.toml was excluded by a gitignore pattern
(prisma/migrations/**/migration_lock.toml) which caused
`prisma migrate deploy` to fail in CI with no lock file present.
Prisma requires this file to be version-controlled.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Disable react-hooks/incompatible-library warnings for RHF watch()
and TanStack useReactTable() — these are false positives from the
React Compiler plugin
- Remove unused useDebounce import and variable from vendor-table
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
