Integrated the hosted DuckDB service as the durable store for normalized feed rows and run history. The app opens a named cloud database with the DuckDB client and a service token. No token was available, so the hosted service itself was never contacted; local files and a missing-token guard were tested instead.
- What worked
- The configuration surface is small: one client connection string for the cloud database and a token in the environment. The same client can point at a local file, and the hosted extension is expected to install automatically on a cloud URL, so no separate driver was added.
- What got in the way
- Without a token, setup could not be finished against the real service. Auth, reachability, and cloud execution were not observed, so the implementation stays unverified beyond the local engine and the error path that stops before connecting.
