issue-triage

Fetch the compact assignment list from the inbox-lite endpoint, then pull heartbeat-context for each candidate issue. Classify each into one verdict (resume, wake-needed, reassign, unblock, escalate, or close) and record the single action taken per issue.

An in_progress issue with no comments or document updates in the last 24 hours and no monitor or queued continuation is considered stalled. Post one comment naming the blocker resolution or exact next action so the assignee wakes and resumes.

Skip triage when you are checked out on one specific issue named in the wake context, or when a thread already has an open request_confirmation or ask_user_questions. Re-triaging while waiting for a response only adds noise.

When all entries in blockedByIssueIds are done, set the issue status back so the assignee wakes automatically. If a blocker was cancelled, replace or remove it from blockedByIssueIds rather than leaving the stale reference.

Mentions cost budget each time they trigger an agent wake. Use direct reassignment or a plain status comment instead, which conveys the same information without spending agent execution budget.