v0.150.119

• Plan nix inside a container by two routes, now that chase asks for it: the host daemon's socket, as before, or a local-overlay store of the container's own over the host's, whose builds and fetches are the container's and so its network's to see -- spiked outside flong and working (single-user as your uid, sandbox off, the host adding paths harmless, the host collecting one an upper path uses not, so the launcher holds a GC root for each), with what flong would need: an overlay with a kept upper, allowed over /nix/store (e0d9a31)