legacy-retirement-clean-history

name	legacy-retirement-clean-history
description	Identify and remove obsolete legacy, fallback, staging, compatibility, duplicate, generated, and reference code before creating clean initial commits or new project history. Use when a repo is being reset, consolidated, or prepared for a cleaner public history.

Legacy Retirement Clean History

Purpose

Create a clean codebase that starts from the current intended architecture, not from the migration path that produced it.

Retirement Workflow

1. Define the supported present.

   • Current default binaries.
   • Current package entrypoints.
   • Current public contracts.
   • Current supported platforms/backends.
   • Current test and smoke commands.

2. Search for transition language.

   • legacy, fallback, old, thin, new, staging, phase, temporary, for reference, compat, deprecated.
   • Treat matches as leads, not proof.

3. Classify each path.

   • Keep: still default, tested, documented as supported, or unique capability.
   • Rename: concept is current but name reveals migration history.
   • Delete: duplicate implementation, unused reference copy, old fallback, staging package, dead test harness, old generated/native extension.
   • Defer: unclear ownership or untested deletion risk.

4. Remove in dependency order.

   • Remove docs and scripts that advertise dead paths.