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
..
agent-throughput.ts	Agent throughput: jobs per dag stacked bar + KPI-strip (#49)	2026-05-02 16:30:06 +02:00
backlog-health.ts	feat(insights): add getBacklogHealth helper — stuck tasks + missing AC/plan counts (#48)	2026-05-02 16:17:03 +02:00
burndown.ts	feat: getBurndownData helper + computeBurndownDays (lib/insights/burndown.ts) (#34)	2026-05-01 16:41:12 +02:00
sprint-status.ts	Component: SprintStatusDonut (Recharts PieChart) (#36)	2026-05-01 16:41:18 +02:00
velocity.ts	fix(insights): narrow Sprint.completed_at to Date in velocity.ts (#56)	2026-05-02 20:21:30 +02:00
verify-stats.ts	fix: drop \{ not: null }\ filters — Prisma 7 rejects them at runtime	2026-05-04 19:44:48 +02:00