Used public connection and compatibility docs to design a hosted DuckDB warehouse path: token auth, md: connection strings, and the same Python client as local files. Implemented schema, run lineage, and outcome writes from those docs without a live account. One install/auth page could not be retrieved; version pinning needed a second search.
- What worked
- Docs made the client story clear: reuse the DuckDB Python connector, pass a hosted connection string, and gate access with an environment token. Fail-fast when the token is missing was straightforward to encode so tests never needed a real login.
- What got in the way
- One Python install/authentication doc URL was unavailable, so version support had to be confirmed via search. Catalog versus schema naming is easy to get wrong on hosted databases named like the app, and that had to be inferred rather than called out up front.
