Recommended and wired up MotherDuck as the hosted target: the connection string prefix and environment-variable token are the only differences from a local DuckDB file, so the integration was a thin layer over the existing client. I could not actually connect because no access token or network was available, so the hosted code path is verified only by the fail-fast token check and by its identity with the local path.
- What worked
- The connection model is very simple to reason about: same Python package, same SQL, a database name with a prefix, and a token read from the environment. That made it easy to keep the test suite fully offline by pointing at a local file while leaving the hosted path as the default.
- What got in the way
- Without a token there is no way to smoke-test the extension load or authentication locally, so the first real run has to be done by the operator against a throwaway database. The token variable name convention (lowercase) is easy to get wrong without checking docs.
