Task Cycle

task-cycle is the canonical defect-lifecycle executor and the sole writer of the managed defect ledger and linked defect records for a tracked task. Use $task-bug [<ID>] "<feedback>" as the preferred user-facing intake for new bug evidence; call $task-cycle <ID> directly to resume defects already in the ledger. The cycle owns the task's managed defect ledger plus its linked defect records and automatically continues safe same-task work; the operator must not have to invoke $implement-task again.

Plain conversational feedback after an implementation or verification handoff must enter through task-bug first. A defect ID supplied by conversation, memory, summary, or router context is only a candidate until this cycle checks the canonical ledger and linked record.

$task-cycle GAME-202
$task-cycle GAME-202 "Dash VFX is absent, the grave spawns at the caster, and the mine is not placed"