The zig build test step rebuilds the executable with bundle-sqlite defaulting to false, which causes it to attempt linking against a system sqlite3 library. On ubuntu-latest this may work if libsqlite3-dev is installed, but it is not guaranteed to be available. The earlier Build step uses -Dbundle-sqlite=true, but that compiled binary at zig-out/bin/sql-pipe will be overwritten when zig build test triggers a rebuild without the flag. The integration test step should also pass -Dbundle-sqlite=true to ensure the binary is built consistently and the tests use the same compilation configuration.

The ~/.cache/zig path is Linux-specific. On macOS, Zig stores its cache in ~/Library/Caches/zig, not ~/.cache/zig. As a result, the cache step will silently miss the Zig cache directory on macOS runners, and the macOS build cache will never be saved or restored. The path list should include ~/Library/Caches/zig for macOS coverage.

mlugg/setup-zig@v2 already includes built-in caching via actions/cache internally (it caches both the Zig toolchain and the global Zig cache directory). Adding a separate "Cache Zig" step that targets the same directories (~/.cache/zig, ~/AppData/Local/zig) will result in two cache operations targeting the same paths. This can cause redundant cache saves, potentially inflating cache storage usage and slowing down the workflow. Consider either relying on mlugg/setup-zig@v2's built-in caching alone, or verifying whether its caching covers ~/.cache/zig/~/Library/Caches/zig before adding a manual step.