I went to do some testing in a sandbox system (as the compilation strategy is unclear, missing builds for some of the artifacts).

I was able to initially construct an archive of the linux tree (that failed in decompression), but subsequently went to rebuild it and the tool is repeatedly producing this output even in an otherwise cleaned up environment:

    Runtime error 203 at $0000000100009B72
    $0000000100009B72
    $00000001000225B6
    $0000000100023153
    $000000010002319A

    Runtime error 203 at $0000000100009B72
    $0000000100009B72
    $00000001000225B6
    $0000000100023153
    $000000010002319A

    Runtime error 203 at $0000000100009B72
    $0000000100009B72
    $00000001000225B6
    $0000000100023153
    $000000010002319A

    Runtime error 203 at $0000000100009B72
    $0000000100009B72
    $00000001000225B6
    $0000000100023153
    $000000010002319A

    Runtime error 203 at $0000000100009B72
    $0000000100009B72
    $00000001000225B6
    $0000000100023153
    $000000010002319A

The first output did work, sadly I deleted it. It was over 400mb, so approximately double the size of a zip or a tar.zst of the same files.

zstd natively compresses a tar of this set to 209mb in 800ms in multi-threaded mode, or 3.5s in single threaded mode.

I suspect that sqlite is being held incorrectly (access from multiple threads, with multi-threading disabled), and the vfs lock forwarding is broken on Windows.