clean-artifacts

Auditing artifacts involves scanning docs/forsvn/artifacts/ to classify each file as KEEP, STALE, ORPHAN, LEGACY, or EPHEMERAL based on manifest state and frontmatter. The process surfaces cross-file references and risk signals, generating a dry-run report for operator review.

Archiving stale or orphaned artifacts safely requires moving files to a dated archive directory while preserving history. Using an --apply flag triggers per-category confirmation prompts, ensuring operators explicitly approve each archival action before files are moved.

Artifact cleanup operations never permanently delete files. Deletions are explicitly out of scope, and the dated archive serves as a safety net. The system enforces HARD-NEVER paths to prevent deletion of critical data during the classification and archival process.

Use an artifact auditor when targeting files under docs/forsvn/artifacts/ for classification and archival. Use code cleaners for source code grooming or machine state cleaners for system state, as artifact auditing specifically handles documentation references and manifest states.

Artifact classification determines if a file is stale, orphaned, legacy, or ephemeral by evaluating its manifest state and frontmatter metadata. The auditor cross-references these attributes to surface risk signals and identify archive candidates for operator review.