SASE disk cleanup

sase disk

Disk commands inspect SASE-created bytes by owner and delegate cleanup back to those owners. With no subcommand, sase disk defaults to sase disk list.

Moved to sase disk.

Moved to SASE disk cleanup.

Command behavior

Unowned Cargo-shaped strays are listed for human action and are never deleted by sase disk reap.

The sase disk list table shows each row's owner, section, size, coverage, horizon, and path. Managed-temp rows cover every registered root writers actually used, not only the effective one. Workspace checkouts get one row per project plus sub-rows for .git/objects, .pytest_cache (including sase-visual), sase/repos, .venv, and in-tree target/, sized before the generic stray walk so budget exhaustion can only clip that walk. Unowned rows are highlighted; a row whose coverage is partial or unresolved means the owner could not account for every byte. When coverage is partial or the filesystem is under pressure, an unattributed row reports filesystem used minus attributed bytes on the filesystem holding SASE_HOME. When rows share physical storage (for example workspaces that borrow primary Git objects), the size cell also shows the exclusively counted bytes, and the footer reports the physical total, the logical row total when it differs, the overall coverage status, and any partial-scan diagnostics.

sase disk reap runs, or previews, the owner passes in order: managed-temp reaping, proc runtime cleanup, ACE-run artifact retention (the same owner as sase artifact prune-runs), and workspace Git object compaction. It exits 1 when any owner step is blocked, fails, or cannot report a trustworthy result, and 0 otherwise. Because ACE-run deletion is currently preview-only, the artifact-run step reports blocked under --apply.

_[project]: A sase project is a named unit of work registered with SASE. _[workspace]: A sase workspace is a numbered clone of a project's primary repo, managed by the workspace store and tracked in that project's registry.json. _[agent]: A sase agent is an agent session or a single agent that does not belong to a session. _[prompt]: A prompt is the text SASE hands to a provider to start an agent turn. _[macro]: A macro is a reusable prompt triggered with #name in agent prompts. _[Patch]: A Patch is SASE's local unit of change. _[bead]: A bead is one tracked work item in SASE's git-native issue tracker. _[plan]: A plan is a persisted, approved artifact recording the intent behind agent work. _[TUI]: The TUI is SASE's terminal interface for running agents and reviewing results. _[epic]: An epic is an executable multi-phase plan run with sase bead work. _[gate]: A sase gate is a durable, command-backed request for one user decision, created when work must pause for the user. _[monitor]: A sase monitor is a monitor turn that runs one long command under a detached supervisor, so the command outlives the agent that started it. *[stitch]: A stitch is the lightweight ordered change record inside a Patch's STITCHES: section.