Manage Conductor Track Lifecycle

Track Manager manages the complete lifecycle of a Conductor track - archiving, restoring, deleting, renaming, and cleaning up orphaned artifacts - across active, completed, and archived states.

Use it for archiving, restoring, renaming, or deleting Conductor tracks, listing track status, or cleaning up orphaned artifacts. It is not suited to repositories where Conductor isn't initialized, situations lacking permission to modify track metadata or files, or tasks unrelated to Conductor track management.

Before proceeding it verifies the conductor/ directory structure and required files are present, determines the operation mode from arguments or interactive prompts, and for destructive actions (delete, cleanup) requires explicit confirmation before applying them. Every operation updates tracks.md and the track metadata consistently rather than leaving them out of sync. Detailed modes, prompts, and workflows are documented in a companion resources/implementation-playbook.md.

Safety rules are explicit: back up track data before any delete operation, and never remove archived tracks without explicit approval.

Developers managing Conductor tracks who need reliable lifecycle operations - archive, restore, rename, delete, cleanup - with confirmation gates on destructive actions and consistent metadata updates.