Keep street maps legible on Navara after dusk

Navara lights the map tiles with the real sun and sky, and only the
landscape maps took the night ambient fill, so an OSM street map turned
black at local night where Cesium keeps it lit. Every base map now takes
the night fill; the landscape maps keep their orbital fill as well.
Daylight is unchanged.

This is why the strict acceptance's Navara pixel and first-frame checks
over Austin failed in evening runs: navara-hd, parked-release,
hidden-switch, context-loss, geo-import and scope saw a black frame, and
the soak and failure matrix waited for a first frame that never came.
At night with the fix all nine pass.

docs/CURRENT-STATE.md

@@ -266,9 +266,10 @@ one application, and only the globe-bound parts move to the next engine.
   tiles from a disk cache and a trap that fails any read of Cesium before it
   has loaded. Every catalog layer must be asserted on both engines. Point
   `PUPPETEER_EXECUTABLE_PATH` at an installed Chrome if Puppeteer's pinned
-  build is missing. With an OSM base map Navara lights the globe by the real
-  sun, so scenarios over Austin or San Francisco see a dark frame at local
-  night and fail their pixel checks; run them in local daylight.
+  build is missing. Navara lights the globe by the real sun; every base map,
+  street maps included, takes the night fill after dusk, so a scenario over
+  Austin or San Francisco at local night still sees a legible map, as on
+  Cesium (`src/globe/navara/look.js`).
 - **Navara 0.2.1 workaround.** The SDK never frees pick batch ids, and the
   mover banks rebuild their instanced meshes on each attach, so every switch
   leaked one id per instance of capacity (about 260 KiB of WebAssembly memory).