tidy

To clean up dead code and stale files without behavior changes, use a repository housekeeping approach that archives obsolete artifacts, corrects inaccurate documentation, and removes verified dead code while preserving authoritative build and runtime assets.

Repository housekeeping verifies unreferenced code before deletion by using grep-based reference checks to ensure files are not actively used, while deliberately avoiding dynamic plugin entrypoints and runtime registrations to prevent accidental removal.

Documentation updates and dead code cleanup can be scoped to specific directories such as docs, scripts, or code paths, allowing targeted housekeeping that refreshes file references and module maps without affecting the entire project.

The best way to ensure repository cleanup does not break tests is to run consistency checks using pytest and ruff after archiving files and removing dead code, verifying that project behavior remains completely unchanged.

Git archiving during codebase tidying works by moving one-time scripts, superseded drafts, and temporary scratch files into an archive directory only after confirming they are not referenced by active code, bundling all changes into a single non-pushed commit.

When tidying a codebase, a key limitation is that unused imports and unreferenced modules are removed while dynamic plugin entrypoints and runtime registrations are deliberately avoided, meaning dynamically loaded code is preserved even if it appears statically unreferenced.