Module cleanup

Structs§

CleanupOutcome: What one cleanup pass did, or would do under --dry-run. Garbage collection has to be reportable to be trustworthy: every list here is something that disappeared (or would).
FinalizedInstance
HookOutcome: One resource’s cleanup hook, and why it did or did not run.
LaneRev: A tracker lane rev on disk.
PrunedRev
PurgedCheckpoints: One instance’s discarded checkpoint history.
SnapshotRoots: Everything that keeps a lane rev alive, kept apart by where the claim came from so cleanup can explain retained disk instead of just retaining it.

ArchivedCheckpoints: Whether an operation that archives an instance also discards the checkpoints it leaves behind. Keeping them is the default: a checkpoint pins the lane revs its undo would need, and newgit never breaks an undo on its own initiative. Purging says the undo will never be wanted.
HookDetail

lane_names
lane_revs: Every rev directory present in every lane, including leftover staging directories.
may_tear_down: Whether per-branch teardown may run this resource’s cleanup hook at all. Ownership decides, not the presence of a command: a user-owned pnpm store with a cleanup command must still survive newgit remove.
orphan_workspaces: Workspace directories under workspace_root that no binding record claims. A workspace is a cache, so an unclaimed one is just garbage — but only the records can say which ones are claimed.