feat(console): operations dashboard - overview, conversations, deliveries

[one-ea]

Summary

• Add /operations/overview — stat cards for messages, deliveries, conversations, AI drafts with color-coded health indicators (failed/permanent_failure highlighted in danger color when non-zero)
• Add /operations/conversations — paginated conversation list (50/page) with status filter (all/open/closed), sorted by last_message_at DESC, JOIN to contacts and telegram_topics
• Add /operations/deliveries — failed delivery queue with manual retry button (only failed status shows retry button; permanent_failure is view-only)
• Add POST /operations/deliveries/retry — resets next_retry_at to now, triggering worker retry on next scan
• Add ConversationService.listConversations with pagination
• Add DeliveryService.listFailedDeliveries and scheduleRetry methods
• Extend AiDraftService.stats to include sent and discarded counts
• Independent dashboard CSS namespace (ops- prefix) with header navigation

Problem

Ops had no web visibility into conversations, failed deliveries, or system metrics. Had to SQL query the database or scroll Telegram Topics. No way to manually trigger a delivery retry from the UI.

Verification

• npm run verify passed (check + 41 tests + audit 0 vulns)

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 20 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: ASSERTIVE

Plan: Pro

Run ID: df8c7fa6-a001-48b7-83fe-cafd2832a977

📥 Commits

Reviewing files that changed from the base of the PR and between b83df53 and 7c4831b.

📒 Files selected for processing (6)

• src/domain/ai-drafts.ts
• src/domain/conversations.ts
• src/domain/deliveries.ts
• src/runtime/main.ts
• src/runtime/web-console.ts
• test/core.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 260629-feat-operations-dashboard

---

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