feat: tone-mapped render rig, studio devices, LA fidelity pass, UI overhaul

The build the studios needed, across eight workstreams and one strict file
partition.

**The render rig was the quality ceiling.** The renderer ran three's
NoToneMapping default while atmosphere drove the sun to 2.35 and assets set
emissives to 3.2, so every value above 1.0 hard-clipped to flat white — which is
why walls blew out and every fitting looked like a white rectangle. ACES filmic
tone mapping and an explicit output colour space land in `stage.ts`, and the
atmosphere intensity table and palette headroom are re-tuned against the new
curve rather than left tuned for the clipping we removed.

`engine/environmentRig.ts` builds a PMREM environment at runtime, procedurally,
so nothing binary is committed. There was no environment map anywhere before, so
every `metalness > 0` role had nothing to reflect and rendered dull grey — a
defect the code already documented against itself in `office/optimus.ts`, where a
whole material role was abandoned over it, and worked around in `modelX.ts` with
a fake emissive that this change deletes. Atmosphere remains the sole light
owner; the rig derives from the `LightingState` it already produced.

**Studio hardware exists.** There was no device concept anywhere in the product:
no type, no route, no state. `devices/types.ts` fixes a declaration/state/
capability/command contract that a smart light, a thermostat, a door sensor and a
charger all fit without a schema change, and both studios now carry a desk mic
and a computer speaker with deterministic simulated behaviour behind an adapter
seam a real API can occupy later. Reads are the demo and are open; commands are a
signed-in action and are kept off the read body entirely, because a shared cache
replaying a GET that turned a microphone on is exactly what the fail-closed
cache default exists to prevent.

**The ADS-B licence hole is closed.** `TERA_ADSB_ENDPOINT` accepted any URL, the
response was served publicly cacheable, and the attribution hardcoded adsb.lol
regardless of where the endpoint pointed — one env var away from republishing
non-redistributable data under an open-terms credit. The host is now allowlisted,
the credit is derived from the host actually configured, public cacheability is
conditional on redistributability, and a refused endpoint demotes to simulated
flights and says so in `degraded[]`. The gate is on the source, not the feature:
live aircraft and their detail cards stay open to anonymous visitors.

**The LA studio was never the smaller pack** — 16 rooms and 248 props against
SF's 4 and 28. Its deficit was fidelity per square metre: 98 of those props were
ceiling troffers, it bound no props to seats, placed none of the habitat kit, and
12 of its 16 rooms had no viewpoint. Density comes from new asset kinds rather
than more instances, because `furnish.ts` draws once per kind and folds colour
into the batch key, so repeat instances add nothing the eye can read.

**The interface stops being forty imperative mutations.** Every visibility
decision moves into a pure, tested `ui/chromeState.ts` and one applier, so the
chrome has coverage for the first time. Deleted: ~100 lines of CSS and two
bindings targeting elements that no longer exist, and a `body:has()` rule that
shifted the desktop layout by 160px for touch controls hidden there. Fixed: the
office picker tabs that drew their label and their badge on top of each other.
Added: a first-run flow, because the product is two verbs and neither was ever
stated on screen. Mobile is designed on its own terms instead of being the
desktop with things hidden — the plan view comes back, and the keyboard-only
shortcuts button is replaced by touch controls.

`arena/studioOps.ts` frames the whole thing as the multi-variable environment it
is, wrapping the same simulators the renderer drives rather than a headless copy.

Also removed `input/vehicle.ts`, which nothing but its own test imported.

Tests 385 -> 961, all passing. Typecheck, build, performance budgets across six
matrix cells, no-binaries, provenance, dependency licences, zero-config boot and
arena source hashes all green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

src/engine/satellites.ts

@@ -300,6 +300,20 @@ export interface SatelliteLayer {
   group: THREE.Group;
   /** Redraw from a set of fixes. Cheap enough to call every frame, and is. */
   update(fixes: SatelliteFix[]): void;
+  /**
+   * How dark the sky is, 0..1 — `nightFactor(sun.elevation)` from
+   * `atmosphere.ts`, and nothing else.
+   *
+   * This layer draws additively, which is correct at night and catastrophic in
+   * daylight: at 15:55 with the sun at +44° every dot was adding to an already
+   * bright sky and clipping to a hard white square, which is what a first-time
+   * visitor to the California board saw scattered across the frame before
+   * anything else registered. A satellite in daylight is not visible to the
+   * naked eye, so the honest alpha is zero — and the fade is the *same* curve
+   * `nightlights.ts` switches the city on with, so the sky does not empty at a
+   * different dusk from the one the windows light up at.
+   */
+  setSkyDarkness(darkness: number): void;
   /**
    * Whether the layer draws at all. The catalogue keeps propagating either way —
    * see `setVisible` for why that is deliberate rather than wasteful.
@@ -481,6 +495,24 @@ export function createSatelliteLayer(boardRadius: number): SatelliteLayer {
 
   const scratchVec = new THREE.Vector3();
 
+  /**
+   * 1 until somebody says otherwise, so a caller that never calls
+   * `setSkyDarkness` gets exactly the behaviour this layer had before it
+   * existed. A silent regression to an invisible sky would be worse than the
+   * defect being fixed.
+   */
+  let skyDarkness = 1;
+  /** Whether the godmode switch wants this layer at all. Two questions, two flags. */
+  let wanted = true;
+
+  /** The hour outranks the switch: a god at noon still gets no white squares. */
+  function applyVisibility(): void {
+    // Below a fiftieth the dots contribute nothing a screen can show, and
+    // skipping the draw entirely is what makes the daytime cost of this layer
+    // zero rather than merely invisible.
+    group.visible = wanted && skyDarkness > 0.02;
+  }
+
   function update(fixes: SatelliteFix[]): void {
     let n = 0;
     for (const fix of fixes) {
@@ -500,10 +532,11 @@ export function createSatelliteLayer(boardRadius: number): SatelliteLayer {
       colors[n * 4] = scratch.r;
       colors[n * 4 + 1] = scratch.g;
       colors[n * 4 + 2] = scratch.b;
-      colors[n * 4 + 3] = horizon * (SHADOW_ALPHA + (1 - SHADOW_ALPHA) * lit);
+      colors[n * 4 + 3] = horizon * (SHADOW_ALPHA + (1 - SHADOW_ALPHA) * lit) * skyDarkness;
       n += 1;
     }
 
+    applyVisibility();
     geo.setDrawRange(0, n);
     positionAttr.needsUpdate = true;
     colorAttr.needsUpdate = true;
@@ -512,6 +545,10 @@ export function createSatelliteLayer(boardRadius: number): SatelliteLayer {
   return {
     group,
     update,
+    setSkyDarkness(darkness) {
+      skyDarkness = Math.min(1, Math.max(0, darkness));
+      applyVisibility();
+    },
     /**
      * Hiding the layer stops it drawing and does **not** stop the catalogue
      * propagating, which is the right way round: turning the sky back on should
@@ -521,7 +558,8 @@ export function createSatelliteLayer(boardRadius: number): SatelliteLayer {
      * re-entry is worth more than reclaiming it.
      */
     setVisible(visible: boolean) {
-      group.visible = visible;
+      wanted = visible;
+      applyVisibility();
     },
     dispose() {
       geo.dispose();