fix: sync homebrew formula version and enable subtask GitHub Issues

[marcusquinn]

Summary

• Fix homebrew formula version drift that was failing CI on all open PRs (v2.107.0 → v2.108.0)
• Enable GitHub Issue creation for subtasks (t199.1-t199.11 etc.) in issue-sync-helper.sh
• Prevent future homebrew drift by adding homebrew/aidevops.rb to version-manager.sh commit step

Root Causes

1. Homebrew Version Drift (blocking all PRs)

version-manager.sh commit_version_changes() staged all version files except homebrew/aidevops.rb. The update_version_in_files() function correctly updated the formula, but the commit step never staged it. Every release left the formula one version behind on origin/main, causing the Version Consistency Check to fail on every PR.

2. Subtasks Not Getting GitHub Issues

issue-sync-helper.sh cmd_push() explicitly skipped indented subtask lines (^- \[ only matches unindented). All 11 subtasks of t199 (t199.1-t199.11) had no GitHub Issues. The same ^- pattern was used across cmd_push, cmd_pull, cmd_close, cmd_enrich, cmd_status, cmd_reconcile, add_gh_ref_to_todo, and fix_gh_ref_in_todo.

Changes

File	Change
version-manager.sh	Add homebrew/aidevops.rb to git add in commit_version_changes()
homebrew/aidevops.rb	Update URL from v2.107.0 to v2.108.0
issue-sync-helper.sh	Change all ^- grep/sed patterns to ^\s*- across 8 functions

Verification

• ShellCheck: zero new violations
• Syntax check: both scripts pass bash -n
• The homebrew fix will make Version Consistency Check pass, unblocking PRs fix: use actual CPU idle% for adaptive throttling on macOS #835, fix: resolve clean_exit_no_signal false retry loop (t198) #834, feat(content): enhance research.md with 7 advanced research frameworks (t199.1) #842, feat(content): rewrite content.md as multi-media multi-channel orchestrator (t199.10) #840, feat: add content/story.md - narrative design, hooks, angles, frameworks (t199.2) #845

[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 17 minutes and 2 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 bugfix/version-consistency-fix

---

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

�[0;34m[INFO]�[0m Recent monitoring activity:
Tue Feb 10 01:31:39 UTC 2026: Code review monitoring started
Tue Feb 10 01:31:40 UTC 2026: SonarCloud - Bugs: 0, Vulnerabilities: 0, Code Smells: 61

📈 Current Quality Metrics

• BUGS: 0
• CODE SMELLS: 61
• VULNERABILITIES: 0

Generated on: Tue Feb 10 01:31:42 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