t248: Fix deploying->deployed transition stuck state

[marcusquinn]

Summary

Fixes the deploying->deployed transition stuck state issue where tasks would remain in 'deploying' status for 10-13 minutes before auto-recovery.

Changes

1. Reduced Phase 4d timeout from 600s (10min) to 120s (2min) for faster recovery
2. Added retry logic with exponential backoff (3 attempts: 0s, 1s, 3s) to both:
   • Initial deploying->deployed transition after merge (Step 4)
   • Auto-recovery transition in Phase 4b
3. Added better error logging to capture transition failure reasons
4. Tasks now recover within 2-4 minutes instead of 10-13 minutes

Root Cause

• cmd_transition failures were logged with || log_warn but not retried
• Silent failures left tasks stuck until Phase 4d timeout (10min)
• DB write errors or process interruptions during transition caused the issue

Evidence from This Session

• t241: 13min delay (19:18:35 -> 19:31:33)
• t240: 2.5min delay (19:31:44 -> 19:34:09)
• t242: 1.5min delay (19:32:37 -> 19:34:09)

Testing

• Syntax validation: bash -n passed
• The fix adds retry logic that will automatically recover from transient failures
• Phase 4d now triggers after 2 minutes instead of 10 minutes
• Error messages are now captured and logged for debugging

Files Modified

• .agents/scripts/supervisor-helper.sh (lines 8385-8420, 8404-8465, 9051-9057)

Closes #248

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Rate limit exceeded

@marcusquinn has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 27 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/t248

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

🔍 Code Quality Report

�[0;35m[MONITOR]�[0m Code Review Monitoring Report

�[0;34m[INFO]�[0m Latest Quality Status:
SonarCloud: 0 bugs, 0 vulnerabilities, 46 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 10 23:15:27 UTC 2026: Code review monitoring started
Tue Feb 10 23:15:28 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 46

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 46
• VULNERABILITIES: 0

Generated on: Tue Feb 10 23:15:30 UTC 2026

---

Generated by AI DevOps Framework Code Review Monitoring

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud