All checks were successful
CI / skinny-install (aco) (push) Successful in 50s
CI / skinny-install (api) (push) Successful in 31s
CI / lint-test (push) Successful in 1m25s
CI / skinny-install (bcda) (push) Successful in 25s
CI / skinny-install (bib) (push) Successful in 35s
CI / skinny-install (bls) (push) Successful in 24s
CI / skinny-install (ccw) (push) Successful in 25s
CI / skinny-install (cli) (push) Successful in 26s
CI / skinny-install (cms) (push) Successful in 33s
CI / skinny-install (conf) (push) Successful in 28s
CI / skinny-install (perf) (push) Successful in 28s
CI / skinny-install (pfs) (push) Successful in 29s
CI / skinny-install (rex) (push) Successful in 27s
Deploy / build-scan-report (push) Successful in 3m37s
The previous fix skipped on sqlite_scanner failure, dropping coverage below 99%. Instead, create a real DuckDB file and monkeypatch the path resolver — no network, no skip, no coverage loss. Refs #231