What happens to admin edits when the app restarts and re-seeds (idempotency)?

Seeding is idempotent — on restart, the app ensures required baseline data exists (like the protected Super Admin role and default configuration) without overwriting your edits. Re-seeding fills gaps; it doesn't clobber changes you've made. So restarting doesn't reset your configuration or wipe customizations — the idempotent seed only creates what's missing. This is the same…

Seeding is idempotent — on restart, the app ensures required baseline data exists (like the protected Super Admin role and default configuration) without overwriting your edits. Re-seeding fills gaps; it doesn't clobber changes you've made. So restarting doesn't reset your configuration or wipe customizations — the idempotent seed only creates what's missing. This is the same idempotency principle applied to imports and billing, ensuring repeatable operations are safe.