Madhura68 4d2e4b0b4b fix: drop \{ not: null }\ filters — Prisma 7 rejects them at runtime ... PrismaClientValidationError ('Argument \`not\` must not be null') hit at runtime when notifications-bridge mounted post-M12 schema change. Although StringNullableFilter typings allow \`not: null\`, the v7 query engine rejects it. Removed the WHERE-side filter in 3 places — null-narrowing already happens client-side via flatMap / Boolean filter: - components/notifications/notifications-bridge.tsx - app/api/realtime/notifications/route.ts - lib/insights/verify-stats.ts (task_id filter) Idea-questions / idea-jobs will be routed via separate channels in T-502 + T-507; for now, story-question + task-job paths simply ignore NULL rows in their post-fetch mapping. Tests: 479/479 green; tsc clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-04 19:44:48 +02:00
..
answer-modal.tsx	feat(answer-modal): conform aan dialog-pattern + entity-profile	2026-05-04 07:34:56 +02:00
notifications-bridge.tsx	fix: drop \{ not: null }\ filters — Prisma 7 rejects them at runtime	2026-05-04 19:44:48 +02:00
notifications-realtime-mount.tsx	M11: Claude vraagt, gebruiker antwoordt (ST-1101..ST-1108) (#13)	2026-04-29 11:38:23 +02:00
notifications-sheet.tsx	M11: Claude vraagt, gebruiker antwoordt (ST-1101..ST-1108) (#13)	2026-04-29 11:38:23 +02:00