What problem does it solve? Removing test or signup-test accounts from a production or local LeadAce database requires deleting the Supabase Auth user plus every tenant-scoped row, and doing it by hand risks partial cleanup or deleting a real user by mistake. ## Core Features & Use Cases - Dry-run inventory: Runs in read-only mode by default, showing email, tenant id, plan, role, member count, Stripe ids, and row counts before anything is deleted. - Guarded deletion: The --apply flag deletes only when every target is deletable; a single BLOCKED or not-found target aborts the whole run so a typo cannot cause partial cleanup. - Stripe handling: Cancels the recorded Stripe subscription before deletion when STRIPE_SECRET_KEY is available, matching the in-app account deletion behavior. - Use Case: After signup-flow testing, an engineer runs the inventory command against production with the test users' emails, confirms each is a test account, then re-runs with --apply to remove the tenants and auth users. ## Quick Start Ask the assistant to delete the test accounts with the given emails or auth UUIDs from the LeadAce database, starting with the dry-run inventory before approving the actual deletion.
