bug: pr-maintainer agent stuck (in-process), blocking TeamDelete (refactor cycle 2026-04-11)

[la14-1]

Summary

During refactor cycle starting ~2026-04-11 18:xx UTC, the pr-maintainer agent became stuck in-process and did not respond to 5+ shutdown_request messages, blocking TeamDelete.

Symptoms

• TeamDelete returns: Cannot cleanup team with 1 active member(s): pr-maintainer
• 5 shutdown_request messages sent, zero responses received
• Agent remained in-process state throughout the cycle

Related Issues

• bug: refactor team agents stuck (in-process), blocking TeamDelete (cycle 2026-04-11 07:27 UTC) #3263, bug: refactor team agents stuck (in-process), blocking TeamDelete (cycle 2026-04-11 ~17:29 UTC) #3262 — same pattern from earlier cycles
• fix: add max-retry force-proceed to prevent infinite shutdown loop #3265 — max-retry force-proceed fix (should have helped but didn't prevent this)

Impact

TeamDelete could not complete. Worktrees cleaned up manually. Work products (PR #3266) were successfully created before the stuck state.

Work Completed This Cycle

• PR fix: resolve 4 production TypeScript type errors #3266: fix: resolve 4 production TypeScript type errors (open, awaiting review)
• Community coordinator triaged open issues
• Style reviewer and code-health scans completed

[la14-1]

Triage

This is a recurrence of the stuck-agent pattern from #3263, #3262, #3259, #3249, #3244. The issue body notes that #3265 (max-retry force-proceed) "should have helped but didn't prevent this."

Root cause: Agents stuck mid-turn (in-process) cannot process shutdown_request messages. #3265 added a 3-round max-retry policy so the team lead can force-proceed after ~6 min of no response, but it appears the pr-maintainer was still blocking TeamDelete in this cycle.

Off-limits for refactor team: The orchestration logic lives in .claude/skills/setup-agent-team/ (refactor.sh, trigger-server.ts) which we cannot modify. Any fix to the shutdown/TeamDelete mechanism requires manual maintainer intervention.

Actionable items outside off-limits files: None identified — the stuck-agent problem is entirely in the team orchestration layer.

-- refactor/community-coordinator

[louisgv]

Security Triage

Category: bug (infrastructure)
Assessment: This issue relates to team orchestration and agent lifecycle management in .claude/skills/setup-agent-team/ — an off-limits directory that requires manual maintainer review. The agents are stuck/non-responsive during the refactor cycle, indicating a problem in the team infrastructure layer.

Recommendation: Escalate to maintainers for review of team orchestration. This is not suitable for automated fixes.

---

-- security/issue-checker