fix(lifecycle): implement stuck detection using agent-stuck threshold

[sigvardt]

Problem

The agent-stuck reaction config supported a threshold field:

reactions:
  agent-stuck:
    threshold: "10m"
    action: notify
    priority: urgent

But determineStatus() never returned "stuck". There was no code path that consumed the threshold or transitioned sessions based on idle time. The SESSION_STATUS.STUCK constant existed, the reaction config schema accepted it, the event mapping was wired (session.stuck → agent-stuck), but the actual detection was missing.

Sessions would stay parked at pr_open or working indefinitely, even when the agent had been idle for hours. No webhook, no notification, no reaction.

Fix

1. Stuck detection in determineStatus()

After the existing activity state checks (waiting_input → needs_input, exited → killed), added:

if ((activityState.state === "idle" || activityState.state === "blocked") && activityState.timestamp) {
  // Look up agent-stuck threshold from project or global reaction config
  // If idle duration exceeds threshold, return "stuck"
}

This respects both project-level and global agent-stuck reaction configs, and uses parseDuration() (already in the file) to parse the threshold string.

2. Remove info-priority notification suppression

The previous code had a priority !== "info" guard that silently dropped all info-level transition notifications. This prevented legitimate info events (session spawned, PR opened, CI passed) from reaching configured notifiers. Removed the guard so all priorities route through notificationRouting, letting the config control delivery.

Testing

• All 398 core tests pass (including 24 lifecycle-manager tests)
• Verified end-to-end: a session idle for 2+ hours with threshold: "10m" immediately transitioned pr_open → stuck and fired the webhook notification

Depends on

This fix works independently, but reaches full effectiveness when combined with #375 (Codex session file matching fix), which ensures getActivityState() returns actual idle timestamps instead of null.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Autofix Details

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: Stuck threshold lookup skips global config when project overrides exist
  • isIdleBeyondThreshold now reads the merged per-session reaction via getReactionConfigForSession so a global threshold is preserved when project overrides omit it.

Or push these changes by commenting:

@cursor push bde1c87f0c

Preview (bde1c87f0c)

diff --git a/packages/core/src/lifecycle-manager.ts b/packages/core/src/lifecycle-manager.ts
--- a/packages/core/src/lifecycle-manager.ts
+++ b/packages/core/src/lifecycle-manager.ts
@@ -182,9 +182,7 @@
 
   /** Check if idle time exceeds the agent-stuck threshold. */
   function isIdleBeyondThreshold(session: Session, idleTimestamp: Date): boolean {
-    const stuckReaction =
-      config.projects[session.projectId]?.reactions?.["agent-stuck"] ??
-      config.reactions["agent-stuck"];
+    const stuckReaction = getReactionConfigForSession(session, "agent-stuck");
     const thresholdStr = (stuckReaction as Record<string, unknown> | undefined)?.threshold;
     if (typeof thresholdStr !== "string") return false;
     const stuckThresholdMs = parseDuration(thresholdStr);

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[harsh-batheja]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

[harsh-batheja]

All bot findings addressed; local lifecycle/core and opencode verifications pass.

[harsh-batheja]

All automated review findings are resolved and CI checks are green. Added reviewer requests for maintainer approval to clear branch protection.

[harsh-batheja]

Added additional collaborator review requests to satisfy branch protection approval requirements.