nexxo edaceb9597 Delete the users row once the operator has moved out of it ... Decided: whoever is in operators has no business in users. A row left behind is the same mixing the separation exists to end, only smaller. The one case that deletes nothing is a row with a customer, a seat or an order on it. That would mean the same person is operator and paying customer, and a silent delete would take billing data with it — so the migration stops and names the address instead. Neither existing account is in that state. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-07-27 20:44:56 +02:00
..
design	Write the handoff, and rescue the approved templates into the repo	2026-07-27 20:18:20 +02:00
handoffs	Write the handoff, and rescue the approved templates into the repo	2026-07-27 20:18:20 +02:00
specs	docs: Phase D spec — service framing, redesign & CRUD completeness	2026-07-25 14:13:23 +02:00
superpowers	Delete the users row once the operator has moved out of it	2026-07-27 20:44:56 +02:00
deployment.md	feat(deploy): releases you can pin to, and a version that tells the truth	2026-07-26 15:21:38 +02:00
handoff-plan-catalogue.md	docs: handoff for the plan catalogue rebuild	2026-07-26 10:43:17 +02:00
monitoring-uptime-kuma.md	fix(monitoring): cap monitoring retries at the run budget; dependency-free liveness probe	2026-07-25 20:19:32 +02:00
wireguard-hub.md	docs(wireguard): document the ownership model and config storage	2026-07-25 22:55:14 +02:00