feat: implement issue #328 — { "message": "API rate limit exceeded for user ID 36422719. If you reach out to GitHub Support for help, please include the request ID 0C21:200094:31C7923:AFBA116:6A5A3A01 and timestamp 2026-07-17 14:19:45 UTC. For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https:\/\/docs.github.com\/en\/site-policy\/github-terms\/github-terms-of-service)", "documentation_url": "https://docs.github.com/en/rest/using-the-rest-api/getting-started-with-the-rest-api#rate-limiting", "status": "403" } Unknown

[don-petry]

Closes #328

Implemented by dev-lead agent. Please review.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Review limit reached

@don-petry, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 5 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8e723efe-623b-4e9e-8e46-f8ee3584b61d

📥 Commits

Reviewing files that changed from the base of the PR and between 8e2a986 and b5d15af.

📒 Files selected for processing (1)

• .github/workflows/dev-lead.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dev-lead/issue-328-20260717-1419

---

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.}

[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

[don-petry]

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

[Copilot]

Pull request overview

Updates the repository’s dev-lead workflow caller stub to comply with issue #328 by passing the correct agent_ref channel and aligning the reusable workflow ref to the same channel, ensuring dev-lead checks out its scripts/prompts from the intended channel tag.

Changes:

• Switch reusable workflow reference from @dev-lead/v1-stable to @dev-lead/stable.
• Update with: agent_ref from dev-lead/v1-stable to dev-lead/stable.

[donpetry-bot]

Review — fix requested (cycle 1/3)

The automated review identified the following issues. Please address each one:

Findings to fix

Automated review — NEEDS HUMAN REVIEW

Risk: LOW
Reviewed commit: b5d15af6ea36f512f1e62119cfb764d2c80a75e4
Review mode: triage-approved (single reviewer)

Summary

Two-line change to .github/workflows/dev-lead.yml switching the reusable-workflow ref and agent_ref from dev-lead/v1-stable to dev-lead/stable. Verified byte-for-byte against the canonical template at petry-projects/.github standards/workflows/dev-lead.yml (only remaining difference is a pre-existing NOSONAR suffix on 'secrets: inherit' not touched by this PR), and confirmed the dev-lead/stable tag exists in .github-private (6d36231). The change itself is correct and mechanical. However, the PR title and commit message are corrupted with an embedded GitHub API rate-limit 403 error JSON, which would land in main's history on squash merge — blocking on that cosmetic-but-real defect.

Linked issue analysis

Issue #328 (compliance-audit: dev-lead-stub-agent-ref) requires the caller stub to pass agent_ref: dev-lead/ where channel is stable, next, or ring. The prior value v1-stable is not a valid channel. This PR sets both the 'uses:' ref and agent_ref to dev-lead/stable, matching the standard's remediation (re-sync from the canonical template). The issue is substantively addressed.

Findings

1. [blocking, trivial fix] PR title and head-commit message contain a raw GitHub API rate-limit error JSON ("API rate limit exceeded for user ID 36422719...") instead of a real description — the authoring agent hit a 403 while composing them. A squash merge would write this garbage into main's commit history. Fix: retitle the PR (e.g. "fix(ci): re-sync dev-lead.yml stub to dev-lead/stable channel (Compliance: dev-lead-stub-agent-ref #328)") and ensure the merge commit message is clean.
2. [info] Workflow change verified identical to the canonical template; dev-lead/stable tag confirmed to exist in petry-projects/.github-private.
3. [info] run_secret_scanning MCP tool not available in this environment; gitleaks CI check passed and the diff contains no secret-like content.

CI status

All checks green: CodeQL (actions) ✓, SonarCloud quality gate ✓ (0 new issues, 0 hotspots), gitleaks secret scan ✓, AgentShield ✓, CI ecosystem detection ✓; remaining checks skipped (not applicable). Mergeable; merge state BLOCKED only on required review.

---

Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

Additional tasks

1. Resolve all unresolved review thread comments from other reviewers
2. Ensure all CI checks pass after your changes
3. Rebase on the target branch if behind
4. Do NOT modify files unrelated to the findings above

The review cascade will automatically re-review after new commits are pushed.

[don-petry]

Closing as part of the 50-PR cap drain. The dev-lead fix-loop repairs #1340 (self-cancellation), #1290 (comment-inertness) and #806 (thread-resolution) have all landed, so this deadlocked PR can be regenerated cleanly through the repaired loop. The driving issue stays open and its dev-lead label is re-fired — no work is lost.