t1189: Fix AI actions pipeline empty-response handling to prevent rc=1 cascade

[marcusquinn]

Summary

• Treat empty/non-JSON AI model responses as an empty action plan [] rather than a pipeline error
• Both ai-reason.sh and ai-actions.sh now return rc=0 with executed=0 when the AI response is unparseable
• A log_warn is still emitted so the issue remains visible in logs without causing false-positive pipeline errors

Root Cause

When the AI model returns plain text or an empty response (observed 6+ times on 2026-02-18 between 15:53-19:15), extract_action_plan returns empty, causing run_ai_reasoning to return rc=1. This propagated through run_ai_actions_pipeline as a pipeline error, generating noise in self-reflection analysis.

Changes

• ai-reason.sh: Unparseable AI response now outputs [] + return 0 (was {"error":"no_action_plan",...} + return 1)
• ai-actions.sh: Non-array plan_type (including empty string from failed jq parse) now outputs {"executed":0,...} + return 0 (was {"error":"invalid_plan_type",...} + return 1)
• tests/test-ai-supervisor-e2e.sh: Added Test 2.3b verifying pipeline returns rc=0 with executed=0 when AI returns non-JSON text

Verification

bash tests/test-ai-supervisor-e2e.sh  # 36 passed, 0 failed
bash tests/test-ai-actions.sh         # 16/17 passed (pre-existing unrelated failure)
shellcheck -x -S warning ai-reason.sh ai-actions.sh  # 0 violations

Ref #1798

[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 22 minutes and 19 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/t1189

---

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, 27 code smells

�[0;34m[INFO]�[0m Recent monitoring activity:
Wed Feb 18 22:13:02 UTC 2026: Code review monitoring started
Wed Feb 18 22:13:02 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 27

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 27
• VULNERABILITIES: 0

Generated on: Wed Feb 18 22:13:05 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