Standards d'engineering

bunx drizzle-kit pull --dialect postgresql --url "$PROD_URL_RO" --out ./prod-pull

psql "$PROD_URL_RO" -XAtq -f src/scripts/schema-fingerprint.sql > prod-pull/prod.txt
DATABASE_URL="$LOCAL_URL" bun run db:migrate
psql "$LOCAL_URL" -XAtq -f src/scripts/schema-fingerprint.sql > prod-pull/baseline.txt
diff prod-pull/prod.txt prod-pull/baseline.txt

BEGIN;
ALTER TABLE "experiences" RENAME CONSTRAINT "gifts_pkey" TO "experiences_pkey";
ALTER TABLE "organization_invitation" RENAME CONSTRAINT "invitation_pkey" TO "organization_invitation_pkey";
DROP INDEX "experiences_token_idx";
DROP INDEX "email_idx";
DROP INDEX "org_api_keys_hash_idx";
DROP INDEX "gift_events_type_idx";
DROP INDEX "invitation_events_type_idx";
DROP INDEX "orders_status_idx";
DROP INDEX "profile_idx";
ALTER TABLE "orders" ADD CONSTRAINT "orders_amount_positive" CHECK ("amount_cents" > 0) NOT VALID;
ALTER TABLE "orders" ADD CONSTRAINT "orders_status_valid" CHECK ("status" IN ('pending','paid','failed','refunded','partially_refunded')) NOT VALID;
ALTER TABLE "payments" ADD CONSTRAINT "payments_kind_valid" CHECK ("kind" IN ('charge','refund')) NOT VALID;
ALTER TABLE "orders" VALIDATE CONSTRAINT "orders_amount_positive";
ALTER TABLE "orders" VALIDATE CONSTRAINT "orders_status_valid";
ALTER TABLE "payments" VALIDATE CONSTRAINT "payments_kind_valid";
COMMIT;

Un `VALIDATE` qui échoue désigne des lignes à examiner, pas une contrainte à abandonner.
</Step>

<Step title="c. Marquer la baseline comme appliquée">
`db:migrate` ne compare pas les hash : il lit la ligne de `drizzle.__drizzle_migrations` au
`created_at` le plus grand et applique les migrations dont le `when` du journal est plus récent.
Marquer la baseline, c'est insérer sa ligne avec `created_at` = son `when`.

- `hash` : `sha256sum src/drizzle/0000_baseline.sql` (macOS : `shasum -a 256`), le hash que
  drizzle calcule sur le contenu du fichier. Informatif, mais à garder exact.
- `created_at` : `entries[0].when` dans `src/drizzle/meta/_journal.json`.

Pour la baseline actuelle : hash `dd0abf748289e7e2a2110c30b12ba7d56ce8706bd58c9544608180fd733f9e05`,
`when` `1791444919068`. D'anciennes lignes peuvent déjà exister (premiers `migrate`) : elles ne
gênent pas tant que leur `created_at` est plus petit — le vérifier avec
`SELECT max(created_at) FROM drizzle.__drizzle_migrations;`.

```sql
CREATE SCHEMA IF NOT EXISTS drizzle;
CREATE TABLE IF NOT EXISTS drizzle.__drizzle_migrations (
  id SERIAL PRIMARY KEY,
  hash text NOT NULL,
  created_at bigint
);
INSERT INTO drizzle.__drizzle_migrations (hash, created_at)
SELECT 'dd0abf748289e7e2a2110c30b12ba7d56ce8706bd58c9544608180fd733f9e05', 1791444919068
WHERE NOT EXISTS (
  SELECT 1 FROM drizzle.__drizzle_migrations WHERE created_at = 1791444919068
);