From fb7885324b88c5f0c3bf237b8f0a8fef1627aa4e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?G=C3=A1borj=C3=A1ni-Szab=C3=B3=20=C3=81d=C3=A1m?=
 <117768520+Programcode@users.noreply.github.com>
Date: Fri, 23 Oct 2026 07:48:06 +0000
Subject: [PATCH] Record DB-03 legacy policy drop as a migration

Adam approved DB-03 on 23 Oct 2026. It was run by hand on staging, tested
there (shared links signed in and out, expired links, own role read, usage
count), then run on production. The file moves from supabase/proposed/ to
supabase/migrations/ under a new timestamp so main matches the hosted
projects; on both it finds nothing left to drop.
---
 .../20261023080000_drop_legacy_policies.sql}              | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
 rename supabase/{proposed/20261023060000_drop_legacy_policies.sql => migrations/20261023080000_drop_legacy_policies.sql} (88%)

diff --git a/supabase/proposed/20261023060000_drop_legacy_policies.sql b/supabase/migrations/20261023080000_drop_legacy_policies.sql
similarity index 88%
rename from supabase/proposed/20261023060000_drop_legacy_policies.sql
rename to supabase/migrations/20261023080000_drop_legacy_policies.sql
index 1e4906e86..4a7c8f3f1 100644
--- a/supabase/proposed/20261023060000_drop_legacy_policies.sql
+++ b/supabase/migrations/20261023080000_drop_legacy_policies.sql
@@ -1,4 +1,7 @@
--- DB-03 (proposed, destructive): drop policies that no migration created.
+-- DB-03: drop policies that no migration created. Approved by Adam on
+-- 23 Oct 2026; moved from supabase/proposed/. It was run by hand on staging
+-- and production first, after shared links, role reads and usage counts were
+-- tested on staging, so on both hosted projects this finds nothing to drop.
 --
 -- The QA run on 22 Oct 2026 found policies on production that are not in
 -- staging or in supabase/migrations, including duplicate permissive ones on
@@ -24,7 +27,8 @@
 -- caller's own rows: without user_roles_select_own, signed-in users could no
 -- longer read their own role (SettingsPage and the curated_sources admin
 -- policies depend on it), and a drifted copy would keep the leak this fixes.
--- Do a dry run first (BEGIN; ...; ROLLBACK;).
+-- Running it again changes nothing: every drop is IF EXISTS and the kept
+-- policies are never dropped.
 
 DO $$
 DECLARE