Give backlog-burndown's Resume Path a Disposition for a Stopped Group's Standalone Clone #3794

.agents/skills/backlog-burndown/SKILL.md, "Raising a Blocked Question" ("Resuming retires that worktree first, then dispatches a fresh worker") and "Away Mode" "Parking Instead of Asking".

Defect

The resume path retires the stopped group's tree before dispatching a fresh worker on the same branch. It reasons that "Git refuses to attach a branch already checked out somewhere". That holds for a linked worktree of the base clone. It does not hold for a standalone clone, the fallback repo-worktree allows, since the base clone knows nothing about it. The away-mode park retires the tree with git worktree remove <exact-path>, which errors on a clone path, and no outcome for that error is described.

Failure

Constructed case: a worker on feature/example works in a standalone clone, leaves it dirty, and the group stops. The maintainer answers "continue". The resume tries to retire the tree. git worktree remove fails on the clone path, or is skipped, and a fresh worker attaches feature/example from the remote while the clone still holds the uncommitted edits. Two checkouts then hold one branch, the state retire-then-dispatch exists to prevent.

Done When

The resume and park paths say what happens to a stopped group whose checkout is a standalone clone, before a fresh worker takes its branch.

Found by the local strict review of feature/burn-3772.