This change makes tenant database routing “auto” by default and introduces a new authenticated management endpoint (/api/sdk/v1/management/tenant-overrides) for listing/upserting/disabling explicit tenant→DB overrides, updating the core SDK client, dashboard UX, and docs to use it while keeping legacy routes as aliases. It reduces setup friction for SaaS users and enables headless server-to-server override management via bearer API keys, but it also expands a high-risk surface that can provision/attach/disable tenant databases, so auth/rate-limit/billing gating mistakes or provisioning failures could lead to unintended DB operations, spend, or tenant routing regressions. Additional concerns include backward-compatibility/transition issues between legacy endpoints and the new envelope behavior, plus operational fragility around Turso provisioning/verification timing and error handling.