loa store prune

loa store prune

Remove native store content unused by registered project lockfiles

Removes globally cached native hashes that are not referenced by the current lockfiles of registered projects. Native pulls register the project root; clone, hardlink, and copy materializations are all tracked through project lockfiles rather than inode counts.

Deleted projects no longer retain content. If an existing registered project has a missing or malformed lockfile, pruning fails rather than guessing which bytes are unused. It leaves project-local caches and live files untouched.

Switching branches can make older asset versions useful again. If their global content was pruned, a later loa pull downloads it again. Removing a binding does not itself prune the store.

Usage

loa store prune

Examples

loa store prune