Mismatch between generated config.toml defaults and docs for auth.mfa.totp settings

[spring-hh]

Describe the bug When running supabase init, the generated config.toml sets both TOTP flags to false:

[auth.mfa.totp]
enroll_enabled = false
verify_enabled = false

However, the documentation at https://supabase.com/docs/guides/local-development/cli/config states that both auth.mfa.totp.enroll_enabled and auth.mfa.totp.verify_enabled default to true. This mismatch makes it unclear which behavior is correct.

To Reproduce Steps to reproduce the behavior:

1. Install the latest Supabase CLI (supabase --version shows 2.26.9).

2. Run in an empty folder:

   supabase init
   

3. Open the newly created config.toml and inspect the [auth.mfa.totp] section. Expected behavior Per the docs, the config.toml should default to:

[auth.mfa.totp]
enroll_enabled = true
verify_enabled = true

System information

• Version of OS: macOS Sequoia 15.5
• Version of CLI: v2.26.9
• Version of Docker: v28.1.1
• Versions of services: SERVICE IMAGE | LOCAL | LINKED ------------------------|------------------------|-------- supabase/postgres | 17.4.1.043 | - supabase/gotrue | v2.176.1 | - postgrest/postgrest | v12.2.12 | - supabase/realtime | v2.36.18 | - supabase/storage-api | v1.24.6 | - supabase/edge-runtime | v1.67.4 | - supabase/studio | 2025.06.16-sha-c4316c3 | - supabase/postgres-meta | v0.89.3 | - supabase/logflare | 1.14.2 | - supabase/supavisor | 2.5.2 | -

Additional context