fix(pi): clear retry status when streaming resumes

[jonathanlab]

Problem

THIS UGLY THING

Changes

• Clear Pi retry status as soon as a successful retry streams text or reasoning.
• Complete an earlier retry before showing a later retry.
• Replace raw retry errors with concise rate-limit and retry messages.

Validation

• pnpm --filter @posthog/agent exec vitest run src/pi/conversation/translatePiConversation.test.ts
• pnpm --filter @posthog/ui exec vitest run src/features/sessions/components/session-update/StatusNotificationView.test.ts
• pnpm --filter @posthog/agent exec tsc --noEmit
• pnpm --filter @posthog/ui exec tsc --noEmit
• Pre-commit pnpm typecheck

Automatic notifications

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

[trunk-io]

😎 Merged successfully - details.

[github-actions]

React Doctor found 1 issue in 1 file · 1 warning.

1 warning

src/features/sessions/components/session-update/StatusNotificationView.tsx

• ⚠️ src/features/sessions/components/session-update/StatusNotificationView.tsx:38 Non-component export in component file only-export-components

_{Reviewed by React Doctor for commit de9badb.}

[greptile-apps]

Prompt To Fix All With AI

### Issue 1
packages/ui/src/features/sessions/components/session-update/StatusNotificationView.tsx:49-51
**Rate-limit variants go unrecognized**

When Pi reports a retry as `Rate limited` or `rate_limit`, this expression does not classify it as a rate limit, causing the UI to show only the generic retry countdown instead of the intended rate-limit explanation.

```suggestion
  const rateLimited = /\b429\b|rate[ _]limit(?:ed)?|too many requests/i.test(
    message ?? "",
  );
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "fix(pi): clear retry status when streami..." | Re-trigger Greptile}