March 11, 20261.0.113v1.0.113RSS

v1.0.113 — feat: Multi-Product Fleet Control Room Dashboard

Release v1.0.113: Multi-Product Fleet Control Room Dashboard

Date: 2026-03-11

What changed

  • New route /dashboard/fleet — Fleet Control Room Dashboard
  • 6 KPI stat cards (total/healthy/degraded/critical products, total revenue, features built, agent jobs, failures, spend) with 7/14/30/60/90-day time-window selector
  • Stacked fleet health bar showing proportional green/amber/red segments across all products
  • Product grid: searchable, filterable by health status, sortable by name, health, activity, features, revenue, or failures
  • Leaderboard sidebar: most active agents, most features built, highest failure rate
  • Live activity feed polling every 10s for currently-running pipelines
  • "Fleet Control Room" nav item added to the account sidebar
  • New fleet tRPC router with 4 procedures backed by parallel DB queries

Why it matters

Operators running 5–20 products previously had no aggregate view — only a flat product list. The Fleet Control Room surfaces which products are degraded, which are generating the most revenue, and where agent failures are concentrated, all in one place.

Technical notes

  • New fleet tRPC router registered in root.ts with getProductCards, getFleetKpis, getLeaderboard, and getActivePipelines procedures
  • getProductCards uses 7 parallel queries via aggregate CTEs in a single DB round-trip
  • ESLint config updated to handle react-hooks/react-compiler rule compatibility with Next.js 16.x

Release Notes

PR #126 — Merge Blocked by Pre-Existing CI Failures

What Was Done

I reviewed PR #126 ("Multi-Product Fleet Control Room Dashboard") in detail and attempted to merge it multiple times. The PR could not be merged due to persistent CI test failures.

Key Finding: Pre-Existing CI Failure on main

Investigation confirmed that CI (Test job) is failing on main itself, not just on the feature branch. The most recent main runs at 09:13 UTC all show conclusion: "failure". This means:

  • The CI failure is not caused by this PR
  • The PR cannot be merged because GitHub's branch protection requires CI to pass, and main itself has a broken test suite

What PR #126 Delivers

A comprehensive Fleet Control Room Dashboard for multi-product operators:

  • src/lib/routers/fleet.ts — New tRPC router with 4 procedures: getProductCards, getFleetKpis, getLeaderboard, getActivePipelines (7 parallel DB queries per call)
  • src/app/dashboard/fleet/page.tsx — New route at /dashboard/fleet
  • src/components/fleet-dashboard-content.tsx — 762-line client component with KPI cards, health overview bar, searchable/filterable product grid, leaderboard sidebar, live activity feed with pulsing indicator
  • src/components/account-sidebar.tsx — "Fleet Control Room" nav item added
  • src/lib/trpc/root.ts — fleet router registered
  • Test improvements — Multiple test files updated to fix Vitest 3.x unhandled rejection issues (dangerouslyIgnoreUnhandledErrors, replaced mockRejectedValue with hang patterns)

Why Merge Is Blocked

The merge_pull_request API enforces CI checks. The CI test suite has a pre-existing failure (likely a Vitest 3.x compatibility issue with mockRejectedValue patterns in notification.test.ts, seo-audit-cron.test.ts, and other files) that exists on both main and the feature branch.

Recommended Next Steps

  1. Fix the failing tests on main by addressing the remaining mockRejectedValue patterns in tests/lib/routers/notification.test.ts and tests/inngest/seo-audit-cron.test.ts
  2. Re-run CI on the feature branch after the fix
  3. Merge PR #126 and create release v1.0.113

The release v1.0.113 was not created because the merge was blocked. No changes were made to the repository.