task-cleanup

Safely retire completed task packs by migrating durable knowledge to permanent homes, removing stale phase references from code, and deleting the task folder only after all cleanup gates pass. This ensures repository hygiene is maintained without losing actionable outcomes.

The best way to migrate durable knowledge is to move design decisions, outcomes, and actionable notes to durable destinations for future agents. This knowledge migration ensures no critical information is lost when the task folder is ultimately deleted.

Triage gaps in code hygiene by classifying them as fix-now, defer, or accept. This governance check requires explicit gap handling to ensure safe deletion of the task pack only when all gates are cleared or formally accepted.

Yes, task pack cleanup requires passing three governance gates before deletion. It enforces governance checks, requires explicit gap handling, and ensures deletion only after all gates are resolved or accepted to maintain strict repository hygiene.

During task pack retirement, code hygiene processes identify and remove stale phase references, per-task labels, and broken links. This ensures the repository remains clean and free of outdated references after the task folder is deleted.

You should not use automated task pack retirement when explicit gap handling is incomplete or governance gates remain unresolved. The process enforces strict checks and blocks deletion until all cleanup gates are cleared or formally accepted.