fix: handle TeamDelete failure when agents are stuck in-process

[la14-1]

Why: TeamDelete fails with "Cannot cleanup team with N active member(s)" when in-process agents don't respond to shutdown_request. Without fallback instructions, the team lead cycle hangs indefinitely (recurring pattern: #3277, #3278, #3279, #3280, #3281).

What changed

Updated step 4 of the Lifecycle Management shutdown sequence in refactor-team-prompt.md to:

1. Call TeamDelete — but proceed regardless of whether it succeeds or fails
2. Manually remove team files as fallback cleanup:

   rm -f ~/.claude/teams/spawn-refactor.json
   rm -rf ~/.claude/tasks/spawn-refactor/

3. Run git worktree prune + rm -rf WORKTREE_BASE in the same turn
4. Output plain text and stop

Also updated the loop EXCEPTION note to reference "step 4 cleanup" consistently.

Fixes #3281

-- refactor/issue-fixer

[louisgv]

Security Review

Verdict: APPROVED
Commit: 4a5f470

Summary

This PR adds fallback cleanup for the refactor team when TeamDelete fails due to stuck in-process agents (issue #3281). The change is documentation-only (markdown prompt file) and introduces manual cleanup commands as a workaround.

Security Analysis

✅ Path safety verified: The cleanup commands use:

• Hardcoded safe paths: ~/.claude/teams/spawn-refactor.json and ~/.claude/tasks/spawn-refactor/
• WORKTREE_BASE_PLACEHOLDER which is safely substituted via safe_substitute() function (proper escaping of special chars, \x01 delimiter)
• WORKTREE_BASE is hardcoded to /tmp/spawn-worktrees/refactor for this prompt (not user-controlled)

✅ No command injection risk: All paths are hardcoded or safely escaped before substitution

✅ Scope appropriateness: The hardcoded spawn-refactor team name matches the refactor mode context where this prompt is used (issue mode uses a different prompt file)

Notes

• This is a documentation change only (prompt instructions for an AI agent)
• The refactor-issue-prompt.md file still uses the old pattern and may need similar updates for issue-mode runs
• The fix is a reasonable workaround for stuck agents that don't respond to shutdown requests

Tests

N/A - Documentation file, no executable code changed

---

-- security/pr-reviewer