feat(loops): Surface billing pauses and gate manual runs

[charlesvien]

Problem

When the backend auto-pauses a loop (usage limit reached, or too many failed runs in a row), the app shows a bare "Paused" badge with no explanation. Manual "Run now" also skips the cloud usage preflight every other cloud run path uses, and a blocked fire surfaces as a raw Run not started: gate_blocked toast.

Companion backend PR records the pause reason on Loop.disabled_reason.

Changes

• "Run now" preflights assertCloudUsageAvailable() like the task composer, and a gate_blocked result opens the usage limit modal instead of a raw toast. Other blocked reasons get readable messages.
• Status badge now distinguishes "Paused: usage limit" and "Auto-paused" from a manual "Paused", and the detail view shows a banner explaining backend pauses, with a "Manage plan" CTA for the billing case.
• api-client: add the fire reasons the backend can already return (owner_inactive, owner_changed) and document the new disabled_reason values.

How did you test this?

Added parameterised unit tests for the new display helpers (loopDisplay.test.ts). Ran the loops feature suite (113 tests) and api-client suite (130 tests), plus typecheck on both packages. No manual app run.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

[trunk-io]

😎 This pull request was merged.

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit af9f944.}

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
packages/ui/src/features/loops/components/LoopDetailView.tsx:86
**Keep Run now single-flight**

The button remains enabled while the asynchronous usage preflight runs, so repeated clicks start concurrent preflights and subsequent run mutations. Track the entire handler as pending to avoid duplicate run attempts and repeated notifications.

_{Reviews (1): Last reviewed commit: "surface loop billing pauses and gate man..." | Re-trigger Greptile}

[github-actions]

The diff surfaces existing usage-limit gating (assertCloudUsageAvailable/useUsageLimitStore, already used by the task composer) into the loop run-now flow rather than adding new billing logic, the sole reviewer concern (non-single-flight Run now button) is already fixed in the current diff via the runNowPending guard/try-finally, and the author has STRONG familiarity with these exact files/lines plus added parameterized test coverage.

• Author wrote 100% of the modified lines and has 8 merged PRs in these paths (familiarity STRONG).
• 👍 on the PR from greptile-apps[bot].

Gate mechanics and policy version

Gate		Result
prerequisites	✓	all clear
deny-list	✓	no deny categories matched
size	✓	139L, 3F substantive, 235L/4F incl. docs/generated/snapshots — within ceiling
tier	✓	T1-agent / T1c-medium (235L, 4F, single-area, feat)
stamphog 2.0.0b3		.stamphog/policy.yml @ 3b560b4 · reviewed head 2a26171