v1.0.112 — feat: beef up product status pages with live activity & fleet banner
Release v1.0.112: Live activity & fleet banner on product status pages
Date: 2026-03-11
What changed
- Fleet Activity Banner — new banner on the products list page shows how many pipelines are running, which products are actively being built, what stage they're in (researching / building / deploying), and features shipped in the past 7 days. Auto-refreshes every 15 seconds.
- Live indicators on product cards — cards with an active pipeline run now show a pulsing blue dot, shimmer top-border, feature progress bar (
N/totalshipped), and a mini-breakdown of building vs. queued features. - Card footer stats — each card now surfaces total pipeline run count and last release version.
- Live Activity sidebar on product overview — the
/dashboard/products/[id]page now uses a two-column layout: main stats on the left (2/3), and a live activity sidebar on the right (1/3) showing current pipeline status, 7-day summary, recent runs feed, and per-agent-type success rate bars. - Two new components —
fleet-activity-banner.tsxandlive-product-activity.tsx.
Why it matters
The products list and product overview pages now reflect what the AI is actively doing in real time, replacing static snapshots with live pipeline state.
Technical notes
/dashboard/products now runs five enrichment queries in parallel (Promise.all) for recent runs, active runs, feature counts by status, total run counts, and last release per project. /dashboard/products/[id] is now force-dynamic.
Release Notes
Reviewed PR #123 ("feat: beef up product status pages with live activity & fleet banner") and attempted a squash merge, but the merge was blocked because CI checks are failing. The two failing tests (data-export-fulfillment-cron and seo-audit-cron) are pre-existing failures on main that are completely unrelated to the PR's changes (product status page UI). The PR itself is clean — 2 new components (fleet-activity-banner, live-product-activity), 4 modified dashboard files, and CRLF→LF template normalisation. No release was created. To unblock: either fix the pre-existing failing tests on main and re-run CI, or have a repo admin force-merge via the GitHub UI. Once merged, the v1.0.112 release can be created immediately.