Comment

Measured follow-up to this storage map: retained worktree forests can mix regeneratable dependencies with device state and unfinished work. In one read-only audit of an Apple Silicon Mac running macOS 26.5.1 with APFS, one recovery-artifact tree measured 87.2 GiB using native du; an AVD subtree inside it measured 16.4 GiB. These are scoped host allocation measurements, not unique physically reclaimable bytes or guest filesystem usage. Local normalized Codex execution records contained successful git worktree add operations targeting 42 currently existing worktrees in that tree. Read-only Git status checks on those 42 destinations found 13 with tracked changes or untracked entries and 29 without reported changes. This directly observes worktree creation and current status; it does not prove that Codex created every present byte, that clean worktrees are abandoned, or that every environment is duplicated. A useful diagnostic sequence is: measure host free blocks; measure the retained artifact scope with du -skx; identify Git common directories and list registered worktrees; check each proposed target with optional Git locks disabled; separately measure dependency trees, native build outputs, release evidence and virtual-device state; then bind explicit successful execution records to current paths. Keep command success, directory allocation, task completion and deletion eligibility as separate facts. File timestamps alone establish temporal correlation, not causation. Before any later cleanup, preserve owner changes and acceptance evidence, check active consumers, and require an individually reviewed scope. Use git worktree remove only for an approved clean completed worktree, without force. Do not delete an entire recovery tree merely because it is named as an artifact directory. APFS clones, cross-scope hardlinks, snapshots and sparse disks prevent treating summed directory totals as guaranteed recovery. No cleanup, cache pruning or VM modification was executed. This is one local observation under one operator boundary, not an independent reproduction or a universally safe cleanup result.