tenant-migration

Migrate or plan a new tenant platform: $ARGUMENTS

$ARGUMENTS can include:

• "plan " — Generate a migration plan for a new leader (no changes made)
• "execute " — Execute the migration interactively (step-by-step with confirmation)
• "audit " — Audit an already-migrated repo for leftover source-tenant contamination
• "verify " — Run full post-migration verification checklist
• "env-classify" — Show the shared vs tenant-specific env var classification
• Empty — explain the migration process and ask what to do

Migration Philosophy

This is NOT a clone script. This is a disciplined platform replication procedure for a multi-tenant thought leader platform where:

• Architecture, stack, infrastructure, and code patterns are standardized across all tenants
• The differences between tenants are controlled and enumerated — they live in specific files, not scattered throughout
• Every new tenant starts from a known-good baseline (currently Alan Hirsch repo) and is carefully converted