Fix Runtime page breaker state rendering

[rdself]

Summary

• handle DEGRADED provider breaker states on the Runtime dashboard
• add a fallback tone for future unknown breaker states so the page does not crash
• cover degraded and unknown states with a jsdom regression test

Root cause

The monitoring payload can return provider breaker states beyond CLOSED, OPEN, and HALF_OPEN. When a DEGRADED state was present, the Runtime page attempted to read styling from an undefined tone entry and crashed into the Next.js Internal Server Error screen.

Validation

• npm exec vitest -- run --config vitest.config.ts tests/unit/ui/runtime-page-client.test.tsx --reporter verbose
• npm exec eslint -- 'src/app/(dashboard)/dashboard/runtime/RuntimePageClient.tsx' tests/unit/ui/runtime-page-client.test.tsx
• npm run typecheck:core
• npm run lint -- --quiet
• git diff --check
• verified /dashboard/runtime locally with a database copy that returns DEGRADED breaker state

[gemini-code-assist]

Code Review

This pull request introduces support for a new "DEGRADED" circuit breaker state and gracefully handles unknown states in the dashboard runtime page. It adds helper functions for state normalization and tone retrieval, updates the UI to display degraded and unknown circuits in metrics and badges, and includes a new unit test suite under the tests/ directory. The review feedback identifies two valuable optimization opportunities: refactoring the multiple .filter() calls inside the useMemo hook into a single-pass loop to avoid redundant array allocations, and passing the raw state directly to getBreakerTone to prevent duplicate string normalization.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

The current implementation performs four separate .filter() operations on the breakers array, calling normalizeBreakerState repeatedly for each element. Since this runs inside a useMemo hook that executes on every health update (every 5 seconds), we can optimize this to a single-pass loop. This avoids multiple array allocations and redundant string normalization operations, improving both performance and readability.

  const counts = useMemo(() => {
    let openCircuits = 0;
    let halfCircuits = 0;
    let degradedCircuits = 0;
    let unknownCircuits = 0;

    const knownBreakerStates = new Set(["CLOSED", "OPEN", "HALF_OPEN", "DEGRADED"]);

    for (const b of breakers) {
      const state = normalizeBreakerState(b.state);
      if (state === "OPEN") {
        openCircuits++;
      } else if (state === "HALF_OPEN") {
        halfCircuits++;
      } else if (state === "DEGRADED") {
        degradedCircuits++;
      } else if (!knownBreakerStates.has(state)) {
        unknownCircuits++;
      }
    }

    const totalBreakers = breakers.length;
    const affectedCircuits = openCircuits + halfCircuits + degradedCircuits + unknownCircuits;

[gemini-code-assist]

Passing state (which is already normalized via normalizeBreakerState(b.state)) to getBreakerTone causes redundant normalization because getBreakerTone calls normalizeBreakerState internally. Passing b.state directly to getBreakerTone avoids this double normalization.

Suggested change

	const tone = getBreakerTone(state);
	const tone = getBreakerTone(b.state);

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds support for additional/unknown circuit breaker states in the Runtime dashboard UI to avoid crashes and improve display, along with a unit test to validate rendering of new states.

Changes:

• Expanded breaker state handling to include DEGRADED plus a safe fallback for unknown states.
• Normalized breaker state comparisons and updated KPI/health aggregation to account for degraded/unknown states.
• Added a jsdom unit test to ensure degraded/unknown provider breaker states render without crashing.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
tests/unit/ui/runtime-page-client.test.tsx	Adds a UI unit test that mocks data with DEGRADED and an unknown breaker state and asserts the page renders expected labels.
src/app/(dashboard)/dashboard/runtime/RuntimePageClient.tsx	Normalizes breaker states, adds DEGRADED tone + unknown fallback tone, and updates derived counts/UI to include degraded/unknown states.

[diegosouzapw]

Thanks @rdself! Solid fix — the Runtime page crashed when a provider breaker reported a state not in BREAKER_TONE (tone undefined → tone.ring throw). Normalizing the state + a FALLBACK_BREAKER_TONE (UNKNOWN) makes it resilient, and adding the DEGRADED tone/feed-event pairs cleanly with #3535 (which exposes the degradation threshold backend). The jsdom test renders the real component with DEGRADED+unknown states and asserts no crash. Shipping in the next release. 🙌