storage clean

The invocation topaz storage clean main.tpz --language-version 5.21 is expected to exit with 1.

Arguments and rejection

Use topaz storage clean with no operands or options. Reject a path operand, root override, compiler or language selector, output format selector and every extra argument before any deletion.

Use the managed build root selected by the same environment precedence as storage status. An environment selected root does not grant authority over unmarked directories.

Output

Write a human line for each removed owned workspace. On successful completion, write the removed workspace count and reclaimed byte count. Process eligible paths in deterministic path order.

Retained active or uncertain workspaces do not count as removed or reclaimed. When no workspace is eligible, write a zero removal summary and succeed.

Write inspection or deletion failures to standard error. There is no JSON report mode and --format json is rejected. A reported deletion count is evidence of completed removals and does not imply rollback of an earlier removal.

Exit status

Exit 0 when every eligible removal completes, including when there are no eligible workspaces.

Exit 1 for invalid arguments, failure to inspect managed storage or a failed eligible deletion. Earlier completed removals remain completed on a later failure.

Filesystem effects

Require a real child directory with a valid regular .topaz-workspace.json marker using topaz.storage.workspace.v1. Skip unowned paths, invalid markers, symlinked workspaces and symlinked markers.

Remove a directory only after the owner is confirmed inactive. A live owner remains protected after 24 hours. Retain the directory when liveness is uncertain. Revalidate the marker and owner state immediately before deleting.

Delete only the selected owned subtree and do not follow nested symlinks outside it. A concurrent disappearance is harmless. Do not change files in retained workspaces or delete caller source, package output or arbitrary directories.

Network access

Perform no network access. Local process inspection does not authorize contacting a remote host.

Reproducibility

Cleanup is state dependent and changes the input state. A second run after a successful cleanup reports zero additional removals unless another eligible workspace appears.

With an identical managed storage snapshot and liveness observations, the same paths are eligible and processed in the same order. Creation time alone never makes a live owner eligible.

Packages and locks

Cleanup does not read or rewrite the current package manifest or lock and does not remove its vendored dependencies. Package locks and compiler workspace ownership markers are different records.

Do not run dependency resolution or materialization to decide which workspaces are owned.