This ended up being a regression in github.com/nix-community/cache which got reported and resolved in the time since yesterday when I first ran into it