fix(showcase/dashboard): correct starter staleness window to hourly cadence

The starter_smoke probe runs hourly (`schedule: "40 * * * *"`), but
STARTER_STALE_AFTER_MS was set to 13h with a comment claiming a 6h cadence
— ~13 missed hourly ticks before amber, defeating the intended two-miss
flip. Re-derive the window from the 1h probe period to 2.5h: strictly
> 2 periods (so two consecutive misses, last row ~3h old, flip amber) yet
< 3h (so a single missed/slow-wake tick, last row ~2h old, stays green,
absorbing a scale-to-zero cold-start). Reconcile both the staleness.ts and
starter_smoke.yml comments to the same hourly basis + 2.5h window in
lockstep (no more "6h" in the starter context). Extend the staleness tests
with explicit hourly-tick boundaries (1 miss → green, 2 misses → amber).

Also drop the inaccurate "hollow" from the not-supported ✗ comments — there
is no hollow render variant; the state renders as grey ✗ text.

Author: jpr5

showcase/harness/config/probes/starter_smoke.yml

@@ -51,10 +51,11 @@
 # four checks are cheap HTTP round-trips, but each tick WAKES sleeping
 # scale-to-zero services, so we keep the cadence well above the 15-min smoke
 # rhythm to keep wake frequency (and idle cost) low. The dashboard's
-# `STARTER_STALE_AFTER_MS` (UI slot) is derived from THIS schedule at
-# strictly > 2 probe periods, so a single missed/slow-wake tick stays green
-# and only two consecutive misses flip amber. Keep this cron and that
-# staleness window in lockstep.
+# `STARTER_STALE_AFTER_MS` (UI slot) is derived from THIS hourly schedule
+# (1h probe period) at strictly > 2 probe periods — it is set to 2.5h, so a
+# single missed/slow-wake tick (last row ~2h old) stays green and only two
+# consecutive misses (last row ~3h old) flip amber. Keep this cron and that
+# 2.5h staleness window in lockstep.
 kind: starter_smoke
 id: starter_smoke
 schedule: "40 * * * *"

showcase/shell-dashboard/src/components/__tests__/cell-matrix.test.tsx

