content/auto-draft

Formula variable-definition line reads as nonsensical multiplication

apps/web/content/blog/tarifa-gdmth.mdx:92

The line 'FC GDMTH = 0.57 · Energía en kWh del periodo · días = días del periodo' uses · as separator between variable definitions. A reader evaluating the formula reads this as 0.57 × Energía × días = días — dimensionally nonsensical. Use aligned label definitions with = and newlines, or commas/semicolons.

billArea polygon has redundant duplicate closing point

apps/web/src/components/blog/charts.tsx:385

dm(100)=108*(1-1)=0 so the loop ends with a point at y(0), and billArea appends another x(100),y(0). Two consecutive identical points — harmless visually but indicates a logic gap.

Spanish-named component breaks English-only identifier convention

apps/web/src/components/blog/charts.tsx:365

All existing chart exports use English names (BillAnatomyDiagram, DemandVsConsumptionChart, etc.). DemandaFacturableSolarChart introduces a Spanish identifier into the component registry. Suggest: BillableDemandSolarChart or DemandCrossoverChart.

SUN color constant declared 250 lines below the brand token block

apps/web/src/components/blog/charts.tsx:265

Brand tokens (HELIOTROPE, VIOLET, GREEN, CYAN, MUTED) are all at lines 10–14. SUN = '#F4B740' is declared mid-file at line 265. Move it to the token block with its 'semantic accent' comment so all colors are discoverable in one place.

as const on rows forces unnecessary cast — no existing chart uses this pattern

apps/web/src/components/blog/charts.tsx:326

Either remove as const from rows or explicitly type impacted: string[]. No existing chart in this file uses as const.

Component definition order in charts.tsx is inverse to MDX usage order

apps/web/src/components/blog/charts.tsx:289

MDX uses DemandaFacturableSolarChart first, then SolarBillImpactChart. In charts.tsx the order is reversed. File previously matched narrative MDX order across all other charts — swap to restore the convention.

Import and mdxComponents lines exceed readable length without multi-line format

apps/web/src/app/(marketing)/blog/[slug]/page.tsx:9

Line 9 (import) is 171 chars; line 26 (mdxComponents) 183 chars. Existing multi-line import pattern elsewhere — split these for readability.

No visual regression or smoke test for new chart components

apps/web/src/components/blog/charts.tsx

Matches existing no-test pattern for static SVG charts. A Playwright snapshot of /blog/tarifa-gdmth would catch silent geometry regressions and MDX registry drift. Low priority.

as const + (readonly string[]) cast defeats type safety for segment key lookup

apps/web/src/components/blog/charts.tsx:326

Declaring rows as const narrows impacted to readonly literal tuples, then (row.impacted as readonly string[]).includes(s.key) widens it back, silencing future typo regressions. Fix: type SegKey = 'Energía' | 'Capacidad' | 'Distribución' and impacted: readonly SegKey[] — .includes becomes fully type-safe with no cast.

segX uses slice+reduce on every call — fragile running-total idiom

apps/web/src/components/blog/charts.tsx:308

segX(i) recomputes prefix sum each call (O(n²) over 3 items). Precompute once: const segXs = segs.reduce((acc, s, i) => [...acc, (acc[i-1] ?? pad.left) + s.pct * barW], []). Trivial overhead but the lambda-over-slice form requires readers to mentally re-evaluate on each use.

dmPts samples at 10% steps — CYAN line misses exact crossover intersection

apps/web/src/components/blog/charts.tsx:381

Crossover is at ≈21.3%, between the 20% and 30% samples. The CYAN dashed line doesn't visually meet the VIOLET peak at the labeled 'Punto de cruce'. Add the crossover point to dmPts (like billPts does) for geometric precision.

Redundant duplicate closing point in billArea polygon

apps/web/src/components/blog/charts.tsx:385

dm(100)=0, so the loop's last push is x(100),y(0); billArea then appends another x(100),y(0). Dead data — SVG renders correctly, but end loop at pct < 100 and rely on billArea's explicit close.

SunMark uses index key for rays — prefer semantic key prefix

apps/web/src/components/blog/charts.tsx:275

key={i} on ray lines. Stable array so no reconciliation issue, but key={`ray-${i}`} is more semantically clear and avoids react/no-array-index-key lint warnings.