OUT-3734 | Schema: add TaskReminderSent table + TaskReminderType enum

[arpandhakal]

Summary

• Adds TaskReminderType enum and TaskReminderSents table — the idempotency ledger for reminder emails (Milestone 1).
• Unique constraint on (taskId, recipientId, reminderType) is the dedupe primitive so retries and manual re-triggers cannot double-send.
• FK to Tasks(id) with ON DELETE CASCADE; workspaceId carried for tenancy parity with the rest of the schema.

Test plan

• prisma validate passes
• prisma migrate dev applies cleanly on local Postgres
• prisma generate produces the expected types
• Duplicate insert on (taskId, recipientId, reminderType) raises a unique-constraint violation
• Hard-deleting the parent Task cascades and removes ledger rows
• Migration applies cleanly in staging on deploy

🤖 Generated with Claude Code

[linear-code]

OUT-3734

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 18, 2026 10:50am

[greptile-apps]

Greptile Summary

This PR introduces the TaskReminderSents idempotency ledger (Milestone 1) — a new TaskReminderType enum with six reminder categories and a TaskReminderSents table that deduplicates outbound reminder emails via a unique constraint on (taskId, recipientId, reminderType).

• Adds TaskReminderType enum (NO_DUE_DATE_3D/7D, DUE_DATE_BEFORE_3D, DUE_DATE_TODAY, DUE_DATE_OVERDUE_3D/7D) and the TaskReminderSents table with a cascade FK to Tasks.
• Migration DDL is consistent with the Prisma schema; the unique index is the sole dedup primitive and blocks retries from double-sending.

Confidence Score: 4/5

Safe to merge; the schema and migration are internally consistent. Two non-blocking issues are worth revisiting before the reminder job ships.

The migration and schema are in sync, CASCADE FK is correctly wired, and the dedup constraint aligns with the stated design intent. The main concerns are that the lifetime-once unique constraint may silently skip reminders after task state resets, and workspaceId has no index despite being the tenancy column — both are worth addressing before the reminder job is turned on in production but neither blocks the schema migration itself.

prisma/schema/taskReminderSent.prisma — unique constraint semantics and missing workspaceId index.

Important Files Changed

Filename	Overview
prisma/migrations/20260515091539_add_task_reminder_sents_table/migration.sql	Creates the TaskReminderType enum and TaskReminderSents table with a composite unique index and CASCADE FK; migration DDL matches the Prisma schema exactly.
prisma/schema/taskReminderSent.prisma	New model and enum are well-structured; two P2 notes: the lifetime-once unique constraint may block legitimate re-sends after task state resets, and workspaceId lacks an index for tenant-scoped lookups.
prisma/schema/task.prisma	Single-line addition of the taskReminderSents back-relation; no issues.

_{Reviews (1): Last reviewed commit: "feat(OUT-3734): add TaskReminderSents ta..." | Re-trigger Greptile}

[greptile-apps]

Permanent dedup blocks legitimate re-sends

The unique constraint on (taskId, recipientId, reminderType) has no time dimension, so each reminder type can only fire once per task-recipient pair for the lifetime of the record. For the NO_DUE_DATE_* types this creates a concrete gap: if a user adds a due date (making the "no due date" reminders irrelevant), then later removes it again, the 3-day and 7-day nudges will never re-fire because the old ledger rows still exist. The same applies to DUE_DATE_TODAY if a due date is postponed and then reset. At minimum a comment explaining why this lifetime-once behaviour is correct, or whether the job is expected to delete stale rows before re-arming, would help prevent future confusion.

[greptile-apps]

Missing workspaceId index for tenant-scoped queries. The column is explicitly carried "for tenancy parity" but has no index, so any query that filters or batches by workspace (e.g., the reminder job scanning pending tasks per workspace) will do a full table scan as the table grows.

Suggested change

	@@unique([taskId, recipientId, reminderType])
	@@map("TaskReminderSents")
	@@unique([taskId, recipientId, reminderType])
	@@index([workspaceId])
	@@map("TaskReminderSents")

[vercel]

Deployment failed with the following error:

Deploying Serverless Functions to multiple regions is restricted to the Pro and Enterprise plans.

Learn More: https://vercel.link/multiple-function-regions

[priosshrsth]

lgtm