Stop workflow status polls draining the shared AI bucket

[groupthinking]

Exempt GET/HEAD workflow run status polls from the AI rate limit so Studio runs don’t 429 and collateral /api/chat calls stay safe.

[linear-code]

GRV-412

[github-actions]

👋 Thanks for opening this issue! It has been automatically labeled for triage.

[groupthinking]

Duplicate of #1517, which describes the same problem (Studio workflow status polls metered against the shared ai:<ip> rate-limit bucket, causing 429s and collateral throttling of /api/chat etc.). #1517 was closed as completed by #1518, merged just prior to this issue being opened. Closing as duplicate — if the fix in #1518 doesn't fully resolve this, please reopen with details on what's still broken.

---

Generated by Claude Code

[groupthinking]

Duplicate of #1517 — same problem (workflow status polls metered against the shared AI rate-limit bucket, causing 429s and collateral /api/chat failures). #1517 was closed as completed via #1518 nine seconds before this issue was opened. Closing as duplicate; please reopen if the fix in #1518 doesn't actually cover this case.

---

Generated by Claude Code

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Studio workflow status polls are metered on the AI budget and drain the shared ai:<ip> bucket #1517

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!