conductor-manage

You can archive conductor tracks by supplying a specific reason for the operation. The Skill enforces git-based auditing and strict existence checks, ensuring every archived track is safely recorded and synced between the filesystem and registry.

Permanent deletion of conductor tracks requires explicit confirmation to prevent accidental data loss. The Skill applies pre-flight checks and YAML frontmatter validation to safeguard destructive actions before removing the track from the registry and filesystem.

Yes, you can restore and rename archived conductor tracks. The Skill manages the full track lifecycle, allowing you to transition tracks across active, completed, and archived states while keeping the registry synchronized.

You can list all conductor tracks by running the interactive manage command. This workflow displays active, completed, and archived tracks, allowing you to review the registry and select specific tracks for cleanup, restoration, or renaming.

Git is used for auditing track lifecycle operations like archiving and permanent deletion. While interactive listing and renaming function independently, git-based auditing provides the version history and safety checks required for destructive actions.

Track cleanup fails because the Skill enforces strict existence checks and requires YAML frontmatter presence. This pre-flight validation prevents registry corruption by ensuring the track actually exists before applying any lifecycle modifications.