Manage Conductor Track Lifecycle

Provides /conductor:manage's full track-lifecycle operations, dispatched by argument or, when invoked with none, a numbered interactive menu (list, archive, restore, delete, rename, cleanup, or exit) opened with quick stats on active, completed, and archived track counts. List (collecting each active track's type and progress percentage from its metadata.json and plan.md, each completed track's duration, and each archived track's reason and date, then rendering them as separate Active/Completed/Archived tables with optional filtering to just one), archive (move a completed track to conductor/tracks/archive/, with a bulk multi-select variant), restore (bring an archived track back to active), rename (change a track's {shortname}{YYYYMMDD} ID, updating the directory, metadata.json's id and previous_ids fields, plan.md's header, and the tracks.md registry, with format and conflict validation), delete (permanently remove a track directory after a full warning screen naming type, status, location, file count, and related commit count, requiring the exact literal string DELETE rather than yes or y, with an extra in-progress warning showing current task and percent complete when the track status is in progress), and cleanup (scan for four issue types - orphaned directories not in tracks.md, registry orphans with no matching folder, incomplete tracks missing spec.md, plan.md, or metadata.json, and stale in-progress tracks untouched over 7 days - then fix them individually or all at once). Every mutating operation ends with a git commit for traceability, and the eight critical rules require verifying track existence first, requiring explicit YES or DELETE confirmation for destructive actions, halting on any error rather than continuing past failures, keeping tracks.md in sync with the file system, never modifying or deleting existing git history, extra caution on in-progress tracks, and always offering archive as an alternative to delete.

Use it when archiving, restoring, renaming, or deleting Conductor tracks, listing track status, or cleaning up orphaned track artifacts. Skip it when Conductor is not initialized in the repository, you lack permission to modify track metadata or files, or the task is unrelated to Conductor track management.

Input is a mode flag - --list, --archive, --restore, --delete, --rename, or --cleanup - with its track ID argument, or no argument for interactive menu selection; output is the file-system change (a moved, renamed, or removed track directory), the matching tracks.md and metadata.json updates, and a git commit recording the operation, plus a formatted before-you-proceed warning for anything destructive.

Operates directly on a Conductor repository's conductor/ directory structure - product.md, tracks.md, tracks/{id}/spec.md, plan.md, metadata.json, index.md, and tracks/_archive/ - and git for commits. Pre-flight checks verify this structure exists and suggest /conductor:setup if it doesn't.

Teams and agents managing a Conductor track registry who need safe, confirmable lifecycle operations - especially permanent deletion and ID renaming - rather than hand-editing tracks.md and moving directories manually.