# Changelog - Local FM seek finds stations after wrapping around 87.5–108 MHz, covers both band edges, skips the starting station and rejects spectra from an earlier tune (Aditya, @Rohilalala, #1174). - Local RTL-SDR keeps USB reads queued in order and bounds pending decoder work. A stalled or overloaded decoder stops with an explicit error; stopping terminates its worker and rejects late audio. FM playback buffers short scheduling gaps, caps its audio queue at 256 ms, and reduces display updates and spectrum calculations while listening. - Add Bogotá (Tembici, 250 stations) and Santiago de Chile (Bike Itaú, 200 stations) to the GBFS bikeshare registry, the layer's first stations in Colombia and Chile. Both are PBSC feeds like the Brazilian Bike Itaú cities, so no proxy change is needed. Both feeds also list depot stations on other continents (São Paulo, Madrid) as in service; stations outside a city's load radius are now dropped instead of drawn as live docks. - Add Barcelona's bike share to the GBFS registry: Bicing (543 stations, the city's PBSC system) and AMBici (237 e-bike stations across the metropolitan area, run by nextbike). Both are keyless GBFS 2.3 feeds listed in MobilityData's systems catalogue; AMBici's is CC0. `gbfs.nextbike.net` joins the proxy allowlist. These are the layer's first stations in Spain. - Add nine Ontario transit feeds: TTC, MiWay, Hamilton HSR, Durham Region, YRT/Viva, Guelph, Burlington, Barrie and Kingston, each carrying its own licence quote and attribution. A feed can now name its own modes, so Toronto's trams read "Streetcar" while Helsinki's stay "Tram", and a feed whose route ids are internal keys can translate them to the number a rider would say. TTC vehicles take their mode from the fleet number first, so replacement buses on streetcar routes read as buses and out-of-service streetcars stay streetcars. - CCTV cameras with identified hardware show the model's datasheet specs. When a source names a camera model found in the vendored CCTV Camera Database records (CC0), the HUD meta line adds its resolution, night vision and PTZ capability. A fixed single-lens model's horizontal FOV fills in when the source states no FOV and the pose is not curated (`FOV n° (DATASHEET)`); a PTZ or varifocal range is what the lens can do, not its current zoom, so those cameras keep the estimate and show `SPEC FOV min–max° (CAPABILITY)` beside it (bassem chagra, #452). - Ship a web app manifest and raster home-screen icons, so adding the app to a phone home screen or installing it on desktop uses the God's Eye View mark instead of a blank tile. The icons are generated from `public/logo.svg` by `node scripts/generate-icons.mjs` and committed, so a plain `vite build` needs no image toolchain. The existing SVG favicon still serves the browser tab. Manifest paths are relative to the manifest, so a build served under a path prefix installs and launches inside that prefix. - Cyclone advisories no longer go dark while NHC publishes an advisory ahead of its nominal time: advisory and position times up to 90 minutes ahead of the server clock are accepted (previously 5 minutes), so the whole feed is not rejected for about half an hour each advisory cycle. - Flights age out vanished aircraft again. OpenSky's routine position-less rows no longer mark every snapshot partial, which had kept vanished and landed aircraft at full opacity for up to five minutes; those rows retain only their own aircraft, and a likely-landed one still leaves on the landed limit. - Add WSDOT highway cameras (Washington State) as a keyless CCTV source pack: WSDOT's official Travel Center camera layer, with frames registered only on WSDOT's own image host (partner-hosted cameras such as Oregon DOT and City of Seattle are skipped). Cameras with a single cardinal `CompassDirection` get a high-confidence heading; `B` (both directions), `O`, and unset directions use the shared id-hash fallback at low confidence. By default the 250 cameras nearest Seattle and Spokane load; `CCTV_WSDOT_MAX_SOURCES` sets the cap (8–1,200) and `CCTV_WSDOT_ENABLED=0` turns the pack off (bassem chagra, #644). - Refuse still-image cameras on the CCTV media relay. `/api/cctv/media` is the live-feed route, but it also relayed any registered still camera through an ordinary fetch that followed redirects to any host, passed through whatever content type came back and had no cap on the body, bypassing every protection `/api/cctv/frame` applies to the same URL. Only HLS, MP4, WebM and MJPEG feeds are relayed now; a still camera, or an unknown id, gets a JSON 404 without an upstream request and is served only through `/api/cctv/frame`. The client already loaded stills through `/frame`, so nothing it requests changes. - Add Lithuania's public Via Lietuva / Eismoinfo road cameras to CCTV, with published coordinates, on-demand snapshots, attribution and bounded catalog requests. No API key is required. The pack is opt-in (`CCTV_LITHUANIA_ENABLED=1`) because its camera endpoints are the eismoinfo.lt website backend, not a service listed in Via Lietuva's open-data statement, so the licence for the photos is unconfirmed. - Add King County road cameras (Washington State) as a keyless CCTV source pack: one public King County DOT ArcGIS layer, fetched with an explicit field list so its staff-name columns are never requested, and frames pinned to the county's own image host and upgraded to HTTPS. WSDOT-owned rows are skipped, and city-owned cameras the county hosts credit their owner. The layer publishes no facing, so headings use the shared id-hash fallback at low confidence. It does publish each camera's hardware, which is served on `/api/cctv/sources` as `model` and `manufacturer`. `CCTV_KINGCOUNTY_MAX_SOURCES` sets the cap and `CCTV_KINGCOUNTY_ENABLED=0` turns the pack off (bassem chagra, #645). - Add City of Toronto RESCU traffic cameras as a keyless CCTV source pack: the ~336 municipal cameras the Ontario 511 pack does not carry — downtown arterials plus the Gardiner, DVP, Allen and Lake Shore. The list is the City's own open data feed; frames are built from the documented `loc####.jpg` convention and a digits-only camera number, so the frame proxy is pinned to the portal origin by construction. The dataset publishes no camera facing — its `D1`-`D4` fields describe static 2016 comparison images, not the live pan-tilt-zoom frame — so headings use the shared id-hash fallback at low confidence and are corrected with the calibration gizmo. Carries the required Open Government Licence – Toronto attribution. Disable with `CCTV_TORONTO_ENABLED=0`. - Stop one retired bikeshare feed from reporting the whole layer as failed. City feeds are fetched independently, but failure was recorded in a single flag that only a successful *activation* cleared — and an already-loaded city never activates again. A dead feed re-entering camera range therefore latched LOAD FAILED permanently over a map still drawing every other city's stations. Failure is now tracked per city: a city that fails beside others still drawing marks the layer DEGRADED, polls that all fail over previously drawn points read STALE without advancing freshness, and LOAD FAILED is reported only when nothing is left to draw. A city that recovers clears its own failure, a failure is dropped once its city leaves range or the camera rises above the activation altitude, and late results from superseded requests are ignored. Repointed the three feeds whose operators had moved: Reddy Bikeshare (Buffalo) to Social Bicycles, Tugo (Tucson) and Trinity Metro (Fort Worth) to PBSC. Dropped CoGo (Columbus) and Broward B-cycle (Fort Lauderdale), whose systems have wound down — CoGo's feed reports no stations and last moved a bike in March 2025. The three repointed feeds were verified live. - Add seven Brazilian Bike Itaú (Tembici) cities to the GBFS bikeshare registry: São Paulo, Rio de Janeiro, Salvador, Recife, Porto Alegre, Brasília and Curitiba (about 1,000 stations in total). These are the layer's first stations in South America. - Add Bike Share Toronto (1,069 stations) to the bikeshare registry. The system publishes the same PBSC GBFS v2 feeds as the Austin, Honolulu and Chattanooga entries, so it needs no new plumbing; a registry test now holds every city's feed URLs against the proxy host and path allowlists, so a city the proxy would refuse fails the suite instead of rendering an empty layer. - GBFS v3 station names use English translations when available, then the first usable translation or short name. Empty or malformed names no longer appear as `[object Object]` or interrupt station loading; legacy string names remain supported in the globe and bike-share tools. Thanks to [Kristóf Kékesi](https://github.com/KristofKekesi) (#61). - Overpass and military-installation disk caches no longer serve answers from a previously configured `OVERPASS_UPSTREAMS` instance after it is repointed. - A Radio Browser mirror answering 204, 205 or 304, or a status outside 200–599, no longer crashes the local dev/preview server. Null-body statuses get an empty body; anything else that cannot become a response fails that mirror so the next one is tried. - Snow flakes sway within a fixed range instead of drifting sideways faster the longer the app runs; the Wind setting still scales the sway. - The right rail ignores panels that other CSS hides, such as during an event view, so they no longer force one-panel-at-a-time layout or collapse visible panels. Panels the rail collapses itself are still restored. - Coordinate searches refuse empty latitude or longitude components instead of navigating to an unintended location. - Bing Aerial and Bing Labels request HTTPS tiles on HTTP localhost through their ion-backed providers, retaining ion and per-tile attribution without widening the Content Security Policy. - Add New York City traffic cameras from the NYC DOT Traffic Management Center as an opt-in CCTV pack. NYC DOT requires a data-sharing agreement for the camera feed, so the pack is off unless `CCTV_NYC_ENABLED=1` is set by an operator who holds one; otherwise no request reaches NYC DOT. NYC DOT's requested disclaimer is in the Data attribution popover. The camera list is one keyless JSON request to `webcams.nyctmc.org/api/cameras`; frames are stills synthesized from each camera UUID on that same host, so a catalog field cannot steer the proxy off-host. Offline cameras are dropped. Once enabled, the 250 cameras nearest the five borough cores load and `CCTV_NYC_MAX_SOURCES` changes the cap. The catalog-wide ceiling is unchanged; extra cameras share it round-robin with the other packs. - Street Level counts unique tiles before ranking so overlapping dateline halves in polar views do not waste slots in the 16-tile overview budget. - Directions no longer shows a truncation notice for a route with exactly 200 turns, and a roundabout at the 200th turn keeps its exit distance. - Weather records keep missing conditions unknown and refuse summaries without a measured temperature. - Tool string length validation counts Unicode characters correctly, including characters outside the basic multilingual plane. - Director timeline seeks cross the dateline along the short longitude arc. - Keep unknown GBFS availability counts neutral instead of turning null or empty values into zero bikes. - Recent Imagery continues past malformed records in full catalog pages, respects the requested record limit, and reports results as truncated when that limit drops valid records. - Regional articles retain unknown publication times when compact source dates do not identify a real calendar instant. - Add Detroit (MoGo), Pittsburgh (POGOH), Aspen (WE-cycle) and Kona & Hilo (HIBike) to the GBFS bikeshare registry, the layer's first stations in Michigan. - Treat explicitly current, complete empty vessel coverage as a successful update, clearing obsolete contacts while retaining stale or incomplete snapshots. - Custom Street Level provider switches survive share links and stored state using URL-safe stable provider IDs and a shared boolean-switch codec; existing Mapillary links keep their meaning. Explicit provider toggles reach durable state without adopting unrelated live switch changes. - Directions and Recent Imagery accept replaceable acquisition sources, including route transport, imagery catalog, thumbnails, tile templates and attribution. Explicitly removing either source leaves its layer unavailable; standalone defaults preserve the existing providers. - Catalog source availability no longer modifies layer objects; unavailable tooltips use layer display names. - Street Level with no providers uses the shared unavailable state and refuses activation before initialization, while keeping its layer identity visible. - Application source configuration accepts replacements and explicit removal. Missing catalog feeds leave their layers unavailable without blocking startup or making fallback requests; malformed supplied feeds remain configuration errors. - Street Level providers are optional in application composition. Omitting a Mapillary source no longer prevents startup; callers can inject a different provider list or an empty list without changing layer identities or share links. - Vector tile sources take their allowed tile origin from the configured `tileJsonUrl`, so repointing only that URL at a mirror loads tiles from the mirror or fails visibly instead of silently using OpenFreeMap. Thanks to [daikaginza](https://github.com/daikaginza) (#935). - MCP setup examples use the app's default port, `4173`. Thanks to [Huanyi Xie](https://github.com/xiehuanyi) (#934) and [shirunjies8-png](https://github.com/shirunjies8-png) (#959) for the same fix. - Voice revisits numbered analyst records through current layer snapshots and preserves resolved pin coordinates. Requested analyst lists and rankings can speak returned items alongside the exact count and coverage caveats. Failed actions settle the voice card without reviving cancelled turns. Coverage benchmarks reject invalid calls before accepting semantic matches. - Street Level is included in the voice layer manifest for visibility toggles; imagery is not exposed as countable analyst records. - Voice debug logs omit complete tool-result bodies and serialized function outputs by default, including location queries and generated spoken replies. `GEV_VOICE_LOG_CONTENT=1` retains them for explicit content debugging. - Unqualified Alps searches use the bundled European range for navigation and annotations instead of a same-named peak returned by a geocoder. Coordinates, supplied presets and geographically qualified place names keep their precedence; annotation proximity and containment guards remain. - Contacts analyst follow-ups retain the snapshot's distance ranking rather than switching to the camera. Requested radii and explicit scopes remain authoritative, and a request for a list still requires an analyst query. Analyst speech names stale or degraded feeds and withholds authoritative counts when unavailable. The existing NOTES disclosure preserves complete, deduplicated coverage and source caveats, including crowded results. - The voice card shows analyst counts ("At least 250,000 aircraft …") with their scope, feed window and caveats, and marks partial answers. Analyst speech uses the same deterministic headline, preserves lower bounds and says when an answer is partial. Follow-ups retain unanswered-layer coverage, and keep the original scope label when they narrow a remembered result. Contacts-window answers read one immutable panel snapshot, mark a 20,000-row layer cap as a lower bound, and commit that displayed cohort only after cancellation checks pass. Concurrent analyst calls from one model response remain independent; a stopped or replaced user turn still cancels them. - Voice answers are shorter and fill slow work instead of going silent. Slow or multi-step requests may open with one short spoken plan; instant ones just happen. Tool results carry a code-built `say` line and a `display` card: sources and notes stay on screen, a caveat is spoken only when it changes the answer, and "at least" and partial answers are always said. A card above the mic shows captions, the plan's steps and the result. When a tool that reports steps (layers, place lookups, outlines, nearest-aircraft) is still running after 1.5 s its current step is spoken once; others say "still working" once after 8 s. A soft tick plays in push-to-talk. Holding Space while the assistant talks cuts it off. Each turn writes latency and speech figures to the debug log (`node scripts/voice-turn-spans.mjs`). Captions of what you say are counted in the voice cost meter; the debug log leaves out what was said unless `GEV_VOICE_LOG_CONTENT=1`. - Point and ask: hold Space with the cursor on an aircraft, ship or spot on the map and say "what's that", "track that one" or "how many flights around here". A reticle marks the point and the voice card shows what "this" meant. In open mic it works when you have just moved the cursor there. "The second one" picks from the last numbered list. Asking about "the last one" resolves to the last of the five rows actually shown, and referent-only tracking calls are accepted while empty targets are rejected. Asking about bare ground up close gives the assistant a small crop of the map around the point. A slow render gets one bounded second frame request, while hidden, stale, moved-camera, invalid and oversized captures still fail closed. ## [Unreleased] - Add a keyless Air quality layer to the Weather group, with Environment and Climate Change Canada's AQHI as the first registered provider. Readings carry `{ provider, scale, value, band }` so another network can be added without inventing a shared numeric meaning across indices that do not share one; the row and readout both state that coverage is Canada only. The WEATHER card shows the band legend and the highest readings currently in view. AQHI is reported as an integer from 1 with an open-ended "10+", so readings round to that published form rather than the decimal precision the API returns. Readings older than six hours are dropped, and the layer reports `stale` through `getStats()` (also when every observation was dropped) so feed provenance cannot describe an aged feed as live. Voice can switch it on and query readings by value, band, station and observation time. - Bound six upstream body reads (FIRMS CSV, CelesTrak TLE groups, adsb.lol `/v2/mil`, TomTom flow tiles, OpenSky `states/all` and adsbdb lookups) with streaming size caps that cancel the body at the cap or the route's deadline; the adsb.lol military poll gains a deadline of its own. An oversized OpenSky snapshot is not retried, and an OpenSky 429 starts its cooldown before the body is read. - Keep later satellites when a TLE catalog entry is missing an orbital line. The parser skips the incomplete set and resumes at the next complete named set, instead of losing the rest of the group (#906). - Satellite clouds keep Clouds only / Full as quick endpoints and add a continuous cloud-filter slider: 0% is Full, 100% is the existing brightness key, and intermediate values blend the keyed alpha. The slider commits on release to avoid restaging imagery for every drag event. Filter percentages round-trip in share links; legacy mode codes retain their old endpoint meanings. Background panel refreshes preserve the pending drag value until release. Contributed by [NotProniss](https://github.com/NotProniss) (#1084). - Street Level: Panoramax is the fourth provider, keyless. Light its chip (orange; off by default, one provider at a time): from orbit dots show where the federated commons has pictures, and below about 60 km its sequences draw as lines from `api.panoramax.xyz` vector tiles. A click on a line opens that sequence's picture nearest the click without moving the camera, flat or 360°, with cones along the sequence around it and ‹ › / ← → following the picture's own links. The 360° and since filters apply, in the lines and in the lookup. The caption names each picture's author and licence (CC BY-SA 4.0, Licence Ouverte 2.0…) and links to it in the Panoramax viewer. HD originals load once, only when the viewer is wider than the 2,048 px version (a panorama: expanded), and every download stops when the photo changes; an image whose header declares more than 64 MP is refused before it decodes. Share links carry it as `0.m.0_0.r.google-0*kartaview-0*panoramax-1` (`0.m.0_0.r.panoramax-1` works too). KartaView's photo viewer is now shared (`photoViewer.js`, `panorama.js`); in it, for KartaView too, Esc clears the selected drive before it collapses the panel. Lines are simplified and drawn within a point budget (a tile's unsimplified lines over Paris hung the tab), decoded in slices so the globe keeps moving, and kept; the cones' tiles have their own connection, and the open picture's tile draws its cones before its neighbours arrive. - Flights and Military Flights highlight emergency transponder broadcasts in fleet billboards, 3D models and Cockpit contacts. Colors update when a status starts or clears. Emergency squawks outrank ADS-B priority statuses; GEV reports minimum fuel and lifeguard without red tint. Cockpit names the code or ADS-B status, and analyst/voice results retain broadcast provenance and the latest known contact time. One omitted ADS-B status poll during a source switch may retain the previous status if the squawk is unchanged; an explicit clear takes effect immediately. Broadcasts are not confirmed incidents. Contributed by [Leo Pechnicki](https://github.com/leopechnicki) (#856). - Street Level: KartaView is the third provider, keyless. Light its chip (purple; off by default, one provider at a time) and zoom in below about 6 km: the lines are the streets KartaView has photos of (z13–14 tiles from `api.kartaview.org`). A click on a line opens the photo nearest the click without moving the camera, flat or 360° (a small WebGL panorama: drag to look, wheel to zoom), with cones along its drive and ‹ › / ← → to step through it. The caption links to the full-size photo (KartaView's photo pages fail for signed-out visitors), and the globe credits "© KartaView contributors, CC BY-SA 4.0". Share links carry it in the provider switches (`0.m.0_0.r.google-0*kartaview-1`). Archived photos (KartaView answers 409) are skipped by the click and by ‹ ›. Shift+← →, ↑ ↓, + − and pinch look around a 360° photo. The open photo's marker is a purple view cone pointing along the drive (KartaView's own compass headings are often 0 or far off). The IMAGERY (ALL / 360° / FLAT) and SINCE filters apply to KartaView as to Mapillary: its lines are filtered by KartaView's own server (its filtered PNG tiles, as a mask over the JSON lines), and the photo a click opens, and the cones, by each photo's projection and upload date. KartaView's SINCE is the upload date (all its server can filter by); a note under the slider says so while KartaView is lit (`sinceBasis: 'upload'` in the provider contract). Mapillary's line coverage and sequence cones are now shared by both (`lineCoverage.js`, `sequenceCones.js`). - Street Level: Google Street View is the second provider. On the Google 3D map (Google's terms keep it off other maps), light its chip (off by default: every panorama is billed to the Google Maps key, which needs the Maps JavaScript API) and click a street, or press OPEN STREET VIEW, to open Google's own panorama in the panel, with its arrows, the address and month in the caption, a link to Google Maps and FOLLOW. Share links carry it in the provider switches (`r.google-1`). One provider is lit at a time (lighting one switches the other off), Mapillary by default since it is free. Street View's panoramas are all 360°, so the IMAGERY and SINCE filters and the legend apply to Mapillary only and hide while GOOGLE STREET VIEW is lit; its globe marker is a Google-blue view cone. - Add an experimental ChatGPT/Codex OAuth option for cloud voice in Provider Settings. API-key voice remains the default. Local sign-in can start from the auth button and reports completion, failure, timeout, or expired credentials. OAuth credentials stay on the server; local routes require loopback access and same-site requests. OAuth sessions retain usage data and show unknown cost; caption transcriptions are counted rather than priced into the API-key cap. The auth button keeps keyboard focus after a mode change, and pending sign-in does not discard text in the key fields. Thanks to [Shayan Khan](https://github.com/devv-shayan) for #621 and [TheSmokeDev](https://github.com/TheSmokeDev) for the credential handling from #653. - **Docker install path.** `docker compose up` builds on CI's Node 24.14.0 image, pinned by digest, and serves the app on `http://localhost:4173` with no local Node install. The repo is bind-mounted and the container runs as the host user (never root), so `.env`, `.gev-cache`, and `.gev-logs` persist on the host exactly as they do under `npm run dev` — Provider Settings included. The launcher (`scripts/docker-start.mjs`) trusts the container's gateway address for that panel, since that is where Docker delivers the host's own browser from; the opt-in behind it, `GEV_KEY_SETUP_TRUSTED_PEERS`, takes exact addresses only and is unset (so loopback-only, unchanged) under every other launcher. Thanks to [jklaze](https://github.com/jklaze) for finding and diagnosing the container-to-host 403, and to [14traits](https://github.com/14traits), [PoBruno](https://github.com/PoBruno) and [milu70hub](https://github.com/milu70hub) for testing on Apple silicon, Docker Engine on Linux, and NAS hosts. - Stdio servers from one install share a panel key so a page read from one process can make requests through another. Concurrent malformed-key repairs now select one winner; unavailable storage or a busy repair retains the logged per-process fallback. Thanks to [Jibran Tahir](https://github.com/jibraaan) for #958, [MarvinNL046](https://github.com/MarvinNL046) for the report and proposed diagnosis in #927, and [kvnloo](https://github.com/kvnloo) for identifying the repair race. Windows/Claude Desktop Cowork confirmation remains outstanding. - Street Level: a street-level imagery layer modelled on the iD editor's photo overlay, with Mapillary as its first provider (free client token, CC BY-SA 4.0 imagery). One right-rail panel holds a chip per provider, shared 360°/flat and captured-since filters, and an embedded viewer with EXPAND, FIT/FILL and FOLLOW (Google 3D only). Coverage lines and image cones are drawn from orbit down to a single street; on Google 3D they sit on the bare earth, refined against the rendered mesh near the camera, so trees and buildings hide them. Share links carry the provider switches, the filters and the panel's collapsed state. A server proxy caches Mapillary coverage tiles (24 h, 1 GiB on disk), refuses cross-site requests, rate-limits per IP and backs off when Mapillary rejects the token or rate-limits. - The CCTV and Street Level panels are portable: drag the header to float the panel, resize it from any edge or corner, and double-click the header to dock it again. The position persists across reloads. - Add Norway's city bikes to the Bike Share layer: Oslo, Bergen and Trondheim Bysykkel (Urban Sharing), Kolumbus Bysykkel in Stavanger and Farte Bysykkel in Skien/Porsgrunn (Entur Mobility), and Bysykkel Lillestrøm (JCDecaux), about 760 stations in all. Every feed is keyless GBFS. `gbfs.urbansharing.com`, `api.entur.io` and `api.cyclocity.fr` join the proxy allowlist; the last two are kept to their GBFS paths. The proxy now sends `Client-Identifier: gods-eye-view` on every request and `ET-Client-Name: gods-eye-view-bikeshare` to Entur, as the operators ask, and accepts Entur's extensionless feed paths. Attributed under NLOD and Licence Ouverte. `get_bike_share` covers the six systems too. - Add Norway's road cameras from Statens vegvesen as a CCTV pack. The camera list is one keyless GeoJSON request to the agency's OGC API view of its DATEX 3.1 CCTV table, so no DATEX account is needed. Every working camera loads (~850; faulty ones are dropped) under one "Norway" category, and the ~135 working cameras that publish HLS play as live video through the existing in-memory relay with the still as fallback. Frames and manifests are pinned to each camera's own path on the agency hosts. `CCTV_VEGVESEN_ENABLED=0` disables the pack, `CCTV_VEGVESEN_MAX_SOURCES` caps it (keeping cameras nearest the largest cities) and `CCTV_VEGVESEN_VIDEO=0` keeps stills only. Attributed under NLOD 2.0. - Add Catalonia (Servei Català de Trànsit) as a keyless CCTV source pack: ~130 cameras from a WFS/GML feed that aggregates SCT's own highway cameras with hotlinked Barcelona and Terrassa municipal cameras, each partner named as a credit beside the shared provider. Ambient-card refresh paced to 3 minutes, matching the empirically observed upstream cadence. `CCTV_CATALONIA_MAX_SOURCES` sets the cap and `CCTV_CATALONIA_ENABLED=0` turns the pack off. The catalog is fetched over https with redirects refused and a 1 MiB body cap, and frame links carrying userinfo or an explicit port, or outside the publisher's frame directory, are rejected even on an allowlisted host. Camera ids come from each frame's SCT camera file or image path rather than the feed's restart-dependent feature id, and rows the feed repeats collapse to one. - Import your own GeoJSON, KML, KMZ and GPX files from DISPLAY or by dropping them onto the app. Show, hide, fly to or remove each file for the session. GeoJSON/GPX draw on the ground; KML retains its styles and explicit heights. Large repeated-style exports use shared local pins, while recorded track vertices and segment gaps stay intact. Imports respect newer camera gestures, leave the shared clock alone, and report malformed or oversized files. File bytes stay on the device; rendered overlays may appear in shared map screenshots. Thanks to [Chase Mills](https://github.com/kapturner) (#925). - GNSS Integrity (Events, voice-addressable, share token `3`) draws navigation accuracy scores from a keyless regional adsb.lol sample; aircraft-level analyst queries are unavailable for these aggregate cells. Cells do not intercept map clicks. Pan/zoom refreshes automatically; feed failures retain the display and explain the next retry. Aircraft-reported quality includes MLAT-positioned contacts after GPS loss, excludes TIS-B/MLAT-derived quality, and locates GPS-loss evidence at the last good GNSS position when available. Scores discount one bad aircraft per cell and retain 30 minutes of visited-view evidence; they do not confirm jamming. See [method and limits](DATA_SOURCES.md#gnss-integrity). Contributed by [Leo Pechnicki](https://github.com/leopechnicki) (#855). - Live HLS cameras play on a page opened over plain HTTP from another machine (`HOST=0.0.0.0`). The client lease id came from `crypto.randomUUID`, which browsers only expose in secure contexts, so starting a live feed threw before playback. The id now falls back to a v4 UUID built from `crypto.getRandomValues`, which the server's lease check accepts. - Move Google geocoding behind the local server. Forward and reverse lookups now go through `/api/google/geocode` and `/api/google/reverse-geocode` with the server key, joining Places and Street View. Google's Geocoding web service refuses referrer-restricted keys, so the previous browser call left `SECURITY.md`'s advice and working search mutually exclusive: the bundled browser key had to be unrestricted for search to work at all. That key now needs only the Map Tiles API and the Maps JavaScript API (Street View). Keyless sessions and the Photon/Nominatim fallback order are unchanged. ## [0.2.1] — 2026-10-02 — God's Eye View through Your Agent (with security fixes and other features) - Ship each bundled data pack once. The region, marine, admin-boundary, county, military-name and neighborhood packs were emitted twice by the production build, as the JSON the browser fetches and as an unused JavaScript copy; `dist/` drops from 54 MB to 42 MB. Under Node the loader reads the JSON file directly (reporting that Node 24.14 or newer is needed on a runtime too old to do so), and a test keeps app code from importing a pack as a module. - Apply the Host check before the app's own routes. Vite installs its Host check after the middleware that plugins add, so the provider and `/api` routes used to answer any Host, including a DNS-rebinding name, in every mode. A first-running middleware now applies the same allowed hosts on the dev and preview servers. - Refuse cross-site browser requests to the cost-bearing and log endpoints (`/api/realtime/token`, `/api/openai/hud-summary`, `/api/google/nearby-places`, `/api/google/text-search`, `/api/realtime/debug-log`): a foreign or opaque Origin, a cross-site `Sec-Fetch-Site`, or proxy forwarding headers get 403, while loopback tools and LAN use keep working. The dev and preview servers send one shared Content-Security-Policy (James Sumpter, #242). - The voice debug log records the server's own time: a record can no longer supply its `loggedAt`. The dev and preview servers also send `X-Content-Type-Options: nosniff` (findings by Sunil, #710). - Keep the Host-header check when binding to all interfaces. `HOST=0.0.0.0` used to accept any Host; the dev and preview servers now accept IP addresses, `localhost` and the LAN hostnames listed in `GEV_ALLOWED_HOSTS` (suffix and wildcard entries are ignored), which also keeps DNS-rebinding names out in LAN mode. The `.local` suffix is no longer accepted by default; list such a name explicitly (Puspo Aditya, #97, fixes #21). - Throttle the cost-bearing proxies by default instead of on request. The OpenAI endpoints (`/api/realtime/token`, `/api/openai/hud-summary`) now allow 30 requests per minute per client IP and the Google Places endpoints (`/api/google/nearby-places`, `/api/google/text-search`) 120 — the caps the Pinokio build already ships, so the packaged app is unaffected and only an unconfigured server changes, from unlimited to what the product already runs with. `GEV_RATELIMIT_OPENAI_PER_MIN` and `GEV_RATELIMIT_GOOGLE_PER_MIN` still override the caps, and exactly `0` disables them; a value that cannot be read as a number now falls back to the default rather than to unlimited, so a typo cannot silently disarm the guard (daikaginza, #683). - Tighten the local MCP server and embed mode. The panel's `panel_request` needs the key in its MCP server's panel page, and refuses Provider Settings, credential and model endpoints, `/mcp` and development server routes in any letter case, encoding or dot suffix; panels on one server share six requests in flight, and further requests wait their turn. `/mcp` applies Provider Settings' proxy and sharing checks, requires a Host on the port it reached and an Origin from that host, and times out request bodies after 30 seconds; stdio honors `notifications/cancelled`. Embed mode is no longer framable unless `GEV_EMBED_FRAME_ANCESTORS` allows the framing page, and view answers go only to the origin that sent the view. SECURITY.md describes the MCP surface and the panel's browser keys. - Cockpit now enters on the existing matching map style while keeping one fixed, duplicate-free carousel over `Normal / CRT / NVG / FLIR / Anime / Noir / Snow`. Normal remains a real unfiltered option; Cockpit-only choices still restore the captured map style through both Exit Cockpit and Reset. - Cyber's compact right-rail and Cockpit utility buttons now center their glyphs vertically and share the same inset and edge alignment. - Keep Cyber Voice help/error popups and Location/Visual Presets pins clear of their decorative frames. Leave space above attribution for its full logo row. - Add an intentionally future-facing, opt-in panel surface contract for new panels to inherit compatible Normal, Cyber and Cockpit styling. Its first production adopter will land separately after this change. - Restore the user's previous visual preset when they explicitly switch from Cyber to another HUD layout, without overriding scene or shared-link state. - Move the aligned Cyber side-panel rails upward on desktop so the left stack clears the lower coordinate card; keep Cockpit's independent visor layout. ## [0.2.0] — 2026-10-02 — God's Eye View through Your Agent - Show God's Eye View inside AI conversations. Answers that can be shown include a view (camera, layers, style, map, marks, something to follow), and `show_in_gods_eye_view` displays it as the live globe in clients that support MCP Apps, such as Claude Desktop and the Codex and ChatGPT desktop apps, and as a link everywhere else. The panel loads the app's panel build (`npm run build:panel`) and its data through the MCP server, so a local server needs no HTTPS or tunnel. `?embed=1` shows the globe alone for pages that frame the app. - Add tools for language-model clients and a local MCP server, served over stdio by `npm run mcp` and over HTTP at `/mcp` on the development and preview servers for local requests only. `npm run mcp` serves earthquake, active-fire, launch, aircraft, ship, satellite, camera, radio, place, routing, bike-share, transit, traffic, weather, cyclone, fire-perimeter, terrain, installation and map-feature queries, plus a situation brief, over stdio to clients such as Claude Code, reading from a running app. Tools are defined once in `gods-eye-view/tools`, reuse the layers' source factories, and are exposed through the protocol adapter in `gods-eye-view/tools/mcp`. The catalog also covers weather maps, wind, recent imagery, submarine cables, license plate reader cameras, datacenters and dams, the Bhote Koshi flood, military awareness and links that open the app over an area with layers on. Voice offers the same queries next to its app actions. - Public Overpass instances are no longer used by default. Street Traffic roads come from TomTom flow tiles, OpenFreeMap vector tiles, or both, chosen on the layer row (TomTom / OSM / Hybrid) or with `?trafficRoads=`. With a TomTom key the default is Hybrid: TomTom roads with live flow, plus OpenFreeMap roads TomTom does not cover, simulated. Without a key every choice draws OpenFreeMap roads. TomTom mode shows only roads with flow; OSM mode matches TomTom flow onto OpenFreeMap roads for congestion colors, speeds and closures, and unmatched roads stay simulated. Road failures name OpenFreeMap and retain HTTP status or timeout reasons separately from TomTom. Flow coverage counts rendered dots on roads with flow; mapped military areas come from OpenFreeMap and follow settled camera changes with cached tiles and retained site entities. Superseded requests preserve the next view’s pending load. Tile and API transports can be injected independently; the optional Overpass ALPR adapter remains available. OSM-derived layers share one attribution entry and a persistent inline map credit, including routing, Warendorf cameras, datacenters, dams and the Nepal locator. Military areas use bundled Overture/OSM names; wide views show bounded, decluttered named points that follow camera motion while Contacts holds a subject, using the shared world-overlay host for wide-point and polygon titles. Polygons appear while names load; cancelled views cannot publish late names, and stalled name downloads can retry. Merged groups keep their identity and parent name when a pan hides the largest member. Late names reconcile ids across zooms while retaining selection and marker ownership. Wide named points remain visible until matching close polygons take over. Installation titles share datacenter/dam card arbitration and keep incumbents while panning. Selecting an installation replaces its label with one card; deselection restores it. Selected footprints receive a translucent fill draped on the active map surface. ALPR cameras come from an hourly OpenStreetMap extract (US and Canada). Features without a replacement say they are unavailable; area and footprint annotations check once whether an Overpass instance is configured and skip the query when none is. Area annotations outline countries, states and provinces (Natural Earth, including UK constituent countries) and US counties (US Census Bureau) from bundled data, with no lookup. County names are disambiguated across countries by aliases, qualifiers and geography. `OVERPASS_UPSTREAMS` sets an Overpass instance you run or pay for. The cockpit regional brief resolves regions from bundled Natural Earth data instead of Nominatim. Traffic starts on enable and paints locally grounded roads incrementally, shares concurrent tile requests and reuses validated heights across pans. Camera moves and arriving tiles retain existing traffic dots on their roads; budget changes fade in/out incrementally, height refinements ease vertically, and live flow changes color and speed in place. The traffic footprint follows the reticle square at oblique angles, with cached detailed near tiles and coarse distant roads. Failed detail tiles retain coarse roads and retry at most three times. Road-pass deadlines also cancel queued tile paints and terrain callbacks; off-screen height corrections cannot hold loading open, and visible corrections stay pixel-limited at canvas and camera-plane boundaries. Completed road snapshots replace streamed previews without duplicating roads. Unresolved previews no longer delay or suppress detailed street roads. Road admission excludes private, parking, walking and unknown traffic categories; OpenStreetMap service ways and tunnels no longer receive surface vehicles. Detail tiles load alongside previews, arrival bypasses the movement debounce, and geographically validated rendered depth avoids repeated mesh redraws. Traffic releases surface-frame listeners on disable/destroy and reuses unchanged surface identities without frame-by-frame allocations. Grounded dots respect building occlusion instead of drawing through roofs, and the traffic status chip reports completion without a delayed text animation. Short road chunks and local surface elevation keep the budget on visible streets in elevated cities. Congestion and closures respect travel direction. ALPR distinguishes unsupported coverage from empty results and asks for zoom-in before exceeding its tile budget. Installation footprints retain visible fragments without joining separate parcels across zooms or across quantization gaps between different mapped identities. Keyless terrain tiles retry HTTP 429 and transient gateway failures with bounded, shared backoff. Operator-configured Overpass area and footprint queries retain relation member geometry so their outlines remain available. Contacts filters mapped installations to a true 100 km surface radius around the current tracked subject, including in Cockpit, instead of "?" or nothing. Search arrivals frame against the resolved ground and lift the eye above the rendered surface, so Camp Mabry and Denver no longer land underground (Milan Khanal, #118). Arrival corrections yield to new camera owners and are cancelled on layer/app teardown. ALPR floor preparation and marker placement share terrain requests, cancelled when the layer is disabled. Map-source changes reposition every ALPR marker without replacing entities. ALPR loads whole-city views from z9-z12 tiles, drops native ground wedges and clamping, keeps frame time with ALPR on within a few percent of ALPR off, seats nearby badges on the rendered surface and says when no loaded camera is on screen. - CCTV cameras whose bearing is a guess now say so. Packs mark bearings derived from a hash of the camera id as `headingConfidence: 'low'`, but nothing read the flag, so roughly 70% of a default catalog rendered like surveyed facings. The HUD now reads `HDG n° (ESTIMATED)` and the coverage wireframe draws dashed; manual calibrations and curated poses are never marked estimated (bassem chagra, #643). - Report which upstream declined a Street Traffic road load. The layer row now reads `Overpass rate-limited`, `Overpass timed out`, or `Overpass refused the road query (HTTP 406)` instead of a general "Road data temporarily unavailable", so a reader is not sent to check a TomTom key when the public OpenStreetMap mirrors are the side that failed. The proxy's own 502 (every mirror unreachable) and 503 (local limiter busy) read `Overpass mirrors unreachable` and `Overpass temporarily unavailable`. Failures the layer cannot classify keep the general line (daikaginza, #665). - Bound the client terrain-height cache at 20 000 entries with least-recently-used eviction, so a long session no longer retains every coordinate it ever resolved. Consumer reads promote their entry and a batch still reports every point it resolved (Pedro Lobato, #594). - Release CCTV media streams whose upstream falls silent after answering. The 15-second media deadline covered only the wait for response headers, so a camera that replied and then stopped sending held both the proxy connection and its upstream socket open for as long as the camera host allowed; the declared `Content-Length` ceiling was the only body bound, and a chunked or length-less body had none. A 30-second idle deadline now bounds the gap between upstream chunks and releases a body that has gone silent. It is rescheduled while the response is still waiting to drain, so a viewer on a slow link is not mistaken for a dead camera; live feeds are unaffected (Ethan Stoner, #688). - Aircraft track backfill (`/api/opensky-track`, `/api/adsblol/trace`) now answers 502 when the upstream body exceeds the 5 MB cap, instead of a 200 whose error body the client read as an empty track. The failure is cached like other upstream errors, so retries inside the 60 s window do not spend OpenSky credits (Raushankumar0720, #720, #722). - Saving a key from Provider Settings works again on Macs where Nix or Homebrew coreutils sit ahead of `/bin` on `PATH`. The credential hardener now spawns Apple's `/bin/chmod -N` by absolute path; GNU `chmod` has no `-N`, so the ACL strip failed closed and every save was refused (Arthur Bogaart, #694). - Render on iPad and iPhone instead of stopping with "An error occurred while rendering." Cesium's per-vertex model atmosphere binds shader `out` parameters directly to varyings, which Apple's Metal/ANGLE backend cannot link, so the program failed and the render loop was torn down. The stage is now kept out of the pipeline on affected devices by clearing `scene.fog.renderable`, which leaves `fog.enabled` — and the fog density that drives 3D Tiles refinement — untouched. Detection is a WebGL2 link probe of the same pattern, so a future driver fix restores the effect with no code change, with iOS/iPadOS detection as a backstop. Sky atmosphere and the ground-atmosphere fragment path route through locals and are unaffected; affected devices lose distance fog on 3D tiles and on the globe basemaps. `src/app/atmosphereCompat.test.mjs` pins the probe, the platform matrix and the `renderable`-not-`enabled` choice (KnottyDyes, #705). - Make share-link layer tokens durable allocations instead of ad hoc picks. Existing one-character mappings are pinned permanently, while new layers use the next free single-character digit, then two-character base-36 tokens. Authors record each token in the permanent JSON ledger after running `npm run layer-token:next -- ` on a rebased branch. `npm run layer-token:check -- --base-ref origin/main` guards published assignments and allocation order in pull-request CI. Existing v2 links keep their exact meaning. Malformed enabled-layer lists now reject the whole layer payload instead of restoring a partial list. A QA-only browser fixture exercises the future two-character path after a fixture-only exhausted-digit scenario, without reserving `00` in production. - Region scopes in voice analyst queries ("in the Gulf of Mexico", "over the Alps") work again in the dev server: the bundled Natural Earth and neighborhood packs are fetched as JSON in the browser (`src/data/bundledJson.js`). When a region is not in the bundled packs, the geocode and admin-boundary fallback answers `region-timeout` after 3 s instead of holding the reply. - Transit and Directions rows repaint as soon as their data lands again: `refreshLayerStats()` now lives on the layer lifecycle, not only on the compatibility facade. `scripts/qa-radio.mjs` uses it instead of a private panel method. - On phones the title bar sits 16 px from the top so both Radio broadcast waves stay on-screen. - Keep Cyber right-rail panels mutually exclusive and Display, CCTV and Context headers and frames fixed during content scrolling. Restore Radio's nested Context placement and compact player. Add Cyber Sonar voice controls with settings and effect-state readback. Keep keyboard-focus outlines visible inside Cyber's clipped map and cockpit expand/collapse buttons, with a matching red hover border. - Add the opt-in Cyber HUD layout with coordinated map and cockpit panel styling. Display exposes Sonar on/off, rings, range, power, opacity and sector. Native point, billboard and label highlighting uses GPU draw commands; there is no scene-dimming effect selector. Unsupported shaders retain native contact rendering, and leaving Cyber restores the standard shell and contact treatment. - Add a **Recent Imagery** data layer (NASA GIBS · HLS + VIIRS, keyless). Select a box (drag, the current view, or around a pin; up to 1,000 km a side) and the right-rail panel lists the last 30 days of Sentinel-2 / Landsat (30 m) and, when switched on, VIIRS daily overview imagery over it, with thumbnails and scene cloud. Three modes: IMAGE shows one day, VS BASEMAP swipes it against the map, A / B swipes two days; a SHOW or A / B chip on each day card pins it, arrow keys preview the focused day while a slot is empty, and no control moves when anything changes. While imagery is shown on Google 3D the map switches to Esri and comes back when it is cleared. Either image exports as a PNG; box, pins, mode and split travel in share links; the NASA acknowledgement is in the credits and `DATA_SOURCES.md`. The swipe is now shared with the Nepal scene (`src/ui/imagerySplit.js`, `src/maps/imageryComparison.js`), and `MapSourceController.subscribe()` reports every settled map switch. ## Unreleased — voice reaches every layer; honest analyst answers - Voice can switch on every shipped data layer (the two scene-driven Bhote Koshi layers stay scene-only), including transit, Recent Imagery, wind, the weather layers, cyclones and mapped installations, and understands their spoken names ("buses", "hurricanes", "military bases"). One voice manifest (`src/voice/layerManifest.js`) generates the tool enums and aliases, and a unit test fails when a new layer has no entry. - `analyst_query` counts up to 250,000 loaded records per layer instead of the first 2,000, and says when a layer went past that (`complete: false`). It also answers over bikeshare stations, transit vehicles, rocket launches, cyclones, ALPR cameras, mapped installations, local ADS-B aircraft and fire perimeters; fire records carry their sensor (VIIRS or MODIS). - Unknown fields, operators, units, value types, scope kinds and invalid centres are refused with the allowed values instead of answering zero or widening to anywhere. A layer that is off, still loading or unavailable is reported as such, not as a count of zero; a partly answerable query is marked `partial`. Distance sorts honour `sortDir`, a written unit such as `altitudeM(ft)` converts, and large rankings no longer sort the whole set. - Results carry `lat`/`lon` for each item and a `display` object with the scope, the feed window (earthquakes and fires cover the last 24 h) and any caveat for the screen. The model is asked to answer in one short phrase. - The weather and Recent Imagery panels can be opened by voice. ## Unreleased — local receiver feeds ### Local receiver feeds - The Local ADS-B layer also reads local 1090 MHz and 978 MHz UAT decoder feeds: the `aircraft.json` that dump1090-fa, readsb, tar1090 or skyaware978 serves. Configure them server-side with `LOCAL_RECEIVER_FEEDS` (`band=url`, comma-separated); there is no feed editing in the browser. Hosts must be loopback, RFC1918, `localhost` or `*.local`, the scheme http or https and the path must end in `aircraft.json`; any other entry is logged at startup, reported `invalid` and never fetched. - Add `GET /api/local-receivers/aircraft`. It reads every configured feed in parallel (2 s timeout, redirects refused, 2 MB body cap, about 1 s of shared cache) and reports each feed `live`, `stale` (its own `now` is over 10 s old), `unreachable` or `invalid`. Unconfigured, it answers `{ configured: false }` and fetches nothing. Upstream error text is never returned. - The layer merges browser-SDR and feed aircraft by ICAO, keeping the newest position, polls the route every second only while it is enabled, and remembers which bands and sources heard each aircraft in the last 60 s. The click card names them (for example "Heard by your receiver · 978 MHz UAT · decoder feed"); aircraft heard only on 978 MHz carry a thin ring. The row status covers both inputs ("2 feeds live · 14 heard", "feed 978 unreachable"), and the Local RTL-SDR card shows a read-only decoder-feed line. - While any input is producing aircraft (the browser receiver streaming, or a feed live), the Local ADS-B row stays ON and lists feeds that are not live as a trailing note ("3 heard · USB 5.8 msg/s · feed 1090 stale") instead of showing DEGRADED. - Records carry `band` (`1090`/`978`) and `source` (`webusb`/`feed`). - See `docs/LOCAL-RECEIVERS.md`. ### Local RTL-SDR and Local ADS-B - Add a Local RTL-SDR card to the Radio panel. It connects a USB RTL-SDR in desktop Chrome or Edge through WebUSB and receives broadcast FM (tune, seek, volume) or 1090 MHz ADS-B. Local FM and internet-radio playback never play together: starting one stops the other. - Add a gain control: AUTO or a manual R820T step, remembered per mode. ADS-B defaults to 28.0 dB (the earlier 20.7 dB gave about 1 msg/s against about 9 at 28.0 dB on the same antenna; a stored choice still wins), FM to AUTO; changes apply without reconnecting. In ADS-B mode the card shows CRC-valid messages per second, aircraft heard, aircraft positioned and the IQ level. - Prefer the ADS-B/1090 MHz channel of a dual-channel receiver, remember an explicitly chosen device per mode, and add CHANGE DEVICE to reopen the WebUSB picker. - Add the Local ADS-B layer (`local-adsb`, off by default, not part of share links). Aircraft heard by the receiver draw in magenta beside public Flights; a marker drops when its position is 60 s old and the aircraft is forgotten after 60 s without a message. Clicking one opens a card; markers are not camera-followed. Voice `set_layer_visibility` accepts `local-adsb`. - Normalize local ADS-B into one record shape, with a pure adapter for dump1090/readsb `aircraft.json` documents. - Add `@jtarrio/webrtlsdr` and `@jtarrio/signals` (Apache-2.0); see `THIRD_PARTY_NOTICES.md`. ### Weather review - On 3D Tiles, draw a 4096×2048 detail window around the view on each observed-weather shell except global infrared, sampled by the shell's own surface. It follows the view on camera move end, keeps its place while the view stays near its centre, and hides until its image is ready after a move; an older frame's detail stays over at most one newer frame. The image proxy accepts a 2:1 `bbox` inside the product bounds, rounded to 0.25°. Lightning's whole-extent image is now 4096×2048; each shell caches up to 128 MiB of decoded images. - On 3D Tiles, show observed weather and the wind color field as raised, translucent shells (5.0–6.6 km, lightning highest) with one full-extent image per frame instead of draping onto tiles; they show at any camera height. Globe hosts are unchanged. The weather image proxy serves every product (radar and regional infrared up to 4096×2048, lightning and global infrared up to 2048×1024) with a size parameter and a 16 MiB cap. Accept bounded tile sizes in the proxy with separate immutable cache entries. - Cache exact-time weather images and tiles for 24 hours. Retain up to 6 decoded global mosaics per renderer and warm the next observation during playback; tile prefetch is bounded to eight requests and cancels when suspended. - Move weather times, coverage, legends and cyclone advisory details into keyed right-rail cards; left rows keep status and configuration. Use one native observed-history timeline with local preview and coalesced drag commits. - Add reusable rail card and timeline components. Keep panel collapse, count, hidden-empty behavior and first-appearance expansion. - Show wind unit controls beside speed legends and inside inspection readings; changing units preserves the sampled location and open reading. - Name satellite imagery Satellite clouds, with Clouds only / Full image modes and explicit regional coverage. Existing share parameters are unchanged. - Share one observed history clock across radar, infrared and lightning. Step through their union timeline with bounded nearest-at-or-before selection; hide products without an eligible frame. Latest uses each product's newest observation; playback waits for all frame loads to settle before advancing. - Label wind as a forecast that does not follow observed history. Keep history transient and product readouts synchronized. - Keep Google 3D Tiles drawing while draped weather imagery loads and retain the old observation until the replacement has rendered. - Decode one bounded global infrared mosaic per frame on both map hosts, then crop local tiles to avoid request-dependent brightness seams. - Add Clouds only / Full image controls and share-link state. Filtered mode uses a soft linear-brightness alpha ramp from 0.40 to 0.70 around the old 0.55 cut. - Dock the weather summary in the right rail with standard panel collapse and drag chrome. - Filter infrared brightness so cold cloud tops stand out; this is a display filter, not a cloud mask. - Retry throttled weather tiles up to three times per tile. - Cull regional wind batches per frame, fade curves below 60 km, and stop idle rendering when no curve is visible. - Fade the wind color field below ~1,200 km camera height and hide it at 200 km. On 3D Tiles, update alpha in 0.1 steps only at camera move end or installation; globe imagery keeps its smooth per-frame fade. - Hide cyclone markers, labels, tracks and cones beyond the horizon on every map source. - Reserve stable weather status space and coalesce panel refreshes per frame. - Add keyless NOAA/NHC cyclone advisory positions, coherent forecast tracks and uncertainty cones, plus NOAA's observed 15-minute lightning density imagery. Preserve source clocks, basin coverage and explicit pending/stale states. - Make wind default to trails, preserve earlier share-link appearance, retain geometry across scalar changes, and show a compact weather summary with a location marker and selected-field emphasis for forecast inspection. - Add keyless NOAA observed rain radar and infrared satellite layers to Weather, with explicit coverage/freshness, recent observation playback and native Cesium tiles. - Increase desktop wind density to 7,200 paths and improve temperature contrast while retaining the 1,200-path narrow-screen budget and unchanged forecast values. - Expand Wind into a surface-weather prototype: globe-draped speed shading, optional same-run 2 m temperature and mean sea-level pressure, GFS/ECMWF model selection, a numeric legend, wind units, Pause, and a dismissible map-center reading. Keep wind visible when an optional field is unavailable; respect reduced motion and stop animation while hidden or disabled. Bake bounded forecast-following curves once per field and animate their phase on the GPU, with a canvas fallback and globe view lighting owned only while Wind is enabled. Display lift does not change the 10 m forecast level; this adds no cloud volume, radar or forecast-time playback. Native hardware GPU behavior remains unverified. Add feed provenance to analyst/view answers and HUD context while retaining existing response fields and runner ownership (Matt Van Horn, #347). Analyst records for loaded satellites, datacenters and dams, with explicit bounded count/rank coverage (Matt Van Horn, #351). - New Fire Perimeters layer (Events group): live NIFC WFIGS interagency wildfire incident perimeters as ground-clamped polygons with a containment-colored fire line, refreshed every 5 minutes from the public keyless feature service with truncation paging. Clicking a perimeter shows an incident card (acreage, containment, cause, behavior, personnel, county, cost, complex membership) and, when the incident has a state- and recency-verified InciWeb page, a click-through link to it. Recency uses incident page origin and update times because the publication API was retired. The layer is reachable from the panel, voice control, share links (token `2`), and the analyst query engine. WFIGS and InciWeb requests use a capped, cached same-origin proxy with timeouts and a per-client limit. Unchanged refreshes retain geometry; incident-link checks abort on disable or selection change, and the row includes a containment legend. - Remove the spurious scrollbars that appeared on both panel stacks at narrow widths (720px and below) as soon as a panel was expanded. The stacks scroll vertically there, and each panel's decorative glow, absolutely positioned with a negative inset, became 18–20px of scrollable overflow on both axes: a horizontal scrollbar band under the expanded CCTV, Context, Data Layers or Scenes panel plus a vertical scrollbar that scrolled nothing but glow. The narrow-screen rules now pin the glow to its panel box; the stacks still scroll for genuinely tall content such as an expanded DISPLAY panel, and the Context radio popover is not clipped. `src/ui/panelRails.test.mjs` pins the rule against every 720px media block. - Enable responsive trackpad pinch zoom on the globe. Browser pixel-mode `Ctrl+wheel` pinch gestures now reach Cesium with bounded amplification, while ordinary wheel, line-mode and touch-pinch inputs retain their existing behavior; the listener is removed with the application scene. - Report AIS speed and course that carry the standard "not available" code as unknown instead of 102.3 knots and 360 degrees. Genuine readings, including a stopped vessel's zero and the highest encodable values, are unchanged. - Render native `