# Provisioning and tenant lifecycle
Available commands are `tenant:create`, `tenant:provision`, `tenant:seed`, `tenant:admin:create`, `tenant:suspend`, `tenant:activate`, `tenant:archive`, and `tenant:domain:verify`. Per-tenant migration and database-destruction commands have been removed.
Creating a tenant validates the store name, subdomain, and locale, creates its central record, and queues `ProvisionTenantJob` after commit. The job uses a tenant-specific overlap lock.

Provisioning no longer creates or migrates a database. It claims a provisioning run under a row lock, initializes tenant context, idempotently seeds authorization and store defaults, initializes feature flags, performs a schema smoke check, and moves the tenant to `pending_admin`. Failures set the tenant and run to `failed` with a bounded error message.

The first administrator is created under tenant context, receives the tenant-scoped `super-admin` role, and moves the store to `active`. Suspension and activation retain data. Archiving disables the store and never deletes its rows automatically.
