test(settings): prove the wipe against real Postgres, and state what deletion means

The defect is about rows that survive, so a mocked client proves nothing. The
new integration test seeds a row into every table in the schema, driven by
information_schema and pg_constraint rather than a fixture, runs the wipe and
asks the database what is left. A table added later is seeded and asserted
without anyone remembering to.

It holds all four halves: nothing in the wipe list survives, everything in the
exemption list does, everything reached only by a database cascade is gone,
and the account row comes back reset but able to sign in. A second file pins
the allergy and checkup-reminder deletes actually removing their row.

The reproductive-health note gains a Deletion section. It taught people to
reason carefully about a host being imaged and never said what pressing
delete does; now it says which of the three deletions removes the row and
which only hides it.
This commit is contained in:
Marc-André Bombeck committed 2026-07-26 14:04:44 +02:00
1 parent 5e66ebaa54
commit dccd2f320b
8 files changed
+678 -7

No files matched your search

@@ -2,8 +2,9 @@
* v1.17.1 — Vorsorge (measurement) reminder by id: get + patch + delete.
*
* PATCH re-derives the server-authoritative `nextDueAt` after applying
* the (mutually-exclusive cadence) edit. DELETE soft-deletes (tombstone)
* for parity with the rest of the tree.
* the (mutually-exclusive cadence) edit. DELETE removes the row; the
* confirmation dialog says the reminder is permanently deleted, and nothing
* here needs a tombstone to keep that promise honest.
*/
import { NextRequest } from "next/server";