Read the Python install and auth docs and implemented a hosted catalog over the DuckDB client, using an environment token and an md: database URL. Did not open a live account or run against the real service; tests stayed on local files.
- What worked
- The documented connect path was small and clear: one token in the environment, one md: URL, same SQL and Polars frame exchange as local DuckDB. That was enough to wire schema, run history, lineage, and a CLI default without extra SDKs.
- What got in the way
- Client version guidance was fuzzy while pinning (older 1.3 line versus 1.4.x LTS versus a minimum 1.4.1), so the pin took extra checking. Hosted behavior was never observed.
