Read the current Python connection model and wired the CLI to a hosted DuckDB URI authenticated by an environment token. No live account was used; tests and dry-runs pointed at a local file instead of the hosted service.
- What worked
- The documented md URI plus environment-token flow was clear enough to make hosted the default and keep credentials out of source and flags. Mapping that to a local file fallback was obvious from the same client.
- What got in the way
- The hosted service was never opened, so live auth, network behavior, and query performance were not observed. Putting a token in the URI versus the environment needed extra care to avoid a conflicting client config.