@@ -769,7 +769,7 @@ describe("CellMatrix — Starter row-group", () => {
   it("not-supported ✗ for an unmapped column, tooltip 'no starter for this integration'", () => {
     const { getByTestId } = renderMatrix(new Map());
     const cell = getByTestId("starter-cell-ag2-health");
-    // grey/hollow ✗ — the chip carries the tooltip title.
+    // grey ✗ — the chip carries the tooltip title.
     expect(cell.textContent).toContain("✗");
     const chip = cell.querySelector("[title]");
     expect(chip?.getAttribute("title")).toBe("no starter for this integration");

showcase/shell-dashboard/src/lib/live-status.test.ts

@@ -956,6 +956,36 @@ describe("buildStarterBadge — 5-state cell vocabulary (§d)", () => {
     expect(b.label).toBe("✓");
   });
 
+  // Hourly-cadence derivation (starter_smoke.yml `schedule: "40 * * * *"`,
+  // 1h probe period; STARTER_STALE_AFTER_MS = 2.5h). These pin the window to
+  // the hourly basis: a single missed tick (last row ~2h old) MUST stay green;
+  // two consecutive misses (last row ~3h old) MUST flip amber.
+  const ONE_HOUR_MS = 60 * 60 * 1000;
+
+  it("window is strictly > 2 hourly probe periods and < 3 (derived 2.5h)", () => {
+    expect(STARTER_STALE_AFTER_MS).toBeGreaterThan(2 * ONE_HOUR_MS);
+    expect(STARTER_STALE_AFTER_MS).toBeLessThan(3 * ONE_HOUR_MS);
+  });
+
+  it("single missed hourly tick (~2h old) stays green", () => {
+    const oneMiss = row("starter:agno/agent", "starter", "green", {
+      observed_at: new Date(NOW - 2 * ONE_HOUR_MS).toISOString(),
+    });
+    const b = buildStarterBadge("agent", true, oneMiss, NOW, "live");
+    expect(b.tone).toBe("green");
+    expect(b.label).toBe("✓");
+  });
+
+  it("two consecutive missed hourly ticks (~3h old) flip amber ~", () => {
+    const twoMisses = row("starter:agno/agent", "starter", "green", {
+      observed_at: new Date(NOW - 3 * ONE_HOUR_MS).toISOString(),
+    });
+    const b = buildStarterBadge("agent", true, twoMisses, NOW, "live");
+    expect(b.tone).toBe("amber");
+    expect(b.label).toBe("~");
+    expect(b.row?.state).toBe("degraded");
+  });
+
   it("gray ?: supported column, no row yet → gray ? (not-yet-run)", () => {
     const b = buildStarterBadge("interaction", true, null, NOW, "live");
     expect(b.tone).toBe("gray");

showcase/shell-dashboard/src/lib/live-status.ts

@@ -430,7 +430,7 @@ const STARTER_LEVEL_DESCRIPTION: Readonly<Record<StarterLevel, string>> = {
  * Build a `BadgeRender` for one starter sub-cell, applying the FULL 5-state
  * cell vocabulary (§d):
  *
- *   - not-supported  → grey/hollow "✗", mapping-derived (`!isSupported`),
+ *   - not-supported  → grey "✗", mapping-derived (`!isSupported`),
  *                      tooltip "no starter for this integration". Distinct
  *                      from the red smoke-failed ✗. Resolved FIRST so it can
  *                      never collide with the gray `?` initial state.
@@ -453,7 +453,7 @@ export function buildStarterBadge(
   connection: ConnectionStatus,
 ): BadgeRender {
   if (!isSupported) {
-    // Mapping-derived: this column has no starter (§a). Grey/hollow ✗,
+    // Mapping-derived: this column has no starter (§a). Grey ✗,
     // visually distinct from a red smoke-failed ✗. NOT data-derived, so it
     // renders identically before and after the first probe tick.
     return {

showcase/shell-dashboard/src/lib/staleness.ts

@@ -50,14 +50,18 @@ export const LIVENESS_STALE_AFTER_MS = 45 * 60 * 1000;
  * rows written by the harness `starter_smoke` probe family). Per spec §d, the
  * window is derived from the probe cadence and MUST be strictly greater than
  * two probe periods, so a single late/missed/slow-wake tick stays green and
- * only two consecutive misses flip amber. The probe ships on a 6h cadence
- * (mirroring the retired `test_smoke-starter.yml` cron the live signal
- * replaces); 13h is > 2×6h with headroom to absorb the scale-to-zero
- * cold-start latency (§c) folded into a single tick. Keep this in lockstep
- * with S2's `starter_smoke.yml` `schedule` — if the cadence changes, this
- * window must be re-derived (> 2× the new period). Not env-tunable.
+ * only two consecutive misses flip amber. The probe ships on an HOURLY cadence
+ * (`schedule: "40 * * * *"`, see harness/config/probes/starter_smoke.yml), so
+ * the probe period is 1h. We set the window to 2.5h: > 2×1h (so two consecutive
+ * missed hourly ticks, which age the last row to ~2h, then ~3h, flip amber on
+ * the SECOND miss) yet < 3h (so a single missed/slow-wake tick — last row ~2h
+ * old — stays green, absorbing a scale-to-zero cold-start wake folded into one
+ * tick, §c). 2.5h is the tightest window satisfying ">2 periods" that still
+ * trips on the second miss. Keep this in lockstep with S2's `starter_smoke.yml`
+ * `schedule` — if the cadence changes, this window must be re-derived
+ * (> 2× the new period). Not env-tunable.
  */
-export const STARTER_STALE_AFTER_MS = 13 * 60 * 60 * 1000;
+export const STARTER_STALE_AFTER_MS = 2.5 * 60 * 60 * 1000;
 
 /**
  * Determine whether a row's `observed_at` is older than `maxAgeMs` relative