Ecosystem review / Disk Space / Git Worktrees
Disk Space / Git Worktrees: review and next steps
Disk safety and worktree lifecycle are delivery prerequisites. Reclaiming capacity is useful only when unique work, active owners and required recovery evidence remain intact.
What the evidence supports
The supplied review reports approximately 9.69 GB reclaimed on 2 November. The retained lifecycle acceptance matrix still requires distinct R01–R14 evidence and estate coverage. This review did not measure present disk, inode or quota headroom, so the historical cleanup figure is not current capacity.
Reevaluation: Keep physical removal, reclaimed bytes, native lifecycle receipts and full acceptance separate. Never treat a clean tree or expired session as sufficient deletion authority.
The next useful outcome
Every named target stays above its agreed reserve while owner-aware lifecycle operations preserve unique work and required evidence, with native receipts and post-action capacity measurements.
Separate workstream plan
DS-01 · Proposed / reuse existing work
Measure the current estate
Inventory free bytes, inodes, quotas, clones, worktrees, caches and evidence on every named host/account.
Acceptance: Dated observations distinguish shared filesystems from account quota headroom.
DS-02 · Proposed / reuse existing work
Verify existing scheduled cleanup
Check current schedules, successful native receipts and actual before/after capacity.
Acceptance: A successful timer or preview is never reported as reclaimed space without measurement.
DS-03 · Proposed / reuse existing work
Triage stale work by owner
Classify stale candidates and route each disposition through its owning canonical repository.
Acceptance: Unique, dirty, unmerged and active work retains a verified recovery carrier and proper authority.
DS-04 · Proposed / reuse existing work
Complete the lifecycle matrix
Qualify the outstanding R01–R14 acceptance rows through their existing owners.
Acceptance: Every accepted row binds the installed executable, observation and retained evidence.
DS-05 · Proposed / reuse existing work
Bound recreatable growth
Measure and address demonstrated worktree, dependency, cache and fleet-sync growth sources.
Acceptance: The agreed reserve remains protected without deleting required recovery material.
DS-06 · Proposed / reuse existing work
Bind artifacts to tasks
Connect worktrees and evidence to owner, task, branch, acceptance and next action.
Acceptance: No retained artifact is silently ownerless and no cleanup relies on age alone.
Dependencies and sequence
Current ownership, Storage health, task bindings and the existing admitted cleanup/lifecycle route.
Start with the first eligible unfinished task above, after checking its existing owner and admission. Later tasks depend on the preceding proof where applicable; this ordering does not override a current implementation plan.
Deferred work
Bulk pruning, deleting dirty or unmerged work, and inventing another cleanup controller.
Evidence and updates
This article combines the supplied 8 November ecosystem review with selected current source and retained planning records. It is an editorial snapshot, not a live service census. Detailed revision bindings and task authority remain in Workspace Docs and private execution records. Publish subsequent accepted changes as linked engineering or release notes rather than silently rewriting this baseline.
Shared roadmap · All Disk Space / Git Worktrees articles · Explore all areas
