Guru重新激活任务

---
name: guru-reactivate-task
description: Reactivate one normally finished archived task while preserving its identity and routing the fresh work.
---

# Guru Reactivate Task

Reactivate owns one normally finished archived TaskLifecycleKey, never Finish
recovery or implementation activation. The AI reviews the fresh archive,
source relation, target base and shared checkout acquisition disposition. Entry
requires the archived generation's sealed Finish result, or the exact completed
manual Cleanup receipt after Finish returned `manual_cleanup_required`, and no
unfinished visible Finish transaction, not merely `status=completed`. A reviewed
SourceCorrectionReadyDTO is applied to the archived task with a private
recoverable receipt before routing to the source owner; it never advances the
generation. A ready correction accompanying acquisition is also applied in
the Reactivate transaction and bound to its recovery receipt, including when
the selected checkout predates the separate archive correction. Confirm source correction or acquisition side effects in the
current dialogue.
Archives with retired personnel fields are never Reactivate candidates. They
may be located only by an exact TaskId or strictly matched Issue clue to return
the `unsupported_legacy_task` read-only diagnostic; no generation, source
correction, Finish residue, or summary index can restore them. Only an archive
that already satisfies the current task schema and current Finish/Cleanup
contract may enter Reactivate.

The executor keeps TaskId, moves the archived artifact into the active locator,
increments the generation and enters planning. It composes the shared checkout,
branch binding and common-dir resource ledger; it never creates task/workspace
mappings or turns historical Finish/Cleanup results into new authority. A
resolved old-generation binding may be released for branch reuse, but any
unresolved prior local resource responsibility blocks that reuse. A
session needing repair routes to Bind; session binding failure never rolls back
an established incarnation.

The package-local transaction identifies the exact acquisition and branch
successor without a persisted checkout path. Same-transaction recovery reads
live Git, task and ledger facts without repeating mutations. Partial or stale
states block; no direct requirements, implementation or evidence-refresh route
is part of this package. The active #434 workflow router consumes its typed
result without transferring Reactivate's package-local recovery ownership.