From ddc4164228a8ca0b17e2c74bd14ea05864b46d9d Mon Sep 17 00:00:00 2001
From: prosolis <5590409+prosolis@users.noreply.github.com>
Date: Mon, 27 Jul 2026 07:53:06 -0700
Subject: [PATCH] Note that the seeded 'local' row reappears after a migration

Claude-Session: https://claude.ai/code/session_016y6gyuHkQXPiEuW8RGQyua
---
 deploy/README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/deploy/README.md b/deploy/README.md
index 56506fb..08ea574 100644
--- a/deploy/README.md
+++ b/deploy/README.md
@@ -275,6 +275,13 @@ one transaction with foreign keys off, and verifies the row counts before it
 commits. It refuses to run while anything else has the database open, and
 refuses to merge into an account that already owns writing.
 
+**`local` comes back, and that's expected.** `db.Open` seeds that row on every
+startup, so it reappears the moment Petal restarts after a migration. It owns
+nothing — the writing is on the real account — and it is only ever resolved to
+by `StaticResolver`, which a deployment with `AUTHENTIK_*` set never uses. Check
+`SELECT COUNT(*) FROM documents WHERE user_id = 'local'` if you want to be sure
+a migration took; the presence of the row itself says nothing.
+
 ---
 
 ## 5. Backups