feat/ui-impact

<th> alignment guard uses removed 'Frecuencia' instead of 'Inicio'/'Fin'

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

The <th> className condition is `h === 'Periodo' || h === 'Frecuencia'` — 'Frecuencia' was removed in this diff; CFE view now emits 'Inicio', 'Fin', 'Días'. The <td> isText guard on line 324 was correctly updated to include 'Inicio' and 'Fin', but the <th> guard was not. Result: in CFE mode the 'Inicio' and 'Fin' column headers render `text-right` while the cells below are left-aligned (`font-medium`) — a visible header/cell alignment mismatch. Fix: change <th> condition to `h === 'Periodo' || h === 'Inicio' || h === 'Fin'` to match the <td> isText guard.

Real customer name 'Grupo Axo' ships in the 'use client' bundle via JSDoc comments

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:2

The JSDoc block says 'REAL Grupo Axo consumption series' and 'Pulled from PRODUCTION Supabase (org "Grupo Axo", read-only)'. This file is a 'use client' module; its source text ships in the Next.js client bundle. Any authenticated user who opens DevTools → Sources can read the customer's real name, defeating the store-label anonymization ('Tienda CDMX 01' etc.). Recommendation: replace 'Grupo Axo' with a codename (e.g. 'the reference portfolio' or 'Grupo A') so the bundle carries only anonymous attribution.

Energia module intentionally ungated (TEMP) — real production data reachable by all authenticated users

apps/platform/src/lib/soft-launch.ts:50

Two '// TEMP: energia live for preview demo — revert before merge' comments at lines 50 and 57 intentionally exclude /energia from the soft-launch gate. This means the Comparativo page with real Grupo Axo kWh+tariff+dates data is accessible to every authenticated platform user, not just entitled orgs. The TEMP markers indicate this is known and pre-merge. Flagging as a pre-merge checklist item: restore the energia gate before this branch lands in main.

Block comment in realConsumption.ts partially duplicates MonthPoint field comments

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:1

The 19-line block comment is justified (data provenance and PII compliance are non-obvious). However, lines 11–18 partially repeat what the MonthPoint interface field comments (lines 26–29) already say about exact/derived dias. Consider trimming the block comment to just the provenance/PII declaration and the top-level dias caveat, and letting the field comments carry the per-field detail.

diasCell() '~N' approximation marker is not i18n-safe

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

The tilde prefix (~) is hardcoded. All user-facing strings should come from messages/{locale}.json per ui-patterns.md. Acceptable as a demo-internal shortcut for now; flag for when the Comparativo surface goes to production.

diasCell() has no unit test — the ~N export format is unguarded

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

diasCell() is a one-liner but its output appears in both the on-screen table and the CSV export. A two-case unit test (exact: true → number; exact: false → string starting with '~') would cost nothing and guard against accidental format changes affecting the WYSIWYG export contract.

MonthPoint extension is additive and type-safe — no existing tests affected

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:23

No __tests__ files reference MonthPoint, realConsumption, or the comparativo route. anomaly.ts only reads .kwh, .dias, .ym — the new fields are invisible to the existing analysis logic. Extension is safe.

Removed store IDs (t26, t27, t28) are not referenced in any test fixture or seeded data

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:50

A codebase-wide grep finds no references to t26/t27/t28 outside the changed file. Dataset replacement is clean.

No e2e coverage for the Comparativo route — existing gap, not new

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

The entire energia module has no e2e tests. The default store change (t26 → t02) and new column names are not tested. This is a pre-existing gap for the whole module, not introduced by this commit.

'Tuple' type alias is positional and not self-documenting

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:37

type Tuple = [string, number, number, boolean, string | null, string | null] carries no domain signal. A reader scanning the data tuples must cross-reference the S() destructuring to know position 3 = exact, 4 = ps, 5 = pe. Minimal fix: rename to BillTuple or add a JSDoc comment `// [ym, kwh, dias, exact, ps, pe]` to the alias.

ps/pe abbreviations reduce external readability of the MonthPoint interface

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/_lib/realConsumption.ts:29

ps and pe for period_start/period_end are explained in field comments, but using the abbreviation in the exported interface forces every consumer (page.tsx, future callers) to look up the docs. Consider using periodStart/periodEnd in the MonthPoint interface and keeping the short names only as destructuring aliases inside S().

No dead code from freq() removal detected

apps/platform/src/app/[locale]/(dashboard)/energia/comparativo/

freq() was not in ded4e61c — it was already removed before this incremental window. No orphan references to freq, Bimestral, or Mensual remain.