Merge branch 'german/right-rail-vertical-tabs' of github.com:bilawalsidhu/gods-eye-view into worktree-right-rail-vertical-tabs

Main removed the compact Radio player and its Context header launcher
(66e19f0c) and the Operator HUD layout (8b2c6993). The right rail follows:

- The tool slot under the tabs (#right-rail-tools) and its launcher styles
  are gone; the strip's column holds only the tablist.
- Main's Radio placement, bindings and markup tests are taken as they are;
  the Details button reveal and the launcher state sync go with the player.
- The Radio reveal after Enable keeps the branch's scrollend landing, folded
  back into main's single method.
- A radio pick still reopens a closed Context in every theme (the early
  owner reveal in panelChrome), so main's non-Cyber block is dropped.
- The one-owner rail tests run over Tactical, Minimal and Cyber.
- CURRENT-STATE and the changelog fragment no longer mention the compact
  launcher or the slot.

.env.example

@@ -115,7 +115,8 @@ GEMINI_LIVE_MODEL=gemini-3.8-live
 # Client Token). Client-exposed by design, like GOOGLE_MAPS_API_KEY.
 MAPILLARY_CLIENT_TOKEN=
 
-# Optional: OpenSky auth mode (oauth | basic | auto | anon)
+# Optional: OpenSky auth mode (oauth | auto | anon). OpenSky retired
+# username/password (basic) sign-in on 2026-03-18; "basic" now loads anonymously.
 # Default: oauth — requires client credentials below
 # Set to "anon" to skip aircraft auth (rate-limited but works)
 OPENSKY_AUTH_MODE=oauth
@@ -128,7 +129,9 @@ OPENSKY_CLIENT_SECRET=
 # Optional paid Patreon tokens raise request limits; there is no free API key.
 LL2_API_TOKEN=
 
-# Optional: OpenSky credentials JSON file path (alternative to above)
+# Optional: OpenSky credentials JSON file path, used when the two values above
+# are empty: the credentials.json your OpenSky account page downloads when you
+# create an API client. Use an absolute path for compatibility with launchers.
 # OPENSKY_CREDENTIALS_FILE=/path/to/credentials.json
 
 # Optional: dev server config
@@ -253,6 +256,8 @@ AISSTREAM_API_KEY=
 # CCTV_TAIWAN_ENABLED=1                                # set 0 to skip Taiwan Freeway Bureau (MOTC) road cameras
 # CCTV_TAIWAN_MAX_SOURCES=600                          # cap Taiwan freeway cameras (1-2000); no API key required
 # CCTV_TAIWAN_URL=                                     # override the Freeway Bureau MOTC 2.0 CCTV.xml URL
+# CCTV_A22_ENABLED=1                                   # set 0 to disable the Autostrada del Brennero (A22, Italy) webcams
+# CCTV_A22_URL=                                        # override the Open Data Hub A22 webcam catalog URL
 # CCTV_MAX_SOURCES=4000                                # catalog-wide ceiling, shared round-robin across packs
 # CCTV_PREFER_AUSTIN=1                                 # prioritize Austin cameras in the registry
 # CCTV_FORCE_AUSTIN=                                   # force live default sources when a source-pack JSON is configured

.github/pull_request_template.md

@@ -0,0 +1,59 @@
+## What this changes
+
+<!-- One or two sentences: what changed and why. Link the issue if there is one. -->
+
+## How I verified it
+
+- [ ] `npm run build`
+- [ ] `npm test`
+- [ ] `npm run test:track` (dev server running)
+- [ ] Feature gate for the area I touched: <!-- e.g. `node scripts/qa-radio.mjs`, or "none applies" -->
+
+<!-- Screenshots are welcome for anything visual. -->
+
+## New layer checklist
+
+<!--
+Fill this in if the PR adds a new data layer. Delete the whole section if it doesn't.
+See "Adding a new layer" in CONTRIBUTING.md.
+-->
+
+**Screenshots**
+
+<!-- At least one screenshot of the layer on the globe, plus its info card or panel if it has one. -->
+
+**Recording**
+
+<!--
+Preferably 15 to 30 seconds: turn the layer on, move around, open a record.
+Drag an .mp4 or .mov in here; GitHub accepts up to 10 MB on free accounts.
+If it's bigger, link to it instead.
+-->
+
+**Proposed category**
+
+<!--
+Which layer-panel group should it sit in? The current groups are in PANEL_GROUPS
+in src/ui/layerPanel.js: Movement, Cameras, Infrastructure, Events, Weather, Utilities.
+If none fits, propose a new group and say why.
+-->
+
+Category:
+
+**Data source and licence**
+
+- Source (provider and endpoint):
+- Licence or terms (link):
+- Attribution shown in the app:
+- Needs a key? (none / optional / required):
+- Fetched at runtime, or bundled in the repo:
+
+<!-- Bundled data must be data we have the right to redistribute. -->
+
+- [ ] Added a row to `DATA_SOURCES.md`
+- [ ] Credit is registered in `src/data/dataCredits.js`
+- [ ] Share-link token assigned with `npm run layer-token:next`, if the layer is shareable
+
+## Docs
+
+- [ ] `docs/CURRENT-STATE.md` updated and a `changelog.d/<pr-number>-<slug>.md` fragment added, or this PR doesn't change runtime behaviour

CHANGELOG.md

@@ -1,11 +1,707 @@
 # Changelog
 
+## [Unreleased]
+
+## [0.3.0] — 2026-10-27 — Street Level, On Your Phone, in Your Language
+
+- Show a Street Level view facing 359.5° or more as 0°. The viewer caption
+  rounded the bearing without wrapping, so a view facing 359.6° read "360°"
+  (Aditya, @Rohilalala, #1431).
+
+- The visual styles and their presets mark their labels with the catalog-free
+  `msg()`, so the share-link codec, and any server that loads it, no longer
+  bundles every translation catalog (about 0.9 MB) (samehkhamis, #1421).
+
+- Keep a location search that found nothing, or failed, in the field so it can
+  be corrected: the query stays, focused and selected, and a persistent
+  announced message under the search row says what to do next, instead of a
+  toast followed by a cleared and closed field (samehkhamis, #1420).
+
+- Hosts can read share links on their server: the share-link codec and the
+  `/share/<code>` address helpers are now package exports,
+  `@gods-eye-view/core/share/view-codec` and `@gods-eye-view/core/share/link-path`
+  (samehkhamis, #1419).
+
+- Share links are now short: the share button makes `/share/<code>` links
+  that open on any copy of the app, follow the aircraft, military aircraft or
+  satellite you were following, and fall back to its last-known position with
+  a notice if it isn't reporting. A mistyped link is refused instead of
+  opening a different view. Long `#v=2` links keep working (samehkhamis, #1418).
+
+- Make Clear All clear the saved and shared layer selection. Layers that a
+  context mode had already switched off no longer stay in the share link and
+  come back on reload (samehkhamis, #1417).
+
+- Restore a share link opened in an already-open tab. Pasting a link into the
+  address bar, following one, or using Back/Forward now moves the camera and
+  restores the style, map, panels and layers instead of changing only the URL
+  (samehkhamis, #1416).
+
+- Add a Scope checkbox and extend feathering to 200%, retaining scope settings
+  across HUD layouts, share links and scenes. First run opens with Scope ON at
+  100% feather; explicit settings and historical links retain their values. Give
+  Tactical, Operator and Minimal text black backplates only when Scope is OFF,
+  including vertical metadata, without changing the original HUD text color, glow or
+  opacity. Scope ON retains its original HUD presentation (bilawalsidhu, #1410).
+  Keep title and tagline positions stable when toggling Scope, include the eye
+  in the title backing, and brighten the two secondary labels only with Scope OFF.
+
+- Remove four modules nothing in the app imports: `src/app/sourceSlot.js`,
+  `src/data/flowTiles.js`, `src/data/issPass.js` and `src/data/localGeojson.js`.
+  The local GeoJSON layer tests now build layers the way the catalog does, so
+  they keep covering `localGeojsonCore.js`. Package exports are unchanged
+  (samehkhamis, #1403).
+
+- Aircraft on the ground keep getting ground-height samples after the
+  computer's clock steps back, instead of waiting for it to catch up
+  (quanticsoul4772, #1399).
+
+- The Sharpen slider at 0 now turns the sharpen pass off instead of still
+  sharpening at a low amount (quanticsoul4772, #1398).
+
+- Show a locally heard aircraft tracking 359.5° or more as TRK 0°. The Local
+  ADS-B card rounded the track without wrapping, so 359.7° read "TRK 360°"
+  (Rudy Celekli, @rudycelekli, #1396).
+
+- Report a fire detection's acquisition time as a UTC timestamp in
+  `get_active_fires`. The tool joined FIRMS's unpadded date and time, so a
+  00:45 UTC detection read "2026-01-01 45"; it now reads
+  `2026-01-01T00:45:00.000Z`. Missing or invalid dates and times remain
+  unknown rather than rolling into another calendar day
+  (Rudy Celekli, @rudycelekli, #1395).
+
+- Report Docker container health with a local HTTP check using Node, with the
+  same port parsing as the launcher (John Rogers, @14traits, #1394).
+
+- Start the Docker install on SELinux hosts such as Fedora and RHEL. Compose now
+  mounts the checkout with `:z`; without it the container could not read `/app`
+  and stopped with "Cannot find module '/app/scripts/docker-start.mjs'"
+  (Anıl Güvenç, @anilguvenc, #1391).
+
+- Render awareness-overlay bearings and courses that round through north as
+  `000°`, rather than `360°` (Rudy Celekli, #1390).
+
+- Show cockpit wind from 359.5° or more as 0°, not 360°. Rounding 359.6°
+  printed "N · 360°" on the local wind direction
+  (Rudy Celekli, @rudycelekli, #1389).
+
+- Show a drawn line of 999.5 m or more as 1.0 km. The draw hint kept metres
+  below 1000, then rounded 999.6 m up to "1000 m"
+  (Rudy Celekli, @rudycelekli, #1388).
+
+- Show a Contacts entry 999.5 m or more away as 1.0 km. The panel kept meters
+  below 1000, then rounded 999.6 m up to "1000 m"
+  (Rudy Celekli, @rudycelekli, #1387).
+
+- Show a route leg of 995 m or more as 1.0 km. The route summary and step
+  cards kept meters below 1000, then rounded 996 m up to "1000 m"
+  (Rudy Celekli, @rudycelekli, #1386).
+
+- Show a route leg of 59.5 seconds or more as 1 min. The route summary and step
+  cards kept seconds below 60, then rounded 59.6 s up to "60 s"
+  (Rudy Celekli, @rudycelekli, #1385).
+
+- The HUD's AI place summary drops a reply that arrives after the camera has
+  started moving, so a summary asked for before a flight no longer names the
+  old place mid-flight. Cancelled or partially typed summaries retry even if the place
+  context stays the same (quanticsoul4772, #1384).
+
+- Reduce repeated work in aircraft detection candidates by caching unchanged
+  callsign/registration text and reusing resolved fleet models. Metadata updates,
+  live positions and tracked-aircraft/model handoffs remain immediate
+  (samehkhamis, #1379).
+
+- Increase touch-first globe zoom sensitivity to three times the default while
+  retaining Cesium collision and distance limits.
+- Reuse one delayed display timestamp per civil-aircraft fleet update and cache
+  extrapolation coordinate frames until their fix coordinates change. Preserve
+  contact counts, movement cadence, tracked motion and ground corrections.
+
+- Turning a layer off frees the memory its entities held. Cesium kept
+  removed layers' draw commands in reused per-pass arrays, so Data Centers
+  kept 116 MiB after it was switched off, submarine cables 74 MiB and dams
+  30 MiB; they now keep 13, 9 and 9 MiB (quanticsoul4772, #1367).
+
+- Aircraft 3D models (Flights, Military Flights, Local ADS-B) skip Cesium's
+  dynamic environment map, a sky render and GPU readback per model. With
+  ~150 models in the scene at Atlanta on Google 3D, GPU time per frame at
+  rest falls from 14.3-14.8 ms to 12.1-12.5 ms; a same-model comparison
+  showed no visible change (quanticsoul4772, #1366).
+
+- Drop the decimal when fire radiative power rounds to 10 MW. A 9.96 MW
+  detection was labeled 10.0 MW because the one-decimal cutoff ran before
+  rounding (Rudy Celekli, @rudycelekli, #1354).
+
+- Count a transit report that is 90 seconds old as one minute. The card kept
+  seconds through 89s, then rounded 90s up to "Reported 2 min ago"
+  (Rudy Celekli, @rudycelekli, #1353).
+
+- Read a destination heading that rounds to north as 000. 359.6° was shown as
+  360° on the destination bearing while the compass tape already uses 000
+  (Rudy Celekli, @rudycelekli, #1352).
+
+- Keep a tracked vessel's speed, course, heading and fix time when AISStream
+  static data arrives; the static message only merges name, type, destination
+  and IMO (rudycelekli, #1351).
+- Apply changed static metadata immediately, retaining known fields when a
+  later static report omits them, without refreshing the vessel's position
+  (samehkhamis, #1351).
+
+- Convert NHC cyclone movement speed from miles per hour to knots, so
+  `movement.speedKt` in cyclone query results is no longer about 15% high
+  (rudycelekli, #1350).
+
+- Label NHC cyclone classifications by their published meanings: `PTC` is a
+  post-tropical cyclone, `PC` a potential tropical cyclone, and subtropical
+  systems arrive as `STS` and `STD` (rudycelekli, #1349).
+
+- Wake staged weather imagery on a 150 ms timer while waiting for readiness,
+  avoiding a continuous render loop and cancelling the wake when work ends
+  (@nu-stats, #1345).
+
+- Phrase slight and sharp ramps as directions, so a ramp reads "slightly left"
+  instead of "on the slightly left", and a lane names its side in both
+  the proxy response and localized browser instructions
+  (Rudy Celekli, @rudycelekli, #1343).
+
+- Keep an impossible wildfire acquisition date off the detection clock, so a
+  fire is not labeled with a later day it did not happen
+  (Rudy Celekli, @rudycelekli, #1342).
+
+- Reject impossible KartaView photo timestamps, so 31 February is unknown
+  instead of rolling forward into March and passing the imagery date filter
+  (Rudy Celekli, @rudycelekli, #1341).
+
+- Read a hemisphere letter that is separated from its number, so a search for
+  `40.7128 N 74.0060 W` flies there instead of falling through to the geocoders
+  (Rudy Celekli, @rudycelekli, #1340).
+
+- Carry HUD LAT/LON seconds that round up to 60.00" into the minutes and
+  degrees, so longitude -122.35 reads `122°21'00.00"W` instead of
+  `122°20'60.00"W` (rudycelekli, #1339).
+
+- Improve touch selection of aircraft and vessels through the shared contact
+  picker, reveal tracked aircraft details when opening Context, support downward
+  swipe dismissal of phone drawers while preserving scrolling and controls, and
+  enlarge the phone logo (samehkhamis, #1338).
+
+- Evict terrain-height cache entries in fetch-time order without repeatedly
+  sorting the full cache, while keeping refreshed points newest and ordering
+  restored entries by their fetch time (daikaginza, #1326).
+
+- Add a phone layout for viewports 720px and narrower: the globe stays full
+  screen and a bottom tab bar (Layers, Cameras, Context, Search, More) opens one
+  panel sheet at a time, keeping attribution visible and scene STOP reachable.
+  Adapted from the phone tab-shell in #203 by blearymoth (samehkhamis, #1325).
+
+- Export the KartaView and Panoramax Street Level providers, so a host composing
+  its own provider list can offer the keyless providers without Mapillary
+  (samehkhamis, #1324).
+- A Mapillary source can take a `graphEndpoint`, a Graph API base that adds the
+  token itself (such as a same-origin proxy). Its sequence lookups go there
+  through the source's transport, and the photo viewer uses MapillaryJS's
+  Graph provider at that endpoint, so no client token is needed in the page
+  (samehkhamis, #1324).
+
+- Remove dead code across the repository: three modules nothing imports
+  (`src/ui.js`, `src/standalone/ui.js`, `src/data/localLayers.js`), exports
+  and locals nothing reads, a duplicate copy of the bundled dams data and an
+  unused ship model. The app no longer builds an unused default wind layer
+  and Bhote Koshi locator layer when it loads. Package exports are unchanged
+  (samehkhamis, #1321).
+
+- Validate provider response formats, strengthen camera source checks, and apply consistent API response protections (samehkhamis, #1317).
+
+- Clarify shared field CSS ownership: CCTV owns calibration editor sizing,
+  while Radio and Cyber supply explicit field palettes without changing the
+  current appearance or native control behavior (mazy1998, #1309).
+
+- Share read-only status badge presentation across CCTV source/frame labels,
+  calibration provenance and Weather coverage, preserving status meanings,
+  palettes, translations and announcements while preparing the view contract
+  for a future Vue migration (mazy1998, #1306).
+
+- Share native dropdown and numeric-field styling across Scene, CCTV, Display
+  and Radio controls, with a shared CCTV number-input builder that preserves
+  existing precision, validation and commit behavior (mazy1998, #1305).
+
+- Point distances wrap longitude differences across the antimeridian, in voice
+  proximity checks and `places_nearby` (quanticsoul4772, #1304).
+
+- `get_wind` flags stale forecasts (`stale`) when the wind proxy serves a
+  cached model run (quanticsoul4772, #1303).
+
+- Give ordinary Scene and CCTV actions shared native buttons with consistent
+  default, destructive and compact styling while preserving their existing
+  behavior and specialized controls (mazy1998, #1302).
+
+- Unify segmented selectors for model coverage, detection allocation, drawing
+  shape, Street View and imagery comparison while preserving their existing
+  behavior. Keep compact labels such as FILL and FLAT on one line, and let
+  collapsed Weather release space to the open rail panel. Reserve the full mode
+  button height in Recent Imagery so keyboard focus is not clipped (mazy1998, #1301).
+
+- Add a shared Voice Preview and Settings panel with browser-local preferences,
+  inactivity controls and accessible floating provider controls on compact layouts;
+  recover inactivity after confirmed audio-less replies, release retired audio
+  observers and keep cost warnings visible outside Settings
+  (manjunath22466, #1299).
+
+- Add Simplified Chinese (zh-CN) to the language picker, with localized dates
+  and readable Chinese labels. Based on translations by @abiyeenzo (#914)
+  and @EDIT-Aeterna (#979).
+  (German, @gekh, #1298).
+
+- Add the S2 GhostMaps layer: S2 Underground's public KMZ intel products
+  (Common Intelligence Picture, 30-day kinetic pull, Border Crisis Map, Iran
+  and Yemen products and the newest incident drop) from
+  github.com/s2underground/GhostMaps, with one chip per product and report
+  cards on click. `/api/ghostmaps` watches the repository's branch head every
+  15 s and pushes each new commit to open pages, which reload only the
+  products that changed (Black Pine Defense).
+- Clear a temporary GhostMaps upstream error and notify open pages when the
+  repository becomes reachable again, including when no new edition was published.
+- Release packed-image resources when a load is cancelled or fails, respect
+  injected or omitted GhostMaps sources, and wait for background cache warm-up
+  before removing provider test fixtures.
+- Include Simplified Chinese translations and keep the combined voice prompt
+  within its existing size limit while retaining all spoken aliases.
+
+- A Street Level provider whose `zoomFor` still answers `{zoom, kind}`, the
+  shape before the core went slim, draws its lines again instead of a silent
+  blank; an overview level or any answer that is not a whole zoom shows the
+  zoom-in hint (asturksever, #1288).
+
+- Give ordinary sliders a shared native control and consistent track, thumb,
+  value, focus and disabled styling while preserving feature behavior and
+  specialized controls (mazy1998, #1287).
+
+- The Street Level SINCE note sits on the value's line, in its type and a
+  size smaller: with KartaView lit it reads ANY DATE (by upload date). It
+  had lost its size variable in the Street Level slim-down and rendered
+  larger than the value, on a line of its own (asturksever, #1286).
+
+- Keep aircraft route labels on the scheduled airport leg instead of accepting
+  its distant great-circle extensions, preserving generous endpoint tolerance
+  across the signed-angle branch cut (rudycelekli, #1284).
+
+- Report cached CelesTrak satellite records as stale in the Data Layers row,
+  preserving separate core and dense catalog provenance through refresh,
+  removal and lifecycle cleanup (rudycelekli, #1283).
+
+- Pause periodic network updates in hidden tabs; the overdue update on return restarts the polling schedule, so the next poll follows one interval later even when that update fails (asturksever, #1282).
+- Report and guard browser visibility during Transit QA so hidden-page polling pauses cannot masquerade as playback regressions (asturksever, #1282).
+- Require each live city to supply its own feed vehicles in Transit QA; retained vehicles cannot qualify another city (asturksever, #1282).
+- Bound the Transit card-anchor probe by observed poll coverage instead of a fixed 20-second window (asturksever, #1282).
+- Keep visible-page Transit probes focused through the browser testing API (asturksever, #1282).
+- Add a real-browser regression gate for hidden-tab periodic work, explicit refresh, resume and teardown (asturksever, #1282).
+- Restore minimized test windows before screenshots so native compositor pauses cannot stall browser acceptance (asturksever, #1282).
+
+- Hold rendering only for animated content (asturksever, #1281).
+- Exercise current vector road sources and published camera bounds in Traffic fixture QA (asturksever, #1281).
+- Establish browser-level foreground visibility for Traffic QA and reject hidden-page samples (asturksever, #1281).
+- Supply CORS headers on cross-origin traffic fixtures and report browser exceptions without disabling browser security (asturksever, #1281).
+- Isolate the Traffic keyless browser scenario from the keyed page’s workers and intercepted cache (asturksever, #1281).
+- Restore minimized test windows before screenshots so native compositor pauses cannot stall browser acceptance (asturksever, #1281).
+- Intercept only Traffic provider URLs, leaving Cesium worker and module loading untouched (asturksever, #1281).
+- Settle an unfinished Traffic height correction when the last animated point leaves, so the layer stops reporting loading once its render hold is released (asturksever, #1281).
+
+- Throttle mission hover picks with a trailing check for the last pointer position, and clear stale cursors (asturksever, #1279).
+
+- Reserve singleflight before disk cache reads (asturksever, #1278).
+
+- Bound each height request to one upstream chunk (asturksever, #1276).
+
+- Preserve enable during first-load replacement (asturksever, #1275).
+- Release disabled weather camera listeners and make teardown resource leaks fail the browser probe (asturksever, #1275).
+- Keep visible-page weather teardown probes focused through the browser testing API (asturksever, #1275).
+
+- Scan the kml root delimiter in bounded time (asturksever, #1274).
+
+- Retire unavailable history and keep local trails (asturksever, #1273).
+
+- Normalize geocoder bias across the antimeridian (asturksever, #1272).
+
+- Reject inherited style keys during restore (asturksever, #1271).
+
+- Respect provider cooldowns and bound tle groups (asturksever, #1270).
+
+- Coalesce refreshes and cool down opensky failures (asturksever, #1269).
+
+- Normalize station tags and retain valid mixed rows; skipped malformed rows still report degraded coverage (asturksever, #1268).
+- Correct Radio QA push-to-talk setup to target the mounted voice controller (asturksever, #1268).
+
+- Honor Docker Compose trusted-peer and allowed-host settings from the shell
+  or project `.env`, and let `GEV_KEY_SETUP_TRUSTED_PEERS=none` disable gateway
+  access to Provider Settings before Vite starts (asturksever, #1265).
+
+- Prevent malformed Overpass filters from blocking the local server, and reject
+  cross-site or excessive query requests before reading their bodies
+  (asturksever, #1264; fixes #1248).
+- Release unread responses from the optional Google-token probe so keyless
+  browser validation can settle; the Overpass gate recognizes only that probe's
+  expected 404 as an unavailable capability (asturksever, #1264).
+- Make tracking arrival checks respect the aircraft update cadence while checking
+  orientation on the first reveal, avoiding false failures at faster render
+  rates (asturksever, #1264).
+
+- The terrain-heights bounds tests no longer read the checkout's
+  `.gev-cache/terrain-heights.json`. Each test gets a cache file of its own, so
+  `npm test` no longer fails after the dev server has cached terrain near
+  Austin (KnottyDyes, #1244).
+
+- Replace the blocky JPEG sky around the globe with the 9,096 stars of the
+  Yale Bright Star Catalogue, drawn as sharp points where they are at the
+  scene time, over a soft Milky Way from ESO/S. Brunier (CC BY 4.0). The Sun
+  and Moon stay; the anime style hides the Milky Way. Assets: 296 kB (gekh,
+  #1243).
+
+- `get_traffic_flow` flags stale cached TomTom tiles and reports the oldest
+  tile fetch time (`stale`, `oldest_tile_at`), with pending freshness metadata
+  released on failed or cancelled tile reads (quanticsoul4772, #1239).
+
+- Add Taiwan's national freeway cameras from the Freeway Bureau, MOTC to CCTV:
+  ~1,800 cameras read at runtime from the official MOTC 2.0 open-data table,
+  with on-demand snapshots and attribution. No API key is required; set
+  `CCTV_TAIWAN_ENABLED=0` to skip it (419vive, #1237).
+
+- Require a geocoded containment anchor for ambiguous analyst region names,
+  preserve boundary provenance and cancellation safety, and retain exact-name
+  precedence for natural outlines (manjunath22466, #1235).
+
+- Serve the camera catalog while it refreshes. An expired catalog made every
+  camera request wait for the slowest pack to reload; it is now answered at
+  once while one background refresh runs, so only the first load waits. Estonia's
+  slow Tarktee feeds get 30 s instead of 15 s, so the pack no longer drops out
+  on about a third of loads (quanticsoul4772, #1234).
+
+- Harden the Tarktee (Estonia) DATEX2 camera catalog fetches: refuse redirects,
+  cancel both response streams when either response fails or overflows the 4 MB
+  byte cap, and deduplicate camera IDs before per-pack prioritization
+  (yaka0007, #1233).
+
+- Skip bike-share stations with missing, blank or invalid coordinates instead
+  of placing them at coerced zero coordinates or accepting out-of-range values.
+  Explicit zero coordinates and numeric strings remain supported (Bortlesboat, #1232).
+
+- OpenSky sign-in matches what OpenSky accepts since 2026-03-18. The server
+  now reads `OPENSKY_CREDENTIALS_FILE` (the `credentials.json` OpenSky's
+  account page downloads) on every platform, not only through the macOS
+  launcher, and no longer sends retired username/password Basic auth:
+  `OPENSKY_AUTH_MODE=basic` loads anonymously with one warning saying what to
+  set instead (quanticsoul4772, #1229).
+- Credential-file warnings omit parser excerpts and filesystem error details;
+  the path example also works with the macOS launchers.
+
+- Load Ontario 511 cameras again. 511on.ca's camera endpoint now requires a
+  free developer key; set `ONTARIO_511_API_KEY` to enable the pack, which is
+  otherwise skipped with one log line saying where to get a key
+  (quanticsoul4772, #1228).
+
+- The first-run card can be closed on a phone or tablet. "ESC to dismiss" is
+  now a button that closes the card the same way ESC does; touch screens read
+  DISMISS, and phones no longer hide it, so choosing a mission is not the only
+  way out (KnottyDyes, #1226).
+
+- Add continuous globe rotation with direction and speed controls and a globe-fit
+  check before starting (manjunath22466, #1225).
+
+- Open God's Eye View from Pinokio in the system browser using the supported
+  `popout` menu option. The application's framing policy is unchanged
+  (NukeThemAII, #1222).
+
+- Avoid starting or queuing a reply when the local channel rejects a typed OpenAI
+  command, while preserving an earlier accepted deferred input
+  (Manjunath, #1220).
+
+- Keep NASA FIRMS fire and ALPR camera labels English in voice tool results
+  (`track_entity`, `get_entity_context`, pointer context); the voice card still
+  shows them in the interface language (daikaginza, #1207).
+
+- Report actual outcomes when voice enables or disables CCTV through the shared
+  layer lifecycle, including failed and cancelled changes (manjunath22466,
+  #1205).
+
+- Draw CCTV stills at their source aspect on the monitor plane instead of
+  stretching them to the 16:9 canvas. Most DOT cameras publish 4:3 frames, so
+  every still was widened; they are now centered and pillarboxed on the dark
+  the placeholder already ends on (Danielslay86, #1201).
+
+- Color CCTV cameras with a video feed violet. Cameras with an HLS, MP4 or
+  WebM feed were the same cyan as stills, so a DelDOT or Statens vegvesen
+  video camera could only be found by opening it. Stills stay cyan and the
+  active camera stays amber, and focus de-emphasis fades the violet the same
+  way (Danielslay86, #1200).
+
+- Keep Space Missions marked STALE when Launch Library 2 falls back to cached
+  launch data, and return to NOMINAL after a fresh response without discarding
+  retained missions (rudycelekli, #1199).
+
+- Share Launch Library request cache keys across installations refreshing in the
+  same UTC minute, identify the app to the provider, and explain that standard
+  space-missions access needs no key. Optional higher-rate LL2 tokens are paid
+  upgrades; existing local cache and server-only token handling are unchanged
+  (rudycelekli, #1197).
+
+- Add nine Spanish city bike systems to Bike Share and `get_bike_share`: BiciMAD
+  (Madrid), Valenbisi (Valencia), Bizi Zaragoza, Sevici (Seville), BIKI
+  (Valladolid), BiciCoruña, Dbizi (Donostia-San Sebastián), Bilbao Bizi and
+  BicinRivas, about 1,840 stations. Station names read underscores as word
+  breaks, and station capacity counts docks rather than PBSC's geofenced area
+  (ulihhhh, #1190).
+
+- Keep missing launch-pad coordinates unknown so launches use the location
+  fallback or stay off the map instead of appearing at 0°N 0°E. Missing stage
+  flight numbers no longer show "FLIGHT 0"
+  (Rudy Celekli, @rudycelekli, #1186).
+
+- Flights' ground floor works across the antimeridian. The viewer-distance
+  check behind the 150 km floor radius and its copy in the photoreal mesh-floor
+  sampler subtracted longitudes without wrapping, so two points 21 km apart
+  across 180° measured about 38,000 km and low or grounded aircraft just across
+  the line from the viewer were never floored. A contact's display corridor
+  walked a segment across 180° the long way round, spending its cell budget on
+  ground behind the contact, and a contact on the seam lost its cell hysteresis.
+  SEARCH NEARBY SITES on a view across 180° searched Google Places around
+  longitude 0, on the far side of the globe, with a radius sized from the view's
+  height alone; it now searches the view (Aditya, @Rohilalala, #1173).
+
+- Keep missing CCTV numbers unknown instead of reading them as zero. `Number`
+  turns null, blank strings and booleans into 0 or 1, and the camera source
+  list sends an unknown number as JSON null, so a source-pack camera that left
+  out its pose reached the browser as zeros clamped to each field's floor —
+  facing north, pitch −2°, FOV 20°, range 120 m, mount 6 m and ground 0 m —
+  instead of the defaults (id-hash heading, −17°, 74°, 700 m, 24 m and the
+  city's ground); a null or blank position placed the camera at 0,0. The
+  server's `toFiniteNumber` and the browser's `safeNumber` now treat absent,
+  blank and boolean values as missing. The same conversion also stops a
+  Tallinn row with a null heading reading as a confident north-facing camera,
+  a Caltrans camera with a blank elevation losing its 150 m ground prior, and
+  a TfL or Catalonia camera with a null or blank coordinate being kept at 0,0
+  or on the zero meridian (omerbberk, #1172).
+
+- Director shot actions land on the requested shot. A seek to a shot's start
+  could round a hair below it and select the end of the previous shot for some
+  shot counts and durations (Aditya, @Rohilalala, #1171).
+
+- Fire-perimeter queries handle outlines and holes crossing the antimeridian:
+  areas enclosed near ±180° are included, areas at the opposite meridian are
+  excluded, and returned perimeter coordinates stay near the dateline. Incident
+  cards use the same circular longitude mean and compare multipart outline
+  areas along short longitude edges, keeping the card on the largest polygon
+  (Arianna Method, @ariannamethod, #1142).
+
+- Scenes keep the "Scene not saved" status when a capture, update, append or
+  import cannot be saved, and an unreadable saved project no longer overwrites
+  the recovery checkpoint. `startScene()` resolves to its documented result,
+  `afterShotId` works without an explicit scene, and `scenesRun` counts the
+  distinct scenes queued (djabhi31, #1135).
+
+- Label camera-tool Street View fallbacks as historical Google imagery rather
+  than the current camera view; keep unknown frame provenance explicit
+  (rudycelekli, #1118).
+
+- Release superseded Google Street View open waits and suppress metadata
+  requests whose viewer was unmounted while the service loaded (rudycelekli,
+  #1117).
+
+- Exclude aircraft without a reported altitude from requested altitude bands;
+  unfiltered aircraft queries still retain them (rudycelekli, #1115).
+
+- A failed Esri Satellite or keyless terrain load still shows OSM or flat terrain
+  at once, but no longer lasts the whole session: while the fallback is on
+  screen, the real provider is retried in the background (30 seconds, doubling
+  to a 10-minute cap) and replaces it live once it loads. Map switches never
+  wait for a retry (Aditya, @Rohilalala, #1111).
+
+- Skip TLE sets whose line 1 and line 2 carry different catalog numbers, so a
+  spliced catalog cannot pair one satellite's elements with another's; the next
+  valid set still parses (VG31OP, #1101).
+
+- Overpass data whose element tags contain a failure phrase ("timed out",
+  "runtime error", "too many requests" and similar, e.g. a place named "Timed
+  Out Escape Rooms") is returned as data instead of being refused and putting
+  the endpoint on cooldown; upstream failures are read from the remark (Aditya,
+  @Rohilalala, #1097).
+
+- Military aircraft keep their last heading and speed when an adsb.lol row omits
+  `track` or `gs`, instead of turning north and stopping; a grounded row without
+  a speed still reads 0 (Aditya, @Rohilalala, #1096).
+
+- Update DOMPurify to 3.4.17, Sharp to 0.35.5 and source-map-js to 1.2.2 for
+  GHSA-p98j-92pf-mc4p, GHSA-6688-9rhm-gjv2, GHSA-wq5f-xc86-pv6w and
+  GHSA-68fv-2mgg-jv7q; `npm audit` now reports no vulnerabilities (NurstarK,
+  #1094).
+
+- Location search accepts two-dimensional WGS84 `geo:` URIs offline, with
+  the existing coordinate framing and label. Unsupported URI fields are passed
+  to the remaining search providers unchanged (cj-vana, #1071).
+
+- Keyless standalone startup answers an unavailable Google tile-token endpoint
+  with uncached 204 instead of a browser-visible 404. Existing providers take
+  precedence, and unrelated API routes behave as before. (dvilrgamerz, #1066)
+
+- On Windows, `npm run doctor` and the Pinokio install no longer print Node's
+  DEP0190 warning ("Passing args to a child process with shell option true can
+  lead to security vulnerabilities"): npm.cmd's fixed subcommand is now part of
+  the shell command string instead of an argument array (quanticsoul4772, #1057).
+
+- `aircraft_in_area` and `vessels_in_area` take `group_by` and `stats`, so an
+  MCP client can ask which airlines, countries, aircraft types or ship types
+  dominate an area, or the average altitude or speed, over every match instead
+  of estimating from the returned rows. Airlines come from the ICAO designator
+  in each callsign (SWA1234 counts as SWA), so the breakdown works on feeds
+  that report no operator; operator and type are counted only where the feed
+  reports them. Ship types count by family, so AIS codes 70 to 79 are all
+  cargo; type 0 ("not available") and the reserved codes 100 to 255 count as
+  unknown. Altitude and speed stats cover airborne aircraft only, so parked
+  aircraft do not pull the means down. Every vessel answer, `find_vessel`
+  included, now reads AIS ship-type codes as their family and a destination
+  with no letters as unknown (quanticsoul4772, #1056).
+
+- Add Hong Kong Transport Department traffic snapshot cameras as a keyless CCTV
+  source pack: the public DATA.GOV.HK English locations XML, frames pinned to
+  `tdcctv.data.one.gov.hk`, with DATA.GOV.HK Terms of Use attribution. By
+  default nearly the full TD catalog (~1,013 cameras; cap 1,100) loads,
+  prioritized across Hong Kong Island, Kowloon and the New Territories. Headings
+  use the shared id-hash fallback at low confidence. `CCTV_HK_MAX_SOURCES` sets
+  the cap (8–1,200) and `CCTV_HK_ENABLED=0` turns the pack off (JCY2515, #990).
+
+- Cross-site pages can no longer fill the terrain-height cache or spend the
+  visitor's own `/api/terrain/heights` rate-limit quota through the visitor's
+  browser. The route refuses a cross-site `Sec-Fetch-Site` or a foreign or
+  opaque `Origin` before rate limiting, cache access or upstream work. Unlike
+  the cost-bearing routes it still answers same-origin requests that arrive
+  through a reverse proxy, so terrain keeps rendering behind nginx, Caddy or
+  Cloudflare instead of falling back to the geoid (Sunil56224972, daikaginza,
+  #975).
+
+- Street Level is rebuilt around one small provider registry: Mapillary,
+  KartaView, Panoramax and Google Street View share one coverage drawer and
+  one photo viewer, one source lit at a time. Floating and docked panels,
+  FOLLOW, surface modes, the legend and the Mapillary proxy's disk cache are
+  gone; `.gev-cache/mapillary/` from earlier runs is no longer read and can be
+  deleted (gekh, #974).
+
+- Cross-site browser requests can no longer spend the TomTom traffic-tile
+  budget through `/api/tomtom/*`. The shared same-site gate runs before status,
+  cache, and upstream work; same-origin app requests and non-browser local
+  callers remain supported (Sunil56224972, #973).
+
+- Recent Imagery: opening DETAILS scrolls its card into view when it opens below
+  the fold. The panel used to restore the previous scroll position right after
+  the reveal, so the card stayed out of sight (Ian Blenke, #970).
+
+- Harden Vite's filesystem deny list for local-only artifacts: repo `dist/`,
+  `.gev-logs/`, and `.gev-cache/` are denied without blocking dependency
+  `dist/` directories, and checkout paths containing glob metacharacters are
+  escaped before building the root-anchored pattern (blowing-a-raspberry, #948).
+
+- Give each Statens vegvesen camera its own ground height from Kartverket's
+  keyless point-height API (CC BY 4.0) instead of one flat 150 m prior, so
+  mountain-pass cameras no longer sit hundreds of metres below the terrain
+  where neither the point-height prior nor the ground snap resolves. About 850
+  of ~855 cameras get a height; the rest keep the old prior. Requests carry 20
+  points, the most the API answers from its 1 m terrain model, eight at a
+  time; a cold lookup takes about 6–13 s. Cameras over water use the water
+  surface rather than the sea-floor depth the API returns there; for bridge
+  cameras that is still below the deck. Heights are cached for good and misses
+  for 6 h, so a refresh only asks about new or moved cameras. After a
+  failing request (a 408, 429 or 5xx, a network error, a request over 10 s or
+  an unreadable body) the lookup stops and backs off (Retry-After, else
+  30 min, longer than the refresh). The lane waits at most 12 s from its
+  start, and only on a cold cache; a slower first lookup leaves the cameras it
+  had not reached on the flat prior until the next 15-minute refresh, and
+  keeps filling the cache meanwhile.
+  `CCTV_VEGVESEN_HEIGHTS=0` turns it off. Follow-up to #929 (trygvehhh, #945).
+
+- Extract a reusable model-free World Packet from the existing voice
+  `get_current_view_state` owner without restoring disabled layers to the
+  model context. Keep the enabled-only payload, disabled-layer count, source
+  provenance, action result and view-state contract; read the layer roster once
+  per packet; voice retains the speech/card envelope at its own boundary.
+  Credits: original GEV voice/layer contributors and #880 implementation.
+
+- Add optional Gemini Live voice to the standalone app, with a provider chooser,
+  server-held API key, microphone streaming, shared map actions and captions.
+  Switching providers ends the old conversation and preserves the input mode
+  (Manjunath, #872).
+
+- Close the compact Radio disclosure when an adaptive tactical right-rail
+  restore directly expands Context, before Space Missions can be covered.
+  A repeated Context-open request also clears stale disclosure state.
+  Real PanelChrome constructor wiring and the rail reflow path are covered
+  by focused regressions. Credits: kvnloo (#816), raysung-2026's original
+  #804 report, asturksever's review, and quanticsoul4772's independent
+  Windows diagnosis.
+
+- Changelog entries are now one file per pull request. A change adds
+  `changelog.d/<pull request>-<slug>.md` instead of editing the top of
+  `CHANGELOG.md`, which two pull requests in flight could not share — it was the
+  most frequent merge conflict in the open queue, and for six of them the only
+  one. `npm run changelog` splices the directory into `CHANGELOG.md` at release
+  time and empties it; `npm run changelog:check` reports the batch and changes
+  nothing. Fragment text is copied through unchanged (daikaginza, #787).
+
+- Read satellite catalog numbers written in Alpha-5, the TLE spelling of
+  numbers above 99999: a letter for the first two digits, skipping I and O
+  (`A0000` is 100000, `Z9999` is 339999). The satellites layer converted such a
+  field to `NaN`, so every Alpha-5 satellite shared one catalog entry and all
+  but the first were dropped as duplicates; the satellite tools read the same
+  field as no number, so such a satellite could not be found by it. The layer
+  and the tools now decode the field in `src/sources/tle.js`, and reject a
+  malformed one (a sign, decimal point, hex, embedded space or stray letter)
+  instead of reading part of it as a number. This is Alpha-5 TLE
+  compatibility: CelesTrak's TLE feed carries no satellite above 99999, which
+  needs the OMM feed (#1191) (Honorius Neogy, #767, fixes #751).
+
+- The dev server no longer watches `.gev-cache` and `.gev-logs`. Providers write
+  cache files and logs there while the app runs, and none of it is source, so
+  the watcher now skips it; this guards against the DNS-lookup delays heavy
+  cache writes have caused, though no difference was measured on current main
+  (monwiss, #761).
+
+- Bound what a caller can grow through `/api/terrain/heights`. Every distinct
+  5-decimal point was a permanent in-memory entry, a permanent line in an
+  uncapped `.gev-cache/terrain-heights.json`, and a live upstream call, with
+  nothing limiting the rate. The point cache now holds at most 50,000 entries
+  and evicts oldest-first, a cache file above
+  24 MB is not read back, and the route is limited to 90 requests/minute per
+  client (270 global). Evicting a point costs one refetch, never a wrong
+  answer, since terrain does not move. Ordinary use is unaffected: a full
+  `test:track` run drives 10 requests, peaking at 8/min (daikaginza, #686).
+
+- Add FL511 (Florida DOT) traffic cameras as an opt-in CCTV source pack:
+  the statewide ArcGIS catalog, read a page at a time under a byte cap with
+  redirects refused, and frames pinned to FL511's two image hosts over HTTPS.
+  FL511's terms limit its content to individual, personal use, and any other
+  use (a public deployment included) needs FDOT's express written consent, so
+  the pack stays off unless `CCTV_FLORIDA_ENABLED=1`. Headings come from the
+  catalog's direction codes, and camera ids come from the image channel, since
+  the catalog's ID column repeats across regions. `CCTV_FLORIDA_MAX_SOURCES`
+  sets the cap (Danielslay86, #605).
+
+- The client's great-circle distances now come from one shared
+  `src/geoDistance.js` (`greatCircleKm`/`greatCircleMeters`, `{lat, lon}`
+  points). The Earth radius is standardized on 6371.0088 km, so distances shift
+  by about 1.4 ppm and region areas by about 2.8 ppm, and missing or
+  out-of-range points return `Infinity` (onionviolet, #287; Rajojha-1, #749).
+
 - The tracked-aircraft descriptor now publishes `verticalRateMps`, on both the
   civil and military layers, so a consumer reading `getTrackedInfo()` no longer
   has to reach past it into the raw poll record for climb/descent. Reported,
   never derived: an aircraft that has not transmitted a rate reads as `null`
   rather than a level-flight `0`.
 
+- Bound how often the GBFS proxy will relay. `/api/gbfs` already restricted
+  where it could go — https, an allowlisted host, a station feed path, no
+  redirects, a 12-second deadline and a 5 MB body cap — but nothing restricted
+  how often, so the dev server would make unlimited requests at a third-party
+  bikeshare operator on any caller's behalf. The route now admits 120
+  requests/minute per client address, refusing the rest with 429 and
+  `Retry-After` before any outbound fetch. The bikeshare layer needs about 15 a
+  minute with every catalogued system in range, so ordinary use is unchanged.
+
 - 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
@@ -282,8 +978,6 @@
   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
@@ -498,6 +1192,28 @@
   needs only the Map Tiles API and the Maps JavaScript API (Street View). Keyless sessions and the Photon/Nominatim
   fallback order are unchanged.
 
+- 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.
+
 ## [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,
@@ -780,32 +1496,6 @@
   (`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
@@ -948,7 +1638,6 @@
 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
@@ -1225,6 +1914,7 @@ of current runtime behavior, see [`docs/CURRENT-STATE.md`](docs/CURRENT-STATE.md
 
 ### Other changes
 
+
 - Add ECMWF IFS model selection to Wind (#464, thanks @beneduzi), with model-scoped forecast-step caches, cancellation of replaced requests, and separate issue/valid timestamps.
 
 - Add bounded Director feature actions with accessible controls, explicit camera/layer admission and cancellation; restore pack geometry on same-shot seek. Preserve existing scenes and content attribution.
@@ -2033,3 +2723,4 @@ represent previously published GitHub Releases.
 ## [0.1.0] — 2026-02-09
 
 - Initial project version.
+

CONTRIBUTING.md

@@ -108,7 +108,7 @@ prints anything; never fix that by renaming or deleting PR A's published token.
 The highest-leverage places to jump in:
 
 - **🌆 Add a CCTV source pack.** Austin is the reference camera source. Adding another city means a clean public camera catalog with coordinates, attribution, and server-registered frame URLs (the proxy only fetches registered URLs — never client-supplied ones, see [SECURITY.md](SECURITY.md)). City packs are the best first lane.
-- **🛰️ Add or improve a data layer.** Layer factories live in `src/layers/<family>/`, with source, record, controller and renderer owners implementing the layer interface (`init/enable/disable/update/destroy/getStats`, optional `getDetectableObjects`/`getStats`). Use an existing layer as a template.
+- **🛰️ Add or improve a data layer.** Layer factories live in `src/layers/<family>/`, with source, record, controller and renderer owners implementing the layer interface (`init/enable/disable/update/destroy/getStats`, optional `getDetectableObjects`/`getStats`). Use an existing layer as a template, and see [Adding a new layer](#adding-a-new-layer) for what the PR needs.
 - **🎙️ Extend voice control.** Voice arguments are defined in `src/voice/actionSchemas.js`, with server-side descriptions in `server/providers/openai/tools.js` and client-side execution in `src/voice/gevActions.js`. Keep the tool surface tight and the responses honest (confirm only what actually happened).
 - **🎨 Add a visual style.** Styles are GLSL post-process shaders in `src/styles/`.
 - **🐛 Fix bugs / improve the first-run experience.** See [docs/KNOWN-ISSUES.md](docs/KNOWN-ISSUES.md).
@@ -116,7 +116,7 @@ The highest-leverage places to jump in:
 ## Architecture in one minute
 
 - **No framework.** Vanilla JS + [CesiumJS](https://cesium.com/platform/cesiumjs/) + [Vite](https://vitejs.dev/).
-- **Assembly lives in `src/app/`; standalone defaults live in `src/standalone/`.** UI controllers live in `src/ui/`, layer factories in `src/layers/`, portable sources in `src/sources/`, and application operations in `src/services/`. Existing `src/ui.js` and `src/data/<layer>.js` entries retain compatibility; new code belongs with its focused owner.
+- **Assembly lives in `src/app/`; standalone defaults live in `src/standalone/`.** UI controllers live in `src/ui/`, layer factories in `src/layers/`, portable sources in `src/sources/`, and application operations in `src/services/`. Existing `src/data/<layer>.js` entries retain compatibility; new code belongs with its focused owner.
 - Sources acquire records; renderers own Cesium resources. Import `gods-eye-view/layers/<family>/source` when only a source factory is needed. Common voice controls consume the session interface; protocol adapters own connection details.
 - **Secrets stay server-side.** Anything needing a private key goes through a local proxy under `server/providers/`. The browser only ever sees the Google Maps key (which you restrict) and ephemeral tokens.
 - `docs/CURRENT-STATE.md` is the authoritative runtime reference — read it first.
@@ -153,6 +153,33 @@ ownership and adoption process.
 3. If you change runtime behavior, update `docs/CURRENT-STATE.md` in the same PR, and add your changelog entry as `changelog.d/<pr-number>-<slug>.md` instead of editing `CHANGELOG.md` — see [changelog.d/README.md](changelog.d/README.md). Distinct filenames don't conflict; a release assembles the directory into `CHANGELOG.md`. A documentation claim that needs a regression test should assert against `docs/CURRENT-STATE.md` or `README.md`, which a PR still edits directly.
 4. If you add or change a data source, update [DATA_SOURCES.md](DATA_SOURCES.md) with its license and attribution. **Don't add data you don't have the right to redistribute** — fetch it at runtime instead.
 5. Describe what you changed and how you verified it (screenshots welcome for anything visual).
+6. If you add a new layer, fill in the new-layer section of the PR template. See [Adding a new layer](#adding-a-new-layer).
+
+## Adding a new layer
+
+A new layer changes what everyone sees on the globe, so maintainers need to see
+it working and know where its data comes from before reviewing the code. PRs
+that add a layer must include all four of these in the description. The PR
+template has a section for them.
+
+1. **Screenshots.** At least one of the layer on the globe, plus its info card
+   or panel if it has one.
+2. **A screen recording**, preferably 15 to 30 seconds: turn the layer on, move
+   around, and open a record. Drag an `.mp4` or `.mov` into the PR description.
+   GitHub accepts videos up to 10 MB on free accounts, so link to a larger file
+   instead of attaching it.
+3. **The proposed category.** Say which layer-panel group the layer belongs in.
+   The groups are defined in `PANEL_GROUPS` in `src/ui/layerPanel.js` (today:
+   Movement, Cameras, Infrastructure, Events, Weather and Utilities). A layer
+   that isn't listed there falls under "Other layers". If none of the groups
+   fits, propose a new one and explain why.
+4. **The data source and licence.** Name the provider and endpoint, link its
+   licence or terms, give the attribution shown in the app, and say whether it
+   needs a key and whether the data is fetched at runtime or bundled. Add the
+   same details to [DATA_SOURCES.md](DATA_SOURCES.md) and register the credit
+   in `src/data/dataCredits.js`.
+
+Maintainers may hold a layer PR until all four are there.
 
 ## Maintainers
 

DATA_SOURCES.md

@@ -38,6 +38,7 @@ How to read this:
 | **Environment and Climate Change Canada** (MSC GeoMet OGC API) | Air quality (AQHI) — Canadian station observations | [ECCC Data Servers End-use Licence](https://eccc-msc.github.io/open-data/licence/readme_en/) (open, attribution required, no endorsement implied) | "Contains information licensed under the Environment and Climate Change Canada Data Servers End-use Licence" |
 | **NASA GIBS** (WMTS tiles + Worldview Snapshots) and **NASA CMR** (granule catalog) | Recent Imagery layer: HLS S30/L30 (Sentinel-2, Landsat 8/9) and VIIRS true-colour tiles draped on the map, per-day thumbnails and PNG exports; the HLS granule catalog (dates, cloud, footprints) for a selected box | U.S. public domain (NASA data); keyless, browser-direct (CORS `*`); no bulk use — one 30-day catalog query per box, tiles bounded to the box, six tile requests in flight | "We acknowledge the use of imagery provided by services from NASA's Global Imagery Browse Services (GIBS), part of NASA's Earth Science Data and Information System (ESDIS)." — [gibs.earthdata.nasa.gov](https://gibs.earthdata.nasa.gov), [HLS](https://lpdaac.usgs.gov/products/hlss30v002/) |
 | **NIFC WFIGS** (Wildland Fire Interagency Geospatial Services, ArcGIS feature service) | Fire Perimeters layer: current interagency wildfire incident perimeters, containment, and incident facts | U.S. public domain (interagency wildland-fire data published through the [NIFC Open Data portal](https://data-nifc.opendata.arcgis.com/)); fetched keyless through `/api/fire-perimeters` (5-minute server cache) with `exceededTransferLimit` paging | "Wildfire perimeters: National Interagency Fire Center (WFIGS)" |
+| **S2 Underground GhostMaps** (`github.com/s2underground/GhostMaps`) | S2 GhostMaps layer: the current edition of S2's KMZ intel products (Common Intelligence Picture, 30-day kinetic pull, Border Crisis Map, Iran and Yemen products, newest incident drop). Keyless. `/api/ghostmaps` reads the branch head from git's ref advertisement every 15 s (`GHOSTMAPS_POLL_SECONDS`, minimum 5 s), lists the tree through the GitHub REST API only when the head changes (optional `GITHUB_TOKEN`), downloads files by commit-pinned raw URLs into `.gev-cache/ghostmaps/` and pushes new catalogs to browsers over server-sent events | [CC BY-NC-SA 4.0](https://creativecommons.org/licenses/by-nc-sa/4.0/) (repository README: "S2 Underground © 2025 by S2A1"); non-commercial, attribution required; files are fetched at runtime, never stored in this repository | "S2 GhostMaps intel products: S2 Underground © by S2A1, CC BY-NC-SA 4.0" — shown in-app |
 | **InciWeb** (inciweb.wildfire.gov)                                    | Per-incident "InciWeb ↗" card links to official incident pages (narratives, evacuation/closure notices) | U.S. government public incident information. Links are matched best-effort by incident name and state, with incident page origin and update times checked on selection. Same-origin `/api/fire-perimeters/inciweb` routes cache the catalog for 1 hour and publication metadata for 30 minutes; linked pages remain InciWeb content | "Incident information: InciWeb (inciweb.wildfire.gov)" |
 | **OpenFreeMap / OpenMapTiles** | Vector tiles | OpenStreetMap data under ODbL 1.0 | OpenFreeMap © OpenMapTiles |
 | **Overture Maps Foundation** | Military area names pack | [ODbL 1.0](https://opendatacommons.org/licenses/odbl/1-0/) | Overture Maps Foundation |
@@ -68,6 +69,7 @@ How to read this:
 | **Kartverket** (`ws.geonorge.no/hoydedata/v1/punkt`)               | Terrain heights (NN2000) used as the ground prior for Statens vegvesen cameras                                                     | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — attribution REQUIRED | "© Kartverket", modified (heights over water set to 0 m, rounded to 0.1 m) |
 | **NYC DOT Traffic Management Center** (`webcams.nyctmc.org`) | CCTV camera catalog + frames, New York City five boroughs | NYC DOT requires developers to sign a [data-sharing agreement](https://www.nyc.gov/html/dot/html/about/datafeeds.shtml) for the camera feed. **Off by default**; enable only under your own agreement | "NYC DOT Traffic Management Center" + NYC DOT's required application disclaimer (in the Data attribution popover) |
 | **City of Toronto Open Data** (`opendata.toronto.ca`)                 | CCTV camera catalog + frames, Toronto city streets                                                                                  | [Open Government Licence – Toronto](https://www.toronto.ca/city-government/data-research-maps/open-data/open-data-licence/) — attribution REQUIRED                                                                                                                                                                                                    | "Contains information licensed under the Open Government Licence – Toronto"                                                                 |
+| **Autostrada del Brennero (A22)** (catalog `tourism.api.opendatahub.com`, frames `www.autobrennero.it/WebCamImg/`) | CCTV camera catalog + frames, A22 Brenner–Modena motorway, Italy | Public Autobrennero webcam images; camera list republished by the Open Data Hub, whose records are tagged CC0 (`ClosedData: false`, licence holder Autobrennero); Autobrennero publishes no terms of its own for the images | "Webcam images © Autostrada del Brennero S.p.A., via the Open Data Hub (NOI Techpark)" (courtesy) |
 | **GBFS (Lyft / BCycle / Social Bicycles / PBSC)**                     | Bikeshare availability                                                                                                              | Per-feed (attribution-only)                                                                                                                                                                                                                                                                                                                           | Credit the operator (e.g. Austin BCycle) + its `license_url`                                                                                                   |
 | **Bike Share Toronto** (`toronto.publicbikesystem.net`) | Bikeshare station availability, Toronto | Operator GBFS feed. No licence is published: the City's open-data package declares none and the feed has no `license_url`. Attribution is given to the operator. | "Bike Share Toronto (Toronto Parking Authority)" |
 | **Bike Itaú / Tembici** (`*.publicbikesystem.net`, seven Brazilian cities, Santiago and Bogotá) | Bikeshare station availability: São Paulo, Rio de Janeiro, Salvador, Recife, Porto Alegre, Brasília, Curitiba, Santiago de Chile and Bogotá | Operator GBFS feeds. No licence is published: the feeds' `system_information.json` carries no `license_url`, operator or attribution fields. Attribution is given to the operator. | "Bike Itaú (Tembici)"; "Tembici Bogotá" |
@@ -175,9 +177,10 @@ The optional Local ADS-B layer and the broadcast-FM receiver use radio you recei
 - **Kartverket ground heights for Statens vegvesen cameras.** The camera feed's points are 2D, so the loader asks Kartverket's keyless point-height API (`ws.geonorge.no/hoydedata/v1/punkt`, CC BY 4.0) for the terrain height at each camera. Requests carry 20 points: the API accepts 50, but above ~20 it answers the extra points from contour lines (`hoydekurver`, metres to ~20 m off) or not at all. Eight requests run at a time, about 36 for the whole country: a cold lookup took 6–13 s in testing (single requests 0.6–9.5 s). Answers are matched by the coordinates the API echoes and recorded only for points that request asked about. Over water the API returns the sea-floor depth (`dybdekurver` or `Havflate`), which is replaced by 0 m, the water surface; for the ~14 bridge cameras that is below the deck, but much closer than the sea floor or the flat prior. Heights are cached in memory by position for the life of the server, and points with no height (a few ferry quays and bridges, or a point a 200 answer leaves out) for 6 h, so the 15-minute catalog refresh only asks about new or moved cameras. The first failing request (a 408, 429 or 5xx, a network error, a request over 10 s, or an unreadable or oversized body) stops the lookup, with no retries, and no new lookup starts until the backoff ends (Retry-After when sent, else 30 min, longer than the refresh; bounded to 1 min–1 h). Any other 4xx marks that request's points as having no height and the lookup carries on. The whole lookup has a 30 s deadline; a lookup cut short by it resumes on the next refresh without a backoff. The lane waits at most 12 s, counted from the start of the loader, and only when more than 10% of the cameras have no answer yet; a few new cameras or expired misses are looked up in the background. A slower lookup keeps filling the cache, and the cameras it had not reached keep the flat prior until the next 15-minute refresh (about 190 of 865 on one slow first run). Only coordinates are sent, with the same User-Agent as the other CCTV requests. `CCTV_VEGVESEN_HEIGHTS=0` turns the lookup off. The Kartverket credit, with a note that heights over water are set to 0 m and heights are rounded to 0.1 m, is shown beside the Statens vegvesen entry in the Data attribution popover.
 - **NYC DOT Traffic Management Center cameras.** Off by default. NYC DOT's [developer data feeds page](https://www.nyc.gov/html/dot/html/about/datafeeds.shtml) asks developers who want the camera feed to contact `[email protected]` and sign a data-sharing agreement. This project does not hold one that covers downstream installations, so the pack loads only when an operator who holds their own agreement sets `CCTV_NYC_ENABLED=1`; with the flag unset, empty or any other value, the server makes no request to NYC DOT. The endpoint needs no key. The camera list is the public `webcams.nyctmc.org/api/cameras` catalog (~980 cameras across the five boroughs); frames are stills at `webcams.nyctmc.org/api/cameras/<uuid>/image`, synthesized from a validated UUID rather than taken from the payload, and only that host is registered. Cameras the feed reports as offline are dropped. The catalog publishes no camera facing, so headings use the shared id-hash fallback at low confidence and are corrected with the in-app calibration gizmo. Once enabled, the 250 cameras nearest the borough cores load; `CCTV_NYC_MAX_SOURCES` (8–400) changes the cap. Frames are fetched at request time and never stored or redistributed. NYC DOT asks every application that uses its data to carry its disclaimer; it is registered verbatim in the Data attribution popover.
 - **City of Toronto RESCU cameras.** Keyless. The camera list is the City's public `tmcearthcameras.json` on `opendata.toronto.ca` (dataset "Traffic Cameras", Transportation Services), served as JSONP and unwrapped with an anchored pattern. This is the municipal network the Ontario 511 pack does not carry: downtown arterials plus the Gardiner, DVP, Allen and Lake Shore. The list publishes no frame URL, so frame URLs are BUILT from the documented `CameraImages/loc####.jpg` convention and a strictly-digits camera number, pinning the frame proxy to the portal origin by construction; the list fetch refuses redirects and bounds the body it buffers. Frames are fetched at request time and never stored or redistributed. The dataset publishes no camera facing: the `D1`-`D4` fields are the directions of the *comparison* images (static reference stills captured in 2016 under a different path), not a bearing for the live pan-tilt-zoom frame, so headings use the shared id-hash fallback at low confidence and are corrected with the in-app calibration gizmo. A camera that is temporarily out of service still answers 200 with a byte-identical "Image Unavailable" placeholder rather than an error (about 6% of the network at any moment), so such a camera reads as healthy; the frame it shows is the agency's, not a synthesized one. The licence requires the attribution statement above. Disable with `CCTV_TORONTO_ENABLED=0`.
+- **Autostrada del Brennero (A22) webcams.** Keyless. The camera list is one request to the Open Data Hub tourism API (`tourism.api.opendatahub.com/v1/WebcamInfo?source=a22`), run by NOI Techpark in South Tyrol, which republishes Autobrennero's own list of 13 motorway webcams with coordinates and kilometre markers. Frames are the operator's stills on `www.autobrennero.it/WebCamImg/km<N>.jpg`, refreshed about once a minute, and only the exact image for each camera's kilometre is registered. The feed names no bearing, so headings use the id-hash fallback at low confidence. The road climbs from about 20 m in the Po valley to about 1,370 m at the Brenner Pass, so each camera's ground elevation comes from a per-kilometre table sampled from the Copernicus GLO-90 DEM (via Open-Meteo's elevation API); a camera not in the table uses a 200 m prior. The Open Data Hub tags every record CC0 (`ClosedData: false`, Autobrennero as licence holder), but that tag is the aggregator's metadata and Autobrennero publishes no terms of its own for the images, so they are credited to the operator as a courtesy and are not redistributed. Frames are fetched at request time and never stored. Disable with `CCTV_A22_ENABLED=0`.
 - **Camera frame content.** Public camera frames can contain people, vehicles and license plates, and the camera layer does nothing with them beyond putting them on the map. A successful upstream response is relayed as the provider served it: nothing in the camera pipeline blurs, redacts, enhances or restores it, and nothing there runs face, plate or object detection or otherwise recognises or classifies what is in the picture. (The ALPR layer described below maps where plate-reader cameras are, from locations contributors tagged in OpenStreetMap; it reads nothing from any camera frame.) When an upstream has no frame for a camera, what you see instead is a Google Street View still or the app's own placeholder card; the panel's source badge names which of them you are looking at, and a refresh that fails after a frame has arrived leaves the last good picture on screen rather than replacing it. The browser resamples each frame for display: onto a fixed 1920x1080 surface for the camera's projection plane in the scene, and onto a 192x108 canvas for the small ambient card. That scaling is the only change made to the picture, and the only pixels the camera layer reads back are a 64x36 downscale hashed to tell whether the picture has changed. Live streams are piped through; the still path reads the image into memory to pass it on — TxDOT wraps its JPEG in a JSON envelope, which is decoded there — and no frame is written to disk (the disk cache, `.gev-cache/`, holds feed JSON for other layers and never camera imagery). Outside that pipeline, the voice assistant is the one feature that sends imagery anywhere: when it answers a question about what is in view it may attach a downscaled screenshot of the rendered scene — including any camera plane on screen — to the request it sends to the voice model. Frames are fetched only from server-registered camera URLs — a client cannot hand the proxy a URL (see [SECURITY.md](SECURITY.md)). What the app does stays inside the line README draws: no named-person search, no face recognition, no tracking individuals.
 - **Transit (GTFS-Realtime).** The proxy requests only registered operator feeds, validates redirects, bounds responses, and uses conditional requests, short snapshot caching and failure backoff. All sixteen registered regions are live-enabled; each can be disabled independently. Vehicles use delayed playback between reports, with report age and waiting states shown separately. Session-local selected trails are available for every feed. MBTA additionally retains up to 15 minutes of recently observed positions in the running proxy, so available history can survive a browser reload; server restart clears it. History reads never fetch upstream, and other feeds have no proxy retention. Nothing is archived to disk or collected in the background. Operator text credits are included as a courtesy and do not imply endorsement. Heights are aligned to work with Google 3D tiles; subway markers are shown at street level because these feeds do not supply depth. The TTC feed is BusTime, the surface system: it carries buses and streetcars and no subway at all. About four in ten of its vehicles report no route at all (unassigned or deadheading), and those are shown with the feed default rather than a route-established mode. It sends no ETag or Last-Modified, so its conditional requests fall through to the ordinary snapshot cache. Three Golden Horseshoe neighbours run alongside it — MiWay, Hamilton HSR and Durham Region Transit — each bus-only and each polled only near its own region. Durham Region Transit publishes no bearing on any vehicle, so those sprites take their heading from observed movement like any other feed that omits it. Guelph, Kingston and Barrie extend the same pattern eastward and north. Hamilton, Guelph, Burlington and YRT publish route ids that are not the number on the vehicle, so those entries carry a route-name table taken from each operator’s own published GTFS; any id missing from a table renders unchanged rather than blank. A label is never invented: YRT runs a route `9101` that appears nowhere in its published routes, so it stays as the feed sends it. Burlington’s is the one that cannot be shortcut: `351` is route 1 while `3510` is route 10, so the table is a real join rather than a trimmed prefix. GO Transit / Metrolinx is deliberately absent: its REALTIME feed requires an API key issued by manual review, which the keyless admission rule excludes (its static schedule download is keyless, but carries no vehicle positions). Barrie and YRT/Viva each invite acceptance of their licence through a form, and each licence also states that using the data is itself acceptance; this deployment relies on that clause, which is recorded in both entries. Grand River Transit in Waterloo is absent for a different reason: it answers, but its feed header was months stale and it publishes no per-vehicle timestamps, so it would render vehicles that look live and are not. Ottawa’s OC Transpo falls to the same keyless admission rule as GO Transit — its realtime feed requires an API key. London Transit and Thunder Bay Transit publish vehicle positions over plain HTTP with no HTTPS endpoint available. Every other Ontario system — Brampton, Oakville, Niagara, Milton, Windsor, Greater Sudbury, UP Express and a dozen smaller operators — publishes static GTFS schedules only, with no realtime vehicle positions to register. Between the nine included and these exclusions, every Ontario realtime vehicle-position feed catalogued in the Mobility Database is accounted for.
-- **Radio Browser.** `/api/radio/stations` discovers official API mirrors, makes bounded and coalesced healthy/geolocated HTTPS-station queries, caches the normalized public-domain directory for 45 minutes, and may serve the last good catalog for up to seven days during an outage. Refreshes must meet minimum accepted-query and station coverage before replacing a warm catalog; schema-valid responses whose rows all fail the product's health policy do not count as successful queries. A usable partial cold catalog is explicitly `DEGRADED`, and malformed or empty successful payloads are rejected atomically. Every directory and click-count request rejects redirects, validates all resolved addresses as globally routable (including reserved/documentation IPv4 and special/non-global IPv6 exclusions), and pins the TLS connection to a validated address. Only MP3/AAC non-HLS directory rows with public HTTPS stream targets are returned; favicons are intentionally omitted. Pressing play connects one browser audio element directly to the selected broadcaster and calls the directory's click counter through known-ID-only `POST /api/radio/click/:uuid`. GEV never proxies, caches, records, bundles, or redistributes audio. Radio Browser supplies station-level tags, not dependable current-song or upcoming-program metadata, so Radio filtering never claims either. Direct playback exposes the listener's IP address to the broadcaster, whose own stream terms apply.
+- **Radio Browser.** `/api/radio/stations` discovers official API mirrors, makes bounded and coalesced healthy/geolocated HTTPS-station queries, caches the normalized public-domain directory for 45 minutes, and may serve the last good catalog for up to seven days during an outage. Refreshes must meet minimum accepted-query and station coverage before replacing a warm catalog; schema-valid responses whose rows all fail the product's health policy do not count as successful queries. A usable partial cold catalog is explicitly `DEGRADED`, and non-array or empty successful payloads are rejected atomically. Individual structurally malformed rows are skipped rather than failing the whole query; the response carries their bounded `rejectedStationCount` (at most 10,000), which the client adds to its own rejected rows and reports as degraded coverage without discarding the accepted generation. Every directory and click-count request rejects redirects, validates all resolved addresses as globally routable (including reserved/documentation IPv4 and special/non-global IPv6 exclusions), and pins the TLS connection to a validated address. Only MP3/AAC non-HLS directory rows with public HTTPS stream targets are returned; favicons are intentionally omitted. Pressing play connects one browser audio element directly to the selected broadcaster and calls the directory's click counter through known-ID-only `POST /api/radio/click/:uuid`. GEV never proxies, caches, records, bundles, or redistributes audio. Radio Browser supplies station-level tags, not dependable current-song or upcoming-program metadata, so Radio filtering never claims either. Direct playback exposes the listener's IP address to the broadcaster, whose own stream terms apply.
 - **TomTom Traffic.** Optional and BYOK: without `TOMTOM_API_KEY` the traffic layer runs its built-in simulation and no TomTom data (or attribution) appears. With a key, flow vector tiles are fetched through the server-side `/api/tomtom` proxy (120 s cache + a daily tile-budget governor — `TOMTOM_DAILY_TILE_BUDGET`, default 6,000 — sized so a 31-day month stays inside TomTom's 200K monthly free allowance; still a configurable application safety ceiling, not a guarantee; TomTom's [current pricing](https://docs.tomtom.com/pricing/) lists 200K free tile requests per month) and the "Traffic flow data © TomTom" credit is registered in the Data attribution popover the moment live mode activates. TomTom data is served live and cached only transiently (≤120 s TTL under `.gev-cache/`, gitignored) — it is not bundled or redistributed. One 23 KB point-in-time tile snapshot is committed as a decode-test fixture (`src/data/fixtures/`, © TomTom, never served to the app).
 - **Routing (OSRM / FOSSGIS).** `/api/route` proxies the public OSRM instances FOSSGIS e.V. runs for the OpenStreetMap community (car, bike, foot profiles). They are keyless and intended for fair, interactive use — the proxy rate-limits clients (60/min, 200/min total), caps route span and response size, caches each route for 10 minutes, and identifies itself in the User-Agent. Heavy or automated use must run its own OSRM. Routes are computed from OpenStreetMap data (ODbL); the Directions layer and voice routes never redistribute them. A route the router cannot find is reported as such; the Directions layer draws nothing in that case, and voice routes fall back to a clearly labeled straight line.
 - **Re:Earth Terrain.** Keyless (no API key). Used two ways: (1) `src/mapStackController.js` swaps in a `Cesium.CesiumTerrainProvider` pointed at Re:Earth's `cesium-mesh/ellipsoid` quantized-mesh endpoint for globe stacks without a Cesium ion token (e.g. OSM), replacing a flat `EllipsoidTerrainProvider`; falls back to the flat provider if the endpoint can't be reached. (2) The server-side `/api/terrain/heights` proxy (disk-cached, serve-stale) resolves per-point ellipsoidal ground height for entity placement. Both are best-effort with a keyless-safe fallback (bundled EGM96 geoid math) if Re:Earth is unreachable.
@@ -205,6 +208,8 @@ The [Bhote Koshi event pack](public/events/bhote-koshi-2026/README.md), under `p
 | **DataSF Analysis Neighborhoods** (41 SF neighborhood polygons)             | `neighborhoods/`                  | **PDDL 1.0** (public domain)                                                                              | ✅ (no restrictions)                             | "City & County of San Francisco — DataSF" (courtesy — not legally required) |
 | **Natural Earth countries, states and provinces** (260 admin-0/map units + 4,587 admin-1 polygons)             | `natural_earth/`                  | **Public domain**                                                                                         | ✅ (no restrictions)                             | "Made with Natural Earth" (courtesy credit — not legally required)          |
 | **US Census Bureau counties** (3,235 county polygons)                       | `us_census_counties/`             | **Public domain**                                                                                         | ✅ (no restrictions)                             | "U.S. Census Bureau" (courtesy — not legally required)                      |
+| **Yale Bright Star Catalogue** (9,096 stars, sky background)                | `sky/`                            | **Public domain**                                                                                         | ✅ (no restrictions)                             | "Yale Bright Star Catalogue (Hoffleit & Warren, via CDS)" (courtesy credit) |
+| **ESO Milky Way panorama** (eso0932a, blurred cube map, sky background)     | `sky/`                            | **CC BY 4.0**                                                                                             | ✅ (attribution; changes stated)                 | "ESO/S. Brunier"                                                            |
 | **CCTV ground heights** (3,445 cameras)                                     | `cctv_ground_heights/`            | Precomputed camera placement heights, aligned to work with Google Photorealistic 3D Tiles (folder README) | —                                                | —                                                                           |
 | **CCTV Camera Database** model-enrichment extract v2.26.0 (17 camera-model records) | `src/layers/cctv/modelSpecs.js` | **CC0-1.0** (public domain dedication) | ✅ (no restrictions) | "Specs: cctv-database.com" (courtesy — not legally required) |
 
@@ -277,6 +282,11 @@ https://www.naturalearthdata.com/about/terms-of-use/). We credit anyway: "Made w
 Earth". Registration in the in-app `dataCredits.js` attribution list ships with the resolver
 wiring (see below).
 
+### Sky background (`sky/`)
+
+Sources, licences, the changes CC BY asks to state, hashes and build commands
+are in [`sky/README.md`](src/data/local_data/sky/README.md).
+
 ### DataSF Analysis Neighborhoods (`neighborhoods/`)
 
 `neighborhoods/san-francisco.json` bundles the City & County of San Francisco's official

Dockerfile

@@ -39,6 +39,11 @@ COPY --chown=node:node . .
 ENV HOST=0.0.0.0
 ENV PORT=4173
 EXPOSE 4173
+# node:slim has no curl, so probe with Node's built-in fetch. 127.0.0.1 is
+# always on the Host allowlist, and the generous start period covers Vite's
+# first-run dependency optimisation.
+HEALTHCHECK --interval=30s --timeout=10s --start-period=30s --retries=3 \
+  CMD ["node", "-e", "fetch('http://127.0.0.1:'+(Number.parseInt(process.env.PORT,10)||4173)+'/').then((r)=>process.exit(r.ok?0:1),()=>process.exit(1))"]
 # The launcher is `npm run dev` plus one step: it trusts the container's
 # gateway address for Provider Settings, because that is where Docker delivers
 # the host's own browser from (never 127.0.0.1). See scripts/docker-start.mjs.

README.md

@@ -61,7 +61,7 @@ Start with the included data sources, then add your own. Each layer is a separat
 - **🎯 Click-to-track anything:** Camera locks on, draws a fading trail, surfaces full metadata — and a tracked fire or vessel hands you off to the nearest live camera in one click.
 - **🖊️ Voice whiteboard:** Speak annotations onto the world — real boundary polygons, marks, and routes.
 - **🛫 3D hangar:** Real per-class aircraft models — 787, ATR-72, Citation, Bell 206, MQ-9 — and a tracked contact swaps from glyph to 3D model as you close in.
-- **🎨 Reskin reality:** GLSL sensor looks over the normal globe — CRT, NVG, FLIR/thermal, Noir, Snow.
+- **🎨 Reskin reality:** GLSL sensor looks over the normal globe — CRT, NVG, FLIR/thermal, Noir.
 - **🟩 Detection overlay:** Screen-space bounding boxes and IDs on everything in view.
 - **🎖️ Military HUD:** Tactical heads-up display with intelligence-style telemetry.
 - **🌐 Global Context:** Stage the full situational picture with one switch — and get your exact view back when you leave.
@@ -111,13 +111,15 @@ app's **POWER UP** panel; [Keys & Costs](#-api-keys) explains the options.
 
 Available on **Windows, macOS, and Linux**. The Pinokio maintainer reports
 cross-platform testing of the fixed installer. The launcher installs the
-locked dependencies, finds a free local port, and opens the app.
+locked dependencies, finds a free local port, and opens the app in your system
+browser. The Server menu item keeps the launcher console available.
 
 **Tried before and installation failed?** Update Pinokio and try again.
 Version 8.2 fixes the launcher installation issue;
 [details from the Pinokio maintainer](https://pinokio.co/posts/01m1m4p9xxm3qw7dnnpj2wr93g).
 
-**Pinokio opens but the globe is very choppy?** Before treating that as a GPU
+**Using an older launcher or opening the embedded view manually?** If the globe
+is very choppy, before treating that as a GPU
 compatibility or minimum-hardware problem, copy the local server URL shown by
 Pinokio and open the same URL in your normal hardware-accelerated browser. One
 Pinokio 8.2.0 user reported severe stutter in Pinokio's embedded view that went
@@ -177,6 +179,16 @@ Publishing it wider is the [Sharing an instance](#-sharing-an-instance) opt-in,
 
 When you widen the publish, also set `GEV_KEY_SETUP_TRUSTED_PEERS=none` so the launcher trusts no gateway address.
 
+```bash
+GEV_KEY_SETUP_TRUSTED_PEERS=none docker compose up
+```
+
+Compose forwards `GEV_KEY_SETUP_TRUSTED_PEERS` and `GEV_ALLOWED_HOSTS` from your
+shell or the project's `.env`; an exported shell value takes precedence. You can
+also put `GEV_KEY_SETUP_TRUSTED_PEERS=none` in `.env` for a persistent setting.
+Unset or blank trusted peers retain automatic gateway discovery; `none` explicitly
+disables it. The startup log confirms that no additional peers are trusted.
+
 <details>
 <summary>Running on Linux, a NAS, or behind a reverse proxy</summary>
 
@@ -197,6 +209,8 @@ env UID=1026 GID=100 docker compose up -d
 
 Keep the `env`: bash treats `UID` as read-only, so a plain `UID=1026` in front of a command is silently ignored. If the container can't write the checkout, it says so at start. Docker Desktop on macOS and Windows maps ownership for you.
 
+On SELinux hosts (Fedora, RHEL), compose mounts the checkout with `:z` so the container may read it; Docker may relabel the checkout for container access, which can take a moment on a large checkout. Without that, the start fails with `Cannot find module '/app/scripts/docker-start.mjs'`.
+
 Behind a reverse proxy, put your keys in `.env` or pass them as environment variables - Provider Settings refuses proxied requests on purpose - and add the hostname you serve it on, for example `GEV_ALLOWED_HOSTS=globe.example.lan` (see [Sharing an instance](#-sharing-an-instance)).
 
 </details>
@@ -280,14 +294,14 @@ Choose a first-run mission, or try these in order. The GIFs show Google Photorea
 
 ![Tracking the ISS along its orbital path as it crosses over Ukraine](docs/media/14-iss-over-ukraine.gif)
 
-6. **Switch the optics.** Tap `1`–`7` — CRT, NVG, FLIR — and the whole live planet re-renders through a different sensor.
+6. **Switch the optics.** Tap `1`–`6` — CRT, NVG, FLIR — and the whole live planet re-renders through a different sensor.
 
 ![Cycling a dense live globe through CRT, FLIR, and NVG in one continuous view](docs/media/01-style-sweep.gif)
 
 7. **Talk to it** _(needs an OpenAI key)_: _"Take me to LAX and select the nearest airborne aircraft."_
 8. **Come home.** Hit **Reset Globe** — or just say _"zoom out to a globe view."_
 
-**Keyboard:** `1`–`7` visual styles · `H` HUD · `D` detection · `C` cockpit · `` ` `` frame rate · `Esc` out. Trackpad pinch zooms the globe.
+**Keyboard:** `1`–`6` visual styles · `H` HUD · `D` detection · `C` cockpit · `` ` `` frame rate · `Esc` out. Trackpad pinch zooms the globe.
 
 ---
 
@@ -333,6 +347,10 @@ Thirty tools, four jobs — the commands below come straight from the product's
 
 **🎥 Direct it** — drone-operator camera verbs:
 
+“Rotate the globe” spins Earth to the right continuously; ask for left, a speed,
+or stop. If it refuses, follow its reset-and-rotate or further-zoom guidance;
+camera input stops rotation.
+
 > 🗣️ _"Take me to Tokyo."_ · _"Orbit around this area slowly."_ · _"Draw the walking route from the Capitol to Zilker Park."_ → _"Fly the route we just drew."_ · _"Zoom out to a globe view."_
 
 **🖊️ Annotate it** — a whiteboard over the real world:
@@ -381,7 +399,7 @@ Twenty layers and map sources. **Eighteen have a keyless path.** Some offer addi
 | 🌍 **Earthquakes**          | Global seismic activity, last 24h                                                                                                                                                                                                                                                                                                                                                   | USGS                                    | 🟢                                                                                                  |
 | ◍ **Air quality**           | Live AQHI on the published 1–10+ health-risk scale, with a Weather-panel card showing the band legend and the highest readings in view. **Canada only** — ECCC is the first registered provider | ECCC MSC GeoMet                          | 🟢                                                                                                  |
 | 🚗 **Traffic**              | Simulated vehicles on OSM roads. With TomTom, live flow speeds drive the simulation and congestion colors below ~8 km; individual vehicle positions are not live observations                                                                                                                                                                                                       | TomTom + OSM                            | 🟢 simulation · 🟡 live flow speeds                                                                 |
-| 📹 **CCTV Mesh**            | ~4,000 public cameras (shared cap) projected _into_ the 3D space — Austin · Texas (TxDOT) · California (Caltrans) · London (TfL) · Ontario (511, free developer key) · Finland (Fintraffic) · British Columbia (DriveBC) · Estonia (Tallinn, Tarktee) · Delaware (DelDOT live video) · New South Wales (Live Traffic NSW) · Calgary · Norway (Statens vegvesen) · Toronto · King County (WA) · Washington (WSDOT) · Catalonia (Servei Català de Trànsit) · Hong Kong (Transport Department) · Taiwan (Freeway Bureau, MOTC), plus opt-in New York City (NYC DOT TMC, needs your own NYC DOT agreement), opt-in Lithuania (Via Lietuva / Eismoinfo, photo licence unconfirmed) and opt-in Florida (FL511, individual personal use only; other use needs FDOT's written consent). Positions are published; poses are estimated priors **you calibrate by dragging a gizmo on the camera itself** | City APIs                               | 🟢                                                                                                  |
+| 📹 **CCTV Mesh**            | ~4,000 public cameras (shared cap) projected _into_ the 3D space — Austin · Texas (TxDOT) · California (Caltrans) · London (TfL) · Ontario (511, free developer key) · Finland (Fintraffic) · British Columbia (DriveBC) · Estonia (Tallinn, Tarktee) · Delaware (DelDOT live video) · New South Wales (Live Traffic NSW) · Calgary · Norway (Statens vegvesen) · Toronto · King County (WA) · Washington (WSDOT) · Catalonia (Servei Català de Trànsit) · Hong Kong (Transport Department) · Taiwan (Freeway Bureau, MOTC) · Italy (A22 Brennero motorway), plus opt-in New York City (NYC DOT TMC, needs your own NYC DOT agreement), opt-in Lithuania (Via Lietuva / Eismoinfo, photo licence unconfirmed) and opt-in Florida (FL511, individual personal use only; other use needs FDOT's written consent). Positions are published; poses are estimated priors **you calibrate by dragging a gizmo on the camera itself** | City APIs                               | 🟢                                                                                                  |
 | 📷 **Mapped ALPR Cameras**  | License-plate-reader camera locations tagged by OpenStreetMap contributors, loaded one city-sized view at a time, with **SHOW NEAREST**. Locations and tags only: no plate data, no video                                                                                                                                                                                           | OpenStreetMap (incl. DeFlock mapping)   | 🟢                                                                                                  |
 | 📷 **Street Level**         | Street-level photos behind one panel, one chip per provider: coverage on the streets, image cones, an embedded viewer with full-screen **EXPAND**. Mapillary, Google Street View, KartaView and Panoramax | Mapillary · Google · KartaView · Panoramax | 🟢 KartaView, Panoramax · 🟡 Mapillary token · 🔴 Google Maps key |
 | 📻 **Radio**                | Geolocated world radio with an **analog tuner** — drag the needle across up to 750 stations and the globe flies to each broadcaster                                                                                                                                                                                                                                                 | Radio Browser / broadcasters            | 🟢                                                                                                  |
@@ -425,7 +443,7 @@ _The Space Missions layer replaying a Falcon 9 ascent — labeled `RECONSTRUCTED
 
 **Setup.** At [mapillary.com/dashboard/developers](https://www.mapillary.com/dashboard/developers), register an application with **Read** access and copy its **Client Token** (`MLY|…`). Paste it into **POWER UP → Mapillary**, or set `MAPILLARY_CLIENT_TOKEN` in `.env` and restart. Without it the panel reads **KEY REQUIRED**. **Google Street View** uses `GOOGLE_MAPS_API_KEY` with the **Maps JavaScript API** enabled for it in Google Cloud; its chip starts off, since every panorama is billed to the key. **KartaView** and **Panoramax** need nothing: their public APIs are keyless.
 
-**Use.** Turn on **Street Level** under DATA LAYERS → Cameras, or with the pill in the STREET LEVEL panel header. Each provider has a chip in its own colour (Mapillary green), and one is lit at a time: lighting one switches the others off. Mapillary, which is free, is lit by default. Zoom in to street level (below 60 km) for the coverage lines; from orbit the panel says to zoom in. The **IMAGERY** (ALL / 360° / FLAT) and **SINCE** filters apply to Mapillary, KartaView and Panoramax; Street View panoramas are all 360°, so with Street View lit the filters are hidden. Click a coverage line for its image cones and a cone to open the photo. Light **KARTAVIEW** (purple) and zoom in below about 6 km: its lines are the streets KartaView has photos of, and a click on one opens the photo nearest the click, flat or 360° (drag to look around), with cones along its drive; **‹ ›** or ← → step through the drive (Shift+← →, ↑ ↓ and + − look around a 360° photo; pinch zooms on a phone). Photos KartaView has archived are skipped, and where all are archived the panel says so. For KartaView, **SINCE** goes by upload date, as KartaView's own map does (it can filter by nothing else), and the panel notes it under the slider; KartaView filters its lines on its own server, and a filtered area KartaView has not drawn before can take several seconds. Light **PANORAMAX** (orange) for the open, federated commons (strongest in France and Belgium): below about 60 km its lines are sequences. 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; **‹ ›** or ← → step through it, and both filters apply. Its caption names the picture's authors (or the instance holding it) and licence (mostly CC BY-SA 4.0; pictures on the IGN instance are Licence Ouverte 2.0). On the **Google 3D** map (Google's terms keep Street View off other maps, where it does not appear), light **GOOGLE STREET VIEW** and click a street from below 3 km, or press **OPEN STREET VIEW** for the view centre, to open Google's panorama there; step along its arrows. Above the photo: **EXPAND** (full screen; Esc leaves) and **FIT / FILL** (Mapillary, and flat KartaView and Panoramax photos). The caption links to the image on the provider's site, and the globe credits each provider that is on ("© Mapillary contributors, CC BY-SA 4.0", "Street View imagery © Google", "© KartaView contributors, CC BY-SA 4.0", "© Panoramax contributors, licence per picture"). KartaView's own photo pages fail for signed-out visitors, so its link opens the full-size photo.
+**Use.** Turn on **Street Level** under DATA LAYERS → Cameras, or with the pill in the STREET LEVEL panel header. Each provider has a chip in its own colour (Mapillary green), and one is lit at a time: lighting one switches the others off. Mapillary, which is free, is lit by default. Zoom in to street level (below 60 km) for the coverage lines; from orbit the panel says to zoom in. The **IMAGERY** (ALL / 360° / FLAT) and **SINCE** filters apply to Mapillary, KartaView and Panoramax; Street View panoramas are all 360°, so with Street View lit the filters are hidden. Click a coverage line for its image cones and a cone to open the photo. Light **KARTAVIEW** (purple) and zoom in below about 6 km: its lines are the streets KartaView has photos of, and a click on one opens the photo nearest the click, flat or 360° (drag to look around), with cones along its drive; **‹ ›** or ← → step through the drive (Shift+← →, ↑ ↓ and + − look around a 360° photo; pinch zooms on a phone). Photos KartaView has archived are skipped, and where all are archived the panel says so. For KartaView, **SINCE** goes by upload date, as KartaView's own map does (it can filter by nothing else), and the panel notes it beside the SINCE value (ANY DATE (by upload date)); KartaView filters its lines on its own server, and a filtered area KartaView has not drawn before can take several seconds. Light **PANORAMAX** (orange) for the open, federated commons (strongest in France and Belgium): below about 60 km its lines are sequences. 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; **‹ ›** or ← → step through it, and both filters apply. Its caption names the picture's authors (or the instance holding it) and licence (mostly CC BY-SA 4.0; pictures on the IGN instance are Licence Ouverte 2.0). On the **Google 3D** map (Google's terms keep Street View off other maps, where it does not appear), light **GOOGLE STREET VIEW** and click a street from below 3 km, or press **OPEN STREET VIEW** for the view centre, to open Google's panorama there; step along its arrows. Above the photo: **EXPAND** (full screen; Esc leaves) and **FIT / FILL** (Mapillary, and flat KartaView and Panoramax photos). The caption links to the image on the provider's site, and the globe credits each provider that is on ("© Mapillary contributors, CC BY-SA 4.0", "Street View imagery © Google", "© KartaView contributors, CC BY-SA 4.0", "© Panoramax contributors, licence per picture"). KartaView's own photo pages fail for signed-out visitors, so its link opens the full-size photo.
 
 Share links carry the provider switches and filters (`0.m.0` Mapillary off, `0.m.0_0.r.google-1` Street View on, `0.m.0_0.r.google-0*kartaview-1*panoramax-0` KartaView on and `0.m.0_0.r.google-0*kartaview-0*panoramax-1` Panoramax on, as the app writes them (`0.m.0_0.r.kartaview-1` and `0.m.0_0.r.panoramax-1` work too; a link that leaves out `m` keeps Mapillary, the default, lit), `0.p.p` panoramas only, `0.s.365` the last year). To add a provider, implement the contract in `src/layers/streetLevel/registry.js` and register it in `src/app/layers/streetLevel.js`.
 
@@ -478,7 +496,7 @@ How the globe handles live data:
 ```
 src/
 ├── main.js                 # Bootstrap: Google 3D tiles, layer registration
-├── ui.js                   # Runtime UI — panels, HUD, styles, control facade
+├── ui/                     # Runtime UI — panels, HUD, styles, controls
 ├── hud.js                  # Intelligence HUD + AI scene summary
 ├── keySetup.js             # POWER UP panel — in-app provider keys (dev server only)
 ├── mapStackController.js   # Basemap switching — Google 3D / Esri / OSM / ion stacks

SECURITY.md

@@ -2,6 +2,11 @@
 
 God's Eye View is a local-first client for **public** data. It is built for exploration, demos, and learning — not as a hardened production service. This document explains the security model so you can run it safely and report issues responsibly.
 
+Vite's development file server also denies `.gev-logs/`, `.gev-cache/`, and
+the package checkout's root `dist/` directory. Dependency `dist/` directories
+remain available. This filesystem deny list does not filter `public/` assets or
+preview output; never put private artifacts in a public asset directory.
+
 ## Reporting a vulnerability
 
 Please report security issues **privately** — do not open a public issue for anything exploitable.
@@ -69,11 +74,13 @@ The data proxies under `server/providers/` are written so the browser cannot tur
 - **No verbatim client headers upstream.** The CCTV media route is the one route that relays a request header (`Range`, for video seeking). It is parsed and canonicalized before it is forwarded: one `bytes=` range only, with every accepted form — explicit span, open-ended and suffix — bounded to the same 64 MiB ceiling the relay applies to a declared response body. Multi-range, malformed, inverted and non-`bytes` values are dropped and the request proceeds without a `Range`, as RFC 7233 §3.1 prescribes. Bounding the request bounds what is asked for: a response that declares no length — live streamed media, or a chunked body from an upstream that ignores the `Range` — has no ceiling. An upstream request the browser has stopped waiting for is cancelled rather than left running, whether the viewer leaves before the headers arrive or during the body.
 - **Transit fetches registered feeds only.** `/api/transit/vehicles/<id>` resolves the id against `src/data/transitFeeds.js`; the browser never supplies a URL, and a feed that is registered but disabled does not resolve at all. Redirects are followed manually and each hop is validated against the feed's own https origin before it is requested, so an off-origin or downgraded hop is refused rather than contacted. Bodies are capped at 8 MB, the protobuf is decoded server-side under entity-count and string-length ceilings, a differential feed is refused, and snapshots live 15 s in memory with no disk cache. A per-feed admission limiter and a failure cooldown ladder bound what this process can ask of any operator.
 - **Local receiver feeds are operator-configured and local-only.** `/api/local-receivers/aircraft` reads only the `aircraft.json` URLs in the server's `LOCAL_RECEIVER_FEEDS`; the browser never supplies an address. Each host must pass the shared tap address rule (`src/data/tapAddress.js`: loopback, RFC1918, `localhost`, `*.local`; no link-local, IPv6 or other names), the scheme must be http(s), the path must end in `aircraft.json`, and credentials, queries and fragments are refused. Invalid entries are logged at startup and never fetched. Reads use a 2 s timeout, refuse redirects, cap bodies at 2 MB and share one read per second; responses name each feed by band only and never carry upstream error text.
+- **Validated response formats.** Proxied bodies are relayed only in the format the route serves. CCTV frames and the Street View fallback accept JPEG, PNG, GIF, WebP and AVIF only, sent under their canonical type; any other type falls through to the next fallback. Live CCTV media must match its feed kind (`video/mp4`, `video/webm`, or `multipart/x-mixed-replace` with a boundary) before it is relayed or the camera counts as healthy, and its redirects stay on the registered origin. GBFS bodies must parse as JSON and are re-serialized as `application/json; charset=utf-8`. Camera catalog URLs are pinned by parsed URL — scheme, exact host, no credentials, default port, and a normalized path inside the agency's image directory — and a redirect on a pinned host must stay inside the same directory. Every `/api/cctv` route uses the keyless cross-site checks described below, so cameras stay reachable behind a reverse proxy; a request carrying forwarding headers never reaches the key-bearing Street View fallback and gets the placeholder frame instead, as when no key is configured.
+- **Consistent API response headers.** Every `/api` response, including errors, partial content, Host refusals and unknown routes, carries `Content-Security-Policy: default-src 'none'; sandbox` and `X-Content-Type-Options: nosniff` (`apiResponseHeadersPlugin` in `build/vite.js`, installed ahead of the Host check). A route that sets its own policy adds it as a further policy; it never replaces this one.
 - **Response-size caps and timeouts** on proxied responses.
 - **Sanitized errors** — internal error details are not echoed back to clients.
 - **Coalesced OAuth refresh** and cached successful responses only (OpenSky).
 - **Redacted debug logging.** The voice debug log (`.gev-logs/`, gitignored) strips API keys, bearer tokens, client secrets, and image data URLs before writing.
-- **Cross-site gate on cost/log endpoints.** The cost-bearing (`/api/realtime/token`, `/api/openai/hud-summary`, `/api/google/nearby-places`, `/api/google/text-search`), quota-bearing (`/api/mapillary/*`, with a per-IP limit on tiles, and `/api/tomtom/*`, backed by its persistent daily tile budget) and log (`/api/realtime/debug-log`) endpoints refuse cross-site browser requests: a foreign or opaque `Origin`, a `Sec-Fetch-Site` other than `same-origin`/`none` (this is what blocks an `<img>`/navigation that carries no `Origin`), or any reverse-proxy/CDN forwarding header returns `403`. Non-browser loopback tools (the repo QA harnesses POST the token endpoint with no `Origin`) and the explicit `HOST=0.0.0.0` LAN opt-in keep working — the gate deliberately does not require a loopback remote address; that stricter requirement belongs only to the credential panel (`admitKeySetupRequest`). The Host check (`allowedHosts`, applied by `hostCheckPlugin` ahead of every route, since Vite's own check runs only after plugin middleware) rejects a rebinding `Host` before any handler runs, in every mode, and the gate is defense in depth behind it: the LAN opt-in keeps that check and accepts only IP addresses, `localhost` and names listed in `GEV_ALLOWED_HOSTS`. **Limit:** a name you list there is trusted like the app's own address, so list only names you control. The keyless terrain route (`/api/terrain/heights`) uses the same cross-site checks, minus the forwarding-header refusal: it guards only the per-client quota and point cache, not a key or a bill, and the map needs it to render behind a reverse proxy.
+- **Cross-site gate on cost/log endpoints.** The cost-bearing (`/api/realtime/token`, `/api/openai/hud-summary`, `/api/google/nearby-places`, `/api/google/text-search`), quota-bearing (`/api/mapillary/*`, with a per-IP limit on tiles, and `/api/tomtom/*`, backed by its persistent daily tile budget) and log (`/api/realtime/debug-log`) endpoints refuse cross-site browser requests: a foreign or opaque `Origin`, a `Sec-Fetch-Site` other than `same-origin`/`none` (this is what blocks an `<img>`/navigation that carries no `Origin`), or any reverse-proxy/CDN forwarding header returns `403`. Non-browser loopback tools (the repo QA harnesses POST the token endpoint with no `Origin`) and the explicit `HOST=0.0.0.0` LAN opt-in keep working — the gate deliberately does not require a loopback remote address; that stricter requirement belongs only to the credential panel (`admitKeySetupRequest`). The Host check (`allowedHosts`, applied by `hostCheckPlugin` ahead of every route, since Vite's own check runs only after plugin middleware) rejects a rebinding `Host` before any handler runs, in every mode, and the gate is defense in depth behind it: the LAN opt-in keeps that check and accepts only IP addresses, `localhost` and names listed in `GEV_ALLOWED_HOSTS`. **Limit:** a name you list there is trusted like the app's own address, so list only names you control. The keyless terrain route (`/api/terrain/heights`) uses the same cross-site checks, minus the forwarding-header refusal: it guards only the per-client quota and point cache, not a key or a bill, and the map needs it to render behind a reverse proxy. The CCTV routes (`/api/cctv/*`) use the same keyless checks; their one key-bearing step, the Street View fallback, is skipped for any request with forwarding headers.
 - **Full Content-Security-Policy.** The dev and preview servers send a real CSP (`script-src 'self' 'unsafe-eval' blob:` plus the YouTube, Facebook and X scripts the Nepal event's embedded media loads and the Maps JavaScript API that Street View runs on, with a matching `frame-src` for their players and posts: no inline script and no other script origin; `blob:` covers the object URLs Cesium's bundled workers bootstrap through in the built app), alongside the existing `X-Frame-Options: DENY` and `frame-ancestors 'none'`. `'unsafe-eval'` stays because Knockout, bundled inside Cesium's widgets package, resolves the global object with `eval` at load time and the globe does not initialize without it; styles permit `'unsafe-inline'` and Google Fonts because Vite's dev client injects `<style>` elements.
 
 Allowing `maps.googleapis.com` in `script-src` also trusts its JSONP endpoints, which can bypass the script allowlist if an HTML-injection bug exists; this is an accepted limitation of loading the Maps JavaScript API, alongside the existing `'unsafe-eval'` allowance.
@@ -98,6 +105,11 @@ The dev server is a **key broker**: every server-side key above is spendable by
   `compose.yaml` publishes on `127.0.0.1`: **widen that mapping and every LAN
   client arrives from the same gateway address, which hands them Provider
   Settings too.** Treat publishing beyond loopback as the LAN opt-in above.
+  Compose forwards `GEV_KEY_SETUP_TRUSTED_PEERS` and `GEV_ALLOWED_HOSTS` from
+  the shell or project `.env` before the launcher runs. Set trusted peers to
+  `none` when widening the publish: it becomes an explicit empty list before
+  Vite loads configuration, so the gateway cannot regain Provider Settings
+  access. Unset or blank values preserve automatic gateway discovery.
 - **Provider-side budgets are the real backstop.** For hard spend protection, configure limits where the money is: OpenAI platform usage limits, Google Cloud budget alerts + per-API quotas, and equivalent controls for any other keyed provider.
 - **Pinokio LAN and Cloudflare sharing are refused.** The current supported
   Pinokio release re-reads sharing state when an app registers its Open URL and

build/vite.js

@@ -1,9 +1,29 @@
+import { fileURLToPath } from 'node:url';
 import { applicationHtmlPlugin } from './application-html.js';
 import cesium from 'vite-plugin-cesium';
 import { DEFAULT_ALLOWED_HOSTS, hostCheckPlugin } from './allowedHosts.js';
 import { embedFramingPlugin } from './embed-framing.js';
 import { panelBuildPlugin } from './panel.js';
 
+/**
+ * The repository root (this file lives at `<root>/build/vite.js`), as a
+ * forward-slash path for glob matching. Vite's `fs.deny` patterns are
+ * matched against the full absolute file path, and a bare `**\/dist/**`
+ * matches a `dist` directory at *any* depth — including dependencies that
+ * ship their own, such as `node_modules/vite/dist/client/client.mjs` (the
+ * dev client itself). Anchoring to this repository's root denies only the
+ * project's own build output.
+ */
+const REPO_ROOT = fileURLToPath(new URL('..', import.meta.url))
+  .replace(/\\/g, '/')
+  .replace(/\/$/, '');
+
+export function escapeFsDenyPath(path) {
+  return path.replace(/[()[\]{}*?!+@|]/g, '\\$&');
+}
+
+const REPO_ROOT_GLOB = escapeFsDenyPath(REPO_ROOT);
+
 /**
  * Content-Security-Policy for every document the dev/preview server serves.
  * No inline script is permitted, and the only foreign script origins are the
@@ -47,6 +67,75 @@ export const BROWSER_HEADERS = Object.freeze({
   'X-Content-Type-Options': 'nosniff',
 });
 
+/**
+ * Content-Security-Policy for every `/api` response. API routes return data,
+ * never a document, so a response opened directly in a tab gets no origin and
+ * can load nothing.
+ */
+export const API_CSP = "default-src 'none'; sandbox";
+
+/** Response headers every `/api` response carries. */
+export const API_HEADERS = Object.freeze({
+  'Content-Security-Policy': API_CSP,
+  'X-Content-Type-Options': 'nosniff',
+});
+
+/**
+ * Whether a request reaches an `/api` mount, by the router's own rule: the
+ * prefix compared without case and followed by the end, `/` or `.`. The router
+ * reads an absolute-form target's path without resolving dot segments, so the
+ * path is taken here the same way (scheme and authority dropped, backslashes as
+ * slashes), alongside the raw and the fully parsed path; any match counts.
+ */
+function isApiPath(url) {
+  const raw = String(url || '/');
+  const target = raw
+    .trim()
+    .split(/[?#]/, 1)[0]
+    .replace(/\\/g, '/')
+    .replace(/^[a-z][a-z0-9+.-]*:(?:\/\/[^/]*)?/i, '');
+  let parsed = '';
+  try {
+    parsed = new URL(raw, 'http://localhost').pathname;
+  } catch {
+    /* the unparsed paths still decide */
+  }
+  return [raw.split(/[?#]/, 1)[0], target, parsed].some((path) =>
+    /^\/api(?:$|[/.])/i.test(path),
+  );
+}
+
+/**
+ * Vite plugin that sets API_HEADERS on every API response before any other
+ * middleware runs, so success, error, partial, refused and unknown-route
+ * answers all carry them. Vite's `server.headers` and `preview.headers` only
+ * reach the documents and assets Vite serves itself. A route may still add
+ * headers; a route's own Content-Security-Policy is sent as an additional
+ * policy, which can only restrict further, never replace this one.
+ */
+export function apiResponseHeadersPlugin() {
+  const install = (server) => {
+    server.middlewares.use((req, res, next) => {
+      if (!isApiPath(req.url)) return next();
+      for (const [name, value] of Object.entries(API_HEADERS))
+        res.setHeader(name, value);
+      const setHeader = res.setHeader.bind(res);
+      res.setHeader = (name, value) =>
+        String(name).toLowerCase() === 'content-security-policy' &&
+        String(value) !== API_CSP
+          ? setHeader(name, `${API_CSP}, ${value}`)
+          : setHeader(name, value);
+      next();
+    });
+  };
+  return {
+    name: 'api-response-headers',
+    enforce: 'pre',
+    configureServer: install,
+    configurePreviewServer: install,
+  };
+}
+
 /** Build browser assets with explicit inputs; never load environment or providers. */
 export function createBrowserViteConfig({
   plugins = [],
@@ -61,7 +150,9 @@ export function createBrowserViteConfig({
 } = {}) {
   return {
     plugins: [
-      // First, so no provider route answers a Host the server does not allow.
+      // First, so every API response, including a Host refusal, carries them.
+      apiResponseHeadersPlugin(),
+      // Next, so no provider route answers a Host the server does not allow.
       hostCheckPlugin(),
       cesium(),
       applicationHtmlPlugin(),
@@ -94,7 +185,19 @@ export function createBrowserViteConfig({
       // build/allowedHosts.js); IP addresses are always accepted.
       allowedHosts: [...allowedHosts],
       fs: {
-        deny: ['.env', '.env.*', '*.{crt,pem}', '**/.git/**', '**/ENVIRONMENT'],
+        deny: [
+          '.env',
+          '.env.*',
+          '*.{crt,pem}',
+          '**/.git/**',
+          '**/ENVIRONMENT',
+          '**/.gev-logs/**',
+          '**/.gev-cache/**',
+          // Root-anchored: a bare '**/dist/**' would also deny every
+          // dependency's own dist/ (e.g. node_modules/vite/dist/client),
+          // breaking /@vite/client and other dev-client assets.
+          `${REPO_ROOT_GLOB}/dist/**`,
+        ],
       },
       // These headers protect the document containing Provider Settings and
       // give the whole page a real Content-Security-Policy (BROWSER_CSP).

changelog.d/1014-director-callback-failures.md

@@ -0,0 +1,4 @@
+- Director clock listeners, interaction observers and scene release failures
+  no longer leave the director inconsistent: each scene is released once, and
+  a phase error is kept (with the release failure logged) when cleanup also
+  fails (deepeshbind, #1014).

changelog.d/1056-area-tool-breakdowns.md

@@ -1,12 +0,0 @@
-- `aircraft_in_area` and `vessels_in_area` take `group_by` and `stats`, so an
-  MCP client can ask which airlines, countries, aircraft types or ship types
-  dominate an area, or the average altitude or speed, over every match instead
-  of estimating from the returned rows. Airlines come from the ICAO designator
-  in each callsign (SWA1234 counts as SWA), so the breakdown works on feeds
-  that report no operator; operator and type are counted only where the feed
-  reports them. Ship types count by family, so AIS codes 70 to 79 are all
-  cargo; type 0 ("not available") and the reserved codes 100 to 255 count as
-  unknown. Altitude and speed stats cover airborne aircraft only, so parked
-  aircraft do not pull the means down. Every vessel answer, `find_vessel`
-  included, now reads AIS ship-type codes as their family and a destination
-  with no letters as unknown (quanticsoul4772, #1056).

changelog.d/1057-windows-npm-dep0190.md

@@ -1,4 +0,0 @@
-- On Windows, `npm run doctor` and the Pinokio install no longer print Node's
-  DEP0190 warning ("Passing args to a child process with shell option true can
-  lead to security vulnerabilities"): npm.cmd's fixed subcommand is now part of
-  the shell command string instead of an argument array (quanticsoul4772, #1057).

changelog.d/1071-geo-uri-search.md

@@ -1,3 +0,0 @@
-- Location search accepts two-dimensional WGS84 `geo:` URIs offline, with
-  the existing coordinate framing and label. Unsupported URI fields are passed
-  to the remaining search providers unchanged (cj-vana, #1071).

changelog.d/1078-firms-ipv4-fallback.md

@@ -0,0 +1,4 @@
+- FIRMS fire data loads on hosts where IPv6 is unreachable and IPv4 is slow to
+  connect: a request whose every address fails to connect retries once over
+  IPv4, and FIRMS warnings name the underlying connection errors instead of
+  only `fetch failed` (jeffblakely, #1078).

changelog.d/1094-dependency-security-patches.md

@@ -1,4 +0,0 @@
-- Update DOMPurify to 3.4.17, Sharp to 0.35.5 and source-map-js to 1.2.2 for
-  GHSA-p98j-92pf-mc4p, GHSA-6688-9rhm-gjv2, GHSA-wq5f-xc86-pv6w and
-  GHSA-68fv-2mgg-jv7q; `npm audit` now reports no vulnerabilities (NurstarK,
-  #1094).

changelog.d/1096-military-hold-track-speed.md

@@ -1,3 +0,0 @@
-- Military aircraft keep their last heading and speed when an adsb.lol row omits
-  `track` or `gs`, instead of turning north and stopping; a grounded row without
-  a speed still reads 0 (Aditya, @Rohilalala, #1096).

changelog.d/1097-overpass-remark-failure-phrases.md

@@ -1,5 +0,0 @@
-- Overpass data whose element tags contain a failure phrase ("timed out",
-  "runtime error", "too many requests" and similar, e.g. a place named "Timed
-  Out Escape Rooms") is returned as data instead of being refused and putting
-  the endpoint on cooldown; upstream failures are read from the remark (Aditya,
-  @Rohilalala, #1097).

changelog.d/1101-tle-catalog-number-match.md

@@ -1,3 +0,0 @@
-- Skip TLE sets whose line 1 and line 2 carry different catalog numbers, so a
-  spliced catalog cannot pair one satellite's elements with another's; the next
-  valid set still parses (VG31OP, #1101).

changelog.d/1111-map-fallback-retry.md

@@ -1,5 +0,0 @@
-- A failed Esri Satellite or keyless terrain load still shows OSM or flat terrain
-  at once, but no longer lasts the whole session: while the fallback is on
-  screen, the real provider is retried in the background (30 seconds, doubling
-  to a 10-minute cap) and replaces it live once it loads. Map switches never
-  wait for a retry (Aditya, @Rohilalala, #1111).

changelog.d/1115-aircraft-altitude-band-unknown.md

@@ -1,2 +0,0 @@
-- Exclude aircraft without a reported altitude from requested altitude bands;
-  unfiltered aircraft queries still retain them (rudycelekli, #1115).

changelog.d/1117-google-viewer-lifecycle.md

@@ -1,3 +0,0 @@
-- Release superseded Google Street View open waits and suppress metadata
-  requests whose viewer was unmounted while the service loaded (rudycelekli,
-  #1117).

changelog.d/1118-cctv-snapshot-fallback-provenance.md

@@ -1,3 +0,0 @@
-- Label camera-tool Street View fallbacks as historical Google imagery rather
-  than the current camera view; keep unknown frame provenance explicit
-  (rudycelekli, #1118).

changelog.d/1135-director-save-status-run-results.md

@@ -1,5 +0,0 @@
-- Scenes keep the "Scene not saved" status when a capture, update, append or
-  import cannot be saved, and an unreadable saved project no longer overwrites
-  the recovery checkpoint. `startScene()` resolves to its documented result,
-  `afterShotId` works without an explicit scene, and `scenesRun` counts the
-  distinct scenes queued (djabhi31, #1135).

changelog.d/1142-antimeridian-fire-perimeters.md

@@ -1,6 +0,0 @@
-- Fire-perimeter queries handle outlines and holes crossing the antimeridian:
-  areas enclosed near ±180° are included, areas at the opposite meridian are
-  excluded, and returned perimeter coordinates stay near the dateline. Incident
-  cards use the same circular longitude mean and compare multipart outline
-  areas along short longitude edges, keeping the card on the largest polygon
-  (Arianna Method, @ariannamethod, #1142).

changelog.d/1171-director-goto-shot.md

@@ -1,3 +0,0 @@
-- Director shot actions land on the requested shot. A seek to a shot's start
-  could round a hair below it and select the end of the previous shot for some
-  shot counts and durations (Aditya, @Rohilalala, #1171).

changelog.d/1172-cctv-missing-numbers.md

@@ -1,13 +0,0 @@
-- Keep missing CCTV numbers unknown instead of reading them as zero. `Number`
-  turns null, blank strings and booleans into 0 or 1, and the camera source
-  list sends an unknown number as JSON null, so a source-pack camera that left
-  out its pose reached the browser as zeros clamped to each field's floor —
-  facing north, pitch −2°, FOV 20°, range 120 m, mount 6 m and ground 0 m —
-  instead of the defaults (id-hash heading, −17°, 74°, 700 m, 24 m and the
-  city's ground); a null or blank position placed the camera at 0,0. The
-  server's `toFiniteNumber` and the browser's `safeNumber` now treat absent,
-  blank and boolean values as missing. The same conversion also stops a
-  Tallinn row with a null heading reading as a confident north-facing camera,
-  a Caltrans camera with a blank elevation losing its 150 m ground prior, and
-  a TfL or Catalonia camera with a null or blank coordinate being kept at 0,0
-  or on the zero meridian (omerbberk, #1172).

changelog.d/1173-antimeridian-ground-floor.md

@@ -1,10 +0,0 @@
-- Flights' ground floor works across the antimeridian. The viewer-distance
-  check behind the 150 km floor radius and its copy in the photoreal mesh-floor
-  sampler subtracted longitudes without wrapping, so two points 21 km apart
-  across 180° measured about 38,000 km and low or grounded aircraft just across
-  the line from the viewer were never floored. A contact's display corridor
-  walked a segment across 180° the long way round, spending its cell budget on
-  ground behind the contact, and a contact on the seam lost its cell hysteresis.
-  SEARCH NEARBY SITES on a view across 180° searched Google Places around
-  longitude 0, on the far side of the globe, with a radius sized from the view's
-  height alone; it now searches the view (Aditya, @Rohilalala, #1173).

changelog.d/1186-launch-unknown-coordinates.md

@@ -1,4 +0,0 @@
-- Keep missing launch-pad coordinates unknown so launches use the location
-  fallback or stay off the map instead of appearing at 0°N 0°E. Missing stage
-  flight numbers no longer show "FLIGHT 0"
-  (Rudy Celekli, @rudycelekli, #1186).

changelog.d/1190-bikeshare-spain-cities.md

@@ -1,6 +0,0 @@
-- Add nine Spanish city bike systems to Bike Share and `get_bike_share`: BiciMAD
-  (Madrid), Valenbisi (Valencia), Bizi Zaragoza, Sevici (Seville), BIKI
-  (Valladolid), BiciCoruña, Dbizi (Donostia-San Sebastián), Bilbao Bizi and
-  BicinRivas, about 1,840 stations. Station names read underscores as word
-  breaks, and station capacity counts docks rather than PBSC's geofenced area
-  (ulihhhh, #1190).

changelog.d/1197-launch-library-provider-guidance.md

@@ -1,5 +0,0 @@
-- Share Launch Library request cache keys across installations refreshing in the
-  same UTC minute, identify the app to the provider, and explain that standard
-  space-missions access needs no key. Optional higher-rate LL2 tokens are paid
-  upgrades; existing local cache and server-only token handling are unchanged
-  (rudycelekli, #1197).

changelog.d/1199-launch-cache-provenance.md

@@ -1,3 +0,0 @@
-- Keep Space Missions marked STALE when Launch Library 2 falls back to cached
-  launch data, and return to NOMINAL after a fresh response without discarding
-  retained missions (rudycelekli, #1199).

changelog.d/1200-cctv-live-icon-color.md

@@ -1,5 +0,0 @@
-- Color CCTV cameras with a video feed violet. Cameras with an HLS, MP4 or
-  WebM feed were the same cyan as stills, so a DelDOT or Statens vegvesen
-  video camera could only be found by opening it. Stills stay cyan and the
-  active camera stays amber, and focus de-emphasis fades the violet the same
-  way (Danielslay86, #1200).

changelog.d/1201-cctv-stills-aspect.md

@@ -1,4 +0,0 @@
-- Draw CCTV stills at their source aspect on the monitor plane instead of
-  stretching them to the 16:9 canvas. Most DOT cameras publish 4:3 frames, so
-  every still was widened; they are now centered and pillarboxed on the dark
-  the placeholder already ends on (Danielslay86, #1201).

changelog.d/1209-layer-errors-english-in-data.md

@@ -0,0 +1,5 @@
+- Keep Directions route errors, the Local ADS-B receiver error and Global
+  Context cohort reasons English in layer data; the Layers panel, Radio card
+  and awareness panel still show them in the interface language. The route
+  proxy's "routing busy" and "route proxy error" refusals are now translated
+  too (daikaginza, #1209).

changelog.d/1220-openai-typed-send.md

@@ -1,3 +0,0 @@
-- Avoid starting or queuing a reply when the local channel rejects a typed OpenAI
-  command, while preserving an earlier accepted deferred input
-  (Manjunath, #1220).

changelog.d/1228-cctv-ontario-511-key.md

@@ -1,4 +0,0 @@
-- Load Ontario 511 cameras again. 511on.ca's camera endpoint now requires a
-  free developer key; set `ONTARIO_511_API_KEY` to enable the pack, which is
-  otherwise skipped with one log line saying where to get a key
-  (quanticsoul4772, #1228).

changelog.d/1233-tarktee-datex-catalog-hardening.md

@@ -1,4 +0,0 @@
-- Harden the Tarktee (Estonia) DATEX2 camera catalog fetches: refuse redirects,
-  cancel both response streams when either response fails or overflows the 4 MB
-  byte cap, and deduplicate camera IDs before per-pack prioritization
-  (yaka0007, #1233).

changelog.d/1234-cctv-catalog-background-refresh.md

@@ -1,5 +0,0 @@
-- Serve the camera catalog while it refreshes. An expired catalog made every
-  camera request wait for the slowest pack to reload; it is now answered at
-  once while one background refresh runs, so only the first load waits. Estonia's
-  slow Tarktee feeds get 30 s instead of 15 s, so the pack no longer drops out
-  on about a third of loads (quanticsoul4772, #1234).

changelog.d/1237-taiwan-freeway-cctv.md

@@ -1,4 +0,0 @@
-- Add Taiwan's national freeway cameras from the Freeway Bureau, MOTC to CCTV:
-  ~1,800 cameras read at runtime from the official MOTC 2.0 open-data table,
-  with on-demand snapshots and attribution. No API key is required; set
-  `CCTV_TAIWAN_ENABLED=0` to skip it (419vive, #1237).

changelog.d/1283-satellite-cache-provenance.md

@@ -1,3 +0,0 @@
-- Report cached CelesTrak satellite records as stale in the Data Layers row,
-  preserving separate core and dense catalog provenance through refresh,
-  removal and lifecycle cleanup (rudycelekli, #1283).

changelog.d/1284-route-plausibility-segment.md

@@ -1,3 +0,0 @@
-- Keep aircraft route labels on the scheduled airport leg instead of accepting
-  its distant great-circle extensions, preserving generous endpoint tolerance
-  across the signed-angle branch cut (rudycelekli, #1284).

changelog.d/1290-local-adsb-altitude-filter.md

@@ -1,10 +0,0 @@
-- Local ADS-B filters implausible altitude changes and holds the accepted
-  value consistently for markers, cards and models. Browser refusals count
-  actual altitude frames rather than unrelated aircraft messages. Decoder
-  feeds use a conservative five-second recovery with three advancing
-  snapshots and aircraft message activity, explicitly marked as inferred.
-  Held values retain their altitude source and measurement time through
-  context and analyst results; feeds report an unknown measurement time.
-  Cached snapshots and transport jitter cannot recount refusals. Ground
-  reports reset the airborne reference, and no absolute altitude ceiling is
-  imposed (Pedro Lobato's original filter, #801, with maintainer corrections).

changelog.d/1344-inline-panel-visibility.md

@@ -0,0 +1,4 @@
+- Pause the HUD's camera readout while the page is hidden, as polled layers
+  already do. An app embedded inline in a panel keeps both updating, because the
+  panel's host can report the page as hidden while it is on screen (nu-stats,
+  #1344).

changelog.d/1374-director-seek-visibility.md

@@ -0,0 +1,4 @@
+- Restore a shot's declared layer visibility when seeking within it after manual
+  layer changes, including toggles still in flight. Only changed layers are
+  reconciled; refused restoration reports a failed seek and keeps the last
+  position, while undeclared operator layers are preserved (@oneill9, #1374).

changelog.d/1401-geocode-place-region.md

@@ -0,0 +1,2 @@
+- A "place, region" search such as "Paris, Texas" now lands on the place in
+  that region instead of a namesake elsewhere (quanticsoul4772, #1401).

changelog.d/1402-terrain-429-pause.md

@@ -0,0 +1,5 @@
+- The terrain proxy stops asking the upstream for a while after a 429
+  (its Retry-After, at most 10 minutes, or 60 s) instead of retrying on every
+  page request, and a Retry-After longer than its 10 s retry budget now ends
+  the retries at once instead of sleeping the budget out (quanticsoul4772,
+  #1402).

changelog.d/1404-perimeters-stale.md

@@ -0,0 +1,3 @@
+- Fire Perimeters and `get_fire_perimeters` say when WFIGS is unreachable and
+  the last snapshot is being shown (STALE, its age, "data may be stale"), and
+  that snapshot is served for at most 24 hours (quanticsoul4772, #1404).

changelog.d/1405-traffic-layer-stale.md

@@ -0,0 +1,3 @@
+- The Traffic layer reads STALE instead of LIVE when the TomTom proxy serves
+  cached flow tiles (budget spent or TomTom failing), and the row dates them by
+  the oldest cached tile (quanticsoul4772, #1405).

changelog.d/1425-right-rail-vertical-tabs.md

@@ -0,0 +1,11 @@
+- The right rail (Display, CCTV, Street Level, Context, plus Weather and Recent
+  Imagery while shown) is a vertical strip of icon tabs instead of an accordion
+  of collapsed launcher cards: at most one panel is open in every desktop HUD
+  layout, and the open tab and its panel share one surface and outline, like a
+  folder tab. On a short window the rail rises toward the HUD corner above it
+  rather than scroll. A first-time visitor on a desktop finds Display open; a
+  stored choice still wins. The panels' own collapse arrows are gone on desktop:
+  the tab opens and closes a panel, Escape inside one closes it and returns
+  focus to its tab, and the strip is a keyboard-navigable tablist. Saved
+  preferences, share links and the phone sheet shell are unchanged (gekh,
+  #1425).

changelog.d/1430-traditional-chinese.md

@@ -0,0 +1,4 @@
+- Add Traditional Chinese (zh-Hant) with language selection and localized
+  Chinese readouts: the Simplified Chinese catalog written in Traditional
+  characters, based on translations by @abiyeenzo (#914) and @EDIT-Aeterna
+  (#979) (German, @gekh, #1430).

changelog.d/1459-hud-place-lookups.md

@@ -0,0 +1,5 @@
+- Cut the Google requests the HUD's AI summary makes on its own. It no longer
+  looks up place names when no OpenAI key is configured, reverse-geocodes at
+  most two points instead of up to four, and looks up again only once the view
+  shows a different area, not after every small pan, so a small pan no longer
+  asks OpenAI for a new summary either (samehkhamis, #0000).

changelog.d/1463-dev-tool-updates.md

@@ -0,0 +1,4 @@
+- Update the development tools to Vite 6.4.4 and Puppeteer 25.16.0, which
+  clears the open npm advisories for the dev server and the browser test
+  tooling, and remove the unused local screenshot helper `scripts/shot-sink.mjs`
+  (samehkhamis, #1463).

changelog.d/1466-panel-chrome-consistency.md

@@ -0,0 +1,5 @@
+- Give the side panels one look. Every panel title now uses the command dock's
+  label type in a brighter colour; a panel's edge and title light up on hover,
+  as the dock's trays do; and in the default theme each collapse button sits
+  19px from its panel's edge (plus the scrollbar's width in an open, scrolling
+  panel where the system always shows scrollbars) (asturksever, #1466).

changelog.d/1467-remove-operator-hud-layout.md

@@ -0,0 +1,3 @@
+- Remove the Operator HUD layout. Display > HUD > Layout and the HUD voice
+  action now offer Tactical, Minimal and Cyber; share links, scenes and saved
+  views that name Operator open in Tactical (asturksever, #1467).

changelog.d/1468-remove-snow-preset.md

@@ -0,0 +1,4 @@
+- Remove the Snow visual preset. Visual Presets, keyboard shortcuts, the
+  Cockpit vision carousel and the visual-style voice action now offer Normal,
+  CRT, NVG, FLIR, Anime and Noir; share links and scene shots that name Snow
+  open on Normal (asturksever, #1468).

changelog.d/1470-ukrainian.md

@@ -0,0 +1,3 @@
+- Add Ukrainian (uk) to the language picker: the whole interface in Ukrainian,
+  with its four plural forms and Cyrillic HUD units. Based on the Ukrainian
+  translation by @meirm (#312) (German, @gekh, #1470).

changelog.d/1471-context-panel-cleanup.md

@@ -0,0 +1,7 @@
+- Remove the Radio icon from the Context panel header, along with the compact
+  Radio player it opened; Radio stays in Context as its own section, and
+  Cockpit's compact Radio is unchanged. Context is also easier to read: the
+  Contacts / Space Missions modes are one segmented control, labels and
+  guidance are larger and higher contrast, the standby hint is plain text
+  instead of a dashed box, and the panel draws no glow halo. Cyber keeps its
+  own framed buttons and red titles (asturksever, #1471).

changelog.d/1473-italian.md

@@ -0,0 +1,3 @@
+- Add Italian (it) to the language picker: the whole interface in Italian,
+  with Italian plural forms and labels shortened to fit the panels. Based on
+  the translation by @abiyeenzo (#912) (German, @gekh, #1473).

changelog.d/1475-brazilian-portuguese.md

@@ -0,0 +1,4 @@
+- Add Brazilian Portuguese (pt) to the language picker, with every screen
+  translated and Portuguese plural forms. The CCTV summary line now names its
+  calibration, source and view in the page language. Based on translations by
+  @abiyeenzo (#909) (German, @gekh, #1475).

changelog.d/1476-french.md

@@ -0,0 +1,4 @@
+- Add French (fr) to the language picker, with French typography and plural
+  forms. With nine languages the picker now shows its search field. Based on
+  the translation by @abiyeenzo (#907), checked against @meirm's French
+  catalog (#312) (German, @gekh, #1476).

changelog.d/1477-german.md

@@ -0,0 +1,3 @@
+- Add German (de) to the language picker, with a full translation of the
+  interface and a German style guide in docs/translations/de.md. Based on
+  translations by @abiyeenzo (#908) (German, @gekh, #1477).

changelog.d/1478-japanese.md

@@ -0,0 +1,4 @@
+- Add Japanese (ja) to the language picker, with year-first dates, Japanese
+  counters, unit words joined to their numbers (5分前, 1時間5分) and CJK label
+  rules for Japanese text. Based on translations by @abiyeenzo (#913)
+  (German, @gekh, #1478).

changelog.d/1485-cctv-view-thinning.md

@@ -0,0 +1,4 @@
+- Draw only the CCTV cameras in view, and thin them to one per ground cell when
+  zoomed out. Dragging the globe with the default 4,000-camera catalog no
+  longer stalls, and the camera picker lists the cameras in view with a count
+  of the ones outside it (samehkhamis, #1485).

changelog.d/287-shared-great-circle-distance.md

@@ -1,5 +0,0 @@
-- The client's great-circle distances now come from one shared
-  `src/geoDistance.js` (`greatCircleKm`/`greatCircleMeters`, `{lat, lon}`
-  points). The Earth radius is standardized on 6371.0088 km, so distances shift
-  by about 1.4 ppm and region areas by about 2.8 ppm, and missing or
-  out-of-range points return `Infinity` (onionviolet, #287; Rajojha-1, #749).

changelog.d/605-fl511-florida-cameras.md

@@ -1,9 +0,0 @@
-- Add FL511 (Florida DOT) traffic cameras as an opt-in CCTV source pack:
-  the statewide ArcGIS catalog, read a page at a time under a byte cap with
-  redirects refused, and frames pinned to FL511's two image hosts over HTTPS.
-  FL511's terms limit its content to individual, personal use, and any other
-  use (a public deployment included) needs FDOT's express written consent, so
-  the pack stays off unless `CCTV_FLORIDA_ENABLED=1`. Headings come from the
-  catalog's direction codes, and camera ids come from the image channel, since
-  the catalog's ID column repeats across regions. `CCTV_FLORIDA_MAX_SOURCES`
-  sets the cap (Danielslay86, #605).

changelog.d/686-terrain-heights-bounds.md

@@ -1,9 +0,0 @@
-- Bound what a caller can grow through `/api/terrain/heights`. Every distinct
-  5-decimal point was a permanent in-memory entry, a permanent line in an
-  uncapped `.gev-cache/terrain-heights.json`, and a live upstream call, with
-  nothing limiting the rate. The point cache now holds at most 50,000 entries
-  and evicts oldest-first, a cache file above
-  24 MB is not read back, and the route is limited to 90 requests/minute per
-  client (270 global). Evicting a point costs one refetch, never a wrong
-  answer, since terrain does not move. Ordinary use is unaffected: a full
-  `test:track` run drives 10 requests, peaking at 8/min (daikaginza, #686).

changelog.d/761-dev-unwatched-runtime-dirs.md

@@ -1,5 +0,0 @@
-- The dev server no longer watches `.gev-cache` and `.gev-logs`. Providers write
-  cache files and logs there while the app runs, and none of it is source, so
-  the watcher now skips it; this guards against the DNS-lookup delays heavy
-  cache writes have caused, though no difference was measured on current main
-  (monwiss, #761).

changelog.d/767-alpha5-catalog-numbers.md

@@ -1,11 +0,0 @@
-- Read satellite catalog numbers written in Alpha-5, the TLE spelling of
-  numbers above 99999: a letter for the first two digits, skipping I and O
-  (`A0000` is 100000, `Z9999` is 339999). The satellites layer converted such a
-  field to `NaN`, so every Alpha-5 satellite shared one catalog entry and all
-  but the first were dropped as duplicates; the satellite tools read the same
-  field as no number, so such a satellite could not be found by it. The layer
-  and the tools now decode the field in `src/sources/tle.js`, and reject a
-  malformed one (a sign, decimal point, hex, embedded space or stray letter)
-  instead of reading part of it as a number. This is Alpha-5 TLE
-  compatibility: CelesTrak's TLE feed carries no satellite above 99999, which
-  needs the OMM feed (#1191) (Honorius Neogy, #767, fixes #751).

changelog.d/787-changelog-fragments.md

@@ -1,7 +0,0 @@
-- Changelog entries are now one file per pull request. A change adds
-  `changelog.d/<pull request>-<slug>.md` instead of editing the top of
-  `CHANGELOG.md`, which two pull requests in flight could not share — it was the
-  most frequent merge conflict in the open queue, and for six of them the only
-  one. `npm run changelog` splices the directory into `CHANGELOG.md` at release
-  time and empties it; `npm run changelog:check` reports the batch and changes
-  nothing. Fragment text is copied through unchanged (daikaginza, #787).

changelog.d/816-radio-owner-restoration.md

@@ -1,7 +0,0 @@
-- Close the compact Radio disclosure when an adaptive tactical right-rail
-  restore directly expands Context, before Space Missions can be covered.
-  A repeated Context-open request also clears stale disclosure state.
-  Real PanelChrome constructor wiring and the rail reflow path are covered
-  by focused regressions. Credits: kvnloo (#816), raysung-2026's original
-  #804 report, asturksever's review, and quanticsoul4772's independent
-  Windows diagnosis.

changelog.d/871-vessels-idle-render.md

@@ -0,0 +1,7 @@
+- Let the scene idle with AIS vessels enabled. Vessels no longer hold the
+  continuous render loop; they request frames for new data and selection, one
+  trailing frame after the camera stops, and hold the loop only while focus
+  emphasis animates or a vessel stays dimmed under a tracked target. A parked
+  vessels-only scene went from continuous rendering to 0 frames in 5 s. While
+  anything is tracked, the vessel focus pass skips hidden sprites at rest:
+  about 4 ms to 1.2 ms per pass over 12,000 vessels (waar19, #871).

changelog.d/872-gemini-live-voice.md

@@ -1,4 +0,0 @@
-- Add optional Gemini Live voice to the standalone app, with a provider chooser,
-  server-held API key, microphone streaming, shared map actions and captions.
-  Switching providers ends the old conversation and preserves the input mode
-  (Manjunath, #872).

changelog.d/880-world-packet-boundary.md

@@ -1,6 +0,0 @@
-- Extract a reusable model-free World Packet from the existing voice
-  `get_current_view_state` owner without restoring disabled layers to the
-  model context. Keep the enabled-only payload, disabled-layer count, source
-  provenance, action result and view-state contract; read the layer roster once
-  per packet; voice retains the speech/card envelope at its own boundary.
-  Credits: original GEV voice/layer contributors and #880 implementation.

changelog.d/945-cctv-vegvesen-kartverket-heights.md

@@ -1,17 +0,0 @@
-- Give each Statens vegvesen camera its own ground height from Kartverket's
-  keyless point-height API (CC BY 4.0) instead of one flat 150 m prior, so
-  mountain-pass cameras no longer sit hundreds of metres below the terrain
-  where neither the point-height prior nor the ground snap resolves. About 850
-  of ~855 cameras get a height; the rest keep the old prior. Requests carry 20
-  points, the most the API answers from its 1 m terrain model, eight at a
-  time; a cold lookup takes about 6–13 s. Cameras over water use the water
-  surface rather than the sea-floor depth the API returns there; for bridge
-  cameras that is still below the deck. Heights are cached for good and misses
-  for 6 h, so a refresh only asks about new or moved cameras. After a
-  failing request (a 408, 429 or 5xx, a network error, a request over 10 s or
-  an unreadable body) the lookup stops and backs off (Retry-After, else
-  30 min, longer than the refresh). The lane waits at most 12 s from its
-  start, and only on a cold cache; a slower first lookup leaves the cameras it
-  had not reached on the flat prior until the next 15-minute refresh, and
-  keeps filling the cache meanwhile.
-  `CCTV_VEGVESEN_HEIGHTS=0` turns it off. Follow-up to #929 (trygvehhh, #945).

changelog.d/956-a22-brennero-webcams.md

@@ -0,0 +1,8 @@
+- Add the Autostrada del Brennero (A22, Brenner–Modena) motorway webcams as a
+  CCTV pack, the first Italian cameras. The 13-camera list is one keyless
+  request to the Open Data Hub (NOI Techpark) tourism API, which republishes
+  Autobrennero's own list with coordinates; frames are the operator's stills,
+  refreshed about once a minute and pinned to each camera's own `km<N>.jpg`.
+  Each camera's ground elevation comes from a per-kilometre DEM table, since
+  the road climbs from the Po valley to the Brenner Pass. `CCTV_A22_ENABLED=0`
+  disables the pack (Jibran Tahir, @jibraaan, #956). Closes #155.

changelog.d/970-recent-imagery-details-scroll.md

@@ -1,3 +0,0 @@
-- Recent Imagery: opening DETAILS scrolls its card into view when it opens below
-  the fold. The panel used to restore the previous scroll position right after
-  the reveal, so the card stayed out of sight (Ian Blenke, #970).

changelog.d/973-tomtom-cross-site-gate.md

@@ -1,4 +0,0 @@
-- Cross-site browser requests can no longer spend the TomTom traffic-tile
-  budget through `/api/tomtom/*`. The shared same-site gate runs before status,
-  cache, and upstream work; same-origin app requests and non-browser local
-  callers remain supported (Sunil56224972, #973).

changelog.d/974-street-level-slim.md

@@ -1,6 +0,0 @@
-- Street Level is rebuilt around one small provider registry: Mapillary,
-  KartaView, Panoramax and Google Street View share one coverage drawer and
-  one photo viewer, one source lit at a time. Floating and docked panels,
-  FOLLOW, surface modes, the legend and the Mapillary proxy's disk cache are
-  gone; `.gev-cache/mapillary/` from earlier runs is no longer read and can be
-  deleted (gekh, #974).

changelog.d/975-terrain-cross-site-gate.md

@@ -1,8 +0,0 @@
-- Cross-site pages can no longer fill the terrain-height cache or spend the
-  visitor's own `/api/terrain/heights` rate-limit quota through the visitor's
-  browser. The route refuses a cross-site `Sec-Fetch-Site` or a foreign or
-  opaque `Origin` before rate limiting, cache access or upstream work. Unlike
-  the cost-bearing routes it still answers same-origin requests that arrive
-  through a reverse proxy, so terrain keeps rendering behind nginx, Caddy or
-  Cloudflare instead of falling back to the geoid (Sunil56224972, daikaginza,
-  #975).

changelog.d/990-hong-kong-cctv.md

@@ -1,7 +0,0 @@
-- Add Hong Kong Transport Department traffic snapshot cameras as a keyless CCTV
-  source pack: the public DATA.GOV.HK English locations XML, frames pinned to
-  `tdcctv.data.one.gov.hk`, with DATA.GOV.HK Terms of Use attribution. By
-  default nearly the full TD catalog (~1,013 cameras; cap 1,100) loads,
-  prioritized across Hong Kong Island, Kowloon and the New Territories. Headings
-  use the shared id-hash fallback at low confidence. `CCTV_HK_MAX_SOURCES` sets
-  the cap (8–1,200) and `CCTV_HK_ENABLED=0` turns the pack off (JCY2515, #990).

compose.yaml

@@ -5,6 +5,11 @@ services:
     # lands in the bind-mounted repo, so run as you, not root. UID/GID are
     # unset on Docker Desktop, where the 1000 fallback is ignored anyway.
     user: "${UID:-1000}:${GID:-1000}"
+    # Forward explicit shell/.env policy before the launcher discovers a gateway.
+    # Unset values stay unset so the default loopback-only install still works.
+    environment:
+      - GEV_KEY_SETUP_TRUSTED_PEERS
+      - GEV_ALLOWED_HOSTS
     ports:
       # Publish to loopback only. Docker's default ("4173:4173") would bind
       # every host interface, which quietly turns the LAN warning in the README
@@ -17,5 +22,8 @@ services:
       # UI land in the .env on your host instead of vanishing with the
       # container. node_modules stays in the image: sharp and friends are
       # compiled for Linux and must not be shadowed by a host install.
-      - .:/app
+      # `:z` relabels the checkout for containers on SELinux hosts (Fedora,
+      # RHEL); without it the container cannot read /app at all and Node
+      # reports the launcher as "Cannot find module". Elsewhere it is ignored.
+      - .:/app:z
       - /app/node_modules

docs/CODE-BOUNDARIES.md

@@ -79,17 +79,13 @@ moves it. Do not label all ingestion modules platform-independent by filename.
 
 | Retained entry                                      | Owner and current reason                                                                                           |
 | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
-| `src/ui.js`                                         | UI facade; direct callers retain standalone StyleManager defaults. Normal assembly uses `src/ui/composition.js`    |
 | `src/data/manager.js`                               | Lifecycle/panel compatibility and existing tests; normal assembly constructs lifecycle and presentation separately |
 | `src/data/<layer>.js`                               | Legacy default instances; new assembly calls layer factories with supplied sources                                 |
-| `src/data/localGeojson.js`                          | Infrastructure compatibility factories; catalog imports services from `src/app/localGeojsonServices.js` directly   |
-| `src/app/sourceSlot.js`                             | Re-export for direct callers/tests; portable slot ownership is `src/sources/sourceSlot.js`                         |
 | `src/app/sources.js`, `src/services/application.js` | Existing default/override API; current application construction supplies its own instances                         |
 | `server/providers/local.js`                         | Existing Node composition barrel and provider helper re-exports                                                    |
 
-The two exact standalone-import exceptions are `src/ui.js` to
-`src/standalone/catalog.js` and `server/providers/local.js` to
-`server/standalone/key-setup.js`. They do not authorize new compatibility
+The one exact standalone-import exception is `server/providers/local.js` to
+`server/standalone/key-setup.js`. It does not authorize new compatibility
 back-edges. Voice actions use plain `src/data/feedState.js`, not the manager
 facade. Settings filesystem hardening belongs in
 `server/standalone/key-setup-hardening.mjs`; its settings policy is unchanged.
@@ -237,7 +233,7 @@ DOM elements and callbacks; importing it creates no browser state. `destroy()`
 removes owned listeners and cancels pending work without changing saved state
 or moving focus. Call it before removing or replacing the controls.
 
-`src/ui.js` retains panel layout, persistence, share restoration and application
+`src/ui/applicationShell.js` retains panel layout, persistence, share restoration and application
 reactions to state changes. Map Source selection and Location draft cleanup are
 provided through callbacks. The component imports no globe, data, application
 or server modules. Package checks and scoped formatting cover this entry.
@@ -374,6 +370,15 @@ renderer, persistence or services. The facade retains panel visibility, share
 restore claims and render scheduling. Both controls are destroyed before the
 facade's asynchronous teardown can yield.
 
+## Ordinary action buttons
+
+`src/ui/actionButton.js` is a native, listener-free view helper used by Scene
+presentation and sharing-toolbar owners. It receives translated text and explicit
+presentation/accessibility properties. Feature controllers own action dispatch,
+state, persistence and cleanup. Static Scenes/CCTV templates use the same CSS
+surface and preserve IDs and layout hooks. The helper imports no application,
+renderer, storage or services; it belongs to the consuming package closures.
+
 ## Display controls
 
 `ui/display` owns Display button, selector and slider subscriptions. It receives
@@ -461,8 +466,8 @@ release listeners; pending action feedback is limited to its current owner.
 ## UI assembly and styles
 
 `ui/shell` assembles controls from supplied existing layer, navigation, terrain,
-rendering, HUD and share operations. `src/standalone/ui.js` provides the running
-application's instances; `src/ui.js` remains the compatibility entry. The shell
+rendering, HUD and share operations. `src/standalone/controls.js` provides the running
+application's instances. The shell
 imports no standalone bootstrap or concrete live layer implementation.
 Panel layout, position/drag, notices, recording and deferred UI work have separate
 owners with synchronous cleanup. Existing scene, share and HUD engines retain
@@ -593,6 +598,10 @@ state subscriptions retain their existing event contract.
   tracking handoff. It reads Cockpit admission and uses supplied tracking operations.
 - `ui/share-restoration` owns the initial restore transaction, layer coordinator,
   status notices and gesture/timer cleanup.
+- `share/view-codec` is the share-link codec (`decodeShareView`,
+  `encodeShareView`). It is pure (no DOM, no Cesium), so a host's server can
+  read a `/share/<code>` link, for example to describe it in link previews.
+  `share/link-path` reads and builds the `/share/<code>` address itself.
 - `ui/visual-settings` owns style preferences, detection overrides, display inputs
   and IR cleanup. Its engine services and panel operations are explicit.
 - `ui/panel-chrome` owns disclosure, docking, collapse preferences and temporary
@@ -729,3 +738,32 @@ sources supply `{records, droppedCount, status, saturated}`; viewport filtering,
 exact-bound retry and rendering stay in the layer. Legacy cache saturation is
 decoded in the source. Source and geometry modules remain independent of Cesium,
 DOM and platform middleware.
+
+### Native form fields
+
+`src/ui/formField.js` constructs native numeric inputs without listeners or
+application state. Static selects and number inputs use the same `gev-field`
+surface, with explicit compact and inline densities. Feature owners retain
+option identity/order, bounds, parsing, draft values, input/change timing and
+teardown. CCTV effective-pose conversion and tuner/device operations remain
+feature responsibilities. A Vue replacement can reuse this contract and CSS;
+it replaces DOM construction, rather than adding a second state owner.
+
+The shared stylesheet owns field surfaces and disabled opacity; feature and theme
+palettes use `--gev-field-background`, `--gev-field-border-color`,
+`--gev-field-color` and `--gev-field-disabled-opacity`. Radio retains its own
+compact density and arrow space. CCTV owns calibration editor width in
+`cctv.css`; the shared inline density does not impose a feature-specific width.
+Cyber supplies a shared-field palette explicitly and keeps its legacy native
+field rules separate, so Radio's palette remains an intentional exception.
+
+### Read-only status badges
+
+`src/ui/statusBadge.js` constructs/updates ordinary badges without listeners,
+status inference or live-region policy. It consumes translated text and controlled
+visibility; appearance variants share CSS rather than mapping machine states to
+universal severity. CCTV owns frame/source and calibration rules and their data
+attributes, while Weather owns coverage labels. The keyed rail-card owner keeps
+node identity, header focus, disclosure and teardown. The shared adapter never
+creates another state store or announces all card updates. A Vue view can replace
+this adapter and retain these presentation inputs and styles.

docs/I18N.md

@@ -35,7 +35,7 @@ A module the server, tools or other portable code also imports must not load the
 <input placeholder="Search any location..." data-i18n-placeholder />
 ```
 
-`data-i18n` replaces the element's text, so put it on the element that directly holds the text, never on a parent with child elements. `data-i18n-title`, `data-i18n-aria-label` and `data-i18n-placeholder` translate that attribute. Markup is translated once at boot, and switching language reloads the page. A module that holds work a reload would lose (an unsaved edit, an open session) registers it with `registerUnsavedWork(() => busy ? msg('unsaved …') : null)` from `src/i18n/index.js`, and the language picker asks before reloading.
+`data-i18n` replaces the element's text, so put it on the element that directly holds the text, never on a parent with child elements. `data-i18n-title`, `data-i18n-aria-label` and `data-i18n-placeholder` translate that attribute. `data-i18n-context="radio tag"` gives the element's text a context, the catalog entry `radio tag|All`, as `t('All', { context: 'radio tag' })` does in code. Markup is translated once at boot, and switching language reloads the page. A module that holds work a reload would lose (an unsaved edit, an open session) registers it with `registerUnsavedWork(() => busy ? msg('unsaved …') : null)` from `src/i18n/index.js`, and the language picker asks before reloading.
 
 ## Rules
 

docs/INFRASTRUCTURE-LAYERS.md

@@ -53,9 +53,8 @@ Cesium installation shared with its viewer; it must not bundle separate copies.
 `gods-eye-view/infrastructure/geojson` exports the lower-level
 `createLocalGeoJsonLayer(options, services)` and existing infrastructure overlay
 helpers. `gods-eye-view/infrastructure/lod` exports the existing LOD policy helpers.
-The standalone app's `src/data/localGeojson.js` keeps its original single-argument
-factory and supplies its existing functions. Other consumers should use the package
-exports, which do not import standalone application globals.
+Consumers use the package exports, which do not import standalone application
+globals.
 
 Dataset files and source/license notices remain under `src/data/local_data/`.
 Their input counts are 4,351 datacenter features and 704 dam features. Cesium may

docs/LOCAL-RECEIVERS.md

@@ -18,26 +18,6 @@ smoothly between fixes, while local receiver aircraft are shown as heard. An
 aircraft in both layers therefore draws twice, the magenta local marker ahead
 of the public one; both markers are drawn on purpose.
 
-Airborne altitude changes are checked against the last accepted value and a
-vertical-rate allowance. A refused value holds the accepted altitude for the
-marker, card and model. Browser SDR recovery counts actual altitude frames;
-identification and velocity messages cannot make a held altitude look new.
-
-Decoder feeds have no altitude measurement timestamp. Their changed values
-are estimates; recovery after a refusal requires at least five seconds and
-three advancing source snapshots with increasing aircraft message counts
-from the same receiver, with coherent altitude changes. Repeated cached
-snapshots and transport delays do not count. This recovery is inferred, so a
-stable corrupt feed can still qualify. Feeds missing progression metadata
-cannot automatically recover a held value, and fresh positions can keep that
-held altitude alive. The rate check caps its elapsed allowance at 60 seconds
-for feeds; there is no absolute altitude ceiling.
-
-Context and analyst records include `altitudeQuality`, `altitudeObservedAt`
-and `altitudeSource`. Held values retain the accepted value's source and
-measurement time; feed measurement times are null. Ground reports clear the
-airborne reference and its quality metadata.
-
 ## Which to use
 
 - **One plain RTL-SDR dongle, desktop Chrome or Edge:** use the browser SDR.

docs/PERFORMANCE.md

@@ -97,7 +97,8 @@ operational sample contained 3,909 observations and two selected labels, but its
 live aircraft and traffic rows were empty, so it remains a limited stress case.
 
 Snow, Noir, dense detection, and text-heavy combined layers are the clearest
-controlled comparison points for later optimization work.
+controlled comparison points for later optimization work. Snow has since been
+retired as a visual preset; its row records the measurement as taken.
 
 ## Keyed live sources
 

docs/SHARE-LINK-FORMAT.md

@@ -0,0 +1,370 @@
+# Share-link format
+
+A share link restores a view: where the camera is, what it follows, the visual
+style, data layers and panel layout. There are two forms.
+
+- **Long form** — `#v=2&lat=30.2672&lon=-97.7431&…`. Parsed by
+  `src/sharelink.js`. The address bar follows the live view in this form, and
+  links already in the wild keep working; the long form is never removed.
+- **Short form** — `<app>/share/<code>`, where `<app>` is wherever the app is
+  served (an origin's root, or a base path) and `<code>` is encoded and
+  decoded by `src/share/viewCodec.js`, which is pure (no DOM, no Cesium) and
+  needs no server. Hosts import it as `@gods-eye-view/core/share/view-codec`
+  (a server can read a code to describe the view in a link preview). The share button makes this form. The same code opens on
+  any copy of the app. `src/share/shareLinkPath.js` reads and builds the
+  address, and `src/share/legacyShareState.js` converts between the long
+  form's parsed state and the code's state.
+
+The same view in both forms (a real session's link):
+
+| Form  | Characters        |
+| ----- | ----------------- |
+| Long  | 302 (the hash)    |
+| Short | 39 (the `<code>`) |
+
+For example, a camera-only place view is a 24-character code (31 with its
+created-at time).
+Following an aircraft is 42–50: 42 when the link is made from the app's own
+follow camera with the fix taken as the link is made, 44 with a fix four
+seconds older, and 50 after orbiting to another heading and pitch. A view in
+any other style that keeps the style's own look adds only the style (two
+bytes): the 42-character followed aircraft in Noir is 44.
+
+## Opening a short link
+
+At start-up the app reads `<code>` from an address whose path ends in
+`share/<code>` (a host can pass the code instead, as `initialShareCode` to
+`createApplicationControls`). A code that decodes runs the same restore as a
+long link; once the app next writes the address, `/share/<code>` is replaced
+by the app's own address and the long form, without a new history entry, so
+a reload follows the live view. A code that is rejected restores nothing: the
+app starts as usual and says the link can't be opened.
+
+A thing view turns on its entity's layer and follows the entity by id, using
+the same restore as a long link's followed flight or satellite (and its
+expiry windows); a vessel is selected once the vessel feed has it. Opening is
+best effort: until the entity is found, and if it is not found in time, the
+camera is where the link was made, looking at the entity's last-known fix,
+and the app says that the entity isn't reporting and when the fix was taken.
+The share button makes a thing view while the camera follows an aircraft,
+military aircraft or satellite. A selected vessel is not followed (the camera
+stays where the user puts it), so a link made then is a place view; vessel
+thing views open, but the app does not make them yet.
+
+## Payload
+
+The code is unpadded base64url (`A–Z a–z 0–9 - _`). The decoded bytes are:
+
+1. one **version byte**, currently `1`;
+2. a sequence of **fields**, each a varint tag `field_number << 3 | wire_type`
+   followed by its value;
+3. one **check byte**: the CRC-8 of everything before it.
+
+| Wire type | Value                                                       |
+| --------- | ----------------------------------------------------------- |
+| 0 varint  | unsigned LEB128, at most 8 bytes, at most 2^53 − 1          |
+| 1 fixed64 | 8 bytes (not used by v1; skipped)                           |
+| 2 LEN     | varint length, then that many bytes (text or a sub-message) |
+| 5 fixed32 | 4 bytes (not used by v1; skipped)                           |
+
+Signed values are zigzag varints (0, −1, 1, −2 → 0, 1, 2, 3). Text is printable
+ASCII. Fields are written in ascending order; the decoder accepts any order.
+
+A field whose value equals its default is **omitted**. The decoder fills every
+omitted field from the same defaults table the encoder reads (for a
+style-dependent field, the decoded style's defaults), so an empty
+payload (code `AQc`: the version byte and its check byte) is the all-default
+view.
+
+### Check byte
+
+The check byte is CRC-8 with polynomial x⁸ + x² + x + 1 (`0x07`), initial
+value 0, no reflection and no final XOR (CRC-8/SMBUS; the check value of the
+ASCII digits `123456789` is `0xF4`). A decoder that computes a different value
+rejects the code (`checksum`) before reading any field, so a mistyped code
+never opens a different view. A degree-8 CRC catches every error burst of up
+to 8 bits; one base64url character is 6 bits, so **every single-character
+typo is rejected** (a test tries every substitution at every position). Two
+swapped neighbours, a dropped or an extra character are caught with a
+probability of about 255 in 256 (many of them already fail as base64url).
+
+## Field registry (top level)
+
+| #   | State key                    | Type  | Default     | Encoding                                                          |
+| --- | ---------------------------- | ----- | ----------- | ----------------------------------------------------------------- |
+| 1   | `view.kind`                  | enum  | see below   | 0 place, 1 thing                                                  |
+| 2   | `lat`                        | coord | 0           | zigzag of degrees × 10⁴                                           |
+| 3   | `lon`                        | coord | 0           | zigzag of degrees × 10⁴                                           |
+| 4   | `alt`                        | sint  | 800         | whole metres                                                      |
+| 5   | `heading`                    | angle | 0           | whole degrees, see angles                                         |
+| 6   | `pitch`                      | sint  | −35         | whole degrees                                                     |
+| 7   | `roll`                       | angle | 0           | whole degrees                                                     |
+| 8   | `sharedAtMs`                 | epoch | none        | zigzag seconds since 2026-01-01T00:00:00Z                         |
+| 9   | booleans                     | flags | 0           | bit set when the value differs from default                       |
+| 10  | `layerState.enabledLayerIds` | LEN   | none        | layer bitset, see layers                                          |
+| 11  | `layerState.options`         | LEN   | none        | packed option triples, see layers                                 |
+| 12  | `panelState`                 | LEN   | none        | packed panel entries, see panels                                  |
+| 13  | thing                        | LEN   | none        | sub-message, see thing views                                      |
+| 14  | `style`                      | enum  | `normal`    | normal, retro, surveillance, thermal, anime, noir, snow (retired) |
+| 15  | `mapStack`                   | enum  | `photoreal` | photoreal, bing-aerial, bing-labels, esri-imagery, osm            |
+| 16  | `hudVariant`                 | enum  | style       | tactical, operator (retired), minimal, cyber                      |
+| 17  | `bloomIntensity`             | uint  | style       |                                                                   |
+| 18  | `bloomVersion`               | uint  | 2           |                                                                   |
+| 19  | `sharpenIntensity`           | uint  | style       |                                                                   |
+| 20  | `detectionMode`              | enum  | style       | OFF, SPARSE, BALANCED, DENSE                                      |
+| 21  | `detectionDensity`           | uint  | style       | one of 0, 25, 50, 75, 100                                         |
+| 22  | `detectionAllocation`        | enum  | style       | ELASTIC, WEIGHTED                                                 |
+| 23  | `detectionFadePct`           | uint  | style       | 0–40                                                              |
+| 24  | `detectionOutsideOpacityPct` | uint  | style       | 0–100                                                             |
+| 25  | `scopeFeatherPct`            | uint  | 100         | 0–200                                                             |
+| 26  | `scopeTerminusPct`           | uint  | none        | 94–100; absent is the adaptive terminus                           |
+| 27  | `styleParams`                | LEN   | style       | packed `(token, value × 100)` pairs                               |
+
+Field 1 absent means `thing` when field 13 is present and `place` otherwise,
+so v1 never writes it; a later view kind writes its code.
+
+Enum codes are the list position (0, 1, 2…). A name not in the list is written
+as LEN text in the same field, so the app can add a style or map before this
+table learns its code. A new style's settings are encoded against its own
+defaults, while a decoder that does not know the style uses Normal's; adding a
+style also extends the pinned style-defaults table.
+
+`hudVariant` code 1 (`operator`) is retired: the app no longer offers that
+layout and restores it as `tactical`. The code stays reserved.
+
+Flag bits (field 9): 0 `bloom`, 1 `sharpen`, 2 `hudVisible`, 3
+`celestialRing` (each defaulting by style), 4 `scopeEnabled` (default on).
+
+### Style defaults
+
+A default marked **style** is what the view's style applies when it is
+selected in a fresh session (`SHARE_VIEW_STYLE_DEFAULTS`): the app's
+first-load baseline (`GLOBAL_POST_DEFAULTS` in `src/ui/visualPresets.js`),
+with the style's preset on top (`STYLE_PRESET_DEFAULTS`), and the style's
+shader parameters at the preset's values, else the shader's own. The encoder
+compares against the defaults of the view's style, and the decoder fills
+omitted settings from the defaults of the style it decoded (an unknown style
+uses Normal's). So a view that keeps its style's look costs its camera and
+style alone. (A recipient-side preference the app remembers, such as the
+detection allocation, is not a style default: a sender who changed it pays
+for it.) In v1:
+
+| Setting                   | Every style   |
+| ------------------------- | ------------- |
+| bloom, intensity          | off, 0        |
+| sharpen, intensity        | on, 49        |
+| HUD visible, variant      | on, tactical  |
+| detection mode, density   | DENSE, 75     |
+| allocation, fade, outside | ELASTIC, 7, 1 |
+| celestial ring            | off           |
+
+| Style        | Shader parameters (field 27 defaults)                           |
+| ------------ | --------------------------------------------------------------- |
+| normal       | none                                                            |
+| retro        | pixelation 1, distortion 0, instability 0.42                    |
+| surveillance | gain 0.18, bloom 0.22, scanlineStr 0.96, pixelation 1           |
+| thermal      | sensitivity 0.85, bloom 0.2, mode 0.33, pixelation 1, palette 0 |
+| anime        | saturation 1, edgeThick 0.5                                     |
+| noir         | contrastAmt 1.2, grainAmt 0.5, vignetteAmt 0.5                  |
+| snow         | retired: decodes as normal; its parameters are dropped          |
+
+These are frozen like every other default: the codec reads them from the
+app's tables today, and a test pins them, so if a table moves the old values
+are frozen in the codec rather than changing what shared links mean.
+
+### Precision
+
+| Value                       | Stored as                 | Matches the long form |
+| --------------------------- | ------------------------- | --------------------- |
+| Latitude, longitude         | 10⁻⁴ degree (about 11 m)  | `toFixed(4)`          |
+| Altitude, range             | whole metres              | `Math.round`          |
+| Heading, pitch, roll        | whole degrees             | `Math.round`          |
+| Intensities and percentages | integers                  | `Math.round`          |
+| Style parameters            | hundredths after clamping | `sp` (× 100)          |
+| Created-at and observed-at  | whole seconds             | `at`                  |
+
+Angles: heading and roll are normalized into [0, 360) — the long form can
+write `roll=360` for a camera at 359.6°, which the compact form stores as 0 —
+and written as the nearer signed turn, so 350° costs one byte (−10).
+When a state is encoded, out-of-range input is clamped (latitude, pitch) or
+wrapped (longitude). A payload that stores a latitude or longitude beyond
+±90/±180 cannot come from the encoder and is rejected.
+
+### Layers (fields 10 and 11)
+
+A layer's number is derived from its permanent layer-state token
+(`src/data/layerStateTokenReservations.json`): a one-character token is its
+index in `0–9a–z`, a two-character token is 36 + first × 36 + second. The
+token ledger never reassigns a token, so layer numbers never change and new
+layers need no change here.
+
+Field 10 is a bitset: bit _n_ of byte ⌊n/8⌋ (least significant first) is set
+when layer _n_ is on. Present-but-empty means "every layer off"; an absent
+field leaves the recipient's layers alone (the long form's `l=` versus no `l`).
+A thing view's entity layer is always on, so its bit is not written: in a
+thing view, present-but-empty means "only the entity's layer", and an absent
+field opens with only the entity's layer on (the app writes the field
+whenever it has a layer set).
+
+Field 11 repeats `(layer number, option key, value)` for each option that
+differs from its frozen absent meaning (`SHARE_VIEW_LAYER_OPTION_ABSENT`). The
+option key is `option token index × 2 + kind`: kind 0 means the value is a
+zigzag varint (an option whose long-form spelling is a canonical integer),
+kind 1 means a varint length and ASCII text (the long-form spelling). Values
+are decoded by the layer-state codec's own option decoders.
+
+A followed aircraft, military aircraft or satellite is a thing view in the
+compact form, not a tracking option: the encoder moves it out of the layer
+options, and the converter moves it back for the long form.
+
+### Panels (field 12)
+
+Each entry is one varint: `panel number × 16 + collapsed × 4 + pinned`, where
+collapsed and pinned are 0 (no value), 1 (false) or 2 (true). Only panels that
+differ from the frozen default layout are written, plus a collapsed-0 entry
+for each panel the state has no opinion about (an older long-form link that
+predates the panel); a panel with no entry takes its default. Values of 3 are
+reserved: a decoder ignores that entry, as for collapsed 0.
+
+| #   | Panel                  | Long-form token | Default             |
+| --- | ---------------------- | --------------- | ------------------- |
+| 0   | `control-panel`        | `c`             | collapsed, unpinned |
+| 1   | `location-bar`         | `l`             | collapsed, unpinned |
+| 2   | `data-panel`           | `d`             | collapsed           |
+| 3   | `cctv-panel`           | `v`             | collapsed           |
+| 4   | `recent-imagery-panel` | `i`             | expanded            |
+| 5   | `street-level-panel`   | `t`             | collapsed           |
+| 6   | `radio-panel`          | `r`             | collapsed           |
+| 7   | `scene-panel`          | `s`             | collapsed           |
+| 8   | `global-context-panel` | `g`             | collapsed           |
+| 9   | `pp-toggles`           | `p`             | collapsed           |
+| 10  | `param-slider-panel`   | `m`             | expanded            |
+
+### Style parameters (field 27)
+
+Pairs of varints `(token index, value × 100)` for the parameters of the
+view's style that differ from its defaults, using the long form's `sp` tokens
+(`SHARE_VIEW_STYLE_PARAMS`). The decoded state always lists every parameter
+of the style: the stored ones over the style's defaults. A long link without
+`sp` converts to the style's defaults.
+
+## View kinds
+
+A **place** view (field 13 absent) opens at its camera, fields 2–7.
+
+A **thing** view (field 13 present) follows an entity. Field 13 is a
+sub-message:
+
+| #   | Field       | Encoding                                                 | Default |
+| --- | ----------- | -------------------------------------------------------- | ------- |
+| 1   | aircraft    | entity id: varint (24-bit ICAO address) or LEN text      |         |
+| 2   | military    | entity id: varint (24-bit ICAO address) or LEN text      |         |
+| 3   | vessel      | entity id: varint (MMSI) or LEN text                     |         |
+| 4   | satellite   | entity id: varint (NORAD catalog number) or LEN text     |         |
+| 5   | range       | uint metres from the entity to the camera                | 2000    |
+| 6   | heading     | angle, the camera's heading while following              | 0       |
+| 7   | pitch       | sint whole degrees, the camera's pitch while following   | −35     |
+| 8   | fix lat     | coord, the entity's last-known latitude                  | none    |
+| 9   | fix lon     | coord, its last-known longitude                          | none    |
+| 10  | fix alt     | sint metres                                              | 0       |
+| 11  | fix age     | sint seconds the fix predates the created-at time        | 0       |
+| 12  | observed-at | epoch, when the fix was taken; only without a created-at | none    |
+
+The entity kind is the field that carries the id (its code in
+`SHARE_VIEW_ENTITY_KINDS`), so it costs nothing; exactly one of fields 1–4 is
+present (two is malformed). Entity ids are the ones the layers look up: an
+aircraft's ICAO 24-bit address (six hex digits, stored as a number; other
+forms such as TIS-B `~abc123` as text), a vessel's MMSI and a satellite's
+NORAD catalog number (decimal numbers; an MMSI with a leading zero stays
+text). Ids are lowercase and match `[0-9a-z~_-]{1,16}`.
+
+Fields 5–7 are the follow offset: the camera looks along (heading, pitch) at
+the entity from `range` metres away, heading clockwise from north, in the
+entity's local east-north-up frame. The defaults match the app's own follow
+camera, which looks north at about −35°, so only its range is written.
+
+Fields 8–12 are the last-known fix, the entity's position when the link was
+made. Fields 8 and 9 are both written whenever there is a fix; their presence
+marks it. Its time is the created-at time (field 8 at the top level) minus
+field 11, or field 12 when the view has no created-at time.
+
+**The camera of a thing view with a fix is derived, not stored**: fields 2–7
+are not written, and the camera is where following the fix from the offset
+puts it (`followCameraFor` in `src/share/follow.js`): the camera sits
+`−r·cos p·sin h`, `−r·cos p·cos h` and `−r·sin p` metres east, north and up
+of the fix (heading h, pitch p, range r), on a sphere of radius 6 371 000 m,
+and looks back at the fix (its heading and pitch are those of that direction
+at the camera, roll 0; at follow distances they equal h and p). A
+decoder ignores fields 2–7 when the fix is present. A thing view without a
+fix (one converted from a long link, which records neither offset nor fix)
+writes its camera in fields 2–7 like a place view.
+
+A decoder that meets a view kind or an entity kind it does not know (an id in
+a thing field it skips) opens the view as a place at its camera — the derived
+one when there is a fix — and reports `fallback`.
+
+## Decoding rules
+
+`decodeShareView(code)` takes the bare code and never throws. It returns
+`{ ok: true, state, unknownFields?, fallback? }` or `{ ok: false, reason }`.
+
+Rejected (the whole link): input over 2048 characters, bad base64url
+(padding, foreign characters, impossible length, stray bits), fewer than two
+bytes, a check byte that does not match (`checksum`), an unknown version byte,
+a truncated value, a varint over 8 bytes or above 2⁵³ − 1, an
+overlong varint, a LEN longer than what remains (at any level, including
+inside the thing sub-message), a reserved wire type, field number 0, a known
+field with the wrong wire type or repeated, two entity ids in one thing, a
+duplicate panel/option/style entry, non-ASCII text, and a latitude or
+longitude (camera or fix) beyond ±90/±180.
+
+Tolerated and reported in `unknownFields`: unknown fields at any level
+(skipped by wire type), unknown enum codes and names (the default is used),
+unknown flag bits, layers, panel values and style parameters, and layer
+options the layer-state codec rejects or that are filed under a layer other
+than their owner. Detection mode and allocation names outside their lists
+fall back to the default rather than reaching the long form's lenient
+migration. The map stack and HUD variant are open: a name outside their lists
+that matches `[A-Za-z0-9_-]{1,32}` is kept as written (the app decides what
+it means) and is not reported; only a name outside that grammar is. A
+created-at time in the future is dropped, as the long form's `at` is.
+
+## Changing the format
+
+These rules keep every link that was ever shared working, in every version of
+the app that can open it.
+
+1. **Field numbers are permanent.** Never renumber, never reuse. A field that
+   is no longer written stays in `SHARE_VIEW_FIELDS` marked `retired: true`.
+2. **A field's type and wire type are permanent.** To change one, add a new
+   field.
+3. **Defaults are frozen meanings.** A default is what an omitted field meant
+   when links were written. If the app's default moves, leave the table alone:
+   the encoder will start writing the new value explicitly. Style defaults
+   are read from the app's style tables; when those move, freeze the old
+   values in the codec (see Style defaults). The same applies
+   to `SHARE_VIEW_LAYER_OPTION_ABSENT` and the panel defaults.
+4. **Codes are append-only.** Enum lists, entity kinds, flag bits, panel
+   numbers and style parameter tokens only grow. A style the app no longer
+   offers keeps its code: `snow` (6) is retired, so a link that names it
+   opens as Normal and the parameters written for it are dropped.
+5. **Add, don't change.** A new setting takes the next free field number
+   (28 onwards; fields 1–15 have one-byte tags and are all taken). A new
+   boolean takes the next flag bit instead, which costs nothing when it is at
+   its default.
+6. **New view kinds and entity kinds** get the next code. A new entity kind's
+   id takes the next free thing field (13 onwards), so older apps skip it and
+   fall back to the camera. A thing that needs more than an id (for example a
+   CCTV camera, a radio station or a transit vehicle) adds further thing
+   fields the same way.
+7. **A new layer option** needs an entry in `SHARE_VIEW_LAYER_OPTION_ABSENT`
+   (a test fails until it has one).
+8. **Bump the version byte only** for a change older decoders must refuse.
+   Decoders reject any version they do not know. The trailing CRC-8 check
+   byte belongs to every version.
+9. **Derivations are frozen too.** `followCameraFor` and the follow-offset
+   defaults are part of the format: changing them moves the camera of every
+   thing link already shared.
+
+Add a test for every change: a round trip, and a payload written with the new
+field that the previous decoder still reads.

docs/TOOLS.md

@@ -92,7 +92,8 @@ pitch), data layers, visual style, map imagery, and an aircraft, military
 aircraft or satellite to follow. `createView` builds and bounds one,
 `viewToParams` and `viewFromParams` write and read it in the share-link
 format the app restores, and `viewUrl` gives the address that opens it. The
-style names are the ones share links use. Ships cannot be followed from a
+style names are the ones share links use; a retired style (`snow`) is read
+as `normal`. Ships cannot be followed from a
 link yet. An aircraft's `follow` may ask for its cockpit view
 (`cockpit: true`); links cannot carry that and open the app following it.
 

docs/TRANSLATORS.md

@@ -1,6 +1,6 @@
 # Translating God's Eye View
 
-Shipped languages: **English** (source and fallback), **Spanish** (`es`) and **Russian** (`ru`).
+Shipped languages: **English** (source and fallback), **German** (`de`), **Spanish** (`es`), **French** (`fr`), **Italian** (`it`), **Japanese** (`ja`), **Brazilian Portuguese** (`pt`), **Russian** (`ru`), **Ukrainian** (`uk`), **Simplified Chinese** (`zh-CN`) and **Traditional Chinese** (`zh-Hant`).
 
 ## How it works
 
@@ -63,4 +63,4 @@ These are contracts, not copy: layer ids and registry keys, status enums and oth
 
 ## Language notes
 
-Each language keeps its glossary, plural forms, units and style in its own file, `docs/translations/<code>.md`: [Spanish](./translations/es.md), [Russian](./translations/ru.md). Read it before translating, and add a term there when you settle on one.
+Each language keeps its glossary, plural forms, units and style in its own file, `docs/translations/<code>.md`: [German](./translations/de.md), [Spanish](./translations/es.md), [French](./translations/fr.md), [Italian](./translations/it.md), [Japanese](./translations/ja.md), [Brazilian Portuguese](./translations/pt.md), [Russian](./translations/ru.md), [Ukrainian](./translations/uk.md), [Simplified Chinese](./translations/zh-CN.md), [Traditional Chinese](./translations/zh-Hant.md). Read it before translating, and add a term there when you settle on one.

docs/opensky-auth.md

@@ -3,10 +3,11 @@
 God's Eye View uses explicit auth modes for `/api/flights`:
 
 - `OPENSKY_AUTH_MODE=oauth` (default, recommended)
-- `OPENSKY_AUTH_MODE=auto` (OAuth first, then Basic fallback)
-- `OPENSKY_AUTH_MODE=basic`
+- `OPENSKY_AUTH_MODE=auto` (OAuth when configured, otherwise anonymous)
 - `OPENSKY_AUTH_MODE=anon`
 
+`OPENSKY_AUTH_MODE=basic` is retired (see below).
+
 Reference: OpenSky REST API docs recommend OAuth2 Client Credentials flow.
 
 ## Quick Start (OAuth Client JSON)
@@ -41,13 +42,18 @@ Launchers resolve OAuth creds in this order:
 2. `OPENSKY_CREDENTIALS_FILE`
 3. Keychain (`opensky-network` / `client_id`, `client_secret`)
 
-## Basic Auth (Legacy)
+The server itself reads 1 and 2, so `npm run dev`, `npm run preview` and
+Pinokio also work with only `OPENSKY_CREDENTIALS_FILE` set in `.env`, on any
+platform. It reads the file on each token refresh.
 
-Basic auth is still supported for now, but OpenSky is moving away from it.
+## Basic Auth (Retired)
 
-```bash
-OPENSKY_AUTH_MODE=basic ./scripts/dev-fresh.sh
-```
+OpenSky stopped accepting username/password (HTTP Basic) sign-in on
+2026-03-18; its API now takes only OAuth2 client credentials. With
+`OPENSKY_AUTH_MODE=basic` the server no longer sends `OPENSKY_USERNAME` /
+`OPENSKY_PASSWORD`: it requests anonymously (reason `basic_retired`) and
+logs once what to set instead. Create an API client on your OpenSky
+account page and use its `credentials.json` as above.
 
 ## Troubleshooting
 
@@ -61,6 +67,6 @@ Useful reasons:
 
 - `oauth_invalid_or_missing`: OAuth client not found/usable
 - `oauth_invalid_credentials`: OAuth client rejected by OpenSky
-- `basic_invalid_credentials`: username/password rejected
-- `missing_basic_creds`: basic mode missing user/pass
+- `missing_oauth_creds`: auto mode found no OAuth client
+- `basic_retired`: basic mode requested; answered anonymously
 - `rate_limited`: OpenSky throttling

docs/translations/de.md

@@ -0,0 +1,108 @@
+# German (`de`)
+
+Catalog: `src/i18n/locales/de.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: abiyeenzo (#908).
+
+## Style
+
+- Standard German that reads naturally in Germany, Austria and Switzerland; ß where it belongs (Straße, schließen), no Swiss ss.
+- No direct address: neither «Sie» nor «du». Actions and hints use the neutral infinitive: «Erneut versuchen», «Kamera anklicken zum Aktivieren», «Zuerst eine Aufnahme wählen», «Mikrofonzugriff erlauben und erneut versuchen». "Your" becomes the article or «eigene»: «Eigener RTL-SDR-Empfänger», «Die IP-Adresse ist für diesen Sender sichtbar».
+- Nouns are capitalized, as German requires; otherwise sentence case, not Title Case: "Live Flights" → «Live-Flüge», "Provider Settings" → «Anbieter-Einstellungen». UPPERCASE English stays UPPERCASE: «LIVE-DATEN AUS», «KEINE ENTWARNUNG». In UPPERCASE, ß is written SS: «SCHLIESSEN», «STRASSENEBENE».
+- Compounds are written as one word or with a hyphen next to a name, code or English term: «Datenebene», «Wetterkacheln», «TomTom-Schlüssel», «AIS-Schiffe», «Street-View-Fallback». Do not split them with spaces.
+- Short labels, chips and HUD readouts stay short. German runs about a third longer than English, so prefer a short word or a standard abbreviation with a period over a wrapped line: REICHW., GESCHW., NIEDERSCHL., SONST., NACHR., VERST., VGL., KAL., KOMM. (a bare «KOMM» reads as the imperative)
+- The avionics codes HDG, BRG, CRS, DEST, SPD, ALT, GS, TRK, V/S, FOV and SQUAWK stay in English, as in the cockpit. Words used in a sentence are translated: heading → «Kurs», bearing → «Peilung», range → «Reichweite».
+- A dash between clauses is a spaced en dash « – »; a colon is fine where it explains: «Feed ausgefallen – neue Versuche in größeren Abständen», «SIMULIERT: Verkehrsdienst nicht erreichbar». Quotes are „…“.
+- Status and waiting messages use the neutral infinitive too: «Warten auf Aktualisierung», not «Warte auf …». Reasons inserted after a dash stay lower case: «Szene nicht gespeichert – das Projekt ist größer als 5 MiB».
+- A layer named in a sentence takes its panel name in quotes: «Die Ebene „Live-Flüge“ ist nicht aktiviert», «die Ebene „Live-Flüge“ lädt Daten für den jeweiligen Bildausschnitt».
+- Rolling time windows say their length, so they cannot read as the previous calendar period: LAST YEAR → «LETZTE 12 MONATE», LAST MONTH → «LETZTE 30 TAGE».
+- Keyboard keys are named as on German keyboards where they differ: Leertaste, Rücktaste, Umschalt; Esc, Enter, Tab and letter keys stay.
+- Decimal comma in fixed text: «M4,4», «28,2710° N». Thousands separator is a period: «1.000 km». Formatted numbers come from `Intl` and are already German.
+- Units: km, m, km/h, m/s, kn (knots, also in the cockpit), ft (feet), hPa, MW, h, min, s, T (days, in short readouts); in UPPERCASE text KM, KM/H, KN, FT, MIN, H, T («VOR {count} H»). A space between number and unit, in compact readouts too: «{value} m», «{count} min», «50 %», «{speed} KN», «{count} / 30 T». `°` sticks to the number.
+- "ago" goes before the time: «vor {count} min», «vor {value}». When a placeholder already holds a localized "ago" text (`{age}` in `STALE · cached {age}`, `{ago}`), do not add «vor» again.
+- Compass points use O for Ost: N, NNO, NO, ONO, O, OSO, SO, SSO, S, SSW, SW, WSW, W, WNW, NW, NNW; hemisphere letters N, S, O, W.
+- Routing: direction words are lowercase adverbs (links, leicht rechts, scharf links, geradeaus), so a sentence never starts with one: «Auf {road} {direction} abbiegen», «Hier {direction} abbiegen», «Weiter {direction}». «Hier», not «Dann»: the step card already says «dann {leg}» and «Nächster Schritt: …». At a fork the verb is «weiter», which also works with «geradeaus»: «An der Gabelung {direction} weiter». Roundabout exits are ordinals with a period: «die {exit} Ausfahrt» → «die 2. Ausfahrt». A lane is named by where it leads, not by its position: «Die geradeaus führende Spur benutzen», «die leicht nach links führende», «die scharf nach rechts führende» (not «halblinke» or «äußerst linke»).
+
+## Plurals
+
+A `tn()` entry needs two forms. `Intl.PluralRules('de')` picks:
+
+| Form    | Counts                      | Example   |
+| ------- | --------------------------- | --------- |
+| `one`   | 1                           | 1 Kamera  |
+| `other` | everything else: 0, 2, 1,5… | 3 Kameras |
+
+Keep the verb in agreement: «{count} Station meldet» / «{count} Stationen melden». Abbreviated units and codes do not change: «{count} NACHR.», «{count} EMPFANGEN».
+
+## Glossary
+
+| English                                        | Deutsch                                                                |
+| ---------------------------------------------- | ---------------------------------------------------------------------- |
+| layer / data layer                             | Ebene / Datenebene                                                     |
+| feed / source / data source / input (cockpit)  | Feed / Quelle / Datenquelle / Quelle                                   |
+| LIVE (status) / live data                      | LIVE / Live-Daten                                                      |
+| SIMULATED                                      | SIMULIERT                                                              |
+| stale / degraded / unavailable                 | veraltet / eingeschränkt / nicht verfügbar                             |
+| retry / retrying / retrying slowly             | neuer Versuch / erneut versuchen / neue Versuche in größeren Abständen |
+| fallback                                       | Fallback                                                               |
+| key (API key) / POWER UP / POWERED UP          | Schlüssel / STARTKLAR / HOCHGEFAHREN                                   |
+| Provider Settings                              | Anbieter-Einstellungen                                                 |
+| ON / OFF (state chips)                         | EIN / AUS                                                              |
+| enable / disable                               | aktivieren / deaktivieren                                              |
+| globe / map / map source / map stack / basemap | Globus / Karte / Kartenquelle / Kartenstapel / Basiskarte              |
+| aircraft / flight / military flights           | Luftfahrzeug (HUD and short labels: Flugzeug) / Flug / Militärflüge    |
+| vessel, ship                                   | Schiff                                                                 |
+| satellite / shell (Starlink) / DENSE           | Satellit / Schale / DICHT                                              |
+| launch (rocket) / launch site / space mission  | Start / Startplatz / Raummission                                       |
+| ascent / replay / payload / stage / downrange  | Aufstieg / Replay, Wiedergabe / Nutzlast / Stufe / Downrange           |
+| contact / tracking                             | Kontakt / Verfolgung                                                   |
+| installation / site                            | Anlage / Standort                                                      |
+| mapped / observed                              | kartiert / beobachtet (Bhote chip OBSERVED IMAGERY: REALE BILDDATEN)   |
+| camera / CCTV camera / camera badge            | Kamera / CCTV-Kamera / Kamera-Markierung                               |
+| earthquake / active fire / fire perimeter      | Erdbeben / aktiver Brand / Brandgrenze                                 |
+| cyclone / advisory (NHC/CPHC) / cone           | Wirbelsturm / Lagebericht (not «Warnung») / Kegel                      |
+| issued (advisory, forecast)                    | ausgegeben                                                             |
+| radio station                                  | Sender                                                                 |
+| broadcast FM                                   | UKW                                                                    |
+| road / flow (traffic) / flow coverage          | Straße / Verkehrsfluss / Live-Abdeckung                                |
+| transit / bike share                           | ÖPNV / Bikesharing                                                     |
+| scene / shot / scene recipe                    | Szene / Aufnahme / Szenenrezept                                        |
+| capture shot / camera move                     | Aufnahme speichern / Kameraflug                                        |
+| anchor / data pack / bundle                    | Anker / Datenpaket / Bundle                                            |
+| story beat / evidence beat                     | Story-Schritt / Beweisschritt                                          |
+| briefing / panel / dock                        | Briefing / Bereich / Dock                                              |
+| cockpit                                        | Cockpit                                                                |
+| preset / visual preset                         | Preset / visuelles Preset                                              |
+| Scope (circular viewport mask) / keyhole       | Scope / Schlüsselloch                                                  |
+| feather / fade                                 | Weichzeichnung / Ausblenden                                            |
+| overlay / detection overlay                    | Overlay / Erkennungs-Overlay                                           |
+| Clean UI                                       | Reine Ansicht                                                          |
+| Night vision / Thermal / Snow (cockpit styles) | Nachtsicht / Wärmebild / Schnee                                        |
+| heading / altitude / ground speed              | Kurs / Höhe / Geschwindigkeit über Grund (short: GESCHW. ÜBER GRUND)   |
+| HDG / BRG / CRS / DEST / SPD / FOV             | unchanged                                                              |
+| RANGE / PITCH / HGT (CCTV calibration chips)   | REICHW. / NEIGUNG / HÖHE                                               |
+| PREV / NEXT                                    | ZURÜCK / WEITER                                                        |
+| RESUME (radio transport button)                | FORTSETZEN (not «WEITER», which is NEXT in the same row)               |
+| nearest (spatial)                              | nächstgelegen (always; «nächste» is NEXT)                              |
+| expand / collapse (sections)                   | ausklappen / einklappen                                                |
+| L / R (relative bearing)                       | L / R                                                                  |
+| SIG / NEWS / LOCAL (briefing tabs)             | SIG / NEWS / LOKAL                                                     |
+| NOT AN ALL-CLEAR                               | KEINE ENTWARNUNG                                                       |
+| Street Level / Street View (Google)            | Straßenebene / Street View                                             |
+| Recent Imagery / box / pin (a day)             | Aktuelle Bilddaten / Bereich / fixieren                                |
+| frame (bring into view)                        | ins Bild nehmen                                                        |
+| mark (map annotation) / outline                | Markierung / Umriss                                                    |
+| voice (control) / voice session                | Sprachsteuerung / Sprachsitzung                                        |
+| YOU / THIS / HERE (voice card labels)          | EINGABE / DIES / HIER                                                  |
+| click / click to …                             | anklicken / … klicken                                                  |
+| tap (touch)                                    | Antippen (not «Tipp», which is a hint)                                 |
+| press / tap a key                              | Taste drücken / kurz drücken (never «tippen» for keys)                 |
+| tilted view                                    | Schrägansicht                                                          |
+| card (host card) / voice card                  | Eintrag (in hints), Infokarte / Sprachkarte                            |
+| label (on the map) / clear (switch off layers) | Beschriftung / ausschalten (not «löschen»)                             |
+| station tag (radio filter)                     | Kategorie                                                              |
+| DIRECTORY BAND / {category} BAND (radio dial)  | SENDERSKALA / SENDERSKALA · {category} (not «-BAND»: «ROCK-BAND»)      |
+| MIC (dock button)                              | MIKRO                                                                  |
+| frame (weather, video) / image                 | Frame / Bild                                                           |
+| collapse / landslide (Bhote Koshi)             | Erdrutsch (not «Abbruch», which reads as "cancel")                     |
+| website (radio station)                        | Website (SENDER-WEBSITE; «Standort» is a physical site)                |

docs/translations/fr.md

@@ -0,0 +1,105 @@
+# French (`fr`)
+
+Catalog: `src/i18n/locales/fr.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: abiyeenzo (#907); the French part of meirm's #312 was used for comparison.
+
+## Style
+
+- Standard French that reads naturally in France, Belgium, Switzerland and Canada; avoid regionalisms.
+- Address the user with "vous" imperatives: « Cliquez », « Activez », « Réessayez ». Tooltips that name an action use the infinitive: « Réduire le panneau », « Réinitialiser la caméra ». UPPERCASE HUD instructions also use the infinitive: « CLIQUER SUR UNE CAMÉRA POUR L'ACTIVER ».
+- Sentence case, not Title Case: "Live Flights" → « Vols en direct ». UPPERCASE English stays UPPERCASE, accents included: « ÉTAT », « PRÉC. ».
+- Typography: a narrow no-break space (U+202F) goes before `:` `;` `?` `!` and `%`, and inside « » quotes: `Supprimer le plan « {shot} » ?`. It keeps the sign on the same line as the word before it. Do not type a plain space there. The same narrow no-break space separates thousands in a number written into the text: « 1 000 km ». Ellipsis is `…`, not `...`. Dashes keep their spaces: « flux indisponible — réessayez ».
+- Short labels, chips and HUD readouts stay short. A standard abbreviation with a period beats a wrapped line: PRÉC., SUIV., RÉINIT., ENREG., INDISP., DIST.
+- The HUD codes HDG, BRG, CRS, FOV, DEST, SPD and ALT stay in English everywhere, as in cockpit avionics. Words are translated: RANGE → « PORTÉE », heading in a sentence → « cap », ground-track course → « route » (« ROUTE 270° »).
+- ON and OFF stay as they are on HUD toggles and chips (« CCTV ON », « PROJECTION OFF »); in a sentence use « activé » / « désactivé ».
+- Keyboard keys stay in English: Space, Esc, Enter, Tab, Shift, Backspace, H, 1–9 (« Maintenez Space pour parler », « ESC pour fermer »).
+- Units: km, m, km/h, m/s, nd (knots), ft (feet), h, min, s, with a space before the unit: « 250 km », « il y a 5 min »; in UPPERCASE text KM, KM/S, ND, FT, MIN. MW, dBZ, hPa and `°` stay. Decimal comma in fixed numbers: « 28,2710° N », « M4,4 ». Money: « 12 k$ », « 3 M$ », « 2 Md$ ».
+- "ago" goes before the time: « il y a {count} min ». When a placeholder already holds a localized "ago" text (`{age}`, `{ago}`), do not add « il y a » again.
+- Round-about exit ordinals: 1re, 2e, 3e… (« prenez la 1re sortie »).
+
+## Plurals
+
+A `tn()` entry needs three forms. `Intl.PluralRules('fr')` picks:
+
+| Form    | Counts                                 | Example              |
+| ------- | -------------------------------------- | -------------------- |
+| `one`   | 0 and 1, fractions below 2 (1,5)       | 1 caméra, 0 caméra   |
+| `many`  | 1 000 000, 2 000 000… (exact millions) | 1 000 000 de caméras |
+| `other` | everything else: 2–999 999, 2,5…       | 3 caméras            |
+
+The `many` form is the `other` text with « de » (« d' » before a vowel) after the number: « {count} de couches effacées », « {count} D'ENTRÉES INCONNUES ». When the words after the number cannot agree (an UPPERCASE readout, a list), put the number after a colon in every form: « CAPTÉS : {count} ». The same goes for a layer name whose gender and number vary: « Couche activée : {label} », not « {label} activé », or a tool name: « Outil actif : {name} », not « {name} est actif ».
+
+## Glossary
+
+| English                                                      | Français                                                                |
+| ------------------------------------------------------------ | ----------------------------------------------------------------------- |
+| layer / data layer / DATA LAYERS (panel title)               | couche / couche de données / COUCHES                                    |
+| feed / source / data source                                  | flux / source / source de données                                       |
+| LIVE (status) / live data                                    | DIRECT / données en direct                                              |
+| SIMULATED                                                    | SIMULÉ                                                                  |
+| stale / degraded / unavailable                               | obsolète / dégradé / indisponible                                       |
+| retry / retrying (status: RETRYING X)                        | nouvel essai / réessayez (NOUVEL ESSAI : X)                             |
+| rate-limited                                                 | limite de requêtes atteinte                                             |
+| key (API key) / POWER UP / POWERED UP                        | clé (clé API) / ALLUMER / ALLUMÉ                                        |
+| Provider Settings                                            | paramètres des fournisseurs                                             |
+| enable / disable                                             | activer / désactiver                                                    |
+| globe / map / map source / basemap / map stack               | globe / carte / source de carte / fond de carte / fond de carte         |
+| tile (map)                                                   | tuile                                                                   |
+| aircraft / flight / military flights                         | aéronef (avion in short copy) / vol / vols militaires                   |
+| vessel, ship / tanker (AIS type)                             | navire / navire-citerne                                                 |
+| satellite / shell (Starlink) / DENSE                         | satellite / couche de la constellation / DENSE                          |
+| launch / launch site / space mission                         | lancement / site de lancement / mission spatiale                        |
+| ascent / replay / payload / stage / downrange                | ascension / rejeu / charge utile / étage / distance au sol (DIST. SOL)  |
+| contact / tracking / track (HUD)                             | contact / suivi / piste                                                 |
+| brackets (HUD corner brackets around contacts)               | cadres de ciblage                                                       |
+| installation / site                                          | installation / site                                                     |
+| mapped / observed                                            | cartographié / observé                                                  |
+| camera / CCTV camera / ALPR camera                           | caméra / caméra CCTV / caméra LAPI                                      |
+| earthquake                                                   | séisme                                                                  |
+| active fire (FIRMS detection) / wildfire                     | feu actif / incendie                                                    |
+| contained / containment (wildfire)                           | circonscrit / part circonscrite (not « maîtrisé », which is controlled) |
+| advisory (NHC/CPHC cyclone)                                  | bulletin                                                                |
+| forecast / lead hours / valid / issued                       | prévision / échéances / valide / émise                                  |
+| AQHI (Canada)                                                | CQAS (cote air santé)                                                   |
+| radio station / tune                                         | station / régler                                                        |
+| bikeshare / transit                                          | vélos partagés / transports en commun                                   |
+| route (directions) / turn (maneuver)                         | itinéraire / manœuvre                                                   |
+| scene / shot / scene recipe                                  | scène / plan / recette de scène                                         |
+| bundle / data pack / anchor                                  | archive / paquet de données / ancre                                     |
+| import / export (noun: file, scene, project)                 | importation / exportation (not « import » / « export »)                 |
+| capture camera as anchor / set move start (scene editor)     | ancre à la position de la caméra / vue actuelle comme départ            |
+| story beat                                                   | étape du récit                                                          |
+| briefing / panel / dock                                      | briefing / panneau / dock                                               |
+| cockpit                                                      | cockpit                                                                 |
+| preset / visual preset                                       | préréglage / préréglage visuel                                          |
+| Scope (circular viewport mask) / keyhole                     | lunette / ouverture                                                     |
+| detection overlay                                            | surcouche de détection                                                  |
+| Clean UI                                                     | vue épurée                                                              |
+| Street Level (layer) / Street View (Google)                  | Niveau rue / Street View                                                |
+| Recent Imagery / box                                         | imagerie récente / zone                                                 |
+| Daily overview / overview (Recent Imagery VIIRS product)     | vue quotidienne (one name for the product, not « vue d'ensemble »)      |
+| pin (Draw tool) / pin (Recent Imagery)                       | épingle / épingler                                                      |
+| Cyber (HUD layout, effect)                                   | Cyber                                                                   |
+| heading / course (ground track) / altitude / ground speed    | cap / route / altitude / vitesse sol                                    |
+| HDG / BRG / CRS / FOV / DEST / SPD / ALT                     | unchanged                                                               |
+| RANGE / PITCH / HGT (CCTV calibration chips)                 | PORTÉE / INCL. / HAUT.                                                  |
+| PREV / PREVIOUS / NEXT (chips)                               | PRÉC. / PRÉC. / SUIV.                                                   |
+| Previous / Next (button text)                                | Précédent / Suivant                                                     |
+| L / R (relative bearing)                                     | G / D                                                                   |
+| SIG / NEWS / LOCAL (briefing tabs)                           | SIG / ACTUS / LOCAL                                                     |
+| compass points (N, NNE, …, W, NW)                            | N, NNE, …, O, NO                                                        |
+| NOT AN ALL-CLEAR                                             | PAS UN FEU VERT                                                         |
+| AI agent                                                     | agent IA                                                                |
+| share (a view or link)                                       | partager                                                                |
+| click / click to …                                           | cliquez / cliquer pour …                                                |
+| map heading (compass, north-up control)                      | orientation (de la carte)                                               |
+| subject (cockpit / shared contact)                           | cible                                                                   |
+| cloud cover / CLOUD (briefing readout)                       | nébulosité / NÉBULOSITÉ                                                 |
+| LEVEL (cockpit horizon guide)                                | HORIZON                                                                 |
+| CALIBRATED / CURATED / RAW PRIOR (CCTV pose)                 | CALIBRÉE / VÉRIFIÉE / ESTIM. INITIALE                                   |
+| DATASHEET / SPEC FOV (CCTV lens range)                       | FICHE TECHNIQUE / FOV CONSTRUCTEUR                                      |
+| PORT TENDER (AIS type)                                       | SERVITUDE PORT. (navire de servitude portuaire)                         |
+| ChatGPT sign-in (action) / opening sign-in / sign-in expired | connexion / page de connexion / la session a expiré                     |
+| authored shot (scene)                                        | plan scénarisé                                                          |
+| report / record (USGS event card) / readout, reading         | rapport / relevé (a measured value only)                                |

docs/translations/it.md

@@ -0,0 +1,108 @@
+# Italian (`it`)
+
+Catalog: `src/i18n/locales/it.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: abiyeenzo (#912).
+
+## Style
+
+- Standard Italian as in Italian software UIs. Address the user with informal "tu" imperatives: «Aggiungi», «Attiva», «Scegli», «Incolla», «Riprova». Tooltips that name an action use the same imperative: «Espandi il pannello», «Ripristina la camera».
+- Sentence case, not Title Case: "Live Flights" → «Voli live», "Space Missions" → «Missioni spaziali». UPPERCASE English stays UPPERCASE: «LIVE», «NON DISPONIBILE».
+- Quotes inside Italian text are straight double quotes: «Eliminare lo scatto "{shot}"?». Use the accented capitals (È, À) in UPPERCASE text: «VELOCITÀ», «CITTÀ».
+- Errors read as a statement, not a past participle on its own: "Search failed" → «Ricerca non riuscita»; "Could not …" → «Impossibile …». A dash that joins a cause and a hint becomes a colon: «Chiave API rifiutata: controlla AISSTREAM_API_KEY». The same goes for a label and its hint in a tooltip: «Direzione (bussola °): clic per digitare».
+- Short labels, chips and HUD readouts stay short. A standard abbreviation with a period beats a wrapped line: REGOLAZ., RILEV., INCL., ALT., VEL., STIM., PROIEZ., ESP.; PREC / SUCC for PREV / NEXT and PREVIOUS / NEXT.
+- The HUD codes HDG, BRG, CRS, FOV and DEST stay in English, as in cockpit avionics. RANGE is «PORTATA». Words used in a sentence are translated: heading → «prua» (aircraft, ships) or «direzione» (camera, buses, trams, trains), course → «rotta».
+- Keyboard keys stay in English: Space, Enter, Esc, Tab, Shift, Backspace, H, 1–9 («Tieni premuto Space per parlare», «Premi Enter per riprovare»).
+- Decimal comma in numbers written in the text, magnitudes included: «28,2710° N», «M5,2». Numbers formatted by the code follow `Intl` and need nothing.
+- Amounts: thousands, millions and billions are written out or abbreviated in Italian, not with K/M/B: «{amount} mila $», «{amount} mln $», «{amount} mld $».
+- Units: km, m, km/h, m/s, kn (knots), ft (feet), h, min, s; in UPPERCASE text KM, KM/S, KT, FT, MIN, H. "m" is always metres, so minutes are «min» («5 min fa»). MW stays MW. `°` and `%` stay.
+- "ago" goes after the time: «{count} min fa». When a placeholder already holds a localized "ago" text (`{age}`, `{ago}`), do not add «fa» again.
+- A feature name used as a sentence subject gets a head noun so the verb agrees: «La modalità Missioni spaziali isola…», «Il pannello Impostazioni provider è disattivato…», «Il livello {layer} è attivo…», «Lo strumento {name} è attivo…». A short card title with a placeholder name puts the state after a colon: «{label}: attivato». The same goes for a placeholder list of names: «Attivazione recente: {layers}». A count in a plain `t()` entry (no plural forms) that can be 1 goes after a label, so nothing has to agree with it: «Record accettati: {accepted} su {raw}».
+- English loanwords that Italian UIs use as they are stay in English: feed, live, cockpit, briefing, preset, overlay, layout, snapshot, tile, provider, timeout, payload, bloom, scope.
+
+## Plurals
+
+A `tn()` entry needs three forms. `Intl.PluralRules('it')` picks:
+
+| Form    | Counts                                 | Example                 |
+| ------- | -------------------------------------- | ----------------------- |
+| `one`   | 1                                      | 1 telecamera            |
+| `many`  | 1 000 000, 2 000 000… (exact millions) | 1 000 000 di telecamere |
+| `other` | everything else: 0, 2–999 999, 1,5…    | 3 telecamere            |
+
+The `many` form is the `other` text with «di» after the number when a noun follows: «{count} di telecamere caricate», «{count} DI CHIAVI IN ATTESA». When no noun follows the number («{count} vicine», «{count} RICEVUTI»), `many` repeats `other`. Nouns that do not change in the plural keep one form for all three (`{count} file`, `{count} data center`), with «di» in `many`.
+
+## Glossary
+
+| English                                       | Italiano                                                     |
+| --------------------------------------------- | ------------------------------------------------------------ |
+| layer / data layer                            | livello / livello dati                                       |
+| feed / source / data source                   | feed / fonte / fonte dati                                    |
+| LIVE (status) / live data / live (feed state) | LIVE / dati live / live                                      |
+| SIMULATED                                     | SIMULATO                                                     |
+| stale / degraded / unavailable                | obsoleto / degradato / non disponibile                       |
+| retry / retrying                              | riprova / nuovo tentativo                                    |
+| rate limited                                  | limite di richieste (raggiunto)                              |
+| key (API key) / POWER UP / POWERED UP         | chiave / ACCENDI / ACCESO                                    |
+| Provider Settings                             | Impostazioni provider                                        |
+| ON / OFF (state chips)                        | ON / OFF                                                     |
+| enable / disable                              | attivare / disattivare                                       |
+| globe / map / map source / map stack          | globo / mappa / fonte mappa / stack mappa                    |
+| basemap / box (Recent Imagery area)           | mappa di base / riquadro                                     |
+| aircraft, plane / flight / military flights   | aereo / volo / voli militari                                 |
+| vessel, ship                                  | nave                                                         |
+| satellite / shell (Starlink) / DENSE          | satellite / shell / DENSO                                    |
+| SPARSE / BALANCED / DENSE (detection modes)   | RADO / BILANCIATO / DENSO (agree with «overlay»)             |
+| broadband (Starlink shell)                    | a banda larga                                                |
+| VISUAL (CelesTrak group)                      | VISIBILI                                                     |
+| launch (rocket) / launch site / space mission | lancio / sito di lancio / missione spaziale                  |
+| ascent / replay / payload / stage             | salita / replay / payload / stadio                           |
+| contact / tracking                            | contatto / tracciamento                                      |
+| installation / site                           | installazione / sito                                         |
+| mapped / observed                             | mappato / osservato                                          |
+| camera (view) / camera, CCTV camera           | camera / telecamera, telecamera CCTV                         |
+| earthquake / active fire / fire perimeter     | terremoto / incendio attivo / perimetro dell'incendio        |
+| lightning strike / cloud (cover, %)           | fulmine / nuvole («non singoli fulmini», «20% di nuvole»)    |
+| incident (wildfire, Type N) / scene incident  | evento (Evento di tipo N, Incendio senza nome) / evento      |
+| trigger record (USGS card) / OPEN SOURCE link | scheda / APRI LA FONTE                                       |
+| advisory (NHC/CPHC cyclone) / cone            | bollettino / cono di incertezza                              |
+| forecast lead hours (cyclone points)          | scadenze di previsione in ore                                |
+| AIR / SEA (radio category) / ground station   | ARIA / MARE / stazione di terra                              |
+| radio station / broadcaster                   | stazione radio / emittente                                   |
+| CH (radio channel readout)                    | CH (unchanged)                                               |
+| road / flow (traffic)                         | strada / flusso                                              |
+| transit / bike share                          | trasporto pubblico / bike sharing                            |
+| last report (vehicle position)                | ultima segnalazione                                          |
+| scene / shot / scene recipe                   | scena / scatto / ricetta della scena                         |
+| anchor / data pack / bundle (scene)           | ancora / pacchetto dati / pacchetto                          |
+| story beat                                    | tappa del racconto                                           |
+| briefing / panel / dock                       | briefing / pannello / dock                                   |
+| cockpit                                       | cockpit                                                      |
+| preset / visual preset                        | preset / preset visivo                                       |
+| Tactical / Minimal / Cyber                    | Tattico / Minimale / Cyber                                   |
+| Scope (circular viewport mask) / keyhole      | scope / foro                                                 |
+| feather / fade                                | sfumatura / dissolvenza                                      |
+| detection overlay                             | overlay di rilevamento                                       |
+| pin (Draw tool) / mark                        | segnaposto / segno                                           |
+| pin (Recent Imagery)                          | fissare                                                      |
+| Draw / Directions (tools)                     | Disegno / Indicazioni                                        |
+| Street Level (layer) / Street View (Google)   | Vista stradale / Street View                                 |
+| Recent Imagery                                | Immagini recenti                                             |
+| Global Context / Context (panel)              | Contesto globale / Contesto                                  |
+| heading, course / altitude / ground speed     | prua, rotta / altitudine / velocità al suolo (VEL. AL SUOLO) |
+| altitude in short HUD captions / Alt unknown  | QUOTA (QUOTA · FT) / Quota sconosciuta                       |
+| fallback (FALLBACK, Street View fallback)     | riserva / di riserva (SUPERFICIE DI RISERVA)                 |
+| forecast track / advisory center (cyclones)   | traccia prevista / centro del ciclone da bollettino          |
+| witness source / authored (scene)             | fonte testimoniale / predefinito, definito dall'autore       |
+| explore manually                              | esplora manualmente                                          |
+| HDG / BRG / CRS / FOV / DEST                  | HDG / BRG / CRS / FOV / DEST (unchanged)                     |
+| RANGE / PITCH / HGT (CCTV calibration)        | PORTATA / INCL. / ALT.                                       |
+| PREV / NEXT                                   | PREC / SUCC                                                  |
+| Previous / Next (button text)                 | Precedente / Successivo                                      |
+| Focus {target} (action, aria label)           | Inquadra {target} (the FOCUS button stays FOCUS)             |
+| L / R (relative bearing)                      | S / D                                                        |
+| SIG / NEWS / LOCAL (briefing tabs)            | SIG / NOTIZIE / LOCALE                                       |
+| compass points (N, NNE, …, W, NW)             | N, NNE, …, O, NO (west is «O», ovest)                        |
+| NOT AN ALL-CLEAR                              | NON È UN VIA LIBERA                                          |
+| weather field / model / valid / issued        | campo / modello / valida / emessa                            |
+| click / click to …                            | fai clic / clic per …                                        |

docs/translations/ja.md

@@ -0,0 +1,112 @@
+# Japanese (`ja`)
+
+Catalog: `src/i18n/locales/ja.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: abiyeenzo (#913).
+
+## Style
+
+- Sentences use です／ます: 「キーを保存しました」, 「もう一度お試しください」. Labels, buttons and HUD chips are short nouns or verb stems without a final 。: 「再試行」, 「保存」, 「ライブ」, 「オフ」.
+- Japanese has no case: an UPPERCASE English label becomes the same short Japanese label. Codes, units and names stay in their own case (HDG, ADS-B, km).
+- Full-width punctuation in Japanese text: 、。：？！（）「」. Quote names and titles with 「」: 「{shot}」を削除しますか？ Keep `·` as the HUD separator, `…` for an ellipsis and `—`, `→`, `↗` as in English. A dash inside a sentence becomes 。 or ：.
+- Button names cited in running text go in ［］: ［次へ］を使ってください.
+- No space between Japanese and Latin letters, digits or a `{placeholder}`: 「AIS船舶」, 「Spaceを長押しで話す」, 「{count}件」, 「{name}を表示」.
+- Two exceptions keep the space: a Japanese label before its value in a readout (「雲量 {pct}%」, 「ステーション {id}」, 「高度 {altitude}」), and the state words in toggles (「CCTV オン」, 「ラジオ オフ」).
+- Waiting states are 「X待ち」, not 「Xを待機中」: 「観測データ待ち」, 「進路/予報円は第{number}報待ち」, 「RTL-SDRデバイスの接続待ち…」. 待機中 is for something on standby with no object: 「フィード待機中」, 「音声待機中」.
+- Key names keep their own case in running text and hints: Tab, Enter, Space, Esc (「Tabでプレビュー · Enter / Spaceで選択」). Text that CSS upper-cases shows them in capitals, as in English.
+- Loanwords are katakana with the long-vowel mark, as in Microsoft and Apple style: ユーザー, ブラウザー, ビューアー, プロバイダー, レイヤー, フィルター, モニター, パラメーター. Pick one katakana form per term and keep it (see the glossary).
+- Product, provider and dataset names stay in Latin script: Google Maps, Cesium ion, OpenSky, CelesTrak, NASA FIRMS, Sentinel-2, KartaView. Google's own product names use Google's Japanese, joined like any Latin word: Googleストリートビュー. Nepal place names in the Bhote Koshi scenes stay in Latin script, as in zh-CN; country and well-known city names are translated (ネパール, 東京, オースティン).
+
+## Numbers, units and dates
+
+- Units: km, m, km/h, m/s, kt, ft, mph, hPa, MW, dB, °, % stay as written, with the English spacing (「250 km」, 「{frp} MW」, 「95 kt」). Code-built cockpit distances follow this too (`cockpitUnitCase` skips the HUD upper-casing for ja, as for zh). The cockpit's own speed caption is the HUD code KT, in 対地速度 · KT and under the readout.
+- Number ranges keep the English en dash, not ～: 「2–6日ごと」, 「50–99%」, 「南緯25°–北緯80°」.
+- Time units are words written straight after the number: 秒, 分, 時間, 日 (「5分前」, 「{count}時間」, 「1時間5分」). `formatQuantity` and `formatRelativeTime` drop the space for Japanese unit words, so code-built values match the catalog.
+- Counters follow the thing counted: 機 (aircraft), 隻 (ships), 基 (satellites), 台 (cameras, vehicles), 局 (stations), 件 (records, results, events), か所 (sites), 個 (generic). Prefer a counter to a bare number.
+- Dates come from `Intl` and read year first: 2026年8月26日. Coordinates in prose are 北緯 / 東経; HUD hemisphere letters stay N, S, E, W.
+
+## Plurals
+
+`Intl.PluralRules('ja')` has one category, `other`: a `tn()` entry has only that form. Put the counter next to the number: 「航空機{n}機」, 「船舶{n}隻」, 「メッセージ {count}件」.
+
+## Glossary
+
+| English                                   | 日本語                                  |
+| ----------------------------------------- | --------------------------------------- |
+| layer / data layer                        | レイヤー / データレイヤー               |
+| feed                                      | フィード                                |
+| source / data source / attribution        | ソース / データソース / 出典            |
+| LIVE (status) / live data                 | ライブ / ライブデータ                   |
+| SIMULATED                                 | シミュレーション                        |
+| stale / degraded / unavailable            | 更新遅延 / 性能低下 / 利用不可          |
+| cached (status)                           | キャッシュの（キャッシュの予報）        |
+| PARTIAL (feed state)                      | 部分的                                  |
+| upstream (remote data source)             | 配信元                                  |
+| retry                                     | 再試行                                  |
+| key (API key) / POWER UP                  | キー（APIキー）/ パワーアップ           |
+| Provider Settings                         | プロバイダー設定                        |
+| globe / map / map source / basemap        | 地球儀 / 地図 / マップソース / ベースマップ |
+| mapped (OSM-mapped sites)                 | マップ済み                              |
+| aircraft / flight / military flights      | 航空機 / フライト / 軍用機              |
+| FLIGHT {count} (a rocket stage's nth flight) | {count}回目の飛行                    |
+| vessel, ship                              | 船舶                                    |
+| satellite                                 | 衛星                                    |
+| launch (rocket) / space mission           | 打ち上げ / 宇宙ミッション               |
+| stage (rocket) / downrange                | 段 / ダウンレンジ                       |
+| contact (tracked object)                  | コンタクト                              |
+| installation, site                        | 施設                                    |
+| camera / CCTV camera                      | カメラ / CCTVカメラ                     |
+| earthquake / active fire / fire perimeter | 地震 / 火災検知 / 延焼範囲              |
+| contained / containment (fire)            | 封じ込め / 封じ込め率                   |
+| scene / shot                              | シーン / ショット                       |
+| briefing / panel / dock                   | ブリーフィング / パネル / ドック        |
+| preset / visual preset                    | プリセット / ビジュアルプリセット       |
+| Tactical / Minimal / Cyber                | タクティカル / ミニマル / サイバー      |
+| Scope (circular viewport mask) / keyhole  | スコープ / キーホール                   |
+| Clean UI                                  | クリーンUI                              |
+| cockpit                                   | コックピット                            |
+| heading / altitude / ground speed         | 機首方位 / 高度 / 対地速度              |
+| track (TRK, direction over the ground)    | 対地針路                                |
+| HDG / BRG / CRS / FOV / SPD / POS        | そのまま（HUDコード）                   |
+| squawk                                    | スコーク                                |
+| radio failure / emergency (7600 / 7700)   | 通信機故障 / 緊急事態                   |
+| map heading / North up                    | 方位 / 北を上に                         |
+| Street Level / Street View (Google)       | ストリートレベル / ストリートビュー     |
+| Recent Imagery                            | 最近の衛星画像                          |
+| Global Context / Context (panel)          | グローバルコンテキスト / コンテキスト   |
+| radio (station) / tune / seek             | ラジオ（局）/ 選局・同調 / シーク       |
+| Public Safety / SAFETY (radio category)   | 警察・消防                              |
+| transit / bikeshare                       | 公共交通 / シェアサイクル               |
+| occupancy: empty / standing room only / crushed | 乗客なし / 立ち乗りのみ / 非常に混雑 |
+| traffic flow (TomTom)                     | 交通流                                  |
+| Previous / Next                           | 前へ / 次へ                             |
+| SIG / NEWS / LOCAL (briefing tabs)        | シグナル / ニュース / ローカル          |
+| compass points (N, NNE, NE, ENE, …)       | 北, 北北東, 北東, 東北東, …             |
+| weather field / FIELD (selector)          | 要素                                    |
+| weather model / forecast lead hours       | モデル / 予報時間                       |
+| valid (forecast time) / issued            | 対象時刻 / 発表                         |
+| radar reflectivity / lightning density    | レーダー反射強度 / 雷密度               |
+| cyclone, storm (NHC/CPHC) / advisory      | サイクロン / 情報（第N報）; alone: サイクロン情報 |
+| potential tropical cyclone (NHC PC)       | サイクロン化のおそれがある擾乱          |
+| forecast uncertainty cone                 | 予報円                                  |
+| tropical storm / tropical depression      | 熱帯暴風雨 / 熱帯低気圧                 |
+| scene cloud / mosaic / daily overview     | シーン雲量 / モザイク / 日次概観        |
+| box (Recent Imagery area)                 | 範囲                                    |
+| WINDOW (search radius around a subject)   | 範囲                                    |
+| coverage / coverage % / full, partial     | カバー範囲 / カバー率（%のみ）/ 全体, 一部 |
+| pin (Recent Imagery)                      | 固定                                    |
+| clear day (Recent Imagery)                | 雲の少ない日                            |
+| outline / mark (map annotation)           | 輪郭 / マーク                           |
+| share (a view or link)                    | 共有                                    |
+| import / export (project, presets)        | インポート / エクスポート               |
+| EXPORT (image, PNG)                       | 書き出し                                |
+| voice (the voice assistant)               | 音声アシスタント / 音声機能             |
+| activate (a control, screen-reader text)  | 押す（「押すと…」）                      |
+| AI agent                                  | AIエージェント                          |
+| frame (bring into view)                   | 視野に収める                            |
+| story beat / evidence beat                | ストーリー区切り / 証拠の区切り         |
+| camera pose / camera move                 | カメラの姿勢 / 移動                     |
+| roundabout / ramp / exit                  | ロータリー / ランプ / 出口              |
+| reduced motion                            | 動きを減らす                            |
+| NOT AN ALL-CLEAR                          | 安全の保証ではありません                |
+| … Watch (scene titles: Earth, Orbital)    | 監視（地球監視, 軌道監視）              |

docs/translations/pt.md

@@ -0,0 +1,107 @@
+# Brazilian Portuguese (`pt`)
+
+Catalog: `src/i18n/locales/pt.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: abiyeenzo (#909).
+
+## Style
+
+- Brazilian Portuguese (pt-BR): câmera, tela, compartilhar, arquivo, baixar, ônibus, metrô. Every `pt` tag, `pt-PT` included, gets this catalog, so avoid slang and regionalisms.
+- Address the user with «você» imperatives: «Clique no mapa», «Ative o CCTV», «Tente novamente». Tooltips that name an action use the infinitive: «Expandir painel», «Redefinir a câmera».
+- Sentence case, not Title Case: "Live Flights" → «Voos ao vivo». UPPERCASE English stays UPPERCASE: «AO VIVO», «SEM DADOS».
+- Quotes inside Portuguese text are straight double quotes: «Excluir o plano "{shot}"?». A sentence that names a panel quotes it: «o painel "Configurações de provedores"» as the subject, so the verb agrees, and «adicione em "Configurações de provedores"» after a preposition.
+- A dash between clauses is a spaced em dash « — », even where the English runs it in.
+- A date or time after a participle takes a preposition: «emitido em {time}», «válida para {valid}», «Posição em {time}», «onde estava em {time}». Use «em», not «às», wherever {time} can include a date.
+- A count in a string with no plural form (no `tn()`) goes after a colon, so it reads right for 1: «sincronizando feeds de cidades: {count}...», «CÂMERAS EM ESPERA: {count}».
+- A placeholder that holds a layer or tool name of unknown gender and number gets a noun to agree with: «{label}: camada ativada», «A ferramenta "{owner}" está usando o ponteiro — feche-a primeiro».
+- Short labels, chips and HUD readouts stay short. A standard abbreviation with a period beats a wrapped line: ANT., PRÓX., DESLIG., EXCL., INCL., ALT., VEL., câm.
+- The HUD codes HDG, BRG, CRS, FOV, DEST, SPD, RANGE, ALT, GS, TRK and V/S stay in English, as in cockpit avionics («ALT {altitude} FT · GS {speed} KT · TRK {track}», «V/S {rate} FT/MIN»), and so does the HUD recording mark REC. Words used in a sentence are translated: heading → «rumo», range → «alcance».
+- Keyboard keys stay in English: Space, Esc, Enter, Tab, Shift, Backspace, H, 1–9 («Segure Space para falar»).
+- Common English tech words used in Brazil stay: feed, stream, snapshot, briefing, dock, layout, bloom, status, app, link, token.
+- Units: km, m, km/h, m/s, kt (knots), ft (feet), h, min, s, always spaced from the number («Terremotos (24 h)», «Missões espaciais (30 d)»; in the layer names the space is a no-break space, U+00A0, so the unit never wraps away from the number); in UPPERCASE text KM, KM/S, KT, FT, MIN, H. "m" is always metres, so minutes are «min» («há 5 min»). MW stays MW. `°` and `%` stay. Decimal comma in written numbers («M4,4»).
+- "ago" goes before the time: «há {count} min», «mais recente há {value}». When a placeholder already holds a localized "ago" text (`{age}`, `{ago}`), do not add «há» again.
+- Money: «US$ {amount} mil / mi / bi» for thousands, millions and billions.
+- Compass points use Leste/Oeste: N, NNE, NE, ENE, L, ESE, SE, SSE, S, SSO, SO, OSO, O, ONO, NO, NNO; hemisphere letters N, S, L, O.
+
+## Plurals
+
+A `tn()` entry needs three forms. `Intl.PluralRules('pt')` follows Brazilian usage:
+
+| Form    | Counts                                 | Example            |
+| ------- | -------------------------------------- | ------------------ |
+| `one`   | 0, 1 and anything below 2: 0, 1, 1.5   | 0 câmera, 1 câmera |
+| `many`  | 1 000 000, 2 000 000… (exact millions) | 1000000 de câmeras |
+| `other` | everything else: 2–999 999, 2.5…       | 3 câmeras          |
+
+The `many` form is the `other` text with «de» after the number: «{count} de câmeras carregadas», «{count} DE CHAVES PENDENTES». A `one` form is also read for 0, so keep it natural with zero («0 arquivo selecionado» is standard Brazilian usage).
+
+## Glossary
+
+| English                                       | Português                                                    |
+| --------------------------------------------- | ------------------------------------------------------------ |
+| layer / data layer                            | camada / camada de dados                                     |
+| feed / source / data source                   | feed / fonte / fonte de dados                                |
+| LIVE (status) / live data                     | AO VIVO / dados ao vivo                                      |
+| SIMULATED                                     | SIMULADO                                                     |
+| stale / degraded / unavailable                | desatualizado / degradado / indisponível                     |
+| retry / retrying                              | nova tentativa / tentando de novo                            |
+| retrying (a fetch) / retrying slowly          | buscando de novo / tentando de novo em intervalos maiores    |
+| rate-limited                                  | «X: limite de requisições atingido»                          |
+| dismiss (window, card, error)                 | fechar                                                       |
+| key (API key) / POWER UP / POWERED UP         | chave / ATIVAR / ATIVADO                                     |
+| Provider Settings                             | Configurações de provedores                                  |
+| ON / OFF (state chips)                        | ATIVO / INATIVO                                              |
+| enable / disable                              | ativar / desativar                                           |
+| globe / map / map source / map stack          | globo / mapa / fonte do mapa / pilha de mapas                |
+| basemap / tile                                | mapa base / bloco                                            |
+| aircraft, plane / flight / military flights   | aeronave, avião / voo / voos militares                       |
+| vessel, ship / TANKER (AIS class)             | embarcação / NAVIO-TANQUE                                    |
+| satellite / shell (Starlink) / DENSE          | satélite / camada orbital / DENSO                            |
+| SPARSE / BALANCED / DENSE (detection modes)   | ESPARSO / EQUILIBRADO / DENSO (o modo)                       |
+| launch (rocket) / launch site / space mission | lançamento / local de lançamento / missão espacial           |
+| KM DOWNRANGE / EST. DOWNRANGE                 | KM DO LOCAL DE LANÇAMENTO / EST. PELA DIST. DO LANÇAMENTO    |
+| ascent / replay / payload / stage             | subida / reprise / carga útil / estágio                      |
+| contact / tracking / track                    | contato / rastreamento / rastro                              |
+| installation / site                           | instalação / local                                           |
+| PLACES CANDIDATE (installation class)         | CANDIDATO DO GOOGLE PLACES                                   |
+| mapped / observed                             | mapeado / observado                                          |
+| camera / CCTV camera                          | câmera / câmera de CCTV                                      |
+| CALIBRATED / CURATED (CCTV badge)             | CALIBRADA / COM CURADORIA                                    |
+| AUTO HOP ON / OFF (CCTV)                      | TROCA AUTO. LIGADA / DESLIG. (as the other CCTV toggles)     |
+| earthquake / active fire                      | terremoto / incêndio ativo                                   |
+| advisory (NHC/CPHC cyclone)                   | boletim                                                      |
+| E/C Pacific (NHC/CPHC coverage)               | Pacífico Leste/Central (no «L/C»)                            |
+| weather (layer, card) / weather satellite     | clima / meteorologia, meteorológico                          |
+| FOG / cloud unknown                           | NEVOEIRO / nebulosidade desconhecida                         |
+| AQHI bands Low … Very High                    | Risco baixo … Risco muito alto                               |
+| radio station / broadcaster                   | estação de rádio / emissora                                  |
+| Oldies / World (radio tags)                   | Flashback / Músicas do mundo                                 |
+| radio genre tags agree with «música»          | Alternativa, Clássica, Eletrônica, Latina                    |
+| road / flow (traffic)                         | via / fluxo                                                  |
+| Street Level (layer)                          | Nível da rua                                                 |
+| scene / shot / scene recipe                   | cena / plano / receita de cena                               |
+| briefing / panel / dock                       | briefing / painel / dock                                     |
+| cockpit                                       | cabine                                                       |
+| preset / visual preset / EXPORT PRESETS       | predefinição / predefinição visual / EXPORTAR PREDEF.        |
+| VISUAL PRESETS (dock caption)                 | PREDEF. VISUAIS                                              |
+| Scope (circular viewport mask) / keyhole      | mira / visor                                                 |
+| feather / fade                                | suavização / esmaecimento                                    |
+| detection overlay                             | sobreposição de detecção                                     |
+| pin (Draw tool) / box (Recent Imagery)        | marcador / área                                              |
+| Cyber (HUD layout, effect)                    | Ciber                                                        |
+| heading / course / altitude / ground speed    | rumo / curso / altitude / velocidade solo (VELOC. SOLO)      |
+| map heading / bearing (compass, north up)     | orientação (do mapa)                                         |
+| HDG / BRG / CRS / FOV / DEST / SPD / RANGE    | HDG / BRG / CRS / FOV / DEST / SPD / RANGE (unchanged)       |
+| V/S (vertical speed code)                     | V/S (unchanged)                                              |
+| PREV / NEXT                                   | ANT. / PRÓX.                                                 |
+| Previous / Next (button text)                 | Anterior / Próximo (Próxima)                                 |
+| L / R (relative bearing)                      | E / D                                                        |
+| SIG / NEWS / LOCAL (briefing tabs)            | SIG / NOTÍCIAS / LOCAL                                       |
+| REGIONAL NEWS (fits the 16-character kicker)  | NOTÍCIAS DA ÁREA                                             |
+| PITCH / HGT (CCTV calibration chips)          | INCL. / ALT.                                                 |
+| NOT AN ALL-CLEAR                              | NÃO GARANTE SEGURANÇA                                        |
+| Last report (transit vehicle position)        | Último registro                                              |
+| intersection (CCTV)                           | cruzamento                                                   |
+| {layers} just turned on (any list of layers)  | «{layers}: ativação recente» (no agreement needed)           |
+| {label} on / off (one layer)                  | «{label}: camada ativada / desativada»                       |
+| turn-by-turn: turn left / keep left / lane    | vire à esquerda / mantenha-se à esquerda / faixa da esquerda |

docs/translations/uk.md

@@ -0,0 +1,106 @@
+# Ukrainian (`uk`)
+
+Catalog: `src/i18n/locales/uk.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation source: meirm (#312).
+
+## Style
+
+- Address the user with polite imperatives: «Натисніть», «Увімкніть», «Спробуйте ще раз».
+- Sentence case, not Title Case: "Live Flights" → «Рейси онлайн».
+- Ukrainian norms, not Russian calques: «у радіусі», «за посиланням», «надто довгий», «потім», «вигляд» (a camera view: «вигляд згори»), «стеження» (tracking); prepositions alternate у/в and і/й by euphony.
+- The apostrophe is always ʼ (U+02BC): обʼєкт, звʼязок, памʼять. Not ' or ’.
+- Quotes inside Ukrainian text are «ялинки»; a button or layer name inside a sentence goes in them: Увімкніть «Вуличні знімки».
+- In short labels, a standard abbreviation with a period beats a wrapped line: ПОПЕР., ДАЛЬН., КАЛІБР.
+- Units: км, м, км/год, м/с, вуз (knots), фт (feet), год, хв, с, МГц, дБ, гПа; in UPPERCASE text КМ, М, КМ/С, ВУЗ, ФТ. MW is МВт in any case. `°` and `%` stay. Decimal comma in coordinates written as text: 28,2710° пн. ш.
+- Coordinates: пн. ш. / пд. ш. / сх. д. / зх. д.; the HUD hemisphere letters are Пн, Пд, Сх, Зх.
+
+## Plurals
+
+A `tn()` entry needs four forms. `Intl.PluralRules('uk')` picks:
+
+| Form    | Counts                   | Example    |
+| ------- | ------------------------ | ---------- |
+| `one`   | 1, 21, 31, 101…          | 1 камера   |
+| `few`   | 2–4, 22–24, 32–34…       | 3 камери   |
+| `many`  | 0, 5–20, 25–30, 111–114… | 5 камер    |
+| `other` | fractions: 1.5, 2.25…    | 1,5 камери |
+
+`other` takes the genitive singular: 1,5 кадру, 1,5 літака, 1,5 ключа. When a word next to a number cannot agree in every form, move the number after a colon instead: «поруч: {count}», «відповідей: {responses}». The same trick keeps place names and tool names out of a preposition's case: «звідки: {origin}», «Активно: {name}».
+
+## Glossary
+
+| English                                         | Українська                                                       |
+| ----------------------------------------------- | ---------------------------------------------------------------- |
+| layer / data layer                              | шар / шар даних                                                  |
+| feed                                            | потік даних (short: потік)                                       |
+| source / data source                            | джерело / джерело даних                                          |
+| LIVE (status) / live data                       | ОНЛАЙН / у реальному часі (status chip: ДАНІ ОНЛАЙН)             |
+| SIMULATED / SYNTHETIC                           | ІМІТАЦІЯ                                                         |
+| stale / degraded / unavailable                  | застарів / з перебоями (chip: ПЕРЕБОЇ) / недоступний             |
+| retry                                           | повтор                                                           |
+| key (API key) / POWER UP                        | ключ / ЗАПУСК                                                    |
+| Provider Settings / provider                    | Налаштування постачальників / постачальник                       |
+| globe / map / map source / basemap              | глобус / карта / джерело карти / підкладка                       |
+| aircraft / flight / military flights            | літак (short HUD: борт) / рейс / військові рейси                 |
+| vessel, ship / vessels                          | судно / судна (gen. pl. суден)                                   |
+| satellite                                       | супутник                                                         |
+| launch (rocket) / space mission                 | запуск / космічна місія                                          |
+| ascent (rocket) / booster FLIGHT {n}            | виведення / ПОЛІТ {n} (not рейс)                                 |
+| contact / tracking                              | контакт / стеження                                               |
+| installation, site / mapped                     | обʼєкт / нанесений (обʼєкт, контакт)                             |
+| camera / CCTV camera                            | камера / камера CCTV                                             |
+| earthquake / active fire / fire perimeter       | землетрус / активна пожежа / контур пожежі                       |
+| advisory (NHC/CPHC cyclone)                     | зведення                                                         |
+| scene / shot / scene recipe                     | сцена / кадр / рецепт сцени                                      |
+| briefing / panel / dock                         | брифінг / панель / док                                           |
+| preset / visual preset                          | пресет / візуальний пресет                                       |
+| Scope, keyhole (circular viewport mask)         | приціл                                                           |
+| overlay (detection overlay) / world overlay     | накладка / накладка на глобусі                                   |
+| heading / altitude / ground speed               | курс / висота / шляхова швидкість                                |
+| map bearing, map heading                        | азимут карти                                                     |
+| HDG / BRG / CRS, TRK / FOV / DEST / SPD / RANGE | КУРС / ПЕЛ. / ШК (шляховий кут) / ОГЛЯД / ПРИЗН. / ШВИД / ДАЛЬН. |
+| Street View (Google)                            | Перегляд вулиць (as in Ukrainian Google Maps)                    |
+| Street Level (layer)                            | Вуличні знімки                                                   |
+| imagery / recent imagery                        | знімки / свіжі знімки                                            |
+| radar reflectivity / lightning density          | радіолокаційна відбивність / щільність блискавок                 |
+| infrared                                        | інфрачервоний (short: ІЧ)                                        |
+| receiver / gain / decoder                       | приймач / підсилення / декодер                                   |
+| broadcaster                                     | мовник                                                           |
+| CONUS, WHOT/BHOT, Ironbow, CRT, NVG, FLIR       | без перекладу                                                    |
+| PREV / NEXT (HUD) / Previous / Next             | ПОПЕР. / ДАЛІ / Попередній / Наступний                           |
+| anchor / data pack / bundle (scene)             | якір / пакет даних / архів                                       |
+| box (Recent Imagery area)                       | область                                                          |
+| camera move                                     | переліт                                                          |
+| SIG / NEWS / LOCAL (briefing tabs)              | СИГН. / НОВИНИ / МІСЦ.                                           |
+| compass points (N, NNE, NE, …)                  | Пн, ПнПнСх, ПнСх, …                                              |
+| L / R (relative bearing)                        | Л / П                                                            |
+| click / tap                                     | клацнути / натиснути                                             |
+| session (voice, OAuth)                          | сеанс                                                            |
+| sequence (street-level photos)                  | послідовність                                                    |
+| search (place search)                           | пошук місця                                                      |
+| pitch (CCTV camera pose)                        | нахил                                                            |
+| traffic (road traffic layer)                    | дорожній рух                                                     |
+| phosphor (CRT)                                  | люмінофор                                                        |
+| view (map extent) / view centre / in view       | видима область (карти) / центр карти / у кадрі                   |
+| select (verb) / selected                        | вибрати / вибраний (not обрати)                                  |
+| ping (cockpit proximity contacts)               | контакт                                                          |
+| merge (turn-by-turn) / on ramp                  | влитися в потік / вʼїзд (off ramp: зʼїзд)                        |
+| watch (Earth/Orbital Watch)                     | спостереження                                                    |
+| timeout                                         | тайм-аут                                                         |
+| icon                                            | значок (not іконка)                                              |
+| run (scene playback) / RUN LOG                  | відтворення / ЖУРНАЛ ВІДТВОРЕННЯ (запуск is a rocket launch)     |
+| Preview (voice panel replies)                   | відповіді                                                        |
+| Marine (radio tag) / pleasure craft             | море (not флот) / прогулянкове судно                             |
+| emergency (ADS-B) / Emergency (radio tag)       | аварійний стан / надзвичайні ситуації                            |
+| confidence (FIRMS fire detection)               | достовірність (short: достов.)                                   |
+| thermal (FLIR-style imaging)                    | тепловий (not термальний)                                        |
+| map stack                                       | набір карт                                                       |
+| stage (rocket) re-entry / recovery              | вхід ступеня в атмосферу / повернення                            |
+| ON / OFF (toggle chips)                         | УВІМК. / ВИМК.                                                   |
+| Clean UI / EXIT CLEAN VIEW                      | чистий інтерфейс / ПОВЕРНУТИ ІНТЕРФЕЙС                           |
+| full globe view                                 | вигляд всього глобуса                                            |
+| inputs (cockpit context chip)                   | потоки (not вхідні дані)                                         |
+| downrange (rocket stage)                        | дальність                                                        |
+| resolution (spatial)                            | роздільна здатність (not роздільність)                           |
+| shared follow expired                           | посилання на стеження застаріло                                  |

docs/translations/zh-CN.md

@@ -0,0 +1,77 @@
+# Simplified Chinese (`zh-CN`)
+
+Catalog: `src/i18n/locales/zh-CN.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+Translation sources: abiyeenzo (#914) and EDIT-Aeterna (#979).
+
+## Style
+
+- Mainland usage and Simplified characters. Address the user neutrally, without 您/你 where a plain imperative works: 「点击地图」, 「重试」.
+- Chinese has no case: an UPPERCASE English HUD label becomes the same short Chinese label. Keep labels as short as the English: 「实时」, 「过期」, 「关」.
+- Full-width punctuation in Chinese text: ，。：；？！（）“”. A dash is 「——」 without spaces; keep `·` as the HUD separator and `…` for ellipsis.
+- One space between Chinese and Latin letters or digits: 「AIS 船舶」, 「24 小时」, 「{count} 个」. No space next to full-width punctuation.
+- Units: km, m, km/h, m/s, kn, ft, MW, °, % stay as written; time words are 小时, 分钟, 秒 after a number (「5 分钟前」).
+- Product names, provider names and codes stay as they are: Google, Cesium, CelesTrak, NOAA, FIRMS, AIS, ADS-B, GNSS, CCTV, HUD, CRT, NVG, FLIR, WHOT/BHOT, Ironbow, CONUS.
+
+## Plurals
+
+`Intl.PluralRules('zh-CN')` has one category, `other`: a `tn()` entry has only that form. Use a measure word next to the number where Chinese needs one: 「{count} 个密钥」, 「{count} 架飞机」, 「{count} 艘船」.
+
+## Glossary
+
+| English                               | 中文                        |
+| ------------------------------------- | --------------------------- |
+| layer / data layer                    | 图层 / 数据图层             |
+| feed                                  | 数据源                      |
+| source / data source                  | 来源 / 数据源               |
+| LIVE (status) / live data             | 实时 / 实时数据             |
+| SIMULATED                             | 模拟                        |
+| stale / degraded / unavailable        | 过期 / 降级 / 不可用        |
+| retry                                 | 重试                        |
+| key (API key) / POWER UP              | 密钥（API 密钥）/ 增强      |
+| Provider Settings                     | 服务商设置                  |
+| globe / map / map source / basemap    | 地球 / 地图 / 地图源 / 底图 |
+| aircraft / flight / military flights  | 飞机 / 航班 / 军用航班      |
+| vessel, ship                          | 船舶                        |
+| satellite                             | 卫星                        |
+| launch (rocket) / space mission       | 发射 / 太空任务             |
+| contact (tracked object)              | 目标                        |
+| installation, site                    | 设施                        |
+| camera / CCTV camera                  | 摄像头 / CCTV 摄像头        |
+| earthquake / active fire              | 地震 / 活跃火点             |
+| scene / shot                          | 场景 / 镜头                 |
+| briefing / panel / dock               | 简报 / 面板 / 停靠栏        |
+| preset / visual preset                | 预设 / 视觉预设             |
+| Display / HUD layout                  | 显示 / HUD 布局             |
+| Tactical / Minimal / Cyber            | 战术 / 精简 / 赛博          |
+| Scope (circular viewport mask) / keyhole | 视域                      |
+| Clean UI                              | 纯净界面                    |
+| cockpit                               | 座舱                        |
+| heading / altitude / ground speed     | 航向 / 高度 / 地速          |
+| map heading / North up                | 方位 / 正北朝上             |
+| Street Level / Street View (Google)   | 街景 / 街景（Google）       |
+| Recent Imagery                        | 近期影像                    |
+| Global Context / Context (panel)      | 全局态势 / 态势             |
+| radio (station)                       | 电台                        |
+| transit / bikeshare                   | 公共交通 / 共享单车         |
+| Previous / Next                       | 上一个 / 下一个             |
+| compass points (N, NNE, …)            | 北, 北东北, …               |
+| weather field / FIELD (selector)       | 气象场 / 要素               |
+| weather model / forecast lead hours   | 模式 / 预报时效             |
+| valid (forecast time)                 | 有效时间                    |
+| scene cloud / mosaic                  | 整景云量 / 镶嵌图           |
+| pin (Recent Imagery)                  | 固定                        |
+| THIS (voice pointer)                  | 所指                        |
+| outline / trace an outline            | 轮廓 / 绘制轮廓             |
+| mark (map annotation)                 | 标注                        |
+| camera badge                          | 摄像头标记                  |
+| provider / embedded provider controls | 服务商 / 平台控件           |
+| share (a view or link)                | 分享                        |
+| AI agent                              | AI 智能体                   |
+| stage (rocket) / downrange            | 子级 / 航程                 |
+| capture shot / camera move            | 保存镜头 / 运镜             |
+| story beat / evidence beat            | 事件节点 / 证据节点         |
+| camera pose                           | 位姿                        |
+| forecast uncertainty cone             | 预报不确定范围              |
+| seed (catalog data)                    | 预置                        |
+| frame (bring into view)               | 将…纳入视野                 |

docs/translations/zh-Hant.md

@@ -0,0 +1,17 @@
+# Traditional Chinese (`zh-Hant`)
+
+Catalog: `src/i18n/locales/zh-Hant.json`. General rules: [TRANSLATORS.md](../TRANSLATORS.md).
+
+`zh-Hant` is the Simplified Chinese catalog (`zh-CN`, credited to abiyeenzo, #914, and EDIT-Aeterna, #979) written in Traditional characters with OpenCC character conversion. Wording and terminology are the same as in `zh-CN`: change a term in [zh-CN.md](./zh-CN.md) and the `zh-CN` catalog first, then convert. Only the script differs.
+
+After `s2tw` conversion, fix the characters OpenCC picks wrongly: 年曆史 → 年歷史, 下遊 → 下游, 並道 → 併道, 發佈 → 發布, 公佈 → 公布.
+
+## Style
+
+- Follow [zh-CN.md](./zh-CN.md) for wording, punctuation, spacing, units and the glossary, written in Traditional characters.
+- Relative-time placeholders may already include 前. In `LIVE · updated {age}`, the caller supplies the complete relative age; do not append another 前.
+- The picker displays 中文（繁體） / Chinese (Traditional); explicit Hans tags select Simplified Chinese.
+
+## Plurals
+
+`Intl.PluralRules('zh-Hant')` uses only `other`. Keep the measure words of the `zh-CN` entry: 「{count} 架飛機」、「{count} 艘船」.