claude/vigorous-stonebraker-41cc2d

HVDC line's 1,500 MW capacity not rendered in popup

apps/web/public/atlas/index.html

The HVDC entry has mw:1500 in GeoJSON properties but the tx-lines popup template omits it. The 1,500 MW capacity is the defining characteristic of this interconnection. Add `${+p.mw?' · '+p.mw.toLocaleString()+' MW':''}` after the km display.

Coordinate swap logic verified correct

apps/web/public/atlas/index.html

JSON stores from/to as [lat,lng]; GeoJSON builder correctly swaps to [lng,lat]. All 10 coordinates cross-check against known Mexican geography (Mexicali 32.63/-115.45, Hermosillo 29.07/-110.96, Laguna Verde 19.72/-96.41).

rehab integer coercion is safe

apps/web/public/atlas/index.html

rehab:pr.rehab?1:0 stores 0/1; read back as +p.rehab (unary plus, no-op on integer). Correct both ways.

New popup handlers extend existing innerHTML XSS surface

apps/web/public/atlas/index.html

The tx-subs and tx-lines click handlers interpolate GeoJSON properties (p.n, p.a, p.b, p.kv, p.note, p.cod, p.edo) into innerHTML via pop() without escaping. Current data is static same-origin JSON so risk is low, but any future supply-chain compromise or CDN replacement would allow stored XSS. Add a minimal escapeHtml() helper used consistently across all popup handlers.

No CSP restricting connect-src for transmission.json fetch

apps/web/public/atlas/index.html

Without a connect-src 'self' CSP, a MITM or CDN misconfiguration could serve a tampered JSON file that reaches the innerHTML sink. Defense-in-depth gap — add a CSP header or SRI hash if the file moves to a CDN.

Toggle color collision: `tx` reuses #2bd4ee already assigned to `lines`

apps/web/public/atlas/index.html

TOGS entry ['tx','Transmisión planeada (Plan SEN)','#2bd4ee',0] uses the same hex as the existing `lines` toggle. Both swatches in the legend are indistinguishable. Use a distinct hue (e.g. #f5a623 amber or #c084fc violet) to visually separate planned transmission from the existing operational lines layer.

Redundant `planeacion` arm in txColor match expression

apps/web/public/atlas/index.html

The MapLibre ['match',...] expression lists 'planeacion','#8aa4c8' explicitly, but #8aa4c8 is also the fallback — the explicit branch is dead code. Either drop it (rely on fallback) or change the fallback to a sentinel color so unrecognised statuses are visually flagged.

txst() maps concluido → 'concluido' (no expansion unlike other statuses)

apps/web/public/atlas/index.html

All other statuses get expanded Spanish phrases (en construcción, en planeación, en licitación) but concluido stays as-is. For consistency use 'concluido' or 'concluída' with accent, matching CFE terminology and the expansion style.

TOGS label rename 'Proyectos → Generación' may be inaccurate if projects include non-generation

apps/web/public/atlas/index.html

The projects layer was renamed to 'Generación · construcción/planeación'. If projects.json contains storage or T&D entries this label is inaccurate. Verify the data scope; 'Proyectos de generación' is safer if uncertain.

transmission.json src attribution uses en-dash (U+2013)

apps/web/public/atlas/data/transmission.json

Minor: the en-dash in the src field (–) is U+2013, not U+2014 EM DASH. Verify consistency with other data file src fields. Not blocking.

No bounds check on l.from/l.to arrays before coordinate indexing

apps/web/public/atlas/index.html

l.from[0], l.from[1], l.to[0], l.to[1] are accessed without verifying from/to are 2-element numeric arrays. A malformed entry silently renders NaN coordinates. Consistent with existing layer pattern but a single Array.isArray + length guard would catch authoring errors.

No numeric validation on substation lat/lng scalars

apps/web/public/atlas/index.html

s.lat and s.lng are used directly. Missing or string values produce silent NaN markers. A typeof-number guard or optional chaining with a fallback skip would surface authoring errors faster.

Graceful fallbacks correctly implemented

apps/web/public/atlas/index.html

.catch(()=>({lines:[],subs:[]})) and (tx&&tx.lines)||[] guards ensure a missing transmission.json never breaks the map. Positive finding.

licitacion and planeacion share the same color — likely unintentional

apps/web/public/atlas/index.html

Both status values resolve to #8aa4c8 in txColor. If these represent distinct lifecycle phases they should be visually distinguishable. If grouping is intentional (both = not-yet-built), document that decision to prevent future confusion.

txst() duplicates status→label mapping; could be a shared statusLabel() helper

apps/web/public/atlas/index.html

The projects layer likely uses the same status vocabulary. Extracting a single statusLabel(st) helper shared by both popup handlers keeps the mapping in one place and makes future label changes atomic.

Straight-line 2-point geometry may misrepresent 1,500 km HVDC corridors

apps/web/public/atlas/data/transmission.json

Long HVDC lines modeled as straight point-to-point segments cross mountain ranges or the Gulf in unrealistic paths. Consider an optional waypoints[] array in the data schema for future multi-segment routing without breaking existing entries.

No waypoints data available for HVDC route — schematic is acceptable for now

apps/web/public/atlas/data/transmission.json

CFE has not published the exact HVDC corridor route. The straight-line schematic is appropriate given data availability; adding a disclaimer in the popup note (already present: 'trazo esquemático') covers this.