storage status

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

Arguments and rejection

Use topaz storage status with no positional operands or options. Reject paths, compiler and language selectors, output format selectors, unknown flags and all extra arguments before inspecting storage.

Select the managed build root from TOPAZ_STORAGE_DIR followed by builds, otherwise XDG_RUNTIME_DIR followed by topaz/builds, otherwise LOCALAPPDATA followed by Topaz/builds on Windows, otherwise the platform temporary directory followed by topaz-storage/builds.

Output

Write a human report to standard output with each owned workspace path, byte usage, creation time and liveness classification in path order. Include the total byte usage. A missing managed root reports zero owned workspaces and succeeds.

Recognize ownership only from a valid .topaz-workspace.json marker using topaz.storage.workspace.v1, an integer process identifier and integer creation epoch seconds.

Classify a confirmed live owner as active regardless of workspace age. Classify an uncertain liveness result as retained. Only a confirmed inactive owner can be called safe to clean.

Write inspection failures to standard error. There is no JSON report mode and --format json is rejected.

Exit status

Exit 0 after a complete report, including an empty report. Exit 1 for invalid arguments or failure to inspect the selected managed root or an owned workspace.

Unowned entries and active or uncertain owners are retained rather than treated as inspection failures.

Filesystem effects

Read only real child directories carrying valid ownership markers. Do not follow a workspace or marker symlink to claim ownership of another directory.

Measure regular file bytes without following nested symlinks. Do not create the managed root, change markers, remove workspaces or write package files.

Network access

Use local filesystem inspection and local process liveness only. Perform no registry or network access.

Reproducibility

The report depends on the managed root, filesystem bytes, process state and inspection time. Equal command arguments alone do not promise equal output.

For an unchanged storage snapshot and the same liveness observations, path order and reported byte counts are deterministic.

Packages and locks

Managed build workspaces are independent of the current Topaz package. Do not load or update its manifest or lock and do not inspect or remove its vendor directory.