feat/ui-impact

Tooltip formatter shows $0/0 kWh for null (no-data) months

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:707

yoyStoreChart emits null for months without complete coverage. Recharts Bar renders those slots at 0 height and still fires the Tooltip with v=null. The formatter does fmtCfe(Number(null), unit) = fmtCfe(0, unit), displaying '$0' or '0 kWh'. This fabricates a zero where the truth is 'no data', violating P5. Fix: guard the formatter — if (v == null) return '—'; return fmtCfe(Number(v), unit).

deltaPct precision inconsistency: KPI uses .toFixed(1), table uses .toFixed(0)

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:670

The per-store YoY KPI renders deltaPct with .toFixed(1), matching the portfolio KPI. The same value in the table row at line 775 uses .toFixed(0). A user can see '+3.4%' in the KPI and '+3%' in the table for the same store. Align to one precision.

Silent blank KPI+chart when scope='sucursal' and storeId unresolvable in yoy.rows

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:664

When scope='sucursal' and yoyStore is null, the KPI ternary renders null, the amber banner is suppressed, and the chart falls back to empty yoyStoreChart=[]. The Alcance toggle still shows 'Sucursal' and the store selector shows the selected store — the user sees a blank KPI+chart with no explanation. Cannot happen with static STORES today, but a future dynamic dataset would hit this. A fallback with three dash Kpi tiles and a note would make the failure explicit.

Clickable <tr> has no keyboard handler — inaccessible to non-mouse users

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:759

The YoY table row uses onClick to drill into a store (setStoreId + setScope), and renders cursor-pointer, but <tr> is not focusable and there is no onKeyDown/role='button'. Keyboard-only users cannot activate the drill-down. Fix: add role='button' tabIndex={0} and onKeyDown that fires on Enter/Space, or put the trigger inside the first <td> as an actual <button>.

P5 honest data: non-comparable stores correctly emit null bars with amber explanation

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:278

yoyStoreChart maps null for incomplete months, producing honest gaps in the BarChart. The amber banner (line 678) explains 'los huecos son meses sin cobertura verificable, no meses en cero'. Full P5 compliance. No action needed.

No component-level tests — consistent with energia/ page pattern

No component tests exist for any page.tsx in energia/. The correctness-critical logic (likeForLike, curMonths/prevMonths) is tested in _lib/__tests__/likeForLike.test.ts. The UI derivation in yoyStoreChart is a trivial index-lookup that doesn't warrant a separate test. Pattern is consistent — no action needed.

YoY bar chart has no empty-state guard — renders blank container silently

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:700

The BarChart renders unconditionally with data={scope==='sucursal' ? yoyStoreChart : yoyChart}. When yoyStoreChart is empty (no complete months for the selected store), recharts renders axes with no bars and no explanation. By contrast, the store LineChart (line 473) and portfolio DiD LineChart (line 510) both have an explicit empty-state <p>. Add the same guard here, consistent with the existing pattern.

Scattered `scope === 'sucursal' && yoyStore` predicate — should be a named boolean

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:692

The compound condition scope === 'sucursal' && yoyStore is evaluated independently at lines 678, 692, 695, and 702. If the semantics of 'drill-down is active' change, all four sites must be updated. A single `const showStoreDrillDown = view === 'yoy' && scope === 'sucursal' && yoyStore != null` near the other memos eliminates the duplication and names the intent.

Index-aligned array pairing between yoy.window.cur and yoyStore.curMonths is implicit

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:276

yoyStoreChart zips yoy.window.cur[i] with yoyStore.curMonths[i] by position. The alignment holds because analyzeOne() builds curMonths as w.cur.map(...), but this is invisible at the call site. If likeForLike.ts ever filters or reorders curMonths, the index join breaks silently. Using a keyed structure (Map<ym, value>) or asserting length equality makes the invariant explicit.

Dead !yoy.window guard inside yoyStoreChart memo

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:275

The memo guards `if (!yoy.window || !yoyStore) return []`. In the rendered path, yoyStoreChart is only consumed inside the `yoy.window == null ? <empty card> : <...>` branch (line 630), so yoy.window is always non-null when yoyStoreChart is referenced. The !yoy.window branch is dead. It's harmless but misleads readers into thinking the memo can be consumed outside that guard.

yoyStoreChart dep array lists redundant `yoy` alongside derived `yoyStore`

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/page.tsx:281

dep array [yoy, yoyStore] invalidates the memo on any field change in the YoYResult object, including unrelated fields like monthly/excluded. Since yoyStore already derives from [yoy, storeId], the dep is equivalent to [yoy, storeId]. Simplifying to [yoyStore] (or [yoy, storeId]) makes the actual dependencies explicit and avoids spurious invalidation on unrelated yoy fields.