Put the official site first in the README and in package.json

Moves the official-site line directly under the README title, and points
package.json's homepage at godseyeview.ai instead of the README anchor.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_011hsCV6Ap9bk7WtxUbbbxnT

.env.example

@@ -61,15 +61,8 @@ CESIUM_ION_TOKEN=
 # ChatGPT/Codex OAuth session; the browser still receives only a short-lived
 # Realtime client secret. Do not prefix with VITE_.
 OPENAI_API_KEY=
-# Typed chat uses Chat Completions, independently of the voice model. It can
-# only bill OPENAI_API_KEY, so GEV_PREFER_CODEX_OAUTH below turns it off.
-OPENAI_CHAT_MODEL=gpt-4.1-mini
-# Typed chat requests (/api/openai/chat) per IP per minute, counted apart from
-# voice. Unset, it takes GEV_RATELIMIT_OPENAI_PER_MIN's cap; 0 disables it.
-# Not a billing cap.
-# GEV_RATELIMIT_OPENAI_CHAT_PER_MIN=30
-# Optional: forbid API-key voice sessions and OpenAI typed chat. Select ChatGPT
-# OAuth in Provider Settings; missing or expired Codex sign-in then fails closed.
+# Optional: forbid API-key voice sessions. Select ChatGPT OAuth in Provider
+# Settings; missing or expired Codex sign-in then fails closed.
 # GEV_PREFER_CODEX_OAUTH=true
 OPENAI_REALTIME_MODEL=gpt-realtime-2
 # Cheaper voice tier, used when the GEV MIC panel's MINI toggle is on.
@@ -263,9 +256,6 @@ 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_HOUSTON_ENABLED=                                # off by default; set 1 to load Houston TranStar cameras only if you hold TxDOT's written permission (TranStar's Content Usage terms prohibit copying, distributing or framing its images without it; see DATA_SOURCES.md)
-# CCTV_HOUSTON_MAX_SOURCES=250                         # cap cameras loaded from the Houston TranStar catalog (nearest metro cores first)
-# CCTV_HOUSTON_CAMERAS_URL=                            # override the Houston TranStar catalog 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
@@ -273,47 +263,9 @@ AISSTREAM_API_KEY=
 # CCTV_FORCE_AUSTIN=                                   # force live default sources when a source-pack JSON is configured
 
 # Optional: comma-separated Overpass URLs; use only instances you run or pay for.
-# Also enables voice place search (osm_query, "hospitals in Kathmandu").
 OVERPASS_UPSTREAMS=
 
-# Optional: place-lookup endpoints. Lookups try bundled data first, then the
-# endpoint set here. Nominatim stays off unless NOMINATIM_URL is set; Photon
-# uses its public service when PHOTON_URL is unset.
-# NOMINATIM_URL: search endpoint for last-resort place search and voice
-# outlines (e.g. https://nominatim.example.org/search). A configured URL
-# selects the endpoint explicitly. Unset, empty and invalid values disable
-# Nominatim; nothing falls back to nominatim.openstreetmap.org. Use an endpoint
-# you operate or are authorized to use. Answers are cached (outlines 90 days,
-# places 30 days, no-results 24 h in .gev-cache/nominatim).
-# Explicit public-service configuration retains per-install pacing and caps;
-# these do not establish an application-wide allowance or authorize public use.
-# NOMINATIM_URL=
-# Public-instance requests per UTC day, outlines and search together. Not
-# applied to your own NOMINATIM_URL.
-# NOMINATIM_DAILY_CAP=50
-# Public-instance pacing is shared through .gev-cache/nominatim/state.json. If
-# the server stopped mid-request (or its disk filled), it leaves a
-# state.json.dispatch.* marker and refuses public lookups ("unfinished durable
-# Nominatim dispatch") for ten minutes rather than risk breaking the spacing;
-# the next lookup after that removes the marker and resumes with fresh spacing.
-# PHOTON_URL: keyless place search endpoint used by the browser
-# (e.g. https://photon.example.org/api/). Unset uses photon.komoot.io; set it
-# empty to disable. Only https endpoints are accepted (the page's
-# Content-Security-Policy allows no plain-http origin); any other value disables it.
-# PHOTON_URL=
-
 # Optional: who may frame the app in embed mode (?embed=1), as CSP
 # frame-ancestors sources such as "https://example.com", or * for any page.
 # Unset, no page may frame it. Other pages of the app can never be framed.
 # GEV_EMBED_FRAME_ANCESTORS=
-
-# Gemini typed chat uses generateContent; voice continues to use Gemini Live.
-GEMINI_CHAT_MODEL=gemini-3.5-flash-lite
-# Typed chat requests (/api/gemini/chat) per IP per minute. Unset, it takes
-# GEV_RATELIMIT_GEMINI_PER_MIN's cap (default 30); 0 disables it.
-# GEV_RATELIMIT_GEMINI_CHAT_PER_MIN=30
-
-# Optional keyless Radio Browser coverage: up to 8 ISO alpha-2 countries.
-# Each reserves up to 40 stations within the existing 750-station directory.
-# Restart after changing. Leave blank for the existing global selection.
-# RADIO_PRIORITY_COUNTRIES=IN,PL

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -40,7 +40,7 @@ body:
     attributes:
       label: OS, Node version, browser
       description: Include the versions you can find. Write "unknown" for anything unavailable.
-      placeholder: "Windows 11, Node 24.22.2, Chrome 151"
+      placeholder: "Windows 11, Node 24.14.0, Chrome 151"
     validations:
       required: true
   - type: input

.github/pull_request_template.md

@@ -34,8 +34,7 @@ If it's bigger, link to it instead.
 
 <!--
 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, Audio,
-and Utilities (its rows render in the separate UTILITIES panel).
+in src/ui/layerPanel.js: Movement, Cameras, Infrastructure, Events, Weather, Utilities.
 If none fits, propose a new group and say why.
 -->
 

.github/workflows/ci.yml

@@ -20,10 +20,10 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node: [24.22.2, 26.x]
+        node: [24.14.0, 26.x]
     env:
       PUPPETEER_SKIP_DOWNLOAD: '1'
-      GEV_REQUIRE_ALLOCATION_GATE: ${{ matrix.node == '24.22.2' && '1' || '0' }}
+      GEV_REQUIRE_ALLOCATION_GATE: ${{ matrix.node == '24.14.0' && '1' || '0' }}
     steps:
       - name: Check out source
         uses: actions/checkout@11d5960a326750d5838078e36cf38b85af677262 # v4.4.0
@@ -59,10 +59,6 @@ jobs:
       - name: Build production bundle
         run: npm run build
 
-      - name: Main chunk size budget
-        if: matrix.node == '24.22.2'
-        run: npm run check:main-chunk
-
   street-level-browser:
     # Hermetic: every Mapillary request is answered from fixtures, so the
     # dummy token below never leaves the page.
@@ -80,7 +76,7 @@ jobs:
       - name: Use Node.js
         uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
-          node-version: 24.22.2
+          node-version: 24.14.0
           cache: npm
 
       - name: Install locked dependencies and headless Chrome
@@ -135,7 +131,7 @@ jobs:
       - name: Use Node.js
         uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
         with:
-          node-version: 24.22.2
+          node-version: 24.14.0
           cache: npm
 
       - name: Run the Pinokio install path

.prettierignore

@@ -20,8 +20,3 @@ node_modules
 .vite
 .vite-*
 *.min.js
-
-# Application views, and panels lifted from them, hold the page markup
-# verbatim; reflowing it changes the DOM
-src/ui/views/*View.vue
-src/ui/views/panels/

.prettierrc.json

@@ -2,11 +2,5 @@
   "singleQuote": true,
   "tabWidth": 2,
   "semi": true,
-  "endOfLine": "lf",
-  "overrides": [
-    {
-      "files": "*.vue",
-      "options": { "htmlWhitespaceSensitivity": "strict" }
-    }
-  ]
+  "endOfLine": "lf"
 }

CONTRIBUTING.md

@@ -4,15 +4,13 @@ Thanks for being here. God's Eye View is an open foundation for live spatial int
 
 ## Getting set up
 
-Use Node.js 24 (24.14.0 or later) or 26.x (also enforced by `package.json`).
-Prefer 24.22.1 or later: earlier releases lack the October 21, 2026 security
-fixes, including CVE-2026-111497 (a Brotli decoder flaw).
+Use Node.js 24.14.x or 26.x (also enforced by `package.json`).
 
 ```bash
 git clone https://github.com/bilawalsidhu/gods-eye-view.git
 cd gods-eye-view
-nvm install 24.22.2
-nvm use 24.22.2
+nvm install 24.14.0
+nvm use 24.14.0
 npm install
 npm run doctor
 ./scripts/dev-fresh.sh        # or: npm run dev (keys are optional)
@@ -29,25 +27,6 @@ through Pinokio; the terminal path above remains the contributor path.
 
 Open `http://localhost:4173`. Before sending a PR run `npm run build`, `npm test`, and `npm run test:track` (dev server must be up) — **all three must stay green.**
 
-### Test prerequisites
-
-- **`npm test`** — unit tests. Runs standalone; no dev server or credentials
-  required. Exit code is the gate.
-- **`npm run test:track`** — the 3D flight-tracking regression harness. It
-  drives the **real app** in headless Chromium, so it **requires a running
-  dev server** (default `http://localhost:4173`). To target another instance,
-  run `npm run test:track -- --url <app-url>` (or
-  `node scripts/track-regression.mjs --url <app-url>`). It does not depend on
-  live OpenSky / adsb.lol / AISStream (those are optional or rate-limited
-  locally); it installs a persistent `fetch` shim that returns synthetic
-  aircraft in the exact upstream payload shapes the layers parse.
-- **`npm run build`** — production Vite build. No server or credentials
-  required; it validates that the client bundle compiles cleanly.
-
-Each feature also has its own headless gate; see
-[Feature regression gates](#feature-regression-gates) below. Docs and changelog
-rules are under [Pull requests](#pull-requests).
-
 ## Checking a built app locally
 
 Run `npm run build` followed by `npm run preview`. Preview serves the built
@@ -136,7 +115,7 @@ The highest-leverage places to jump in:
 
 ## Architecture in one minute
 
-- **Vue 3 + Pinia for the interface,** [CesiumJS](https://cesium.com/platform/cesiumjs/) for the globe and [Vite](https://vitejs.dev/) to build. See [Building UI](#building-ui).
+- **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/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.
@@ -147,65 +126,9 @@ The highest-leverage places to jump in:
 - ES modules, **2-space indent, single quotes, semicolons.**
 - JSDoc on exported/public functions.
 - Match the surrounding code — comment density, naming, and idiom.
-- User-visible text goes through `t()` or `tn()`, with `msg()` marking English that is stored and translated later. Components call `t()` in their templates, so their text follows the locale; `data-i18n*` attributes are only for static page markup such as the loading screen, and `npm run i18n` rejects them in a template. `npm run i18n` must pass. See [docs/I18N.md](docs/I18N.md).
+- User-visible text goes through `t()`, `tn()` or `msg()`, or a `data-i18n*` attribute in markup, and `npm run i18n` must pass. See [docs/I18N.md](docs/I18N.md).
 - Prefer small, reviewable commits. Conventional-commit-style prefixes (`feat:`, `fix:`, `perf:`, `docs:`) are appreciated but not required.
 
-## Building UI
-
-New UX elements are Vue components whose state lives in a Pinia store, and so
-are existing ones when a change converts them:
-
-- **Views are Vue components.** Application views live in `src/ui/views/` and
-  the components they place in `src/ui/views/panels/`; a component that
-  belongs to one feature sits beside its owner (`src/ui/rail/`,
-  `src/ui/weather/`). A view renders what its store holds and forwards
-  clicks and input to the store; it holds no application logic.
-- **State lives in a Pinia store** in `src/ui/stores/`. The owner presents a
-  plain view object and publishes it to the store; the view renders it. User
-  actions return to the owner through handlers it connects to the store,
-  which replace an earlier owner's. Where several owners answer different
-  actions of one store, use `createOwners()` from `src/ui/stores/owners.js`:
-  `act(name, ...args)` calls the newest connected owner that handles `name`,
-  and the owner calls `detach(token)` when it stops.
-- **Portable owners stay framework-free.** An owner in a portable export
-  imports neither Vue nor Pinia: it takes a `publish` option or offers a
-  `subscribe…()`, and the application shell connects it to the store.
-  `npm run check:boundaries` enforces this.
-- **Reuse the kit first.** `src/ui/kit/` has one component per control:
-  `UiButton` (including pressed toggles and pressable chips), `UiSelect`,
-  `UiSlider`, `UiSegmented`, `UiChip` (a label, not a control), `UiBadge`,
-  `UiEmpty`, `UiIcon`, `UiTooltip`, `UiPanel` and `UiRail`. Use these before
-  writing a control. When the kit lacks something, extend a kit component or
-  add one that follows the kit's names, props, events and class names (see
-  [Component kit](docs/VUE-MIGRATION.md#component-kit)), rather than
-  building a one-off.
-- **No hand-written DOM binding.** Don't build elements or write text,
-  classes or attributes from a controller to show UI state; render it from
-  the store. New controls take input through the store rather than through
-  listeners the owner adds. To render outside the view's host (the body, the
-  globe container, or a slot another surface opens), use `<Teleport>` to
-  `body`, a fixed id or a container the owner publishes; don't move nodes by
-  hand. What stays imperative: classes on `<body>` and `<head>`, which sit
-  outside Vue (`cockpit-mode`, `ui-clean-view`); focus moves; positions a
-  layout pass measures in the same task that writes them; and surfaces an
-  owner paints or plays, such as the Cesium canvas, overlay canvases and live
-  video. A few existing surfaces keep listeners or bindings that
-  [docs/VUE-MIGRATION.md](docs/VUE-MIGRATION.md) records; keep those
-  contracts when you change them, and don't copy them into new UI.
-- **Text** goes through `t()` or `tn()` where the template renders it.
-  English kept in a constant or a store is marked with `msg()` and passed to
-  `t()` when it renders, since a `t()` at module load would fix the English.
-- **Test components, not markup strings.** Mount the component over
-  happy-dom with `@vue/test-utils` or `createApp` and assert what it renders
-  from its store (see `src/testSupport/vueDom.mjs`, `src/ui/kit/*.test.mjs`
-  and `src/ui/views/intelHudView.test.mjs`). Run one such file with
-  `node --import=./build/registerVue.js --test <file>`. Don't pass happy-dom
-  nodes to `assert.equal`/`deepEqual`; compare them with `assertSameNode()`
-  from `src/testSupport/domAssert.mjs`.
-
-[docs/VUE-MIGRATION.md](docs/VUE-MIGRATION.md) records how each surface moved
-and what stays imperative, and why.
-
 ## Formatting and reusable components
 
 Run `npm run format` before submitting changes, then `npm run format:check`
@@ -247,9 +170,8 @@ template has a section for them.
    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 Audio, plus Utilities,
-   whose rows render in the separate UTILITIES panel). A layer that isn't
-   listed there falls under "Other layers". If none of the groups
+   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

DATA_SOURCES.md

@@ -5,7 +5,7 @@ God's Eye View's **code** is [MIT](LICENSE)-licensed. **The MIT grant covers the
 How to read this:
 
 - **The non-permissive datasets are carved out, not omitted.** Some bundled data (e.g. TeleGeography, CC BY-NC-SA) isn't MIT-compatible. Rather than hide it, we **bundle it with a clear license carve-out** so the app works out of the box — but it stays under the provider's terms.
-- **If your use doesn't fit a dataset's license, remove that dataset.** Most importantly: TeleGeography is **NonCommercial** — commercial users must delete it (or license it from TeleGeography). It's one self-contained folder. **EOX Sentinel-2 cloudless 2020** is also **NonCommercial** (CC BY-NC-SA 4.0): remove that basemap or obtain a commercial licence from EOX.
+- **If your use doesn't fit a dataset's license, remove that dataset.** Most importantly: TeleGeography is **NonCommercial** — commercial users must delete it (or license it from TeleGeography). It's one self-contained folder.
 - **Attribution is shown in-app** and listed here. Keep it intact. The required Google/Cesium credit renders on the on-globe credit line (bottom-left, `#cesium-credits`), and every per-layer credit below is registered into the expandable **"Data attribution"** lightbox on that line (`src/data/dataCredits.js` → `viewer.creditDisplay.addStaticCredit`). Both stay visible in clean-view and recording modes.
 - **Bundled model attribution lives beside the model files.** [`public/models/README.md`](public/models/README.md) records each shipped model's creator, source, license, and modification status.
 
@@ -33,7 +33,6 @@ How to read this:
 | **AISStream.io**                                                      | Live vessels (AIS)                                                                                                                  | Free, beta, no formal ToS; AIS is a public broadcast                                                                                                                                                                                                                                                                                                  | "AISStream.io" (courtesy)                                                                                                                   |
 | **CelesTrak**                                                         | Satellite TLEs (SGP4)                                                                                                               | US-government-origin data, no license; citation requested                                                                                                                                                                                                                                                                                             | "CelesTrak (celestrak.org), Dr. T.S. Kelso"                                                                                                 |
 | **The Space Devs — Launch Library 2 v2.3**                            | Recent launch, payload, stage, and recovery metadata for Space Missions (30d)                                                       | [The Space Devs terms of use](https://github.com/TheSpaceDevs/Tutorials/blob/main/faqs/faq_TSD.md#terms-of-use): data may be used and shared in any form; avoid forwarding it without added value; attribution is encouraged (not mandatory). [Official API limits](https://ll.thespacedevs.com/docs/): 15 unauthenticated calls/hour; optional token | "Launch Library 2 — The Space Devs" (courtesy attribution)                                                                                  |
-| **EOX Sentinel-2 cloudless 2020**                                     | Optional satellite basemap in Cesium and Navara. Navara uses daylight for terrain inspection.                                       | [EOX Maps](https://maps.eox.at/); [CC BY-NC-SA 4.0](https://cloudless.eox.at/license-non-commercial). Commercial use requires a commercial licence from EOX.                                                                                                                                                                                                                                                                     | [EOxCloudless](https://cloudless.eox.at/) by [EOX IT Services GmbH](https://eox.at/) (Contains modified Copernicus Sentinel data 2020)                                         |
 | **Esri World Imagery** (ArcGIS Online tile service)                   | The keyless satellite basemap — the default landing when no Google/ion credential is configured, and the "Esri Satellite" map stack | [Esri Master Agreement](https://www.esri.com/en-us/legal/terms/full-master-agreement): the public World Imagery service is usable in public-facing apps with attribution; no key is required for this classic endpoint, but Esri governs and can change access — an app at scale should review current ArcGIS Location Platform terms                 | "Powered by Esri — Source: Esri, Maxar, Earthstar Geographics, and the GIS User Community" (provider carries the service's own credit line) |
 | **USGS**                                                              | Earthquakes                                                                                                                         | U.S. public domain                                                                                                                                                                                                                                                                                                                                    | "Data courtesy of the U.S. Geological Survey"                                                                                               |
 | **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" |
@@ -41,9 +40,6 @@ How to read this:
 | **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)" |
-| **FAA Special Use Airspace** (`services6.arcgis.com` FeatureServer `Special_Use_Airspace`) | Prohibited & Restricted Airspace layer: US prohibited (P) and restricted (R) special-use airspace polygons (not the UAS Facility Map or UAS flight restrictions), altitude limits from the `*_VAL`/`*_UOM`/`*_CODE` fields, times of use, and controlling agency | U.S. public domain (FAA aeronautical data published through the [FAA AIS Open Data portal](https://adds-faa.opendata.arcgis.com/)); fetched keyless through `/api/drone-airspace` (1-hour server cache). Informational only — not a substitute for official UAS flight-planning tools | "Prohibited & restricted airspace: FAA Special Use Airspace" |
-| **iNaturalist API** (`api.inaturalist.org/v2/observations`, `/v1/grid/{z}/{x}/{y}.grid.json`) | Wildlife Sightings layer: verifiable wildlife observed within the last 48 h (whales 7 d), by observation time, in the current view, with taxon, observation time, quality grade and eligible photo | Per-record licences; observations default CC BY-NC. Photos CC0/BY/BY-SA/BY-NC/BY-NC-SA shown; ND and all-rights-reserved photos link-only. Keyless via `/api/inaturalist/observations` (5-min cache; global sample 10 min; stale ≤ 1 h; 60 requests/min and 8,000/day upstream caps). **NonCommercial content:** commercial redistributors must filter to CC0/BY/BY-SA or remove the layer. No AI training on this content | "Wildlife sightings: iNaturalist contributors (licences per record; photos credited on each card)" |
-| **Acartia** (`acartia.io/api/v1/sightings/current`) | Wildlife Sightings layer: Salish Sea marine mammal reports with validated species, observation time, reporting provider and trust flag; WHALES includes only the frozen cetacean list | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), each provider credited per sighting. Keyless via `/api/acartia/sightings` (10-min cache; stale ≤ 24 h). Positions rounded to 0.01° on the server; free-text comments excluded. Marine-conservation use; Be Whale Wise | "Wildlife sightings: Acartia (CC BY 4.0; each provider credited per sighting) · Be Whale Wise" |
 | **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 |
 | **TomTom Traffic API** (flow vector tiles)                            | Traffic roads and live congestion (optional, BYOK)                                                                     | [TomTom for Developers terms](https://docs.tomtom.com/legal/terms-and-conditions) (proprietary, your own key; free tier currently 200K tile requests/month — see [current pricing](https://docs.tomtom.com/pricing/))                                                                                                                                                       | "Traffic flow data © TomTom" — registered when live mode activates                                                                          |
@@ -73,7 +69,6 @@ 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"                                                                 |
-| **Houston TranStar** (`traffic.houstontranstar.org`, frames `www.houstontranstar.org`) | CCTV camera catalog + frames, Greater Houston | No licence. The [TranStar disclaimer](https://traffic.houstontranstar.org/disclaimer.aspx) (Content Usage) prohibits copying or distribution, and external framing or linking to specific images, without TxDOT's prior written permission. **Off by default**; enable only if you hold TxDOT's written permission | "Houston TranStar" (courtesy) |
 | **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)" |
@@ -101,11 +96,8 @@ How to read this:
 | **Barrie Transit** (myridebarrie.ca) | Transit layer live vehicles, Barrie ON | Barrie Transit realtime data, published by the City of Barrie under a licence accepted by use of the data. The licence is revocable and requires no attribution. | Courtesy credit to the City of Barrie (the licence requires none, and its trademark clause is broad) |
 | **YRT/Viva** (rtu.york.ca) | Transit layer live vehicles, York Region ON | York Region Transit realtime data, first-party York Region infrastructure under the YRT Open Data Licence v2.0, which permits commercial use and makes attribution optional. Viva route ids are named by colour from York Region’s published GTFS. | "Contains public transit Information made available under YRT’s Open Data Licence" — the licence’s own wording, given though not required |
 | **Burlington Transit** (opendata.burlington.ca) | Transit layer live vehicles, Burlington ON | Burlington Transit realtime data under the City of Burlington Open Data Terms of Use, which permit any lawful purpose. The terms are revocable and must travel with the data, so the credit links them. Route ids are internal keys and are joined to the City’s published GTFS. | Credit to the City of Burlington plus a link to its Open Data Terms of Use, which the licence requires |
-| **SMTR Rio de Janeiro** (dados.mobilidade.rio) | Transit layer live vehicles, Rio de Janeiro: municipal buses (SPPO) and the Mobi-Rio BRT, as two feeds | CC BY 4.0, stated on both data.rio catalog pages. Keyless GTFS-Realtime published by the Secretaria Municipal de Transportes, labelled beta, with a gateway limit of 5 requests a second and 60 a minute. Line names come from SMTR’s GTFS `routes.txt` (dados.mobilidade.rio/gtfs/schedule), under the same licence. | Attribution to SMTR / Prefeitura da Cidade do Rio de Janeiro under CC BY 4.0 |
 | **Radio Browser**                                                     | Geolocated internet-radio station directory and station-level tags                                                                  | Public-domain directory data under PDDL 1.0; individual broadcaster stream terms apply                                                                                                                                                                                                                                                                | "Radio Browser" plus a link to the selected broadcaster                                                                                     |
 | **Re:Earth Terrain** (Mapterhorn)                                     | Terrain (keyless globe stacks — OSM etc. — + `/api/terrain/heights` ellipsoidal-height lookups)                                     | Terrain mesh: CC BY 4.0; geoid: EGM2008 (NGA, public domain)                                                                                                                                                                                                                                                                                          | "Terrain (keyless globe stacks): Re:Earth Terrain / Mapterhorn (CC BY 4.0) / EGM2008 (NGA)"                                                 |
-| **OpenSeaMap** (`tiles.openseamap.org`) | Sea Marks layer: raster overlay of buoys, lighthouses and ports (#10) | Chart tiles CC BY-SA 2.0; data ODbL 1.0 via OpenStreetMap | "Sea marks © OpenSeaMap contributors (CC BY-SA 2.0) · Data © OpenStreetMap contributors (ODbL)" |
-| **OpenSnowMap** (`www.opensnowmap.org`) | Ski Pistes layer: raster overlay of ski runs and lifts (#10) | Tiles CC BY-SA; data ODbL 1.0 via OpenStreetMap; bulk tile download forbidden without prior agreement | "Ski pistes © www.opensnowmap.org (CC BY-SA) · Data © OpenStreetMap contributors (ODbL)" |
 | **OSRM on the FOSSGIS routing servers** (`routing.openstreetmap.de`) | Street-following routes for the Directions layer and voice route annotations, via `/api/route` | [FOSSGIS routing usage policy](https://routing.openstreetmap.de/about.html): "Display the required attribution and display a link to 'fix the map'", "Use a valid user agent and, if applicable, a correct referrer", "One request per second max", "No scraping, no heavy usage". The full policy is the German [FOSSGIS Nutzungsbedingungen](https://www.fossgis.de/arbeitsgruppen/osm-server/nutzungsbedingungen/); FOSSGIS also states that the server may be embedded in your own pages but "eine gewerbliche Nutzung ist nur mit Einschränkungen erlaubt" (commercial use only with restrictions). Route data derives from OpenStreetMap (ODbL 1.0) | "Routing: OSRM on the FOSSGIS servers" + a "fix the map" link — shown in the Data attribution popover |
 
 ### Local receiver input (not fetched from a service)
@@ -126,7 +118,6 @@ The optional Local ADS-B layer and the broadcast-FM receiver use radio you recei
 - **Freeway Bureau, MOTC (Taiwan).** National freeway cameras from the Freeway Bureau's keyless [CCTV static table](https://tisvcloud.freeway.gov.tw/history/motc20/CCTV.xml) in the MOTC 2.0 standard, refreshed daily and fetched at runtime (never bundled). Freeway Bureau traffic data is published under the [Open Government Data License, Taiwan (Version 1.0)](https://data.gov.tw/license), which permits reuse, including commercial reuse, with attribution; the app credits the Freeway Bureau, MOTC, names the dataset and links the licence, as its attribution exhibit asks. The table publishes each camera's MJPEG stream on one of four official camera servers (`cctvn`, `cctvn5`, `cctvc`, `cctvs` under `freeway.gov.tw`). The frame proxy relays single images, so each published stream URL is mapped to the same server's single-JPEG path for the same camera number (`/abs2mjpg/bmjpg` → `/abs2mjpg/jpg`, `/live-view/mjpg/video.cgi` → `/live-view/jpg/image.cgi`); only those exact HTTPS pairs are registered, and the still path is not itself listed in the table. These are on-demand snapshots, not continuous video. Camera headings are low-confidence estimates. No API key is required. The table host does not answer from some networks outside Taiwan (the camera servers do); there the pack is empty, logs one warning and retries hourly. On by default; `CCTV_TAIWAN_ENABLED=0` skips the pack, and `CCTV_TAIWAN_MAX_SOURCES` defaults to 600 (bounded to 1–2000).
 
 - **Google Maps Platform.** You supply your own API key and are bound by [Google's ToS](https://cloud.google.com/maps-platform/terms). Google Maps Content (tiles, geocodes, places) **may not be cached, stored, rehosted, or committed** — this app only ever uses it live, which is the compliant pattern. The "Google" attribution is displayed on the globe and must stay visible. Restrict your key (see [SECURITY.md](SECURITY.md)).
-- **Sea Marks and Ski Pistes (#10).** Two keyless raster overlay layers under Infrastructure, OpenSeaMap sea marks and OpenSnowMap ski pistes, requested tile by tile as the camera views them, with no prefetch, bulk download or caching on our side (OpenSnowMap forbids bulk tile download without prior agreement). They drape on the globe on the OSM and Bing stacks and on the Google Photorealistic tileset on Google 3D (see `src/maps/imageryHost.js`). OpenRailwayMap and OpenInfraMap, also requested in #10, are not included: OpenRailwayMap's tile server only answers requests whose Referer is its own site, and OpenInfraMap serves vector tiles that need a vector rendering pipeline.
 - **OpenSky Network.** Its license is **non-commercial**, and operational use of the REST API in a live product can require a prior written agreement with OpenSky — even for non-profit/government use. If you deploy this commercially, contact OpenSky for your own terms. The flights layer is a toggle and runs anonymously by default.
 - **adsb.lol flight fallback.** When OpenSky is unavailable and no last-good OpenSky response exists, the server requests a cached, capped 250 nm adsb.lol point snapshot around the current camera subpoint. This is regional observed context, not worldwide completeness; provenance is exposed in the Flights stats/context row. Military ICAOs remain reconciled through the existing dedicated military registry rather than duplicated.
 <a id="gnss-integrity"></a>
@@ -186,25 +177,16 @@ 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`.
-- **Houston TranStar cameras.** Keyless. The camera list is the public `traffic.houstontranstar.org/data/layers/cctvSnapshots_json.js` catalog (~1,000 cameras across Greater Houston); frames are stills at `www.houstontranstar.org/snapshots/cctv/<id>.jpg`, synthesized from a validated numeric id rather than taken from the payload, and only that host is registered. Cameras whose catalog id is `0` (a different, non-snapshot class) and cameras outside Greater Houston are dropped. TranStar's `dir` field is the side of the freeway the camera sits on, not the way it faces: TranStar's own map shows it as "Traffic closest to the camera is traveling …" (South → eastbound, North → westbound, West → southbound, East → northbound). That travel direction (90°, 270°, 180°, 0°) seeds the heading as a low-confidence prior with the low-confidence pose; `None` or an unknown value uses the shared id-hash fallback at low confidence. Headings are corrected with the in-app calibration gizmo. Off by default. TranStar's [Content Usage terms](https://traffic.houstontranstar.org/disclaimer.aspx) prohibit copying or distributing the site's information, and external framing or linking to specific images, without TxDOT's prior written permission; its FAQ grants permission-free use only for the RSS feeds. This project does not hold that permission for downstream installations, so the pack loads only when an operator who holds TxDOT's written permission sets `CCTV_HOUSTON_ENABLED=1`; with the flag unset, empty or any other value, the server makes no request to TranStar. Once enabled, it loads the 250 cameras nearest downtown, Uptown, the Medical Center, IAH and Galveston; `CCTV_HOUSTON_MAX_SOURCES` (8–400) changes the cap. Snapshots update about every 3 minutes, which is also the ambient still cadence. Frames are fetched from TranStar and relayed to the browser on demand, buffered only transiently per request, sent with `Cache-Control: no-store`, and not archived.
 - **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 eighteen registered feeds, covering seventeen 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, YRT and Rio’s SMTR 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 country coverage (optional).** Set `RADIO_PRIORITY_COUNTRIES=IN,PL` in the local `.env` and restart to include stations beyond the global click charts. The operator may choose up to eight unique ISO alpha-2 country codes; no key is needed. Each country adds one bounded query (at most 200 rows) and reserves up to 40 unique, usable stations inside the existing 750-station catalog. Country seeds precede specialist-tag seeds and global popularity fill; unused slots return to the shared pool. This is a coverage preference, not an exhaustive national directory or a guarantee of stations in every city. Countries with no eligible HTTPS MP3/AAC geolocated stations remain empty. An unset list preserves global selection. Country requests share the directory cache and three-worker pool; failed country queries are reported in coverage without blocking a healthy global refresh. Failed/degraded refreshes back off for one minute, with at most three mirrors per query.
-
-- **Radio Browser.** In every installation, including when `RADIO_PRIORITY_COUNTRIES` is unset, each request tries at most three mirror candidates (later fallback candidates are skipped), and failed or partial catalog refreshes back off for 60 seconds. A cold-start failure therefore continues returning 503 during that delay even if upstream recovers. `/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; broad/specialist responses whose rows all fail the product's health policy do not count as successful queries. Optional priority-country outcomes are advisory: valid, in-limit responses with no eligible stations succeed as empty results, while failed or malformed country queries report unsuccessful coverage without degrading the global catalog. A usable partial cold catalog is explicitly `DEGRADED`, and non-array or empty broad/specialist 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.
+- **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 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.
 - **OSRM on the FOSSGIS routing servers.** Keyless (no API key). Every route is requested by a person: clicking A and B in the Directions layer, or a voice "route from A to B". The server-side `/api/route` proxy sends an identifying `User-Agent`, pins the upstream host, accepts 2-12 coordinates, rejects any leg over 600 km or a total over 2,500 km, caps the buffered response at 8 MB, times the upstream out at 12 s, rate-limits per client, caches each route for 10 minutes, and coalesces identical requests that are in flight at the same time. Turn-by-turn maneuvers are asked for only when a caller wants them (`steps=1`), so the callers that do not read them send the smaller request. The "fix the map" link the policy asks for is in the Data attribution popover beside the OpenStreetMap credit.
-- **FAA Special Use Airspace.** Keyless. `/api/drone-airspace` queries the public FAA AIS FeatureServer for prohibited (P) and restricted (R) zones only — not MOAs, TFRs or other SUA types — with simplified geometry, a body cap, paging, a one-hour cache and stale-on-error. The layer is US coverage, informational only, and is not a substitute for B4UFLY, LAANC or a preflight briefing. Data is fetched at request time and never stored or redistributed. US government public domain; courtesy attribution is registered in the Data attribution popover.
-- **iNaturalist.** Keyless. `/api/inaturalist/observations` returns cached random view samples (newest first globally), at most 200 per request. Recency uses observation time: the v1 `d1` filter and a rolling 48 h cutoff (whales 7 d); date-only rows qualify when their day starts within the window. Observation caches last 5 min (global 10 min), with stale fallback ≤1 h. `/api/inaturalist/grid` supplies density counts, cached 15 min. Both share a paced queue capped at 60/min and 8,000/day; only request counters persist in `.gev-cache/`. The server caches projected records, never raw responses. Private records are excluded; obscured coordinates become 0.2° cells. Observer identity is retained only for photo attribution. Eligible photos load directly from `inaturalist-open-data.s3.amazonaws.com`, with creator credit on ambient cards and creator/licence on selection. Per-record licences and noncommercial restrictions apply as listed above. Attribution appears in the layer row and Data attribution popover. Coverage follows community observations, not a census; Acartia adds Salish Sea marine mammals.
-- **iNaturalist grid (cell schema risk).** `/api/inaturalist/grid` shares observation-date, taxa, quality, pacing and budget rules with observations. A strict 64×64 UTFGrid schema guard fails closed; only logical-cell keys, counts and coordinates survive projection. Raw tiles, observation identifiers and free text are not retained. Projected tiles use a 400-entry LRU, 15-minute freshness and at most one hour of stale fallback. Views request at most six tiles; cached and adjacent-zoom coverage publishes before network waits, independently of observation pages. Cells supply a noninteractive density glow ranked within the view, from teal to amber with mono/CRT support. Every sighting badge comes from a real observation at its public position. Counts describe observations, not a population census. The endpoint is documented in the v1 and v2 API docs as “Grid Tiles UTFGrid” (`/grid/{z}/{x}/{y}.grid.json`), but its per-cell records are not specified; schema drift disables grids until revalidated. See `docs/KNOWN-ISSUES.md`.
-- **Acartia.** Keyless. `/api/acartia/sightings` reads the current 7-day marine-mammal feed for ALL, MAMMALS and WHALES views intersecting 45.5–50.5° N, 126–121° W in the Salish Sea. WHALES accepts recognized cetaceans; other identified marine mammals appear under ALL/MAMMALS. The server rounds positions to 0.01° and drops comments before caching projected records (10 min fresh, stale ≤24 h); raw responses are not retained. Selected text cards credit the reporting provider under CC BY 4.0 and show Be Whale Wise guidance. `/sightings/current` answers without a key today, but Acartia's README asks API users to create an account and generate an API key on the [Acartia dashboard](https://acartia.io/) and to follow its [community guidelines](https://acartia.io/register). Attribution also appears in the layer row and Data attribution popover. Opportunistic sightings, not a census.
 - **Mapped installations.** OpenFreeMap military polygons use a bundled Overture/OSM name index; wide views show named points. Optional operator-configured Overpass and explicit Google Places searches keep their own source paths. Mapped data does not establish current activity or complete coverage.
-- **Place search.** Named-place fly-to uses Google Geocoding when a Maps key is configured, then Photon (`PHOTON_URL`; unset uses the public instance, empty disables it), then `/api/geocode` (Nominatim search) when neither answers. `/api/geocode` and the voice outline route `/api/geocode/outline` share one Nominatim queue (`NOMINATIM_URL`; unset, empty and invalid values disable it; an operator must explicitly select an authorized endpoint): one request at a time at least 1.1 s apart, an identifying `User-Agent` and `Referer`, a short queue that refuses a burst, a pause after 429/403/5xx answers (honouring `Retry-After` in full), at most one retry after a network failure, and a per-install daily cap on public-instance requests (`NOMINATIM_DAILY_CAP`, default 50). Processes using the same installation state file hold one lock through the actual fetch invocation and recording the next public start, with the daily slot persisted before invocation; restarts share that count, spacing and any pause. An unfinished dispatch marker fails closed until operator recovery; it is never automatically reclaimed. Public access fails closed if the state file cannot be read, locked, written or semantically validated. This coordination does not span independent installations or state directories and does not establish an application-wide public-service allowance or authorize public use. An operator-selected non-public endpoint is outside the public cap, spacing and durable-state requirement; an upstream cooldown is kept with the endpoint that returned it rather than leaking across operator URLs. Answers are cached on disk (outlines 90 days, places 30 days, no-results 24 hours); failures are not cached. Outlines are looked up only for an explicit ask, after bundled data and any configured Overpass, and only results whose type suits the ask are used. Administrative outline responses expose country/admin-1/admin-2 identity only when the selected Nominatim row has a recognized, unambiguous address type consistent with its own name; numeric rank, ambiguous types, missing fields and contradictory names do not manufacture identity. It is not used for systematic or bulk queries.
-- **Street and building outlines.** Voice street highlights, pointed-at buildings and grounds use the OpenFreeMap vector tiles the traffic layer already loads. Traffic and outlines share one bounded pending fetch/decode owner per immutable XYZ tile; materialized outline geometry is charged to the retained-byte ceiling and capped by coordinate count. Consumer result caches and request lifetimes remain independent, while eviction or explicit teardown cancels queued idle projections and releases their decoded owner. No Overpass request is made unless `OVERPASS_UPSTREAMS` is configured. Named grounds require a returned name matching the selected place, except that an ask whose head noun names a kind of grounds (a school, university or college, hospital, cemetery, stadium or zoo) may use the part of the smallest unnamed tile area of that class that holds the resolved place; a differently named area never answers. Other anonymous landcover polygons cannot establish identity, so unsupported grounds stay unavailable rather than borrowing a nearby POI name.
-- **Voice areas and place search.** Voice areas (`resolve_area`) use the same outline sources as voice outlines. Voice place search (`osm_query`, `/api/osm/features`) runs only on an operator-configured Overpass: a fixed list of kinds, a bounded box and result count, one query at a time, answers cached for a day. It never uses Nominatim.
+- **Place search.** Named-place fly-to uses Google Geocoding when a Maps key is configured, then Photon's public instance, then `/api/geocode` (Nominatim search) when neither answers. `/api/geocode` uses the shared Nominatim forward-search queue at no more than one request per second, sends an identifying `User-Agent` and `Referer`, caches answers for five minutes, shares one upstream call between identical searches already in flight, bounds the queue so a burst is refused rather than held, and drops a queued search whose caller has given up. It asks for one result per search and is not used for systematic or bulk queries.
 - **Cockpit regional briefing.** `/api/regional-brief` rounds aircraft coordinates into 0.1° cache cells, caches results for five minutes, and resolves physical regions from bundled public-domain Natural Earth polygons without reverse-geocoding requests. Google News RSS is queried with the resolved locality/region first; GDELT is used only when that RSS query fails or is empty. Google's published Google News terms restrict that source to personal, noncommercial use, so commercial deployments must disable/replace it or obtain separate permission; GDELT permits commercial dataset use with citation. The Data attribution popover identifies the active headline sources; article links retain publisher attribution. Headlines are location-query matches, not verified incidents, risk rankings, or evidence that a location is safe. Empty, partial, stale, and unavailable source states remain distinct. Open-Meteo supplies current conditions independently of the news source. `WX OFF` disables cockpit weather rendering only; the Local Info briefing still fetches its source-backed weather values and displays the required linked Open-Meteo credit.
 - **Dynamic weather presentation.** While cockpit mode is active, `/api/weather-effects` requests current Open-Meteo observations for the aircraft/camera location, rounds coordinates into 0.1° cache cells, caches results for five minutes, and may retain a stale observation for up to 30 minutes during a transient outage. WMO condition code selects the visual family; observed cloud cover, precipitation, visibility, wind speed, and wind direction bound its strength and motion. Missing or expired weather renders no synthetic atmospheric effect, and normal globe view never renders the weather overlay.
 
@@ -218,7 +200,7 @@ The [Bhote Koshi event pack](public/events/bhote-koshi-2026/README.md), under `p
 
 | Dataset                                                                     | Folder                            | License                                                                                                   | Commercial use?                                  | Attribution                                                                 |
 | --------------------------------------------------------------------------- | --------------------------------- | --------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------- |
-| **Datacenters** (4,352) | `datacenters/` | **ODbL 1.0** (OpenStreetMap extract) | ✅ (attribution + share-alike on data) | © OpenStreetMap contributors (shared credit) |
+| **Datacenters** (4,351) | `datacenters/` | **ODbL 1.0** (OpenStreetMap extract) | ✅ (attribution + share-alike on data) | © OpenStreetMap contributors (shared credit) |
 | **Dams** (704) | `dams/` | **ODbL 1.0** (OpenInfraMap / OSM extract) | ✅ (attribution + share-alike on data) | © OpenStreetMap contributors (shared credit) + Open Infrastructure Map |
 | **Military area names** (36,466) | `osm_military_names/` | **ODbL 1.0** (OpenStreetMap, via Overture Maps) | ✅ (attribution + share-alike on data) | © OpenStreetMap contributors (shared credit) + Overture Maps Foundation |
 | **TeleGeography Submarine Cable Map** (712 cables + 1,917 landing points)   | `telegeography_submarine_cables/` | **CC BY-NC-SA 3.0**                                                                                       | ❌ **NonCommercial — remove for commercial use** | "© TeleGeography — submarinecablemap.com"                                   |
@@ -226,12 +208,10 @@ 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)                      |
-| **US Census Bureau places** (32,629 city, town and CDP polygons)            | `us_census_places/`               | **Public domain**                                                                                         | ✅ (no restrictions)                             | "U.S. Census Bureau" (courtesy — not legally required)                      |
-| **Who's On First neighborhoods** (61,441 polygons)                          | `wof_neighborhoods/`              | Per source: CC BY, ODC-By, Open Government licences, CC0, PDDL, public domain (folder `ATTRIBUTION.md`)   | ✅ (attribution)                                 | "Neighborhood boundaries: Who's On First and contributors"; per-source credits in the folder |
 | **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 + v2.29.0 (20 camera-model records) | `src/layers/cctv/modelSpecs.js` | **CC0-1.0** (public domain dedication) | ✅ (no restrictions) | "Specs: cctv-database.com" (courtesy — not legally required) |
+| **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) |
 
 ### ⚠️ TeleGeography is bundled but NonCommercial
 
@@ -259,16 +239,13 @@ fixtures retain their provenance in `src/data/fixtures/README.md`.
 
 ### CCTV Camera Database (`src/layers/cctv/modelSpecs.js`)
 
-The CCTV layer's hardware-model specs are a small extract (v2.26.0, plus the Bosch MIC
-records from v2.29.0) of the
+The CCTV layer's hardware-model specs are a small verbatim extract (v2.26.0) of the
 [CCTV Camera Database](https://github.com/ch-bas/cctv-camera-database), an open dataset of
 camera models transcribed from manufacturer datasheets, dedicated to the public domain under
-**CC0-1.0**. Only records for hardware named by the integrated public catalogs (King County,
-Sarasota County and Sioux Falls) or by the City of Amsterdam register proposed in
-[#251](https://github.com/bilawalsidhu/gods-eye-view/pull/251) are bundled, compiled into the
-module. Nothing is fetched at runtime. The MIC records keep their specification fields; their
-titles are shortened to model codes and colour aliases are added. The records describe camera
-products (optics, resolution, night vision) only, never endpoints, stream paths or access data. CC0 requires no attribution; the CCTV HUD
+**CC0-1.0**. Only the records for hardware that the integrated public catalogs name (King
+County, Sarasota County and Sioux Falls) are bundled, compiled into the module. Nothing is
+fetched at runtime. The records describe camera products (optics, resolution, night vision)
+only, never endpoints, stream paths or access data. CC0 requires no attribution; the CCTV HUD
 credits it anyway as `SPECS: CCTV-DATABASE.COM` beside any spec line it renders.
 
 ### Bundled OpenStreetMap data
@@ -327,15 +304,6 @@ the retrieval date (2026-07-30), exact download URL, license evidence, and the
 deterministic transform (`scripts/build-sf-neighborhoods.mjs`: `nhood` → `name`, ~2 m
 Douglas-Peucker simplification, 6-decimal rounding).
 
-### Local CCTV source packs (`config/`)
-
-The server can read a local camera list from `CCTV_SOURCES_FILE` (default
-`config/cctv_sources.austin.json`, which ships empty) and inline JSON from
-`CCTV_SOURCES_JSON`; the two are merged, and inline entries win on a duplicate
-id. A non-empty local pack replaces the live open-data camera packs unless
-`CCTV_FORCE_AUSTIN=1` is set. The packs under `config/` show the schema, and a
-pack's cameras keep their own source's license and attribution.
-
 ---
 
 ## Weather sources

Dockerfile

@@ -4,7 +4,7 @@
 # proxies (ADS-B, AIS, Overpass, OpenAI Realtime, ...) as middleware, so there
 # is nothing else to containerise. See compose.yaml for the usual entry point.
 # Same Node as CI (package.json engines, .github/workflows), pinned by digest.
-FROM node:24.22.2-slim@sha256:c86ecead9e55a5210ac1727de38a4ca840bf03dcaf34dc9749addbf383b1920c
+FROM node:24.14.0-slim@sha256:d8e448a56fc63242f70026718378bd4b00f8c82e78d20eefb199224a4d8e33d8
 
 # Puppeteer is only used by the QA scripts; skip its ~150MB Chromium download.
 ENV PUPPETEER_SKIP_DOWNLOAD=1

README.md

@@ -2,6 +2,8 @@
 
 # 🌐 God's Eye View
 
+**Official site: [godseyeview.ai](https://godseyeview.ai)** · Official source: this repository · Hosted version coming soon
+
 [![CI](https://github.com/bilawalsidhu/gods-eye-view/actions/workflows/ci.yml/badge.svg?branch=main)](https://github.com/bilawalsidhu/gods-eye-view/actions/workflows/ci.yml) [![Reached #1 on GitHub Trending](https://img.shields.io/badge/%231_GitHub_Trending-thank_you!-F0A63C?style=flat-square&logo=github)](https://x.com/bilawalsidhu/status/2093798887815348521)
 
 ### A spy-satellite simulator in your browser — then you realize the sources are public and the data is real.
@@ -89,7 +91,7 @@ Start with the included data sources, then add your own. Each layer is a separat
 
 ## ⚡ Quick Start
 
-**Local setup needs no account or API keys.** The app opens with
+**Start without an account or API keys.** Both paths open the same app with
 Esri satellite imagery and keyless terrain. OSM is the fallback if Esri is
 unreachable. Flights, military traffic, satellites, earthquakes, public
 cameras, radio, and launches are available without keys.
@@ -129,9 +131,8 @@ hardware; it does not establish a minimum GPU requirement.
 
 ### Path 2 — Terminal / coding agent
 
-Use **Node.js 24.x (24.14.0 or later) or 26.x**; 24.22.1 or later (26.12.1 or
-later on 26) includes the October 21, 2026 security fixes, among them
-CVE-2026-111497. The setup doctor warns about Node 25, which is end-of-life.
+Use **Node.js 24.x (24.14.0 or later) or 26.x**. The setup doctor warns about
+Node 25, which is end-of-life.
 
 ```bash
 git clone https://github.com/bilawalsidhu/gods-eye-view.git
@@ -212,7 +213,7 @@ Keep the `env`: bash treats `UID` as read-only, so a plain `UID=1026` in front o
 
 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)). The map routes compare the browser's `Origin` with the `Host` the server sees, so the proxy must pass the original `Host` and, when it terminates TLS, `X-Forwarded-Proto`. Caddy does both by default; for nginx add `proxy_set_header Host $http_host;`, `proxy_set_header X-Forwarded-Proto $scheme;` and `proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;`. On an install outside Docker, that forwarding header also rate-limits the proxy's users apart from your own browser. Under the default Docker bridge network every client on the host, your browser included, reaches the container from its gateway address and shares one Overpass bucket.
+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>
 
@@ -234,48 +235,10 @@ the container.
 
 </details>
 
-### Path 4 — GitHub Codespaces (cloud, no local install)
-
-Codespaces requires a GitHub account. Overpass queries and OpenAI voice token
-requests return HTTP 403 through its forwarded HTTPS URL, even with API keys
-in `.env` and `GEV_ALLOWED_HOSTS` configured. Use a local setup for these features.
-
-The codespace runs the dev server in a cloud workspace, so Node and the dependencies
-never touch your machine. The globe still renders in your own browser, so it
-needs the same graphics there as any other path. GitHub Free includes 120
-core-hours a month with no card on file — about 60 hours on the default 2-core
-machine. Org and Enterprise plans include no free quota; current terms and
-quotas apply.
-
-1. Fork this repository, then open **your fork** on GitHub.
-2. Click the green **Code** button, the **Codespaces** tab, then **Create codespace on main**.
-3. In the codespace terminal:
-   ```bash
-   nvm install 24 && nvm use 24
-   npm ci
-   npm run doctor
-   GEV_ALLOWED_HOSTS="$CODESPACE_NAME-4173.$GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN" npm run dev
-   ```
-4. Open the **Ports** tab, find `4173`, and click the globe icon to open it in
-   the browser. The port is private by default, so the URL asks for your GitHub
-   login. Keep it private: a public port lets anyone use the app and the keys
-   in your `.env`.
-
-`GEV_ALLOWED_HOSTS` there is required, not optional. The dev server answers only
-the hostnames it trusts, and a forwarded port arrives on
-`$CODESPACE_NAME-4173.$GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN`. Without it the
-page is `Blocked request. This host is not allowed.` Leading-dot wildcards are
-ignored on purpose, so pass that exact name.
-
-⚠️ **A codespace is reachable from the internet.** Treat it as the
-wider-publish case in [Sharing an instance](#-sharing-an-instance). Provider
-Settings is unavailable on the forwarded URL. Never commit your workspace
-`.env`. [SECURITY.md](SECURITY.md) has the threat model.
-
 ### Then power it up — in the app, not in a file
 
-For a local setup, keys are upgrades, not prerequisites. When you want one,
-click the **POWER UP** chip in the bottom-right corner: Provider Settings lists every supported key,
+Keys are upgrades, not prerequisites. When you want one, click the **POWER UP**
+chip in the bottom-right corner: Provider Settings lists every supported key,
 what it switches on, and where to get it. Paste, hit **SAVE KEYS**, and the app
 restarts itself with the new capability on. Once everything is configured the
 chip reads **POWERED UP** — and if a compact layout hides it, `?setup=1`
@@ -340,8 +303,6 @@ Choose a first-run mission, or try these in order. The GIFs show Google Photorea
 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."_
 
-Open **Visual Presets → Globe Engine** to switch between Cesium and experimental Navara. The globe switches in place at the current view and remembers your choice. A link with `?engine=cesium` or `?engine=navara` overrides the saved choice. A fresh visit starts with Cesium.
-
 **Keyboard:** `1`–`6` visual styles · `H` HUD · `D` detection · `C` cockpit · `` ` `` frame rate · `Esc` out. Trackpad pinch zooms the globe.
 
 ---
@@ -364,11 +325,9 @@ _Why cockpit mode exists: you're riding a real aircraft over real terrain — an
 
 ## 🎙️ Talk to It
 
-The standalone app offers **OpenAI** and **Gemini** under **AI Provider** in Settings, one choice shared by voice and chat. OpenAI is the initial default; your choice is saved in this browser. To use Gemini, add `GEMINI_API_KEY` in Provider Settings or your local `.env` file, then select Gemini. `GEMINI_LIVE_MODEL` defaults to `gemini-3.8-live`. The permanent key stays on the local server, which issues a constrained, single-use session credential.
+The standalone app offers **OpenAI** and **Gemini** in the GEV MIC provider chooser. OpenAI is the initial default; your choice is saved in this browser. To use Gemini, add `GEMINI_API_KEY` in Provider Settings or your local `.env` file, then select Gemini. `GEMINI_LIVE_MODEL` defaults to `gemini-3.8-live`. The permanent key stays on the local server, which issues a constrained, single-use session credential.
 
-Changing provider ends the current conversation. If voice is on, the new provider starts with the same open-mic or push-to-talk mode; a held Space key is not carried over. Gemini uses the same map actions and captions, but has no OpenAI cost meter or MINI tier. When Gemini reports that its session has expired, start voice again for a new conversation. The AI Provider setting does not change the OpenAI-backed AI HUD summary.
-
-Next to the mic, **CHAT** opens a typed chat with silent replies. It uses the selected provider and the same map actions, and never asks for the microphone. OpenAI chat needs an API key (`OPENAI_CHAT_MODEL`), so it is off while `GEV_PREFER_CODEX_OAUTH` pins OpenAI to ChatGPT OAuth; Gemini chat uses a separate text model (`GEMINI_CHAT_MODEL`). Chat and voice panels share the left panels' glass surface and sit above the dock or dock to the right.
+Changing provider ends the current conversation. If voice is on, the new provider starts with the same open-mic or push-to-talk mode; a held Space key is not carried over. Gemini uses the same map actions and captions, but has no OpenAI cost meter or MINI tier. When Gemini reports that its session has expired, start voice again for a new conversation. The provider chooser does not change the OpenAI-backed AI HUD summary.
 
 > Voice can use an **OpenAI API key** or, on the same machine, an opt-in signed-in **ChatGPT/Codex OAuth** session. The API-key path remains the default. Selecting ChatGPT OAuth in Provider Settings reuses an existing local sign-in or starts the Codex browser sign-in flow and selects OAuth when it completes. The OpenAI key still drives the **AI HUD summary**: a terse, five-word intelligence-style readout of the current view that regenerates as you move.
 
@@ -400,7 +359,7 @@ camera input stops rotation.
 
 > 🗣️ _"Outline the state of Texas."_ · _"Annotate the Texas State Capitol and its grounds"_ — it draws the **actual enclosing boundary**, not a circle. · _"How far is the Eiffel Tower from the Louvre?"_ — a connector arrow appears and it speaks the distance. Everything persists until you say _"clear the map."_
 
-**✍️ Or draw it yourself** — UTILITIES ▸ **Draw**: pick Area, Line or Pin and a colour, click the vertices on the real world, double-click to finish, then name, recolour, hide or fly to each shape from its row. Same whiteboard, same persistence, no microphone needed.
+**✍️ Or draw it yourself** — DISPLAY ▸ **Draw**: pick Area, Line or Pin, click the vertices on the real world, double-click to finish, label it. Same whiteboard, same persistence, no microphone needed.
 
 ![Zilker Park and Lady Bird Lake drawing onto the 3D city as persistent vector annotations, by voice](docs/media/01-voice-annotate-zilker.gif)
 
@@ -428,7 +387,7 @@ _Ask for radio near anywhere and the globe starts broadcasting — every station
 
 ## 🛰️ What's on the Globe
 
-Twenty-two layers and map sources. **Twenty have a keyless path.** Some offer additional capabilities with a provider key. (🟢 no key · 🟡 free key · 🔴 metered.)
+Twenty layers and map sources. **Eighteen have a keyless path.** Some offer additional capabilities with a provider key. (🟢 no key · 🟡 free key · 🔴 metered.)
 
 | Layer                       | What you get                                                                                                                                                                                                                                                                                                                                                                        | Source                                  | Auth                                                                                                |
 | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | --------------------------------------------------------------------------------------------------- |
@@ -442,26 +401,23 @@ Twenty-two layers and map sources. **Twenty have a keyless path.** Some offer ad
 | 🌍 **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) · 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), opt-in Florida (FL511, individual personal use only; other use needs FDOT's written consent) and opt-in Houston (TranStar, enable only with TxDOT's written permission per TranStar's Content Usage terms). 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            | 🟢                                                                                                  |
-| 🚌 **Transit**              | Live buses, trams, metros, trains and ferries with delayed playback between reports, selected-vehicle trails, and mode-coloured DETECT labels — Boston, Austin, Minneapolis, Helsinki, the Netherlands, Norway, South East Queensland, Rio de Janeiro (buses and BRT), and nine in Ontario: Toronto (surface vehicles; the subway publishes no positions), Mississauga, Hamilton, Durham Region, York Region, Guelph, Burlington, Barrie and Kingston                                                                                                                                               | Operator GTFS-Realtime feeds            | 🟢                                                                                                  |
+| 🚌 **Transit**              | Live buses, trams, metros, trains and ferries with delayed playback between reports, selected-vehicle trails, and mode-coloured DETECT labels — Boston, Austin, Minneapolis, Helsinki, the Netherlands, Norway, South East Queensland, and nine in Ontario: Toronto (surface vehicles; the subway publishes no positions), Mississauga, Hamilton, Durham Region, York Region, Guelph, Burlington, Barrie and Kingston                                                                                                                                               | Operator GTFS-Realtime feeds            | 🟢                                                                                                  |
 | 🚲 **Bikeshare**            | Live station availability                                                                                                                                                                                                                                                                                                                                                           | GBFS                                    | 🟢                                                                                                  |
 | 🧭 **Directions**           | Click A and B on the globe for a street-following drive, walk or cycle route draped on the terrain with turn-by-turn steps — then FLY the camera along it. No key, no geocoder, no mic                                                                                                                                                                                              | OSRM on FOSSGIS servers (OpenStreetMap) | 🟢                                                                                                  |
-| ⌖ **OSM Places**           | Voice place search ("hospitals in Kathmandu") from OpenStreetMap, drawn as numbered points that follow-up questions can filter. Needs your own Overpass server (`OVERPASS_UPSTREAMS`); off otherwise                                                                                                                                                                                                                                                                                                                               |
 | 🔥 **Active Fires**         | Live NASA FIRMS detections, trailing 24h                                                                                                                                                                                                                                                                                                                                            | NASA FIRMS                              | 🟡                                                                                                  |
 | 🚀 **Space Missions**       | Rolling 30-day launches with payload, stage, and recovery detail                                                                                                                                                                                                                                                                                                                    | Launch Library 2                        | 🟢 (🔴 optional paid token raises the allowance)                                                         |
 | 🎖️ **Mapped Installations** | Viewport-bounded military-site context from community mapping — incomplete by nature, and labeled that way                                                                                                                                                                                                                                                                          | OpenStreetMap                           | 🟢                                                                                                  |
-| 🚫 **Prohibited & Restricted Airspace** | FAA prohibited (P) and restricted (R) special-use airspace as ground polygons, with name, altitude range and times of use on select. Not the UAS Facility Map or UAS flight restrictions; informational only, not for flight planning | FAA SUA                                 | 🟢                                                                                                  |
-| 🦉 **Wildlife Sightings** | Wildlife observed within 48 h (whales 7 d): density glow, taxon badges and anchored photo cards with creator/licence credit. Salish Sea marine mammals via Acartia; sensitive locations shown as 0.2° cells. Not a census | iNaturalist, Acartia | 🟢 |
 | 🌬️ **Wind**                 | Animated 10 m forecast wind with an optional speed, temperature or pressure color field and a reading at map center                                                                                                                                                                                                                                                                 | NOAA GFS / ECMWF IFS                    | 🟢                                                                                                  |
 | 🌦️ **Observed Weather**     | Rain radar (contiguous US), Satellite clouds (GOES regional or global infrared, Clouds only or Full image) and Lightning density (Americas and Pacific) on one history timeline                                                                                                                                                                                                     | NOAA nowCOAST                           | 🟢                                                                                                  |
 | 🌀 **Cyclones**             | Advisory positions, forecast tracks and uncertainty cones for the Atlantic and eastern/central North Pacific                                                                                                                                                                                                                                                                        | NOAA NHC / CPHC                         | 🟢                                                                                                  |
 
 **Weather, keyless.** **Wind** animates 10 m forecast flow from NOAA GFS or ECMWF IFS, with an optional color field and a reading at map center. **Rain radar**, **Satellite clouds** and **Lightning density** are observations on one history timeline in the **WEATHER** panel (step back, **Play**, **Latest**); **Cyclone advisories** draw NHC and CPHC positions, forecast tracks and cones. On Google 3D Tiles the observed layers float above the city as translucent shells, sharpened around your view.
 
-In the app, **Data Layers** groups them as Movement, Cameras, Infrastructure, Events, Weather and Audio; Directions and OSM Places sit in the separate **Utilities** panel with Draw and Import.
+In the app, **Data Layers** groups them as Movement, Cameras, Infrastructure, Events, Weather and Utilities.
 
 **The basemap ladder — what each tier buys you:**
 
@@ -475,7 +431,7 @@ In the app, **Data Layers** groups them as Movement, Cameras, Infrastructure, Ev
 
 _The Space Missions layer replaying a Falcon 9 ascent — labeled `RECONSTRUCTED ESTIMATE`, scrubbable 0.25×–4×._
 
-**Also on the globe:** neighborhood overlays · an optional cockpit WX cloud effect. **Bundled static infrastructure:** Datacenters (4,352), Dams (704), and Submarine Cables (712).
+**Also on the globe:** neighborhood overlays · an optional cockpit WX cloud effect. **Bundled static infrastructure:** Datacenters (4,351), Dams (704), and Submarine Cables (712).
 
 ![Diving into the Bahamas and revealing labeled submarine cable routes beneath the globe](docs/media/09-undersea-cables.gif)
 
@@ -487,9 +443,9 @@ _The Space Missions layer replaying a Falcon 9 ascent — labeled `RECONSTRUCTED
 
 > Street-level photos from any provider in one panel. This build ships **Mapillary** (a free client token), **Google Street View** (your Google Maps key), **KartaView** and **Panoramax** (no key).
 
-**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 Street Level starts on **KartaView** instead, and the Mapillary chip says which key to add. **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.
+**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 when its token is set; otherwise KartaView is. 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.
+**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`.
 
@@ -537,12 +493,12 @@ How the globe handles live data:
 - **Sits on the real ground.** Entity heights are aligned to work with Google 3D tiles, so aircraft park on aprons and cameras stand on street corners instead of floating.
 - **Caching and request budgets.** An OpenSky credit governor, a TomTom daily tile budget, and disk-cached TLEs reduce repeated requests. These controls do not replace provider quotas or billing controls.
 - **Server-side credentials.** Every API that touches a private key (OpenAI, AISStream, OpenSky OAuth, camera frames) is brokered through a hardened server-side proxy with SSRF protection, response caps, and sanitized errors. The only keys the browser sees are Google Maps and Cesium ion (restrict both at the provider).
-- **A small stack.** **Vue 3** and **Pinia** for the interface, **CesiumJS** for the globe and **Vite** to build it — plus **Google Photorealistic 3D Tiles** for the planet and the **OpenAI Realtime API** for voice. Fast to read, fast to hack on.
+- **No framework.** Vanilla JavaScript, **CesiumJS**, and **Vite** — plus **Google Photorealistic 3D Tiles** for the planet and the **OpenAI Realtime API** for voice. Fast to read, fast to hack on.
 
 ```
 src/
 ├── main.js                 # Bootstrap: Google 3D tiles, layer registration
-├── ui/                     # Runtime UI — Vue views, Pinia stores, kit, controllers, styles
+├── 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
@@ -727,7 +683,7 @@ One heads-up from the inside: build in this space for a week and you learn that
 
 <div align="center">
 
-▶️ [Watch the God's Eye View series](https://youtube.com/playlist?list=PL6qSg2I-7_koPbDnSMo0QeeHX_RknA2uv&si=nBGYMoHWQw41v93Q) · 📬 [Map the World](https://maptheworld.ai/) — the newsletter behind the project
+🌐 [godseyeview.ai](https://godseyeview.ai), the official site · ▶️ [Watch the God's Eye View series](https://youtube.com/playlist?list=PL6qSg2I-7_koPbDnSMo0QeeHX_RknA2uv&si=nBGYMoHWQw41v93Q) · 📬 [Map the World](https://maptheworld.ai/) — the newsletter behind the project
 
 **🌐 God's Eye View. No place left behind.**
 

SECURITY.md

@@ -74,19 +74,17 @@ 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.
-- **Voice place search runs only on the operator's Overpass.** `/api/osm/features` answers only when `OVERPASS_UPSTREAMS` is set and never falls back to a public instance. The client sends a curated preset id, a box, a mode and a limit; the server writes and quotes the Overpass query itself, so no client or model text reaches it. Boxes are capped (36 deg² for a count, 4 deg² for a listing), as are the feature limit, the Overpass timeout and memory, and the response bytes read. Each client (IPv6 clients keyed by /64, as on `/api/overpass`) runs one search at a time and two run at once in all, under a per-client rate limit (12/min) and a global one (30/min); a search gets 22 s across every configured endpoint in turn (Overpass itself is told 20 s), which ends before the voice answer stops waiting at 25 s. The route sits behind the cross-site gate below. Answers are cached in memory and on disk (`.gev-cache/osm-features/`, at most 400 entries and 256 MB, kept a day), keyed to the configured instance so a repointed `OVERPASS_UPSTREAMS` never serves the old one's answers; a malformed answer is never cached.
 - **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 map routes (`/api/terrain/heights`, `/api/drone-airspace`, `/api/inaturalist/observations`, `/api/acartia/sightings`, `/api/overpass` and voice place search's `/api/osm/features`, which spends the same operator Overpass) use the same cross-site checks, minus the forwarding-header refusal: they guard only per-client quotas and caches, not a key or a bill, and the map and voice need them to work behind a reverse proxy. `/api/overpass` also admits at most 300 POSTs a minute per peer (IPv6 peers keyed by /64) and 900 a minute across all remote peers before it reads a body. A direct loopback request — a loopback socket with none of the forwarding headers `hasProxySignals` checks (`Forwarded`, `Via`, `X-Forwarded-For`, `X-Forwarded-Host`, `X-Forwarded-Port`, `X-Forwarded-Proto`, `X-Real-IP`, `CF-Connecting-IP`, `CF-Ray`) — draws on its own per-peer admission window, so remote peers cannot exhaust the owner's admission. A reverse proxy on the same machine must add at least one of those headers (Caddy and Cloudflare do by default; nginx needs `proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;`, plus `proxy_set_header Host $http_host;` and `proxy_set_header X-Forwarded-Proto $scheme;` so the `Origin` check matches), or its traffic is indistinguishable from the owner's and shares the owner's window. With one, its requests are then counted as remote, in one bucket per proxy socket — the forwarded client address is never trusted as identity — so all users behind one proxy share 300/min. The isolation needs a loopback socket: under the default Docker bridge network every host-side client, the owner included, arrives from the container gateway and is one remote peer. **Limit:** this isolates admission only. The upstream budget (90 requests/min per client key, 300/min across all clients) is shared, so once remote traffic has used the global upstream budget, an owner request that misses the cache can still get `429`, or `503` when remote misses hold every upstream concurrency slot; cache hits are unaffected. 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.
+- **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.
 - **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, 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.
-- **Typed chat spends the provider keys.** `/api/openai/chat` and `/api/gemini/chat` send the conversation to OpenAI Chat Completions or Gemini `generateContent` with the server's `OPENAI_API_KEY` or `GEMINI_API_KEY`. They require a same-site `Origin` (the Gemini request check), cap request bodies at 512 KB, refuse upstream redirects, cut the upstream call off after 60 s and return only sanitized errors. OpenAI chat can only bill `OPENAI_API_KEY`, so while `GEV_PREFER_CODEX_OAUTH` pins OpenAI to ChatGPT OAuth it refuses with `503` (`CODEX_OAUTH_REQUIRED`) rather than spend the key. After the provider refuses the key or account (a `401`, a `403`, Gemini's `400` `API_KEY_INVALID` or OpenAI's `429` `insufficient_quota`), a route stops sending that key upstream for a minute, or until the key changes.
 - **ChatGPT OAuth voice reuses the local Codex sign-in.** `/api/realtime/oauth-status`, `/api/realtime/oauth-login` and `/api/realtime/token?auth=oauth` answer only loopback connections, behind the same cross-site gate as the token endpoint; the login route also refuses a foreign `Origin`. None of them returns the access token. The login route runs `codex login` (or the executable named by `CODEX_BIN`) with an allowlisted environment that leaves out GEV's provider keys, keeps one attempt pending at a time and cancels it after two minutes or when the server stops. **Limits:** any program on this machine that can reach the server can mint Realtime sessions on the signed-in ChatGPT account, as it can with the API key; a local reverse proxy that hides the client's address defeats the loopback check; and OpenAI has not documented this use of Codex credentials for Realtime, so it may stop working or fall outside the account's terms.
 
 ## Network exposure — the operator threat model
@@ -95,7 +93,7 @@ The dev server is a **key broker**: every server-side key above is spendable by
 
 - **Local-only by default.** `./scripts/dev-fresh.sh` (and the Vite config itself) bind to `localhost`, so only your machine can reach the server — and only local names are accepted (`allowedHosts` stays restricted, which also blunts DNS-rebinding tricks). Binding to all interfaces keeps that restriction: IP addresses and `localhost` work, and LAN hostnames must be listed in `GEV_ALLOWED_HOSTS` (for example `GEV_ALLOWED_HOSTS=globe.lan`); suffix and wildcard entries are ignored.
 - **LAN exposure is an explicit opt-in**: `HOST=0.0.0.0 ./scripts/dev-fresh.sh`. The launcher prints a prominent warning plus your LAN URL. Understand what opting in means: **every device on that network can drive the proxies and spend your OpenAI / Google / OpenSky / AISStream / TomTom / FIRMS quota** for as long as the server runs. Do this only on networks you trust.
-- **App-level throttles (on by default):** `GEV_RATELIMIT_OPENAI_PER_MIN` (default `30`) and `GEV_RATELIMIT_GOOGLE_PER_MIN` (default `120`) — the values the Pinokio build already ships — cap the cost-bearing endpoints per client IP per minute (over-limit requests receive a sanitized `429`). Typed chat keeps its own per-IP window, set by `GEV_RATELIMIT_OPENAI_CHAT_PER_MIN` and `GEV_RATELIMIT_GEMINI_CHAT_PER_MIN`; left unset, each takes its provider's resolved cap (`GEV_RATELIMIT_OPENAI_PER_MIN`, or `GEV_RATELIMIT_GEMINI_PER_MIN`, default `30`), so lowering a provider throttle lowers chat too, while an explicit chat value, including `0`, wins. Both defaults sit well above what the app itself generates; set either to exactly `0` to run unthrottled. They are **per-IP, process-local, in-memory guards** — they reset on restart, a caller with several addresses gets a bucket per address, and they are **not billing caps**.
+- **App-level throttles (on by default):** `GEV_RATELIMIT_OPENAI_PER_MIN` (default `30`) and `GEV_RATELIMIT_GOOGLE_PER_MIN` (default `120`) — the values the Pinokio build already ships — cap the cost-bearing endpoints per client IP per minute (over-limit requests receive a sanitized `429`). Both defaults sit well above what the app itself generates; set either to exactly `0` to run unthrottled. They are **per-IP, process-local, in-memory guards** — they reset on restart, a caller with several addresses gets a bucket per address, and they are **not billing caps**.
 - **Docker trusts one address, and only because the port is on loopback.**
   Docker delivers the host's own browser to the container from the container
   network's gateway, never from `127.0.0.1`, so a loopback-only Provider

THIRD_PARTY_NOTICES.md

@@ -2,8 +2,8 @@
 
 The project depends on third-party npm packages whose own licenses apply. This
 file records the packages added for the browser-local SDR feature and the
-Street Level viewer, and the CesiumJS code ported into `src/geo/`; the complete
-resolved dependency inventory remains in `package-lock.json`.
+Street Level viewer; the complete resolved dependency inventory remains in
+`package-lock.json`.
 
 ## Web RTL-SDR
 
@@ -45,23 +45,3 @@ resolved dependency inventory remains in `package-lock.json`.
 - Source: <https://github.com/mrdoob/three.js>
 - License: MIT
 - License text: <https://github.com/mrdoob/three.js/blob/dev/LICENSE>
-
-## CesiumJS (portions ported to src/geo)
-
-- Package: `cesium` 1.138.0 (`@cesium/engine` 22.3.0); the files in `src/geo/`
-  are adapted from `@cesium/engine/Source/Core` (`Math.js`, `Ellipsoid.js`,
-  `scaleToGeodeticSurface.js`, `Cartographic.js`, `Cartesian2.js`,
-  `Cartesian3.js`, `Matrix3.js`, `Matrix4.js`, `Quaternion.js`,
-  `Transforms.js`, `BoundingSphere.js`, `EllipsoidGeodesic.js`, `JulianDate.js`,
-  `Simon1994PlanetaryPositions.js`) and say so in their first
-  line. The changes: the classes' static functions became module functions,
-  vectors, geodetic positions and quaternions became plain-data instances of
-  module-private constructors (own enumerable fields only, no methods),
-  matrices plain arrays, and the ellipsoid a frozen object; the debug
-  argument checks were left out, as in Cesium's release build; only the subset
-  gev uses was kept.
-- Author: Copyright 2011-2024 CesiumJS Contributors
-- Source: <https://github.com/CesiumGS/cesium>
-- License: Apache License 2.0
-- License text: `node_modules/@cesium/engine/LICENSE.md` (shipped with the
-  dependency) and <https://www.apache.org/licenses/LICENSE-2.0>

build/application-html.js

@@ -0,0 +1,40 @@
+import { readFileSync } from 'node:fs';
+
+export const APPLICATION_TEMPLATES = Object.freeze([
+  'scene-chrome',
+  'cockpit',
+  'display-controls',
+  'command-dock',
+  'layer-panels',
+  'context',
+  'welcome',
+  'provider-settings',
+  'hud-loading',
+]);
+const allowed = new Set(APPLICATION_TEMPLATES);
+
+/** Expand only known component templates; markers cannot name filesystem paths. */
+export function expandApplicationHtml(html) {
+  return html.replace(
+    /^[ \t]*<!-- gev:template ([^\s]+) -->\r?\n?/gm,
+    (_, name) => {
+      if (!allowed.has(name))
+        throw new Error(`Unknown application template: ${name}`);
+      return readFileSync(
+        new URL(`../src/ui/templates/${name}.html`, import.meta.url),
+        'utf8',
+      );
+    },
+  );
+}
+
+/** Assemble static application markup before Vite processes scripts and assets. */
+export function applicationHtmlPlugin() {
+  return {
+    name: 'application-component-templates',
+    transformIndexHtml: {
+      order: 'pre',
+      handler: expandApplicationHtml,
+    },
+  };
+}

build/initialChunkGuard.js

@@ -1,58 +0,0 @@
-// Build guard: the Cesium-mode page must not load three or Navara. The
-// initial chunks are every entry chunk and what it imports statically;
-// navaraMode.js reaches Navara only through import(), so three and
-// @navaramap/* belong to lazy chunks. This checks the bundle's module ids
-// (what Rollup put in each chunk), and fails the build otherwise.
-
-/**
- * Module ids that only the Navara engine may load, when no package list is
- * given (the browser build passes the full dependency closure,
- * navaraDependencies.js).
- */
-export const ENGINE_ONLY_MODULES =
-  /[\\/]node_modules[\\/](?:three|@navaramap[\\/][^\\/]+|postprocessing)[\\/]/;
-
-/**
- * Engine-only modules in initial chunks of a Rollup bundle, sorted by chunk.
- * @param {Record<string, { type: string, isEntry?: boolean, imports?: string[], moduleIds?: string[] }>} bundle
- * @returns {{ chunk: string, module: string }[]}
- */
-export function initialChunkViolations(bundle, pattern = ENGINE_ONLY_MODULES) {
-  const initial = new Set();
-  const visit = (fileName) => {
-    const chunk = bundle[fileName];
-    if (!chunk || chunk.type !== 'chunk' || initial.has(fileName)) return;
-    initial.add(fileName);
-    for (const imported of chunk.imports ?? []) visit(imported);
-  };
-  for (const [fileName, chunk] of Object.entries(bundle))
-    if (chunk.type === 'chunk' && chunk.isEntry) visit(fileName);
-  const violations = [];
-  for (const fileName of [...initial].sort())
-    for (const module of bundle[fileName].moduleIds ?? [])
-      if (pattern.test(module)) violations.push({ chunk: fileName, module });
-  return violations;
-}
-
-/** The Rollup plugin: fails generateBundle when an initial chunk holds three or Navara. */
-export function initialChunkGuard({
-  log = console.log,
-  pattern = ENGINE_ONLY_MODULES,
-} = {}) {
-  return {
-    name: 'gev-initial-chunk-guard',
-    generateBundle(_options, bundle) {
-      const violations = initialChunkViolations(bundle, pattern);
-      if (violations.length) {
-        this.error(
-          'Navara-only modules in the Cesium-mode initial chunks:\n' +
-            violations
-              .map(({ chunk, module }) => `  ${chunk}: ${module}`)
-              .join('\n'),
-        );
-        return;
-      }
-      log('[initial-chunks] no Navara-only modules in the initial chunks');
-    },
-  };
-}

build/navaraAssets.js

@@ -1,65 +0,0 @@
-import { existsSync, readdirSync, readFileSync } from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-/** Where @navaramap/three keeps its prebuilt worker assets, or null. */
-function defaultAssetsDir() {
-  try {
-    const entry = fileURLToPath(import.meta.resolve('@navaramap/three'));
-    return path.join(path.dirname(entry), 'assets');
-  } catch {
-    return null;
-  }
-}
-
-/**
- * Navara's prebuilt workers (@navaramap/three/dist/assets) load their wasm by
- * file name next to themselves (`new URL('x-hash.wasm', self.location)`), a
- * reference the bundler cannot see. When a build includes Navara (the
- * ?engine=navara chunk), copy every such wasm the bundle lacks into
- * `assets/` under its own name. A build without Navara gets none.
- * @param {{ assetsDir?: string | null }} [options]
- */
-export function navaraWorkerAssets({ assetsDir } = {}) {
-  return {
-    name: 'navara-worker-assets',
-    generateBundle(_options, bundle) {
-      const usesNavara = Object.values(bundle).some(
-        (file) => file.type === 'chunk' && file.code.includes('navara_wasm'),
-      );
-      if (!usesNavara) return;
-      const dir = assetsDir === undefined ? defaultAssetsDir() : assetsDir;
-      if (!dir || !existsSync(dir)) return;
-      for (const name of readdirSync(dir).sort()) {
-        if (!name.endsWith('.wasm')) continue;
-        const fileName = `assets/${name}`;
-        if (bundle[fileName]) continue;
-        this.emitFile({
-          type: 'asset',
-          fileName,
-          source: readFileSync(path.join(dir, name)),
-        });
-      }
-    },
-  };
-}
-
-const NAVARA_MODULE = /\/src\/globe\/navara\//;
-
-/**
- * Rollup chunkFileNames: the lazy chunk holding the Navara engine
- * (src/globe/navara, with the Navara packages it pulls in) is named
- * `navara-engine-[hash].js`; every other chunk keeps Vite's default name.
- * Naming only (not manualChunks, which would pull modules shared with the
- * Cesium entry into the Navara chunk), so the chunking is unchanged.
- * @param {{ isEntry?: boolean, moduleIds?: string[] }} chunk
- * @returns {string}
- */
-export function navaraChunkFileNames(chunk) {
-  const navara =
-    !chunk.isEntry &&
-    (chunk.moduleIds ?? []).some((id) =>
-      NAVARA_MODULE.test(id.replaceAll('\\', '/')),
-    );
-  return navara ? 'assets/navara-engine-[hash].js' : 'assets/[name]-[hash].js';
-}

build/navaraDependencies.js

@@ -1,73 +0,0 @@
-// The packages only the Navara engine brings: the dependency closure of
-// @navaramap/three and @navaramap/three-default-plugin (dependencies and
-// peer dependencies, read from node_modules), without the packages the
-// app's other bundled dependencies reach too (Cesium is external), plus
-// three and postprocessing, which
-// the Cesium-mode page never loads statically either. The initial-chunk
-// guard (initialChunkGuard.js) fails the build when one of them is in an
-// initial chunk.
-
-import { existsSync, readFileSync } from 'node:fs';
-import path from 'node:path';
-
-export const NAVARA_ROOTS = Object.freeze([
-  '@navaramap/three',
-  '@navaramap/three-default-plugin',
-]);
-const ALWAYS_ENGINE_ONLY = Object.freeze(['three', 'postprocessing']);
-// Not bundled: vite-plugin-cesium serves Cesium as a script, so what only
-// Cesium reaches (draco3d, …) is not in the app's bundled graph.
-const EXTERNAL = Object.freeze(['cesium']);
-
-function readManifest(root, name) {
-  const file = path.join(root, 'node_modules', name, 'package.json');
-  return existsSync(file) ? JSON.parse(readFileSync(file, 'utf8')) : null;
-}
-
-/** Every package reachable from `names` through installed manifests. */
-export function dependencyClosure(root, names) {
-  const seen = new Set();
-  const queue = [...names];
-  while (queue.length) {
-    const name = queue.pop();
-    if (seen.has(name)) continue;
-    const manifest = readManifest(root, name);
-    if (!manifest) continue;
-    seen.add(name);
-    for (const next of Object.keys({
-      ...manifest.dependencies,
-      ...manifest.peerDependencies,
-    }))
-      queue.push(next);
-  }
-  return seen;
-}
-
-/** The engine-only package names, sorted. */
-export function navaraOnlyPackages(root) {
-  const app = JSON.parse(readFileSync(path.join(root, 'package.json'), 'utf8'));
-  const navara = dependencyClosure(root, NAVARA_ROOTS);
-  const appRoots = Object.keys(app.dependencies ?? {}).filter(
-    (name) =>
-      !navara.has(name) &&
-      !ALWAYS_ENGINE_ONLY.includes(name) &&
-      !EXTERNAL.includes(name),
-  );
-  const shared = dependencyClosure(root, appRoots);
-  return [
-    ...new Set([
-      ...[...navara].filter((name) => !shared.has(name)),
-      ...ALWAYS_ENGINE_ONLY,
-    ]),
-  ].sort();
-}
-
-/** A module-id pattern matching node_modules/<package>/ for the names. */
-export function packagePattern(names) {
-  const escaped = names.map((name) =>
-    name.replace(/[.*+?^${}()|[\]\\]/g, '\\$&').replace('/', '[\\\\/]'),
-  );
-  return new RegExp(
-    `[\\\\/]node_modules[\\\\/](?:${escaped.join('|')})[\\\\/]`,
-  );
-}

build/panel.js

@@ -6,9 +6,6 @@
  * PANEL_BASE next to the app.
  */
 
-import cesium from 'vite-plugin-cesium';
-import { fileURLToPath } from 'node:url';
-
 // The panel loads these paths (src/tools/globePanel.js); a test keeps the
 // two in step.
 export const PANEL_BASE = '/panel/';
@@ -21,27 +18,6 @@ export function panelBuildConfig(config) {
   return {
     ...config,
     base: PANEL_BASE,
-    plugins: (config.plugins ?? []).map((plugin) =>
-      plugin?.name === 'vite-plugin-cesium' ? cesium() : plugin,
-    ),
-    resolve: {
-      ...config.resolve,
-      alias: [
-        // The panel runs Cesium: the Navara mode and Navara's wind mesh
-        // (the panel's only paths to Navara and three) become stubs.
-        {
-          find: /^(?:\.\/|.*\/app\/)navaraMode\.js$|^.*\/globe\/navara\/windFlowMesh\.js$/,
-          replacement: fileURLToPath(
-            new URL('./panelNavara.js', import.meta.url),
-          ),
-        },
-        ...(Array.isArray(config.resolve?.alias)
-          ? config.resolve.alias
-          : Object.entries(config.resolve?.alias ?? {}).map(
-              ([find, replacement]) => ({ find, replacement }),
-            )),
-      ],
-    },
     build: {
       ...config.build,
       outDir: PANEL_OUT_DIR,
@@ -50,10 +26,6 @@ export function panelBuildConfig(config) {
       cssCodeSplit: false,
       rollupOptions: {
         ...config.build?.rollupOptions,
-        // The panel is a single chunk; its alias excludes the Navara engine.
-        plugins: (config.build?.rollupOptions?.plugins ?? []).filter(
-          (plugin) => plugin?.name !== 'gev-initial-chunk-guard',
-        ),
         output: { inlineDynamicImports: true },
       },
     },

build/panelAlias.test.mjs

@@ -1,45 +0,0 @@
-// A Vite build through the panel alias resolves renderers.js's relative
-// import of Navara's wind mesh to the stub (scripts/build-panel.mjs uses the
-// same alias).
-import test from 'node:test';
-import assert from 'node:assert/strict';
-import { mkdtempSync, mkdirSync, rmSync, writeFileSync } from 'node:fs';
-import { tmpdir } from 'node:os';
-import { join } from 'node:path';
-import { build } from 'vite';
-import { panelBuildConfig } from './panel.js';
-
-test('a Vite build resolves the relative wind-mesh import through the panel alias', async (t) => {
-  const root = mkdtempSync(join(tmpdir(), 'panel-alias-'));
-  t.after(() => rmSync(root, { recursive: true, force: true }));
-  mkdirSync(join(root, 'src/app/layers'), { recursive: true });
-  mkdirSync(join(root, 'src/globe/navara'), { recursive: true });
-  writeFileSync(
-    join(root, 'src/app/layers/renderers.js'),
-    "export const load = () => import('../../globe/navara/windFlowMesh.js');\n",
-  );
-  writeFileSync(
-    join(root, 'src/globe/navara/windFlowMesh.js'),
-    'export const real = true;\n',
-  );
-  const { resolve } = panelBuildConfig({ plugins: [] });
-  const [output] = await build({
-    configFile: false,
-    root,
-    logLevel: 'silent',
-    resolve,
-    build: {
-      outDir: join(root, 'out'),
-      write: false,
-      lib: {
-        entry: join(root, 'src/app/layers/renderers.js'),
-        formats: ['es'],
-        fileName: 'x',
-      },
-      rollupOptions: { output: { inlineDynamicImports: true } },
-    },
-  });
-  const [chunk] = output.output;
-  assert.match(chunk.code, /Navara is unavailable in the panel/);
-  assert.doesNotMatch(chunk.code, /real = true/);
-});

build/panelNavara.js

@@ -1,12 +0,0 @@
-// The panel host transports Cesium assets; Navara workers need a web page.
-export function createNavaraScene() {
-  throw new Error('Navara is unavailable in the panel');
-}
-
-export function navaraToolBackend() {
-  throw new Error('Navara is unavailable in the panel');
-}
-
-export function createWindFlowMesh() {
-  throw new Error('Navara is unavailable in the panel');
-}

build/panelResources.test.mjs

@@ -1,44 +0,0 @@
-import test from 'node:test';
-import assert from 'node:assert/strict';
-import { createBrowserViteConfig } from './vite.js';
-import { panelBuildConfig } from './panel.js';
-
-test('panel HTML lists Cesium assets for the host resource loader', () => {
-  const config = panelBuildConfig(createBrowserViteConfig());
-  const plugin = config.plugins.find(
-    ({ name }) => name === 'vite-plugin-cesium',
-  );
-  plugin.config(config, { command: 'build' });
-  assert.equal(typeof plugin.transformIndexHtml, 'function');
-  const tags = plugin.transformIndexHtml();
-  assert.ok(tags.some(({ attrs }) => attrs.src === '/panel/cesium/Cesium.js'));
-  assert.ok(
-    tags.some(
-      ({ attrs }) => attrs.href === '/panel/cesium/Widgets/widgets.css',
-    ),
-  );
-});
-
-test('the panel replaces Navara entry points and retains browser aliases', () => {
-  const browser = createBrowserViteConfig();
-  const config = panelBuildConfig(browser);
-  const alias = config.resolve.alias.find(({ find }) =>
-    find.test('./navaraMode.js'),
-  );
-  assert.ok(alias.replacement.endsWith('/build/panelNavara.js'));
-  // Navara's wind mesh imports three; the Cesium wind backend stays.
-  assert.equal(
-    '../../globe/navara/windFlowMesh.js'.replace(alias.find, alias.replacement),
-    alias.replacement,
-  );
-  assert.equal(alias.find.test('../../globe/cesium/windFlow.js'), false);
-  assert.ok(config.resolve.alias.includes(browser.resolve.alias[0]));
-});
-
-test('Three imports and requires share its ESM entry', () => {
-  const { resolve } = createBrowserViteConfig();
-  assert.deepEqual(resolve.dedupe, ['three']);
-  const alias = resolve.alias.find(({ find }) => find.test('three'));
-  assert.ok(alias.replacement.endsWith('/three/build/three.module.js'));
-  assert.equal(alias.find.test('three/addons/loaders/GLTFLoader.js'), false);
-});

build/registerVue.js

@@ -1,8 +0,0 @@
-import { registerHooks } from 'node:module';
-import { load } from './vueLoader.js';
-
-// Lets Node import single-file components: `node --import=<this file>`.
-// Hosts reach it as `<core package>/build/register-vue`. The hooks run on the
-// loading thread: off-thread hooks (module.register) would add a round trip
-// to every module a test imports, not only the components.
-registerHooks({ load });

build/vite.js

@@ -1,13 +1,9 @@
 import { fileURLToPath } from 'node:url';
+import { applicationHtmlPlugin } from './application-html.js';
 import cesium from 'vite-plugin-cesium';
-import vue from '@vitejs/plugin-vue';
-import { VUE_PLUGIN_OPTIONS } from './vueOptions.js';
 import { DEFAULT_ALLOWED_HOSTS, hostCheckPlugin } from './allowedHosts.js';
 import { embedFramingPlugin } from './embed-framing.js';
 import { panelBuildPlugin } from './panel.js';
-import { navaraChunkFileNames, navaraWorkerAssets } from './navaraAssets.js';
-import { initialChunkGuard } from './initialChunkGuard.js';
-import { navaraOnlyPackages, packagePattern } from './navaraDependencies.js';
 
 /**
  * The repository root (this file lives at `<root>/build/vite.js`), as a
@@ -28,32 +24,6 @@ export function escapeFsDenyPath(path) {
 
 const REPO_ROOT_GLOB = escapeFsDenyPath(REPO_ROOT);
 
-/**
- * Browser-safe form of the optional Photon endpoint build input. Only https
- * is accepted: the page's connect-src allows no plain-http origin, so an
- * http endpoint would only fail later, silently, in the browser.
- */
-function photonEndpointSetting(value) {
-  if (value === undefined) return undefined;
-  const text = String(value ?? '').trim();
-  if (!text || ['off', 'none', 'disabled'].includes(text.toLowerCase()))
-    return null;
-  try {
-    const url = new URL(text);
-    if (
-      url.protocol !== 'https:' ||
-      url.username ||
-      url.password ||
-      url.search ||
-      url.hash
-    )
-      return null;
-    return url.href;
-  } catch {
-    return null;
-  }
-}
-
 /**
  * Content-Security-Policy for every document the dev/preview server serves.
  * No inline script is permitted, and the only foreign script origins are the
@@ -172,25 +142,20 @@ export function createBrowserViteConfig({
   publicDir,
   googleApiKey,
   cesiumToken,
-  photonUrl,
   mapillaryToken,
   host = 'localhost',
   port = 4173,
   allowedHosts = DEFAULT_ALLOWED_HOSTS,
   command,
 } = {}) {
-  const photonSetting = photonEndpointSetting(photonUrl);
   return {
     plugins: [
       // 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(),
-      // Keep the SDK asset serving/copying and external imports, but let the
-      // scene load the script and stylesheet only when Cesium is requested.
-      { ...cesium(), transformIndexHtml: undefined },
-      // Application views are Vue single-file components.
-      vue(VUE_PLUGIN_OPTIONS),
+      cesium(),
+      applicationHtmlPlugin(),
       ...plugins,
       embedFramingPlugin(),
       panelBuildPlugin(),
@@ -199,20 +164,6 @@ export function createBrowserViteConfig({
     // A production build must not clean the dependency cache a running dev
     // server is still serving optimized module URLs from.
     ...(command === 'build' ? { cacheDir: 'node_modules/.vite-build' } : {}),
-    resolve: {
-      dedupe: ['three'],
-      alias: [
-        {
-          find: /^three$/,
-          replacement: fileURLToPath(
-            new URL(
-              '../node_modules/three/build/three.module.js',
-              import.meta.url,
-            ),
-          ),
-        },
-      ],
-    },
     optimizeDeps: {
       // First reached through the SDR worker or a dynamic import. Pre-bundle
       // them at startup so first use cannot invalidate already-transformed
@@ -225,18 +176,6 @@ export function createBrowserViteConfig({
         // Loaded on demand when the first street-level image opens.
         'mapillary-js',
       ],
-      // Navara's wasm-bindgen glue loads new URL('x_bg.wasm', import.meta.url)
-      // and its workers by URL; both must resolve next to the package's own
-      // files, not inside .vite/deps. Dev server only: the experimental
-      // Navara engine is a dynamic import outside the Cesium-mode bundle.
-      exclude: [
-        '@navaramap/three',
-        '@navaramap/three-default-plugin',
-        '@navaramap/engine',
-        '@navaramap/engine-api',
-        '@navaramap/engine-worker',
-        '@navaramap/engine-font-worker',
-      ],
     },
     server: {
       host: host || 'localhost',
@@ -270,42 +209,13 @@ export function createBrowserViteConfig({
     // framing + CSP hardening (one constant, no drift).
     preview: { headers: BROWSER_HEADERS },
     define: {
-      // vue-i18n holds the locale and catalogs; Core formats the messages
-      // (src/ui/i18n.js), so the build drops vue-i18n's message compiler.
-      __VUE_I18N_FULL_INSTALL__: 'false',
-      __VUE_I18N_LEGACY_API__: 'false',
-      __INTLIFY_PROD_DEVTOOLS__: 'false',
-      __INTLIFY_DROP_MESSAGE_COMPILER__: 'true',
       'import.meta.env.GOOGLE_MAPS_API_KEY': JSON.stringify(googleApiKey),
       'import.meta.env.CESIUM_ION_TOKEN': JSON.stringify(cesiumToken),
-      // Only expose a validated URL or the explicit disabled sentinel.
-      ...(photonSetting === undefined
-        ? {}
-        : {
-            'import.meta.env.PHOTON_URL': JSON.stringify(photonSetting),
-          }),
       // Mapillary client tokens are public by design (see SECURITY.md).
       'import.meta.env.MAPILLARY_CLIENT_TOKEN': JSON.stringify(
         mapillaryToken ?? '',
       ),
     },
-    build: {
-      chunkSizeWarningLimit: 1500,
-      // Build only: the wasm Navara's workers load by name (the Navara
-      // engine is a separate chunk loaded on ?engine=navara).
-      // The lazy chunk with the Navara engine is named navara-engine.
-      rollupOptions: {
-        // initialChunkGuard: no three/Navara module in the initial chunks.
-        plugins: [
-          navaraWorkerAssets(),
-          initialChunkGuard({
-            pattern: packagePattern(
-              navaraOnlyPackages(fileURLToPath(new URL('..', import.meta.url))),
-            ),
-          }),
-        ],
-        output: { chunkFileNames: navaraChunkFileNames },
-      },
-    },
+    build: { chunkSizeWarningLimit: 1500 },
   };
 }

build/vueLoader.js

@@ -1,170 +0,0 @@
-import { createHash, randomBytes } from 'node:crypto';
-import {
-  lstatSync,
-  mkdirSync,
-  readFileSync,
-  renameSync,
-  rmSync,
-  writeFileSync,
-} from 'node:fs';
-import { createRequire } from 'node:module';
-import { tmpdir } from 'node:os';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-import { VUE_TEMPLATE_OPTIONS } from './vueOptions.js';
-
-const require = createRequire(import.meta.url);
-
-// The compiler loads on the first component that is not cached, so a test
-// process that imports no views, or only cached ones, never pays for it.
-let compiler = null;
-const sfcCompiler = () => (compiler ??= require('vue/compiler-sfc'));
-
-/**
- * Compile a single-file component to an ES module for Node, so unit tests (the
- * application's and a host's) can import components without a bundler.
- * Styles are dropped: tests read the global stylesheet separately.
- */
-export function compileVueModule(source, filename) {
-  const { compileScript, compileTemplate, parse } = sfcCompiler();
-  // The template is parsed with the SFC; parse it as the browser build does.
-  const { descriptor, errors } = parse(source, {
-    filename,
-    templateParseOptions: VUE_TEMPLATE_OPTIONS.compilerOptions,
-  });
-  if (errors.length) throw errors[0];
-  const id = filename;
-  if (descriptor.scriptSetup) {
-    return compileScript(descriptor, {
-      id,
-      inlineTemplate: true,
-      templateOptions: VUE_TEMPLATE_OPTIONS,
-    }).content;
-  }
-  const script = descriptor.script
-    ? compileScript(descriptor, { id, genDefaultAs: '__sfc__' }).content
-    : 'const __sfc__ = {};';
-  let template = '';
-  if (descriptor.template) {
-    const compiled = compileTemplate({
-      source: descriptor.template.content,
-      filename,
-      id,
-      ...VUE_TEMPLATE_OPTIONS,
-    });
-    if (compiled.errors.length) throw compiled.errors[0];
-    template = compiled.code;
-  }
-  return `${script}\n${template}\nif (typeof render === 'function') __sfc__.render = render;\nexport default __sfc__;\n`;
-}
-
-// The loader's own code is part of every key, so a change to how components
-// compile never reuses output from before it.
-let loaderFingerprint = null;
-const fingerprint = () =>
-  (loaderFingerprint ??= createHash('sha256')
-    .update(readFileSync(fileURLToPath(import.meta.url)))
-    .update(readFileSync(new URL('./vueOptions.js', import.meta.url)))
-    .update(require('vue/package.json').version)
-    .digest('hex'));
-
-/**
- * Where compiled components are kept between test processes, never a
- * package's own tree (a host's checks refuse files inside Core): the system
- * temp directory, or on Windows the per-user local app data directory, since
- * a temp directory there may be shared and its ownership is not checked.
- * GEV_VUE_CACHE=0 compiles every time.
- */
-export function vueCacheDirectory(
-  env = process.env,
-  platform = process.platform,
-) {
-  if (env.GEV_VUE_CACHE === '0') return null;
-  if (platform === 'win32') {
-    return env.LOCALAPPDATA ? path.join(env.LOCALAPPDATA, 'gev-vue-sfc') : null;
-  }
-  return path.join(tmpdir(), `gev-vue-sfc-${process.getuid()}`);
-}
-
-/** The cache entry for one component: its path, its text and the loader. */
-export function vueCacheKey(source, filename) {
-  return createHash('sha256')
-    .update(JSON.stringify([fingerprint(), filename]))
-    .update('\0')
-    .update(source)
-    .digest('hex');
-}
-
-/**
- * Compile a component, reusing a previous process's result for the same text.
- * A cache that cannot be read or written only costs the compile.
- */
-export function cachedVueModule(
-  source,
-  filename,
-  directory = vueCacheDirectory(),
-) {
-  if (!directory || !ownCacheDirectory(directory)) {
-    return compileVueModule(source, filename);
-  }
-  const entry = path.join(directory, `${vueCacheKey(source, filename)}.mjs`);
-  try {
-    return readFileSync(entry, 'utf8');
-  } catch {
-    // Not compiled yet.
-  }
-  const compiled = compileVueModule(source, filename);
-  // Concurrent test processes and threads may compile the same component;
-  // each writes its own new file and the rename makes the entry appear whole.
-  const partial = `${entry}.${randomBytes(6).toString('hex')}.tmp`;
-  try {
-    writeFileSync(partial, compiled, { flag: 'wx', mode: 0o600 });
-    renameSync(partial, entry);
-  } catch {
-    // An unwritable directory, or a rename another process holds open,
-    // leaves the cache without this entry.
-    try {
-      rmSync(partial, { force: true });
-    } catch {
-      // A partial file that cannot be removed is only clutter.
-    }
-  }
-  return compiled;
-}
-
-/**
- * Cached modules run as code, so the directory must be this user's own: a
- * real directory (not a link), owned by the current user and writable by no
- * one else. In a shared temp directory another user could otherwise create it
- * first and plant modules. On Windows it sits in the user's own profile.
- */
-const checkedDirectories = new Map();
-export function ownCacheDirectory(directory) {
-  if (!checkedDirectories.has(directory)) {
-    checkedDirectories.set(directory, isOwnDirectory(directory));
-  }
-  return checkedDirectories.get(directory);
-}
-
-function isOwnDirectory(directory) {
-  try {
-    mkdirSync(directory, { recursive: true, mode: 0o700 });
-    const stats = lstatSync(directory);
-    if (!stats.isDirectory()) return false;
-    if (process.platform === 'win32') return true;
-    return stats.uid === process.getuid() && (stats.mode & 0o022) === 0;
-  } catch {
-    return false;
-  }
-}
-
-/** Synchronous module hook (module.registerHooks): `.vue` loads compiled. */
-export function load(url, context, nextLoad) {
-  if (!url.endsWith('.vue')) return nextLoad(url, context);
-  const filename = fileURLToPath(url);
-  return {
-    format: 'module',
-    source: cachedVueModule(readFileSync(filename, 'utf8'), filename),
-    shortCircuit: true,
-  };
-}

build/vueOptions.js

@@ -1,16 +0,0 @@
-/**
- * Template options shared by the browser build, the boundary check and the
- * unit-test loader. Whitespace between nodes is kept (as a single space) so
- * an application view renders as its static markup did; Prettier formats
- * single-file components with strict whitespace sensitivity to match. Asset
- * URLs such as `/pin.svg` stay literal instead of becoming module imports.
- */
-export const VUE_TEMPLATE_OPTIONS = Object.freeze({
-  compilerOptions: Object.freeze({ whitespace: 'preserve' }),
-  transformAssetUrls: false,
-});
-
-/** `@vitejs/plugin-vue` options for application builds. */
-export const VUE_PLUGIN_OPTIONS = Object.freeze({
-  template: VUE_TEMPLATE_OPTIONS,
-});

changelog.d/1086-prohibited-restricted-airspace.md

@@ -1,8 +0,0 @@
-- Add a Prohibited & Restricted Airspace layer for FAA prohibited (P) and
-  restricted (R) special-use airspace. The keyless `/api/drone-airspace` proxy
-  pages the public SUA FeatureServer, keeps a one-hour snapshot, and serves
-  stale data when a refresh fails. Zones draw as ground polygons (red
-  prohibited, orange restricted); selection shows name, altitude range, times
-  of use and agency, and the row legend states the layer is informational only
-  and does not include the UAS Facility Map or UAS flight restrictions. Off by
-  default; share-link token `8` (mvanhorn, #1086).

changelog.d/1093-multipart-cable-feature-ownership.md

@@ -1,4 +0,0 @@
-- Keep every submarine-cable segment associated with its source feature after
-  Cesium expands multipart geometry, correcting segment colors, click destinations
-  and horizon culling while retaining one reference stem per feature
-  (@Aliciawque, #1093).

changelog.d/1125-houston-cctv-pack.md

@@ -1,18 +0,0 @@
-- Add Houston traffic cameras from Houston TranStar as a CCTV pack. The camera
-  list is one keyless JSON request to
-  `traffic.houstontranstar.org/data/layers/cctvSnapshots_json.js`; frames are
-  stills synthesized from each numeric camera id on `www.houstontranstar.org`,
-  so a catalog field cannot steer the proxy off-host. Cameras without a
-  snapshot id, and cameras outside Greater Houston, are dropped. TranStar's
-  `dir` field (the side of the freeway the camera sits on) seeds a
-  low-confidence heading along the nearest lanes' travel direction. TranStar's
-  Content Usage terms (traffic.houstontranstar.org/disclaimer.aspx) prohibit
-  copying, distribution and external framing of its images without TxDOT's
-  written permission, so the pack is off by default; operators should set
-  `CCTV_HOUSTON_ENABLED=1` only if they hold that permission. Frames are
-  relayed on demand with `no-store` and not archived. Once enabled, it loads
-  the 250 cameras nearest downtown, Uptown, the Medical Center, IAH and
-  Galveston; `CCTV_HOUSTON_MAX_SOURCES` changes that cap.
-  Snapshots update about every 3 minutes. The catalog-wide ceiling is
-  unchanged; extra cameras share it round-robin with the other packs
-  (mvanhorn, #1125).

changelog.d/114-open-map-overlays.md

@@ -1,3 +0,0 @@
-- Add Sea Marks (OpenSeaMap) and Ski Pistes (OpenSnowMap) as two raster
-  overlay layers under Infrastructure. They drape on the globe stacks and on
-  Google 3D, and share links keep each one (Tom-Neverwinter, #114).

changelog.d/1206-radio-priority-countries.md

@@ -1,6 +0,0 @@
-- Add optional keyless Radio priority-country coverage with up to 40 stations
-  per configured country inside the existing 750-station cap; the UK alias uses
-  the canonical GB code. Country query
-  failures do not block a healthy global catalog. Bound mirror attempts to three
-  and retry failed or partial refreshes after 60 seconds on all installations,
-  including those without priority countries configured (m3ayush, #1206).

changelog.d/1308-overpass-admission-review-fixes.md

@@ -1,13 +0,0 @@
-- Keep Overpass-backed layers working behind a reverse proxy: `/api/overpass`
-  now uses the keyless same-site gate, admits forwarding headers and still
-  refuses cross-site requests. Direct loopback requests keep their own
-  admission window; proxied requests, including those a local reverse proxy
-  relays over loopback, are admitted as remote traffic keyed by their socket,
-  and IPv6 peers are keyed by /64, so neither LAN peers nor proxied users can
-  exhaust the owner's admission. The upstream budget stays shared, so an owner
-  cache miss can still be rate-limited (asturksever, #1308).
-- Give the tracking arrival check a wall-clock budget per observed frame and
-  retry only an inconclusive timeout: a timeout keeps every angle it
-  measured, including a late frame's, and a wrong one fails without retry, so slow software-rendered
-  frames no longer fail the check and a real violation is never retried into a
-  pass (asturksever, #1308).

changelog.d/1319-cctv-bosch-mic-specs.md

@@ -1,3 +0,0 @@
-- Vendor the Bosch MIC PTZ datasheet records that the City of Amsterdam camera
-  register names (MIC-7522, MIC-7502, MIC-7130), with the register's `x` colour
-  wildcard as an alias, from the CCTV Camera Database v2.29.0 (ch-bas, #1319).

changelog.d/1426-fire-intensity-filter.md

@@ -1,12 +0,0 @@
-- Color every Active Fires detection by fire radiative power on a six-stop
-  ember → white-hot ramp (ember · red · flame · orange · gold · white-hot at
-  0 · 5 · 20 · 50 · 100 · 300 MW, brighter as power rises), and add a
-  log-scale minimum-FRP slider whose track is the ramp, an All / Nominal+ /
-  High confidence switch and an "N of M shown" counter to the layer row. Far
-  zoom shows a Snap Map–style heatmap in the same colors instead of squares,
-  one distinct spot per fire, empty where nothing burns, and cross-fades with
-  the markers around 4,500 km with no gap, keeping weak fires as markers. The filter applies once before
-  rendering, so markers, cards, the heatmap, context and the top-fires query
-  agree; share links keep it (`w` token: `f`, `c`), and `get_active_fires`
-  takes matching `min_frp_mw` and `confidence` arguments. Default 0 MW / All
-  (gekh, #1426).

changelog.d/1427-military-installations-cross-site-gate.md

@@ -1,4 +0,0 @@
-- The military-installations proxy (`/api/military-installations`) now refuses
-  cross-site and reverse-proxy-forwarded browser requests with 403 before any
-  Overpass work, through the same shared gate as `/api/overpass`. Same-origin
-  app requests and local tools such as curl still work (@Sunil56224972, #1427).

changelog.d/1432-vessel-course-north.md

@@ -1,3 +0,0 @@
-- Show a vessel course of 359.5° or more as 0°. Vessel cards and the AIS HUD
-  rounded the course without wrapping, so a ship with no reported heading on
-  a 359.7° course read "360°" and "HDG: 360DEG" (Aditya, @Rohilalala, #1432).

changelog.d/1433-awareness-marker-kilometre.md

@@ -1,6 +0,0 @@
-- Show a Contacts marker 999.5 m or more away as 1.0 km. The on-globe marker
-  chose metres before rounding, so 999.6 m read "1000 m" while the panel read
-  "1.0 km" (Aditya, @Rohilalala, #1433).
-- Distance labels share one formatter that takes each unit cut after rounding,
-  so the Contacts panel and markers, the drawn-line measure and the Cockpit
-  show 9.96 km as 10 km rather than 10.0 km (#1433).

changelog.d/1434-voice-unknown-altitude.md

@@ -1,3 +0,0 @@
-- Selecting the nearest aircraft by voice no longer says "0 feet" for a contact
-  whose feed reported no altitude; the reply and card leave the altitude out
-  (Aditya, @Rohilalala, #1434).

changelog.d/1435-military-positionless-rows.md

@@ -1,5 +0,0 @@
-- Military aircraft that leave the adsb.lol feed fade and are removed again.
-  The feed's routine position-less rows no longer mark every snapshot partial,
-  which kept vanished aircraft at full opacity for up to five minutes; those
-  rows keep only their own aircraft, and a likely-landed one still leaves on
-  the landed limit (Aditya, @Rohilalala, #1435).

changelog.d/1436-military-geom-vertical-rate.md

@@ -1,3 +0,0 @@
-- Military aircraft whose transponders report a GNSS vertical rate now carry it
-  in analyst and tracked-aircraft data instead of null (Aditya, @Rohilalala,
-  #1436).

changelog.d/1441-cctv-heading-north.md

@@ -1,3 +0,0 @@
-- Show a CCTV camera facing 359.5° or more as HDG 0°. The HUD heading token
-  and the camera panel rounded the bearing without wrapping, so a camera
-  facing 359.6° read "HDG 360°" (Aditya, @Rohilalala, #1441).

changelog.d/1442-traffic-coverage-edges.md

@@ -1,4 +0,0 @@
-- Keep Street Traffic's flow status honest at the edges. A few TomTom-matched
-  dots among hundreds rounded to 0% and read "(no matches)", and a few
-  simulated dots rounded to "100% cov"; coverage now stays within 1–99% while
-  both are shown (Aditya, @Rohilalala, #1442).

changelog.d/1443-replay-countdown-ten.md

@@ -1,3 +0,0 @@
-- Run Space Missions' Replay Ascent countdown from T−10 after the five-second
-  tile hold; the hold ran 10 s and the countdown started at T−05 (Aditya,
-  @Rohilalala, #1443).

changelog.d/1444-replay-speed-countdown.md

@@ -1,3 +0,0 @@
-- Keep Space Missions' replay countdown in real time when the replay speed
-  changes before liftoff; 0.25× had stretched T−8 to T−32 (Aditya,
-  @Rohilalala, #1444).

changelog.d/1445-annotation-label-units.md

@@ -1,3 +0,0 @@
-- Label a route, arrow or drawn line of 995 m or more as 1.0 km, and of
-  9,950 m or more as 10 km. The placed label picked the unit before rounding,
-  so it read "1000 m" and "10.0 km" (Aditya, @Rohilalala, #1445).

changelog.d/1447-bikeshare-derived-capacity.md

@@ -1,3 +0,0 @@
-- Bike Share stations whose feed publishes no capacity now take it from each
-  status poll's bikes and docks instead of keeping the first poll's value or
-  the placeholder 15 (Aditya, @Rohilalala, #1447).

changelog.d/1448-local-adsb-geom-rate.md

@@ -1,6 +0,0 @@
-- Local ADS-B decoder feeds now carry a GNSS-sourced vertical rate
-  (`geom_rate`) when no barometric rate is sent, so the card shows V/S
-  instead of a dash (Aditya, @Rohilalala, #1448).
-- Local ADS-B, military and the adsb.lol flight fallback read the vertical
-  rate through one shared readsb field reader, so all three prefer the
-  barometric rate and fall back to the GNSS rate the same way (#1448).

changelog.d/1449-cable-tool-duplicates.md

@@ -1,3 +0,0 @@
-- List each submarine cable once in find_submarine_cables. TeleGeography
-  splits 17 cables (2Africa, Echo, Hawaiki) into several features, so a
-  search for Echo read "3 submarine cables" (Aditya, @Rohilalala, #1449).

changelog.d/1450-directions-ten-km.md

@@ -1,3 +0,0 @@
-- Show a route of 9.95 km or more as 10 km. The Directions row and step
-  cards kept one decimal until the raw distance reached 10 km, so 9.96 km
-  read "10.0 km" (Aditya, @Rohilalala, #1450).

changelog.d/1451-alpr-direction-north.md

@@ -1,2 +0,0 @@
-- Show an ALPR camera's mapped bearing of 359.5° or more as DIRECTION 0°
-  rather than DIRECTION 360° (Aditya, @Rohilalala, #1451).

changelog.d/1452-transit-heading-north.md

@@ -1,3 +0,0 @@
-- Show a transit vehicle's reported bearing of 359.5° or more as 0°. The
-  selected-vehicle card rounded it without wrapping, so a bus heading 359.6°
-  read "reported hdg 360°" (Aditya, @Rohilalala, #1452).

changelog.d/1453-satellite-launch-year.md

@@ -1,6 +0,0 @@
-- Space Missions no longer shows an older satellite with a similar name and a
-  different known launch year as a new payload's orbit: the launch-year check
-  on loaded satellites now runs (Aditya, @Rohilalala, #1453).
-- Satellite launch years come from one TLE designator parser for both the
-  loaded catalog and the active-TLE fallback; a blank designator is an
-  unknown year instead of 2000 (#1453).

changelog.d/1454-voice-context-heading-north.md

@@ -1,5 +0,0 @@
-- Describe a selected flight or military contact on 359.5° or more to the
-  voice assistant as heading 0°, not 360° (Aditya, @Rohilalala, #1454).
-- Heading and bearing readouts share one rounding helper, so the Cockpit's
-  TRACK ACQUIRED course no longer reads 360°, and a negative bearing wraps
-  instead of printing a minus sign (#1454).

changelog.d/1456-terrain-partial-heights.md

@@ -1,3 +0,0 @@
-- A terrain request the proxy can only partly answer (a 429 pause, or a point
-  the upstream returns without a height) now keeps the real heights it has
-  instead of putting the whole chunk on the geoid (quanticsoul4772, #1456).

changelog.d/1457-dock-icon-only-wings.md

@@ -1,5 +0,0 @@
-- Between 721px and 900px wide (tablet portrait, phone landscape), the
-  Location and Visual Presets dock wings show only their icons, so their
-  labels no longer spill over the voice control or take taps meant for the
-  mic button. The full name stays in the tooltip and accessible name, and the
-  Cyber layout keeps its labels (Denis Groshev, @ZloyS, #1457).

changelog.d/1458-node-24-22-1-security-release.md

@@ -1,4 +0,0 @@
-- The Docker image and CI now pin Node 24.22.2, the current 24 LTS patch. It
-  carries the October 21, 2026 security fixes first released in 24.22.1,
-  including CVE-2026-111497 in the Brotli decoder (Luis Ortiz, @anobjectn,
-  #1458).

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

@@ -2,4 +2,4 @@
   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, #1459).
+  asks OpenAI for a new summary either (samehkhamis, #0000).

changelog.d/1462-voice-alias-hint-budget.md

@@ -1,5 +0,0 @@
-- Leave layer aliases the layer id already spells, such as "dams" for
-  `local-dams`, out of the voice layer hint. The Realtime prompt is 305
-  characters shorter, leaving room under the 52,000 gate for new
-  voice-toggleable layers; every alias is still accepted (@quanticsoul4772,
-  #1462).

changelog.d/1464-infrastructure-ground-sample-in-view.md

@@ -1,4 +0,0 @@
-- Ground-sample Data Centers and Dams markers only when the camera sees the
-  ground under them. Unseen ground read through the Earth and retried every
-  2 s; over Ashburn, Virginia on the Esri map, slow frames reached 2 s
-  (quanticsoul4772, #1464).

changelog.d/1469-utilities-panel.md

@@ -1,6 +0,0 @@
-- Gather Directions, Draw and Import in a new UTILITIES panel in the left
-  column, between Data Layers and Scenes. Draw and Import leave DISPLAY, and
-  Radio stays in Data Layers under "Audio". Each drawn shape now gets a row
-  under Draw, like an imported file: name it, recolour it, hide it, fly to it
-  or remove it there. Area, Line and Pin are icon buttons, and the colour for
-  the next shape is a row of swatches (asturksever, #1469).

changelog.d/1474-radio-next-no-autoplay.md

@@ -1,5 +0,0 @@
-- Radio Next, Previous and the tuning dial no longer start a broadcaster stream
-  before Play is pressed; while a stream plays, it follows the new station.
-  Play reads Pause while a stream connects, and a tuner release onto a station
-  the directory removed or changed no longer leaves a Resume for another
-  station (gekh, #1474).

changelog.d/1479-arabic.md

@@ -1,5 +0,0 @@
-- Add Arabic (ar), the first right-to-left language: the title, rails, dock and
-  corner row mirror, numbers keep Western digits, and plurals use all six
-  Arabic forms. FIRMS cards and Space Missions landing labels are now
-  translated in every language. Based on translations by @abiyeenzo (#915)
-  (German, @gekh, #1479).

changelog.d/1481-rio-transit.md

@@ -1,5 +0,0 @@
-- Add Rio de Janeiro to the Transit layer: municipal buses and the Mobi-Rio BRT
-  from SMTR's keyless GTFS-Realtime feeds (CC BY 4.0), the layer's first Latin
-  American region. Rio's internal route keys are joined to SMTR's published
-  GTFS `routes.txt`, so a card reads "Route SN731" rather than
-  "Route O0731AAN0A" (IMBrandao, #1481).

changelog.d/1488-hud-summary-language.md

@@ -1,3 +0,0 @@
-- Write the AI HUD summary in the interface language, led by the HUD's own
-  translated feed-state warning. A partial layer no longer reads as off or
-  nominal in the HUD, voice and analyst answers (German, @gekh, #1488).

changelog.d/1495-traffic-paired-sides.md

@@ -1,4 +0,0 @@
-- Street Traffic gives the two TomTom `one_side` lines of one two-way street
-  a two-way direction's half share of simulated vehicles each, so the street
-  is no longer drawn twice as dense as the same street from OpenStreetMap
-  (quanticsoul4772, #1495).

changelog.d/1499-vue-and-pinia.md

@@ -1,205 +0,0 @@
-- The language picker switches language in place instead of reloading the
-  page. Views re-render; code that publishes translated text words it again
-  through `onLocaleChange` (`src/i18n/index.js`), and `<html lang>`/`dir` and
-  the page's `data-i18n` markup follow. `persistLocale` replaces
-  `persistLocaleAndReload`, and `registerUnsavedWork` and the switch's
-  unsaved-work prompt are removed, since a switch no longer loses anything
-  (samehkhamis, #1499).
-
-- A map source's `unavailableReason` may be a function, read when the reason
-  is shown so it follows the locale; the sources from `createDefaultMapSources`
-  (`./maps/defaults`) give functions. `MapSourceController` reads either form
-  (samehkhamis, #1499).
-
-- The application views translate their text with `t()` as they render,
-  so it follows the active locale; they no longer carry `data-i18n*`
-  attributes, and `npm run i18n` rejects those in a Vue template. The boot
-  pass (`applyDocumentTranslations`) still translates static page markup
-  such as the loading screen and a host's own markup (samehkhamis, #1499).
-
-- The page's locale lives in a vue-i18n instance installed in every
-  application view, and `t()`, `tn()` and the Intl formatters read it from
-  there, so a view that translates while rendering renders again when the
-  locale changes. `bindLocale` (`src/i18n/index.js`) keeps the locale in a
-  given ref; Core's Vite config builds vue-i18n without its message
-  compiler. Catalogs, messages and call sites are unchanged
-  (samehkhamis, #1499).
-
-- Cockpit's Display popover shows the Display panel's own HUD, Detection,
-  Parameters and 3D groups through Vue teleports: `CockpitDisplayPortal`
-  publishes the popover's slots (`publish`, with `afterRender` to lay out once
-  they have moved) instead of moving the groups itself (samehkhamis, #1499).
-
-- The Cockpit utility strip's measured layout renders from the `gev-cockpit`
-  store: the layout pass publishes `utilityLayout` (the HUD's
-  `--cockpit-utility-*` lengths, `primaryOnly` and `hideCollapsed`), and a host
-  constructing `CockpitController` passes `publish.utilityLayout` beside its
-  other publishers (samehkhamis, #1499).
-
-- The Cockpit Contact and briefing cards' collapse renders from the
-  `gev-cockpit` store: the controller publishes `contextCollapsed` and
-  `signalCollapsed` in its presence, and each card's `data-collapsed` and its
-  toggle's state, words and icon follow it (samehkhamis, #1499).
-
-- The panels' own state classes (`collapsed`, `dock-pinned`, `dock-pinned-top`,
-  `layout-auto-collapsed`, `accordion-collapsed`) render from the
-  `gev-panel-chrome` store: the shell, the rails and the accordion present each
-  panel's state there instead of writing its classes. `layoutLeftPanelRail` and
-  `layoutRightPanelRail` (`./ui/layout`) now call
-  `onCollapse(panel, {collapsed, auto})` and leave drawing it to the host.
-  Without a shell to own the panels, the voice tools' `set_panel_open` now
-  reports that there is no panel to open instead of writing its classes
-  (samehkhamis, #1499).
-
-- The shell's panel chrome no longer writes the panels' collapse buttons, the
-  dock tray toggles' names or the dock pins' pressed state: it presents each
-  panel's open and pinned state to the `gev-panel-chrome` store, and the
-  buttons, now views, call it there. `bindPanelDisclosure` (`./ui/panels`) binds
-  only a panel's Escape; it no longer takes `buttons` or `onChange`. `UiButton`
-  joins the component kit (samehkhamis, #1499).
-
-- `SceneControls` (`./ui/scenes`) no longer takes `elements` or writes the Scene
-  panel's buttons, status, progress or runtime chip: it presents them to the
-  `gev-scenes` store and the panel's buttons call its actions there.
-  `sceneElements`, `presentSceneButtons`, `presentSceneProgress` and
-  `presentSceneRuntime` give way to `sceneButtonsDisabled` and `scenePercent`.
-  It no longer stands down when the page has no Scene panel: ESC still stops a
-  playing scene and the runtime chip still shows (samehkhamis, #1499).
-
-- `initFirstRunExperience` (via `./application/chrome`) no longer writes the
-  launcher's classes, attributes or text, or removes the card: it presents them
-  to the welcome view's `gev-first-run` store (its new `store` option) and
-  connects the controls the view's buttons call (samehkhamis, #1499).
-
-- `IntelHUD` (`./ui/hud`) no longer builds or writes `#intel-hud`: it hands its
-  readouts, visibility, layout variant and style colors to its `publish` option,
-  and Core's `intel-hud` view renders them. A page places that view with
-  `<div class="gev-view" data-gev-view="intel-hud">` instead of a bare
-  `#intel-hud` element. `./layers/vessels` shows the selected vessel's HUD
-  readout through `services.readouts.presentSelectedVessel()` instead of writing
-  `#hud-ais-vessel`; the application passes `src/hudReadouts.js`, which IntelHUD
-  follows (samehkhamis, #1499).
-
-- `LocationControls` (`./ui/location`) no longer builds the city and landmark
-  pills or writes the mini status: it presents the tray, including the search
-  error (`setSearchError()`), and hands it to its `publish` option, and Core's
-  dock renders it and calls `chooseCity()` and `choosePoi()`. Its `elements` are
-  now only `search`: `resetButtons` and `searchToggle` are gone, and the reset
-  buttons and the search toggle call its new `reset()` and `toggleSearch()`. It
-  presents the search field's open and searching state too (`searchExpanded`,
-  `searching`; a `searchExpanded` option starts it open), set through
-  `setSearching()`, `settleSearch()` and `closeSearch()`, and a host renders the
-  field's `expanded` and `searching` classes from it; `LocationSearch` takes a
-  `setSearching` option in place of writing the field's class, and
-  `NavigationController` a `settleSearch` option in place of `searchInput`.
-  `createOrbitIndicator()` is replaced by `showOrbit(active)`, which adds the
-  ORBIT indicator to the presented tray as `orbit: { active }` (null until
-  offered) (samehkhamis, #1499).
-
-- `createMapSourceControls()` (`./ui/maps`) no longer renders the map source
-  chips into a `container` or writes a `statusElement`: it presents the chip row
-  and status badge and hands them to its `publish` option, and Core's dock
-  renders them and calls `select()`. `renderMapStackChips`, `syncMapStackChips`
-  and `MAP_STACK_CHIP_CLASS` are removed (samehkhamis, #1499).
-
-- `./layers/launches` no longer writes the Space Missions roster or the selected
-  mission panel into `#space-mission-panel-host`: the layer publishes both
-  through `subscribePanel(listener)` and Core's Space Missions views render
-  them, calling the layer's panel commands (`selectMissionAt`,
-  `selectPreviousMission`, `selectNextMission`, `deselectMission`,
-  `focusSelectedLaunchSite`, `startSelectedReplay`, `toggleReplayPause`,
-  `cancelReplay`, `setReplaySpeed` and the `roster*` preview inputs). The
-  `bindMissionRosterItemKeyboardPreview`, `captureMissionRosterFocus` and
-  `restoreMissionRosterFocus` helpers are gone; the roster keeps focus itself
-  (samehkhamis, #1499).
-
-- `./layers/awareness` no longer writes the Contacts panel into
-  `#military-awareness-panel`: the layer publishes a plain panel view through
-  `subscribePanel(listener)` and Core's Contacts view renders it, calling the
-  layer's `navigatePrevious`, `focusCurrent`, `navigateNext` and `focusTarget`.
-  The `awarenessPanelControlKey`, `captureAwarenessPanelFocus` and
-  `restoreAwarenessPanelFocus` helpers are gone; the view keeps focus itself
-  (samehkhamis, #1499).
-
-- `./ui/cctv` and `./ui/radio` import Vue and Pinia: their controllers publish
-  the panel's state to a store that the CCTV and Radio views render, instead of
-  writing the panel's markup themselves (samehkhamis, #1499).
-
-- `./ui/display`'s `bindDisplayControls` is gone: the Display panel's controls
-  and the dock's style buttons call their owner through the display store's
-  `connect`/`act`, and its allocation and 3D model choices are the kit's
-  `UiSegmented`. `initDrawTool` takes `connect(actions)`, which returns their
-  disconnect, and no longer listens on the Draw controls; its view publishes
-  `color` and `label` too, and the shape choice is a `UiSegmented`.
-  `initGeoFileImport` takes `connect(actions)` the same way and no longer
-  listens on the Import button, picker or list, nor restores focus itself: the
-  `GeoImport` view does both, and its `publish` need not settle once the list
-  renders. Street Level's fit and panorama filters and Recent Imagery's mode are
-  `UiSegmented` too: the Street Level store's owner answers `setPano` and
-  `setRenderMode`, and `RecentImageryReadout` takes `onSetMode`. The Radio
-  panel's and Cockpit's internet radio controls and the tuner slider's events
-  call `RadioControls`, and the local RTL-SDR card's controls
-  `LocalSdrControls`, through the radio store's new `connect`/`act`; the card
-  labels its gain options itself. `act` returns what the answering action
-  returned. The Display, Radio, RTL-SDR, Cockpit, mission replay, style
-  parameter, rail card, observation timeline, imagery opacity, Street Level date
-  and Bhote Koshi sliders are the kit's `UiSlider`, a native range input that
-  emits numbers, and the pressed toggles are the kit's `UiButton`, which gains
-  `pressedClass`; so are the rail card chips, map source chips and location
-  pills (which now report `aria-pressed`), and the voice card's chips are the
-  kit's new `UiChip`. The selects are the kit's new `UiSelect`, the status
-  badges its new `UiBadge` and the one-line empty states its new `UiEmpty`. The
-  top-center clear, share, tilt, north-up and reset buttons, and the cockpit's
-  reset, call the shell through the new globe actions store, which also carries
-  the camera's tilt and compass heading. The recording safe frame renders what
-  `RecordingControls` publishes to the new recording store. `syncScopeControls`
-  (`./ui/display`), `shouldHideCollapsedRightPanels` (`./ui/layout`),
-  `bindClearLayersControl` (`./ui/layers`) and `createStyleParameters`
-  (`./ui/input`; the Display panel renders the style parameters VisualSettings
-  publishes to the display store) are deprecated: the Display view, the rail and
-  the globe actions view now own what they did. `./ui/input` imports Vue
-  (samehkhamis, #1499).
-
-- `./scenes` presents the scene sharing dialogs and the EDIT DETAILS / SHARE
-  SCENE bar through a store that the scene panels view renders, so a page that
-  omits `layer-panels` shows neither (samehkhamis, #1499).
-
-- `./voice/control`'s `createVoiceControl({ panel })` returns the voice
-  control's presenter instead of element handles: owners write it by part
-  (`update('detail', { text })`) and listen with `on('button', fn)`, and the
-  command dock renders it from a store. `createVoiceCommands`' `createControl`
-  and `VoiceCardControls` (`{ ui }` instead of `{ root }`) take the same
-  presenter; the `reset` option is gone, since a newer control replaces the
-  previous one (samehkhamis, #1499).
-
-- Pages place each view with a `<div class="gev-view" data-gev-view="NAME">`
-  host and write their own loading screen; the `build/html` template expansion
-  and its `gev:template` markers are gone. `createApplication` takes `omitViews`
-  (for example `['provider-settings']`) for views an application leaves out
-  (samehkhamis, #1499).
-
-- The page's panels, dock, cockpit and dialogs are Vue views with the same
-  markup as before. Hosts that do not initialize Core's locale pass
-  `localePicker: false` to `createApplicationControls` to drop the language
-  picker, and Node tests that import application modules register the component
-  loader with `--import=<core>/build/register-vue` (samehkhamis, #1499).
-
-- The Data, Authoring, Weather, Recent Imagery, Context, CCTV, Street Level and
-  Radio panels are one component, `UiPanel` (`src/ui/kit/`), with the same
-  markup plus the kit's `ui-panel` classes, their titles translated by `t()`
-  rather than `data-i18n`; `RailPanel` binds it to the panel chrome store.
-  `PanelCollapseButton` drops its `initial` and `initialTitle` props and takes
-  `startCollapsed`, so before startup presents a panel its button already shows
-  that state's glyph, words and `aria-expanded` (samehkhamis, #1499).
-
-- The Authoring, shot list and CCTV buttons and Street Level's nearest button
-  are the kit's `UiButton` (danger buttons in the `alert` tone, primary ones the
-  `primary` variant), keeping their classes; the CCTV on/off, coverage,
-  auto-hop, projection and adjust toggles now say their state with
-  `aria-pressed` (samehkhamis, #1499).
-
-- Each desktop sidebar has an icon rail that lists every panel on that side and
-  opens one with a click. One panel is open per side in every HUD layout, so the
-  collapsed panel headers no longer take up the sidebars. Phones keep the bottom
-  tab bar. The rail is the first view built with Vue and Pinia, which now ship
-  with the app; see docs/VUE-MIGRATION.md (samehkhamis, #1499).

changelog.d/1500-vue-loader-cache.md

@@ -1,4 +0,0 @@
-- `build/register-vue` loads components on the test thread and keeps compiled
-  components between test processes in a per-user cache directory, so Node
-  tests that import views run about twice as fast. `GEV_VUE_CACHE=0` compiles
-  every time (samehkhamis, #1500).

changelog.d/1501-rail-pills.md

@@ -1,3 +0,0 @@
-- The side panel rails show each panel as a labelled pill while no panel on
-  that side is open, and fold to icons once one opens. `UiRail` takes
-  `collapsible` for this (samehkhamis, #1501).

changelog.d/1507-typed-ai-chat.md

@@ -1,9 +0,0 @@
-- Add a typed AI chat beside the voice mic in the command dock. Replies are
-  silent and never use the microphone; messages run the same map actions as
-  voice through OpenAI Chat Completions (`OPENAI_CHAT_MODEL`) or Gemini
-  `generateContent` (`GEMINI_CHAT_MODEL`). Chat is throttled per IP by
-  `GEV_RATELIMIT_OPENAI_CHAT_PER_MIN` or `GEV_RATELIMIT_GEMINI_CHAT_PER_MIN`,
-  which default to that provider's voice throttle, and `GEV_PREFER_CODEX_OAUTH`
-  turns OpenAI chat off. The chat and voice panels minimize to a bar or dock
-  beside the right rail, and step aside for the Location and Visual Presets
-  trays (Manjunath, @manjunath22466, with Darren Dignam, @darrendignam, #1507).

changelog.d/1518-range-ring-visibility.md

@@ -1,4 +0,0 @@
-- Draw the Global Context 250 km range ring as a 4 px line with a dark halo,
-  so it stays visible over desert, snow, ocean and forest and under the FLIR,
-  NVG and CRT styles, where the old 1 px outline disappeared (manjunath22466,
-  #1518).

changelog.d/1519-range-ring-sonar-pulses.md

@@ -1,8 +0,0 @@
-- The Global Context range ring pulses like a sonar: three dim rings with a
-  soft inward glow grow from the subject to 250 km, and the ring flashes as
-  each one arrives. Flights, military aircraft and AIS vessels a pulse crosses
-  get a brief echo around their brackets. The pulses run for about 9 s after
-  a selection or camera move, dimming the ring between flashes, then rest
-  with the ring steady on screen, so a parked view stops repainting. Under
-  reduced motion there are no pulses and the ring stays on screen
-  (manjunath22466, #1519).

changelog.d/1520-voice-camera-tilt.md

@@ -1,6 +0,0 @@
-- Voice "tilt the camera" works from the top-down view a fly-to lands on: the
-  camera swings about the place under the crosshair, keeps its heading, and can
-  tilt to a spoken angle ("tilt 45 degrees") or a default oblique view. A tilt,
-  orbit, pan or rotate said with a fly-to ("fly to Paris and orbit it") now
-  waits for the flight to land, and is dropped if you move the map meanwhile
-  (Manjunath, @manjunath22466, #1520).

changelog.d/1521-provider-labels.md

@@ -1,4 +0,0 @@
-- Cockpit Contact counts and the Contacts list name the provider that
-  answered, marked `FALLBACK` or `STALE` as in the Layers panel. Flights from
-  the adsb.lol fallback no longer read OpenSky, and vessels no longer always
-  read AISStream (German, @gekh, #1521).

changelog.d/1522-zoom-out-runaway.md

@@ -1,5 +0,0 @@
-- Keep the globe on screen when zooming out from a tilted view. User zoom is
-  capped at 40,000 km, and above 300 km outward zoom pitches the view down so
-  Earth stays framed. Correction finishes when zoom stops, respects tilt
-  gestures and stricter host limits, and yields to other camera actions
-  (asturksever, #1522).

changelog.d/1528-s2-ghostmaps-age-filter.md

@@ -1,4 +0,0 @@
-- Add an adjustable event-age filter across S2 GhostMaps products, defaulting
-  to seven days with 1-, 3-, 14- and 30-day choices and an All markers option.
-  Preserve undated features, save the selected window and expire old events
-  while the map stays open. Thanks @dylanmaniatakes (#1528).

changelog.d/1532-globe-in-view.md

@@ -1,11 +0,0 @@
-- Keep the globe in view from orbit. Cesium's free look (Shift+drag) turned
-  the camera in place, so a few drags from the whole-globe view left only
-  stars, and the pose stayed in the share link. Free look now works only below
-  1,000 km, and above it a drag that starts on the stars orbits the globe
-  instead of turning the camera; a camera move that ends above it with no
-  planet surface in view (inside the scope keyhole when the scope is on) turns
-  straight down; and voice tilt and turns from orbit stop while the planet is
-  still on screen and say so instead of reporting a turn they could not make.
-  Thanks to [Chad Elliott](https://github.com/THEtheChad) for the review that
-  closed the drag path and kept authored scenes framed (Manjunath,
-  @manjunath22466, #1532).

changelog.d/1535-fires-empty-heat-reenable.md

@@ -1,2 +0,0 @@
-- Keep retained Active Fires heat imagery hidden when an empty filtered layer is
-  re-enabled while a new snapshot is pending (radianx, #1535).

changelog.d/1545-typed-chat-translations.md

@@ -1,5 +0,0 @@
-- Finish the typed AI chat translations. The "Reset to globe view" and "Show
-  earthquakes" quick commands are now translated, Traditional Chinese follows
-  Simplified Chinese again, Arabic docks the panel to the side it actually
-  lands on, and the new strings use each language's glossary terms
-  (German, @gekh, #1545).

changelog.d/1546-chat-provider-switch.md

@@ -1,5 +0,0 @@
-- Keep typed chat's view when switching AI Provider: Settings opened from
-  chat stay chat's Settings for the new provider instead of falling back to
-  voice and widening the dock. Opening chat or closing the
-  voice panel now also clears a voice error left on the dock (Manjunath,
-  @manjunath22466, #1546).

changelog.d/1555-navara-globe-engine.md

@@ -1,10 +0,0 @@
-- Add Navara, an experimental three.js/WASM globe, as a second engine next to
-  Cesium, switchable live under VISUAL PRESETS → Globe Engine or with
-  `?engine=navara`. Navara draws at CSS pixels like Cesium; Navara HD
-  (`?engine=navara-hd`) draws at the screen's full resolution and needs about
-  1 GiB more on a Retina screen. Layers keep their data across a switch and
-  draw on both engines; Cesium loads only when a Cesium globe or a
-  Cesium-only feature needs it (German, @gekh, #1555).
-- Keep the cockpit camera steady near the ground: it no longer jumps up and
-  down when an aircraft's reported altitude sits below the globe's terrain,
-  on either engine (German, @gekh, #1555).

changelog.d/1556-cockpit-own-layer-entry.md

@@ -1,6 +0,0 @@
-- Enter Cockpit with only the ridden aircraft's layer on. Contacts is no longer
-  required, and ending Contacts mid-session keeps the view and the layer it
-  rides; turning off the aircraft's own feed ends the view, a missing other
-  feed reads `… FEED OFF · PARTIAL PICTURE`, and double-clicking the followed
-  aircraft or the entry beside its readout enters it (Denis Groshev, @ZloyS,
-  #1556).

changelog.d/1561-chat-autocomplete-arabic-marks.md

@@ -1,3 +0,0 @@
-- Chat autocomplete finds Arabic suggestions typed without short vowels or
-  shadda, so «تتبع» now suggests «اعرض تتبّع الرحلات المباشر»
-  (German, @gekh, #1561).

changelog.d/1578-space-missions-failed-entry.md

@@ -1,4 +0,0 @@
-- Space Missions no longer locks the workspace when its mission index fails to
-  load (429, timeout or bad payload): entry rolls back to the previous layers
-  and camera view and a toast says the index could not load (German, @gekh,
-  #1578).

changelog.d/1581-new-strings-translations.md

@@ -1,4 +0,0 @@
-- Fix the translations of the voice area cards, the fire confidence filter,
-  the drone airspace layer and Sea Marks: one word for "landmark" per
-  language, the airspace layer names the airspace again, and Traditional
-  Chinese follows Simplified Chinese again (German, @gekh, #1581).

changelog.d/1585-keyless-unicode-search.md

@@ -1,3 +0,0 @@
-- Keep keyless place search on a nearby exact match for names written in
-  non-Latin scripts instead of discarding the match and retrying without its
-  proximity ranking (mertkayacs, #1585).

changelog.d/1591-wildlife-sightings.md

@@ -1,12 +0,0 @@
-- Add Wildlife Sightings in the Wildlife layer group, off by default, using
-  keyless iNaturalist observations within 48 h (whales 7 d) and Acartia Salish
-  Sea marine mammals. CONFIRMED and taxa filters share via token `9`.
-  A noninteractive density glow accompanies real-sighting taxon badges,
-  decluttered species labels and credited ambient photos. Selection stays
-  pinned across camera and sample changes and opens an anchored photo card
-  with a contained image, creator/licence and one iNaturalist source link.
-  Obscured and Acartia sightings use text-only cards; private records and
-  Acartia comments are excluded. Attribution appears in the layer row and
-  Data attribution popover. Cached progressive tiles, bounded image/billboard
-  work and a paced queue preserve iNaturalist's 60/minute and 8,000/day limits.
-  All 11 locales supported. (lyehe, #1591)

changelog.d/1601-street-level-keyless-default.md

@@ -1,4 +0,0 @@
-- Without a Mapillary token, Street Level starts on the first keyless source
-  (KartaView) instead of opening on Mapillary's `KEY REQUIRED` with nothing on
-  the globe. A share link that turns a source off is respected
-  (asturksever, #1601).

changelog.d/210-contributor-docs-refresh.md

@@ -1,4 +0,0 @@
-- Contributor docs: CONTRIBUTING lists what each of the three baseline checks
-  needs to run, DATA_SOURCES documents loading a local CCTV source pack, and
-  KNOWN-ISSUES points the floor-placement note at its verification script
-  instead of a missing report (Gaurav Patidar, @gaurav7902, #210).

changelog.d/842-voice-outlines.md

@@ -1,52 +0,0 @@
-- Add source-backed voice outlines without public Overpass calls: bundled Census and
-  Who's On First boundaries cover places and neighborhoods, OpenFreeMap tiles
-  cover streets, buildings, and grounds, and guarded Nominatim lookup handles
-  remaining named areas with bounded caching and usage limits (bilawalsidhu,
-  #842).
-- Preserve standalone server-token maps, project tile outlines only on demand,
-  select building components with their holes independently, preserve non-Latin
-  street-name marks, and enforce public Nominatim spacing at fetch invocation.
-  Nominatim now requires explicit endpoint configuration (manjunath22466, #842).
-- Keep Census labels in filled geometry, handle local dateline outlines in one
-  coordinate frame, and require whole settlement names or explicit returned
-  aliases while retaining landmark shorthand (manjunath22466, #842).
-- Harden and integrate voice outlines with main (manjunath22466, #842).
-- Wait for the original building installation before reporting duplicate results,
-  including deferred outline installs, without restarting probes
-  (manjunath22466, #842).
-- Carry actual outline provenance to visible geometry and retain inline map
-  credits only while the owning outline is displayed (manjunath22466, #842).
-- Require a named building's resolved anchor inside its tile footprint, outside
-  courtyard holes, while keeping nearby selection for pointed-at buildings
-  (manjunath22466, #842).
-- Start each queued building's ground-sampling budget when it reaches the head
-  of the queue, keep Nominatim outlines that cross the antimeridian, let an
-  unnamed school, university, hospital, cemetery, stadium or zoo area answer a
-  grounds ask whose head noun names that kind, keep the shared OpenFreeMap tile
-  caches within the 64 MiB budget of the single source traffic and installations
-  shared before, fold place names in one shared helper, and exclude Who's On
-  First sources whose licence is only listed as CC BY or CC0 "equivalent",
-  including the Ottawa, Saskatoon, Gatineau and Madrid records
-  (manjunath22466, #842).
-- Skip Nominatim place and outline lookups when the server reports that no
-  Nominatim endpoint is configured, so a default install sends no request it
-  would refuse (manjunath22466, #842).
-- Keep the phone credit line on screen when map and outline credits make it
-  longer, wrapping it within the screen instead of running off the edge
-  (manjunath22466, #842).
-- Outline nothing from tiles when the tile under the point failed to load, so a
-  neighbouring building or area never stands in for it, and match each of a
-  Nominatim name tag's ";"-separated names (manjunath22466, #842).
-- Keep bent streets outlined when the geocoded point sits beside the
-  centreline, never answer a landmark ask with the park or square around it,
-  pick the same-name Nominatim outline that holds the resolved place, and keep
-  a new outline when an identical older mark fails to clean up
-  (samehkhamis, #842).
-- Tighten the remaining voice outline review items: Nominatim name checks use
-  the bundled packs' place-name key ("St. Paul" = "Saint Paul"), "E Street" no
-  longer matches "East Street" while "E St NW" answers "E Street" near it,
-  "Burj Khalifa Tower" still finds the tower, no neighbour standing in
-  for a building cut at the tile edge, no cut area answering grounds, https-only
-  PHOTON_URL, an interrupted Nominatim dispatch reclaimed after ten minutes,
-  no node:sqlite startup warning, and lazily decoded shared OpenFreeMap layers
-  (samehkhamis, #842).

changelog.d/846-voice-geometry.md

@@ -1,15 +0,0 @@
-- Voice can reuse what it outlines. `resolve_area` turns a named place into a
-  reusable area, keeping every part and hole, from the same sources as voice
-  outlines; a name several countries or states share ("Georgia", "Punjab") is
-  asked about unless the view is inside one of them. "Draw an area around
-  <landmark>" outlines the mapped area enclosing it, or a 250 m buffer marked
-  approximate. `analyst_query` counts inside an area, the area you drew or an
-  outline on the map, and `find_imagery` shows the best recent acquisition for
-  an area, the view or the spot under the pointer (manjunath22466, #846).
-- `osm_query` ("hospitals in Kathmandu") lists places of one kind into a
-  session-only OSM Places layer. It is offered only when `OVERPASS_UPSTREAMS`
-  is set, and `/api/osm/features` refuses before fetching otherwise; public
-  Nominatim is never used for it (manjunath22466, #846).
-- Analyst counts that combine flights, military aircraft and local ADS-B are
-  named "aircraft". Follow-ups keep the displayed scope and the loaded-data
-  caveat until a new scope replaces them (manjunath22466, #846).

changelog.d/847-cyclone-shared-selection.md

@@ -1,3 +0,0 @@
-- Let the voice assistant read the storm you select in Cyclone advisories:
-  its official advisory, position, intensity and movement. Clearing the
-  selection and the storm leaving the feed are reported apart (kvnloo, #847).

changelog.d/870-hidden-contact-dr.md

@@ -1,4 +0,0 @@
-- Reduce dead-reckoning work for flights already hidden behind the horizon.
-  Hidden contacts update on a staggered one-in-13-ticks rotation (about once a
-  second) while visible contacts and contacts with fleet models retain the full
-  update path (Wilmer Alzate, #870).

changelog.d/953-datacenters-norway-refresh.md

@@ -1,2 +0,0 @@
-- Add Troll Housing to the Datacenters layer (4,352 features) by refreshing
-  Norway from OpenStreetMap data of 2026-10-05 (trygvehhh, #953).

changelog.d/980-codespaces-setup.md

@@ -1,3 +0,0 @@
-- Document GitHub Codespaces as a fourth setup path in the README: a cloud
-  workspace runs the dev server while the globe renders in your own browser
-  (John Leshan, @johnleshan, #980).

docs/APPLICATION.md

@@ -200,24 +200,6 @@ its pending results. Source disposal does not silently reinstate a default.
 `ui/composition` supplies the default engines to the shell. Applications can
 supply a HUD implementation or request policy through control services. The
 shared chrome owns the welcome/loading transition; standalone composition adds
-Provider Settings. A page places each Vue view in `src/ui/views` with a host,
-`<div class="gev-view" data-gev-view="NAME"></div>`, and writes its own loading
-screen (`#loading-screen` with a `.loader-status` line) as static markup so it
-paints before any script runs. `createApplication()` renders the views before
-anything reads the page; `omitViews` names views the application leaves out,
-such as `provider-settings`, and their hosts are removed. Leaving out
-`layer-panels` also leaves out the scene sharing dialogs it draws, and leaving
-out `scene-chrome` the before/after imagery dividers (the imagery still splits,
-with no line or handle to move it), the status chips, the toast, the ORBIT
-indicator, the FPS readout, the Scene actions panel, the data-pack attribution
-cards, the wind inspection marker, the Space Missions replay vehicle, the
-full-globe celestial ring, the screen-space map annotations, the visible
-map target list and the Global Context compass;
-leaving out `command-dock` the voice control and its pointer reticle;
-leaving out `context` the Bhote Koshi reconstruction panel; and leaving out
-`intel-hud` the Intel HUD overlay (`#intel-hud`), whose readouts the HUD
-implementation publishes to the `gev-hud` store. An unknown
-view name is an error. A host that does not initialize Core's locale passes
-`localePicker: false` to `createApplicationControls` instead of editing the
-markup. Node tests that import application modules register the component
-loader with `node --import=<core package>/build/register-vue`.
+Provider Settings. `build/html` expands an allowlist of component markers from
+`src/ui/templates`; unknown names cannot read arbitrary filesystem paths. The
+standalone document expands to the same markup as before this extraction.

docs/CODE-BOUNDARIES.md

@@ -30,10 +30,8 @@ export inventory. Use declared exports rather than reaching into internal files.
 | `src/standalone/`      | Select the default catalog, local sources and setup controls                                            |
 | `src/ui/`              | Navigation generations, restoration, visual state, panel snapshots and their subscriptions              |
 | `src/data/`            | Lifecycle, context and feed state; legacy default-layer facades                                         |
-| `src/layers/<family>/` | Source acquisition, records and shared contract displays with explicit lifecycle owners                 |
+| `src/layers/<family>/` | Source acquisition, records and Cesium resources with explicit controller/renderer owners               |
 | `src/sources/`         | Portable protocols and source contracts; request state belongs to each factory instance                 |
-| `src/geo/`             | Engine-neutral WGS84 maths, ported from Cesium, never imports Cesium                                    |
-| `src/globe/`           | Engine-neutral globe contract and its test support; engines only in `globe/cesium`, `globe/navara`      |
 | `src/services/`        | Supplied application operations; scene construction owns caches and cancellation                        |
 | `src/voice/`           | Portable action schemas/session, common controls, action execution and separate protocol adapters       |
 | `server/providers/`    | Node route factories, process-scoped provider caches and shutdown cleanup                               |
@@ -55,53 +53,18 @@ See [application construction](APPLICATION.md) and the
 2. `scripts/check-package-boundaries.mjs` builds every declared export without
    app Vite configuration or environment files. `scripts/package-boundaries.json`
    assigns each export exactly once and lists its owned modules and external
-   dependencies; a module entry ending in `/` (such as `src/geo/`) owns every
-   file under that directory. Unused imports still count. Node exports have only a `node`
+   dependencies. Unused imports still count. Node exports have only a `node`
    condition; browser groups cannot use build-only dependency exceptions.
 
 Portable source graphs cannot reach application/rendering, Node, Cesium or
 browser globals. This includes `sources/*`, dedicated `layers/*/source` exports,
 flight/military/vessel record and ingestion exports, action schemas, the session
-interface, lifecycle and feed state, and every runtime file in `src/geo/` (the
-engine-neutral geometry ported from Cesium). The browser-global rule reserves
-platform names such as `document` and `window` in these modules; it is an
-architectural check, not a JavaScript sandbox. The globe contract
-(`src/globe/*.js` and `src/globe/testing/**`) cannot reach `cesium`,
-`@cesium/*`, `three`, `postprocessing` or `@navaramap/*`, directly or through
-helpers, nor import an engine implementation; the `src/globe/cesium/**` graph
-reaches no Navara/three package or `src/globe/navara/**` module, and the
-`src/globe/navara/**` graph no Cesium package or `src/globe/cesium/**` module,
-through helpers too. Outside its own directory, `src/globe/navara/**` is
-reached only through a literal `import()` (the app's `?engine=navara` mode), so
-Navara stays out of the Cesium-mode bundle. Common voice controls cannot depend on a
+interface, lifecycle and feed state. The browser-global rule reserves platform
+names such as `document` and `window` in these modules; it is an architectural
+check, not a JavaScript sandbox. Common voice controls cannot depend on a
 Realtime protocol implementation. Negative fixtures cover indirect helpers,
 self-package imports, symlinks and unreachable files.
 
-Runtime SDK imports are restricted by directory, including unreachable modules:
-`cesium` and `@cesium/*` belong in `src/globe/cesium/`; `three`,
-`postprocessing` and `@navaramap/*` belong in `src/globe/navara/`. Package
-subpaths, re-exports and literal dynamic imports obey the same rule, and the
-`<script>` blocks of Vue components count as runtime modules. A module outside
-the Navara engine reaches it only through `import()`: a static import of the
-same specifier fails even beside a dynamic one. Tests and Node test support
-retain their existing exemptions. The production script loader is
-`src/app/loadCesium.js`; it imports no SDK package and needs no exception, and
-it adds no `widgets.css` when the page's markup has already run `Cesium.js`
-(the MCP panel). The panel build replaces `src/app/navaraMode.js` and
-`src/globe/navara/windFlowMesh.js` with stubs (`build/panelNavara.js`), so the
-panel carries no Navara or three. There is no blanket exception for layer
-`render/` directories.
-
-The temporary `engineImportExceptions` list in `scripts/package-boundaries.json`
-contains exact file/package pairs with reasons. The checker reports the used
-entries and rejects duplicates, missing reasons and unused entries. Its three
-exceptions are the Bhote Koshi event, locator and embedded-media models in
-`src/data/`, which still construct Cesium property records. Their drawing uses
-shared displays. Exceptions do not relax the portable, contract or cross-engine
-graph checks. Cesium annotation renderers live in `src/globe/cesium/annotations/`;
-wind backend adapters live in their engine folders. Wind's older injected-SDK
-helpers and the remaining annotation migration are separate debt.
-
 Source-only factories use dedicated `layers/<family>/source` exports where
 available, preserving the same factory implementation without loading rendering.
 Record normalization and endpoint policies have plain owners separate from
@@ -313,7 +276,7 @@ compatible through re-exports.
 
 ### Adding a right-rail readout panel
 
-Add the shell in `src/ui/views/ContextView.vue` inside `#right-context-rail`:
+Add the shell in `src/ui/templates/context.html` inside `#right-context-rail`:
 a `.panel-collapsible` with a stable `id` and matching `data-panel-id`, the
 existing `.panel-header`, collapse button and a dedicated body. Register it
 with the existing panel chrome/layout owners; do not allocate rail space in
@@ -334,13 +297,13 @@ compactStatus, blocks }` in place. Their full-width native button headers expose
 adapter owns accordion state. Generic cards do not select data or enable layers.
 
 `blocks` is an ordered array of loose, optional `{ id, type, ... }` descriptors,
-rendered by `rail/RailCardBlocks.vue`. There are no per-section disclosures:
+rendered by `railCardBlocks.js`. There are no per-section disclosures:
 
 - `summary`: `text`, a single summary line.
-- `list`: `list: { ariaLabel, items }`, keyed by `rail/RailRowList.vue`.
+- `list`: `list: { ariaLabel, items }`, reconciled by `syncRowList` in `rowList.js`.
 - `lines`: keyed `lines: [{ id, text, muted? }]` for details and status.
 - `settings`: `settings: [{ id, label, chips }]`; each labelled row has a 56 px
-  label column and wrapping keyed chips from `rail/RailChips.vue`.
+  label column and a wrapping `syncChipGroup` from `chipGroup.js`.
 - `legend`: `legend: { colors, labels, units?, zeroIndex?, categorical? }` for a
   ramp/scale (including a physical freezing anchor) or separate keyed swatches.
 - `actions`: keyed `actions: [{ id, label, params?, href?, onClick?, disabled?,
@@ -409,10 +372,12 @@ facade's asynchronous teardown can yield.
 
 ## Ordinary action buttons
 
-The scene panels view and the CCTV panel draw their action buttons with the shared
-`gev-action-button` classes in `src/ui/styles/action-button.css`. Feature
-controllers own action dispatch, state, persistence and cleanup, and the views
-preserve IDs and layout hooks.
+`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
 
@@ -424,12 +389,10 @@ the caller.
 ## Visual effects
 
 `ui/effects` exports the effects controller and existing preset definitions.
-It owns transitions and their clock, with explicit render ownership callbacks,
-and writes styles, bloom and sharpening through `engine.render`. Construction
-installs no stages or frame callbacks. Stop animation before releasing UI
-consumers; controller destruction disables its effects. Cesium's
-`src/globe/cesium/postStages.js` owns stage creation and destruction and restores
-the borrowed bloom state when the engine is destroyed. `ui/effects/bloom` exposes the pure intensity/version helpers
+It owns shader stages and their clock, with explicit render ownership callbacks.
+Construction installs no stages or frame callbacks. Stop animation before
+releasing UI consumers, then destroy to remove owned stages and restore the
+borrowed bloom state. `ui/effects/bloom` exposes the pure intensity/version helpers
 without loading the renderer. UI presentation and product-action coordination
 remain in their callers.
 
@@ -438,9 +401,9 @@ remain in their callers.
 `ui/maps` owns source-chip presentation, selection feedback and its subscription
 lifetime. It receives the existing controller and explicit state/action callbacks;
 it imports no renderer or application. Source construction and availability policy
-remain with the map controller. The dock renders the chips; rebuilding controls
-drops their previous subscription, and destruction suppresses late completions
-without owning or destroying the supplied controller.
+remain with the map controller. Rebuilding controls removes their previous chip
+listeners, and destruction suppresses late completions without owning or destroying
+the supplied controller.
 
 ## Layer panel
 
@@ -541,7 +504,7 @@ perform no network requests and discover no additional modules.
 `maps/controller` coordinates scene changes and lifetimes. `maps/imagery`,
 `maps/terrain` and `maps/3d` supply constructors; `maps/defaults` selects the
 standard sources and their setup/fallback policy. The standalone facade wires
-these to their engine's render requests.
+these to the application's render governor.
 
 A registry supplies `sources`, `defaultId`, `unknownId` and optional `recoveryId`.
 Each source has a user-facing `descriptor`, availability/reason, and either an
@@ -585,22 +548,12 @@ services into each family factory. Standalone provider selection lives in
 `src/standalone/layerSources.js`. The construction export has its own checked
 dependency graph, excluding standalone setup and compatibility layer instances.
 
-`src/app/layers/renderers.js` is the layer manifest. Its lazy display loaders
-resolve the shared factories exported by `displays.js` through `display`. All
-five drawing primitives are required by the globe contract. The only display
-backend options are wind streamlines, loaded from the engine folders. A missing wind backend leaves the raster field
-available. Wildlife Sightings draws itself through the contract; Sea Marks and
-Ski Pistes use their overlay controller. No layer display imports an engine SDK.
-`displayRehearsal.test.mjs` loads every manifest display on the fake engine with
-an unknown kind and no extensions, draws a small fixture and checks cleanup.
-
 Both aircraft layers share the catalog's classification registry; launches use
 its satellites and Contacts uses its aircraft, vessels and installations. Data
 registration, controls and voice actions read those same instances. Destruction
 remains the manager's responsibility; classification also observes application
-abort when startup has not reached registration. The session retains models while
-scene attachment builds displays on the active engine. A parked engine can remain
-allocated for a warm switch; its layer drawing is detached.
+abort when startup has not reached registration. Scene engines remain page-owned,
+so this change does not introduce multiple simultaneous viewers.
 
 Direct `src/data` compatibility entries retain their old defaults and testing
 exports. Browser regression probes use the registered instance's testing surface
@@ -639,23 +592,6 @@ listener cleanup. Application data assembly constructs both owners explicitly;
 `data/manager` is the compatibility facade for direct callers. The ordinary
 state subscriptions retain their existing event contract.
 
-`data/layerSceneBinding.js` owns renderer attach/detach, asynchronous settlement,
-parking and failed-release retries. Lifecycle keeps visibility intentions and
-refresh policy. `app/layerSession.js` defines the retained session fields and
-handoff predicate. `standalone/sceneSwitcher.js` coordinates page handoff;
-`ui/shellScene.js` owns scene-bound shell construction, while `applicationShell`
-keeps page controls and policy. `app/sceneHost.js` owns the transition queue,
-request ordering and recovery decision. Application acquisition, attachment,
-restoration and renderer release run in that queue, and shell calls use it too.
-Nested work receives an explicit transaction; outside calls wait for the whole
-transition. A replacement application shares the transition owner with fresh
-parts, and a shell used alone creates its own host. Pick ownership, selection
-dispatch and render demand belong to
-`scene.services`; render demand drives the engine contract, with no dependency
-from the Cesium render backend to the governor. Overlay and tracked-readout
-services still include module singletons; debug access still exposes the native
-viewer and tileset.
-
 ## UI state owners
 
 - `ui/navigation` owns navigation generations, pending search presentation and
@@ -805,13 +741,13 @@ DOM and platform middleware.
 
 ### Native form fields
 
-Native numeric inputs are rendered by the views that own them; the CCTV pose
-chip renders its inline input in `src/ui/cctv/CctvCalValue.vue`. Static
-selects and number inputs use the same `gev-field` surface, with explicit
-compact and inline densities. Feature owners retain
+`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.
+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`,
@@ -823,23 +759,11 @@ field rules separate, so Radio's palette remains an intentional exception.
 
 ### Read-only status badges
 
-Views draw read-only badges with the `gev-status-badge` classes, without
-listeners, status inference or live-region policy. 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 rail card keeps node identity, header focus,
-disclosure and teardown, and does not announce every card update.
-
-## Engine implementation modules
-
-Cesium's viewer construction, atmosphere compatibility, zoom-out guard, starry
-sky, map scene application, imagery and terrain live in `src/globe/cesium/`.
-The public viewer export still resolves through `package.json`. Celestial
-rendering, screen-event constants, scene projection and the legacy trail
-backend also live there. Sonar commands and post stages are engine internals;
-feature controllers call `engine.render`.
-
-Imported-file parsing (`geoFileImport.js`, `geoImportRecords.js`,
-`geoImportKml.js`) returns plain records. `geoImportDisplay.js` consumes them
-through ground, movers, lines and imagery. The UI owns file bytes, visibility
-and attachment lifetime, with no DataSource or engine-specific import backend.
+`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/DIRECTOR-DATA-PACKS.md

@@ -90,7 +90,7 @@ load, removes partial results and reports a stable error without exposing a URL.
 Successful loading leaves the attribution cards visible with the assets.
 
 `createApplicationTools({ sceneDataPacks: { sources } })` and
-`new SceneDirector(scene, style, data, { dataPacks: { sources } })` accept a
+`new SceneDirector(viewer, style, data, { dataPacks: { sources } })` accept a
 registry of source functions. Each receives `{ path, signal, maxBytes }` and
 returns `{ bytes: Uint8Array, mimeType }`. Custom transports must honor the
 signal, bound reads and return the real MIME type. They remain application code,

docs/GLOBE-PRIMITIVES.md

@@ -1,641 +0,0 @@
-# Globe primitives
-
-A layer draws through the globe-engine contract (`src/globe/contract.js`),
-not through Cesium or Navara. The contract has five drawing primitives:
-
-- `engine.movers`: things at points;
-- `engine.lines`: lines in the air;
-- `engine.ground`: fills on the ground;
-- `engine.imagery`: rasters on the ground;
-- `engine.meshes`: textured or coloured world triangles.
-
-Each engine implements all five. Cesium's are in `src/globe/cesium/`,
-Navara's in `src/globe/navara/`, and the fake engine's in
-`src/globe/testing/fakeEngine.js`. The checks every engine must pass are in
-`src/globe/testing/contractSuite.mjs`.
-
-## Movers: things at a point
-
-`engine.movers.createSet({ id, kind, capacity, ... })` makes a set of up to
-`capacity` instances drawn as one batch. Write them with
-`set(index, fields)` and `setCount(n)`, then upload the changes with one
-`commit()`.
-
-There are three kinds:
-
-- `sprite`: an image from an atlas, a square of `sizePx`, turned by
-  `rotation`;
-- `point`: a filled disc with an outline;
-- `model`: a glTF in metres, at least `minimumPixelSize` on screen.
-
-Use movers for aircraft, vessels, satellites, cameras, stations: anything
-that has a position and is drawn the same size on screen (or as a model).
-
-Point instances may also set `outlineColor` independently of the fill,
-so an expanding callout can fade its outline without changing its width.
-
-Instances move every frame without a rebuild. `depthTest` decides whether
-the scene hides them. A pick returns the instance's `pickId` when the set is
-`pickable`. `ready(index?)` says whether a model's glTF or a sprite atlas has
-loaded and `failed(index?)` whether it failed to: a failed set is not loaded
-again, so a layer that retries makes a new set. Cesium loads a model per
-instance: an index written with another `pickId` loads its own model, so an
-instance moved into a failed index does not inherit the failure.
-
-## Lines: polylines in the air
-
-`engine.lines.createLine({ id, widthPx, color, ... })` makes one polyline.
-You can change its positions, colour and model matrix at any time.
-
-The width is in CSS pixels. The line follows the 3D positions it is given;
-it does not follow the ground. Options:
-
-- `arc: 'geodesic'` bends it along great circles;
-- `dash` draws dashes;
-- `depthFailAlpha` draws a dimmer copy where the scene hides it.
-
-Use lines for trails, orbits, launch paths, a ring at a fixed height, and
-leader lines.
-
-## Ground: fills on the ground
-
-`engine.ground.createSet({ id, kind, order, pickable, drape })` makes a set
-of flat fills that drape over the terrain and the 3D tiles. Nothing is
-extruded.
-
-Work with a set like this:
-
-- `replace(items)` checks and stores all its items at once;
-- `commit()` draws them in place of the last ones;
-- `show(visible)` shows or hides the whole set;
-- `list()` names the sets.
-
-Positions are `[longitude, latitude]` in degrees, as GeoJSON stores them.
-Edges follow great circles.
-
-There are four kinds:
-
-| kind       | item                                                    | for                                                       |
-| ---------- | ------------------------------------------------------- | --------------------------------------------------------- |
-| `polygon`  | `rings: [outer, ...holes]`, `fill`, `outline`           | perimeters, airspace, footprints, cones, KML polygons     |
-| `disc`     | `center`, `radiusM` (metres along the ground)           | earthquakes, air-quality stations, a pad zone             |
-| `cell`     | `west`, `south`, `east`, `north` (meridians, parallels) | GNSS and FIRMS cells, privacy cells                       |
-| `corridor` | `positions`, `color`, `widthPx` or `widthM`             | routes, cables, roads, coverage lines, outlines in metres |
-
-Item options:
-
-- Every item has its own colours, rgba in 0..1; the alpha is the opacity.
-- `fill` and `outline` (`{ color, widthPx }`) are optional; an outline runs
-  along every ring.
-- Within a set, a later item draws on top. Between sets, a higher `order`
-  draws on top. All ground fills draw under movers, lines and models.
-- `pickable: true` makes picks return an item's `pickId`, with `owner` (the
-  set) and `instance` (the item's index).
-- `drape` is `'both'` (the default), `'terrain'` or `'tiles'`. Both engines
-  honour it: Navara tells 3D tiles from terrain by its globe depth, and its
-  CPU picks skip a set draped only on the surface not shown (terrain while
-  photoreal tiles show, tiles otherwise).
-
-Discs with a fill may use `radial: { fillAlpha, rimAlpha, rimStart, rimEnd,
-emission }`. Alpha multipliers are in 0..1; the radius fractions satisfy
-`0 <= rimStart < rimEnd < 1`; emission is nonnegative. The rim grows with
-smoothstep between the two radii, then fades smoothly to zero at the outer
-edge. Space Missions uses a 500 m disc with alpha 0.105 inside and 0.72 at
-the rim, transitions at 0.952 and 0.985, and emission 0.35. Cesium retains
-its textured ground material and polygon depth bias. Navara composes the
-same radial envelope in its ground pass after tone mapping.
-
-An unpickable pixel corridor set with `reveal: true` accepts
-`setReveal(fraction)` in 0..1. Each path is clipped at that fraction of its
-length. Geometry stays intact: Cesium updates material uniforms and Navara
-updates the corridor item texture. Hiding, showing and committing a new
-path retain the fraction. A corridor may have `backing: { widthPx, color }`:
-a wider edge with its own colour, with the core blended only once.
-
-Transit drapes its history and active head through ground corridors. Its
-completed runs retain their age bands, 5 px dark backing and 3 px colour,
-with band updates once per displayed second. The active head is one backed
-corridor revealed along the whole current segment; only a segment crossing
-rebuilds its geometry. Transit uses dynamic sets so new history and head
-corridors build synchronously once Cesium's terrain bounds are available.
-The ground pass handles occlusion on both engines.
-
-Cesium also builds reveal sets synchronously after loading those bounds.
-For nonempty sets, `ready()` includes the visible globe's tile readiness:
-classification needs the current surface depth as well as built geometry.
-
-A `widthPx` corridor can also take the looks Cesium's ground polyline
-materials gave it. The GPU works them out every frame from the time, so a
-commit never rebuilds them:
-
-| look    | fields                                           | Cesium's                                                         |
-| ------- | ------------------------------------------------ | ---------------------------------------------------------------- |
-| `glow`  | `power`, `taper` (1: none)                       | `PolylineGlow`'s `glowPower` and `taperPower`                    |
-| `pulse` | `periodMs`, `min`, `max`                         | the alpha times a factor from `min` to `max` and back, a sine    |
-| `dash`  | `cells`, `duty`, `speed`, `gapAlpha`, `emission` | the annotation route's `GevRouteFlow`: dashes flowing to the end |
-
-- `glow` brightens the line toward white along its centre and fades it to
-  nothing at its edges.
-- `pulse` follows the page's monotonic clock (`performance.now()`), as the
-  old materials did, not the app clock.
-- `dash` lays `cells` dashes along the whole line. Each is lit for its first
-  `duty`, with soft edges of 0.08 of a cell, and brightened by `emission`
-  times its colour. Between them the alpha is times `gapAlpha`. The dashes
-  move toward the line's end at `speed` cells a second.
-- A shown set with a `pulse` or a `dash` makes the engine draw a frame after
-  every frame, as Cesium's continuous render did. `list()` reports it as
-  `animated`. A `glow` alone does not animate.
-
-Traffic's jam heat lines glow (power 0.25) and pulse (alpha 0.35 to 0.75,
-1.63 s). The Directions route's 64 dashes flow at 0.55 cells a second.
-
-A pixel corridor may instead use `dashPattern: { lengthPx, pattern: 255 }`,
-a static 16-bit screen-space dash mask with transparent gaps, as Cesium's
-PolylineDash material. It cannot combine with the other corridor looks.
-Bhote Koshi uses an 18 px dash behind its 5 px glowing flood core.
-
-Use `dynamic: true` on a set whose path changes each frame. Cesium waits
-for its shared terrain-height bounds, then builds these small reveals
-synchronously so successive frames do not discard unfinished worker jobs.
-Other sets retain asynchronous building.
-
-### Radial pulse fields
-
-`engine.ground.createPulseField({ id, center, radiusM, heightM, color,
-lineColor, haloColor, depth, lineWidth, haloWidth })` draws up to four
-concentric pulse fronts. The centre is Earth-fixed metres; the radius is
-metres along the surface. The disc lies on the ellipsoid raised by
-`heightM` (default 0), with normal scene depth testing. Colours are rgba in
-0..1, widths are CSS pixels, and `depth` is the inward band depth as a
-fraction of the radius. A band's opacity falls quadratically to zero.
-
-Call `draw({ radii, alphas, level })` with up to four radius fractions and
-opacities in 0..1. Missing fronts are zero. `level` controls visibility;
-the caller includes it in the alphas. The field starts hidden. `move(center)`
-follows a new centre; `destroy()` releases it and is safe to repeat.
-`ground.list()` includes it as `kind: 'pulse-field'`. The caller owns its
-clock and render requests; the field starts no animation loop.
-
-Global Context keeps its 2,500 m pulse height, fixed-width front and halo,
-wake and rest windows, reduced-motion behaviour and 80 ms frame cadence.
-Cesium retains one material disc, updating its uniforms and rotating for
-small moves. Navara evaluates the same bands after tone mapping against a
-raised ellipsoid and scene depth; its shader lives in
-`src/globe/navara/ground/pulse.js`. The fake engine records the same state.
-
-Bhote Koshi's event and locator share `src/layers/bhoteKoshi/render/story.js`:
-the authored reveal properties feed ground corridors and polygons, and
-point movers retain their independent fill and outline opacity. No story
-backend is selected by engine. The authored model still uses its existing
-property records; removing that model dependency is separate work.
-
-### Ground drawing guarantees
-
-Both engines preserve item order, fill and outline colours, pixel and metre
-widths, visibility, and pick ownership. Non-pickable sets let picks through.
-`ready()` reports when committed geometry is ready to draw. Animated corridor
-looks use the shared ground time and request frames while shown.
-
-Cesium translates ground items to classified fills and polylines. Navara
-classifies visible scene depth and blends the ground in display space.
-Navara picks ground items at the surface under the pointer. Packing, tiling
-and bin sizes are implementation details in `src/globe/navara/ground/`.
-
-## Imagery: rasters on the ground
-
-`engine.imagery.createLayer({ id, source, alpha, show, split, order, raise })`
-makes one raster layer draped over the terrain and the 3D tiles, under
-every ground fill, mover, line and model. Its colours are the image's own,
-blended by the texel's alpha times the layer's `alpha`.
-
-There are two kinds of source:
-
-| kind    | source                                                                                                | for                                                      |
-| ------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------- |
-| `tiles` | `url` with `{z}`, `{x}`, `{y}` (and `{s}` of `subdomains`), `minLevel`, `maxLevel`, `tileSize`        | Recent Imagery's GIBS days, weather tiles, open overlays |
-| `image` | `image`: a canvas, an ImageBitmap or image element, or `{ width, height, data }` RGBA bytes; or `url` | the FIRMS heat raster, a field image, event imagery      |
-
-Both take:
-
-- `rectangle` (`{ west, south, east, north }` in degrees; west > east
-  crosses the antimeridian): where the layer draws, the globe when omitted;
-- `credit`: HTML shown while the layer is.
-
-Tiles are Web Mercator XYZ tiles, which stop at ±85.05°, or with
-`scheme: 'geographic'` EPSG:4326 tiles (2×1 at level 0, y down from 90°N,
-Cesium's `GeographicTilingScheme`). `opaque` tiles have no alpha channel,
-and `maxRequests` caps the layer's tile requests in flight.
-`transform(image)` turns each decoded tile (row 0 on the north edge) into
-the canvas or image that draws: the weather's infrared mask. An image is
-stretched over its rectangle in longitude and latitude, row 0 on the north
-edge; one over the whole globe wraps across 180°.
-
-`raise: heightM` puts an image layer on a shell that high above the
-ellipsoid instead of draping it: it draws over terrain, 3D tiles and the
-sky's edge, hidden only by what is nearer. The shell rises with the camera
-(4 m per kilometre of camera height, at most 60 km, in 500 m steps) so the
-coarse 3D tiles seen from far never hide it. Raised layers take image
-sources only.
-
-Work with a layer like this:
-
-- `setSource(source)` draws another source in its place, at its place in
-  the order; the same canvas or bytes again draw their new pixels, and a
-  source that differs only in its `credit` keeps its pixels;
-- `setSource(source, { staged: true, signal })` keeps the drawn source
-  until the new one is complete (the image loaded; the tiles in view in),
-  then swaps them. It resolves true then, and false when the new source
-  failed, `signal` aborted it, or another `setSource` replaced it first. A
-  hidden layer takes it at once. `staging()` says one is on its way;
-- `setDetail({ image, rectangle } | null)` (raised layers): inside the
-  rectangle the layer draws the detail image in place of its own (a
-  sharper view of the area in view). The last detail draws until the new
-  one is uploaded; it resolves true once it draws. null clears it;
-- `setAlpha(alpha)` fades it: at 0 it draws nothing but stays on its
-  surface, so it comes back without a gap (the FIRMS hand-off);
-- `show(visible)` shows or hides it (Cesium unmaps a hidden layer's tiles);
-- `setSplit('left' | 'right' | 'none')` puts it on one side of the split;
-- `ready()` says the source is built (an image URL loaded); tiles arrive
-  after it;
-- `destroy()`.
-
-On the engine:
-
-- `list()` names the layers in draw order, bottom first: a higher `order`
-  draws on top, then the later layer;
-- `setSplitPosition(fraction)` sets where the split runs, a fraction of the
-  canvas width from the left (one per engine, Cesium's
-  `scene.splitPosition`); `splitPosition()` reads it;
-- `surface()` says where imagery drapes now: `'globe'`, `'tiles'` (3D tiles)
-  or `'none'`.
-
-### Imagery drawing guarantees
-
-Both engines draw imagery below ground shapes, movers, lines and models,
-in layer order. Each texel blends by its alpha times the layer alpha.
-Visibility, split position, rectangle bounds and raised-shell height follow
-the imagery contract. Replacing or destroying a source releases its owned
-resources; stale loads cannot replace the current source.
-
-Cesium translates sources to imagery providers and raised shells. Navara
-samples imagery in its surface pass, including raised ellipsoid intersections.
-The adapters own texture storage, tile selection and depth reconstruction.
-
-Cesium moves draped layers between the visible globe and tileset surfaces;
-without either surface, layers wait. Its split applies to globe imagery,
-not raised shells. Navara draws the top eight visible imagery slots, with
-detail images consuming a slot. Staged sources keep the current image visible
-until their replacement is ready; a failed source leaves it intact.
-
-Open map overlays use `engine.imagery` when `maps.addOverlay` is absent.
-Navara's optional native raster path retains terrain detail, but does not
-provide rectangle bounds, split, alpha, order, or drawing on 3D tiles.
-
-### Who draws through imagery
-
-- **FIRMS heat** (`src/layers/firms/render/display.js`): one image.
-- **Recent Imagery** (`src/layers/recentImagery/render/display.js`): two
-  Web Mercator tile layers under a split.
-- **Weather radar, satellite clouds and lightning**
-  (`src/layers/weather/render/display.js`): on the globe, the product's
-  geographic tiles (the regional infrared through its mask, a tile
-  transform), or the global infrared mosaic as one image; each new frame a
-  staged source; clouds, radar and lightning at orders 21, 22, 23. On 3D
-  tiles, a raised layer at the product's shell height
-  (`shellRendering.js` `WEATHER_SHELL_HEIGHTS`) with the detail window
-  around the view as its detail.
-- **The wind field** (`src/layers/wind/render/display.js`): one image over
-  the globe at order 20, faded with the camera's height while streamlines
-  draw, raised at 5 km on 3D tiles. The streamlines stay each engine's,
-  behind the display's `flow` backend, loaded by the manifest:
-  `src/globe/cesium/windFlow.js` supplies Cesium's streamlines
-  (`src/layers/wind/rendering.js`), and `src/globe/navara/windFlow.js`
-  supplies Navara's flow mesh.
-- **The Bhote Koshi event imagery** (`src/layers/bhoteKoshi/render/display.js`):
-  two `url` images over the event's rectangle at alpha 0.96, split left
-  and right at the engine's split position, order 15. The event's and the
-  locator's story graphics use the shared ground and mover display described
-  above.
-
-- **Imported KML/KMZ ground images** (`src/data/geoImportDisplay.js`): one
-  image layer per rectangle at order 30, with the authored alpha capped at
-  0.99 as on Cesium; a tinted or rotated image is drawn on a canvas first,
-  and an absolute one is raised to its altitude.
-- **Sea Marks and Ski Pistes** (`src/data/osmOverlays.js`): tile layers at
-  order 10 on engines without `maps.addOverlay`.
-
-## Imported files
-
-`geoFileImport.js` reads GeoJSON, GPX, KML and KMZ into the plain records in
-`src/data/geoImportRecords.js`. `geoImportKml.js` resolves KML styles with
-Cesium's precedence; its tests compare the records with `KmlDataSource`.
-No import loads the Cesium SDK. One `geoImportDisplay.js` draws the records
-on every engine: points on movers, ground paths and polygon fills on ground,
-raised paths and outlines on lines, raised polygon fills on meshes, and packed
-ground images on imagery.
-Every owned id starts with `geo-import-`; the file controller owns visibility,
-framing, refresh and destruction across engine switches.
-
-Pins use composed square sprites to retain Cesium's pin tip, hot spot,
-subregion, colour, scale and rotation; a KML heading turns with the camera's
-heading, so it stays measured from north. Icon textures share a per-file
-budget of 16 million pixels: many distinct styles get lower-resolution
-textures at the same size. Ground heights come from the loaded surface,
-refreshed after the camera or map settles, in batches of 256; on 3D tiles
-only pins in the window are clamped to the tiles drawn. Ground pins ignore
-scene depth and are culled beyond the horizon; absolute pins retain their
-height.
-
-Raised polygons (KML absolute or relative) draw their fills as meshes and
-their outlines as lines at the vertices' heights. A ground overlay's colour
-tints its image and its alpha fades it; a rotated overlay's image is turned
-on a canvas over the box around it, as Cesium turns its rectangle in degrees,
-and an absolute overlay is raised to its altitude (Cesium raises only
-absolute ones). The shared display has known limits against Cesium: wall
-fills and extruded prisms are omitted (their top geometry remains), and
-`gx:LatLonQuad`, a rotated overlay whose box passes a pole and a raised
-plain-colour overlay are omitted. These are counted as undrawn. Ground edges
-use great circles rather than rhumb lines.
-
-## Input ownership
-
-`engine.input.on(type, listener, { pick, drill, pickWindow })` accepts
-`pickWindow: { width, height }` with positive integer dimensions passed to
-the picker. Omitted dimensions keep the engine default. Listeners share a
-pick only when their windows match, and each receives its requested drill
-limit. Pointer-down picks are synchronous. Moves, including drills, coalesce
-to the latest position per frame. Navara clicks still use one GPU answer
-from the gesture; a missing hit falls back to the requested CPU window.
-Street Level requests 9 × 9 px; CCTV's gizmo requests its own window and
-limit for presses and hover. Pointer ownership and removal still suppress
-delivery while a pick is pending.
-
-`engine.projector.horizonVisible(position, { ellipsoid })` accepts a plain
-ellipsoid with positive finite `radii: { x, y, z }` in metres. Without the
-option it uses WGS84. Street Level supplies WGS84 radii reduced by 1,000 m
-so nearby cones remain visible below sea level. The shared math is tested
-against the native ellipsoidal occluder, including points near the limb.
-
-`engine.input.suspendCameraInputs()` disables camera gestures and returns an
-idempotent resume function. Suspensions are counted: only the last resume
-restores the state captured before the first suspension. This preserves an
-already-disabled camera. `cameraInputsEnabled()` reads the current state.
-Cockpit, imagery-box drawing, CCTV calibration and infrastructure flights use
-these methods on every engine. Pointer claims remain separate from camera
-input suspension.
-
-Pick ownership belongs to the scene attachment, not to an engine implementation.
-`scene.services.picking` owns its predicates and `scene.services.selection` owns
-its shared click dispatcher. Layer entry points resolve these services using
-their attached engine (`sceneServicesFor(engine)`); the pick-registry helper
-functions take that engine as their final argument. Standalone entries acquire
-the same services on first use. The application destroys them on detach and
-creates fresh services when reattaching a parked engine. Identical layer IDs in
-simultaneous scenes cannot replace or unregister one another's picks.
-
-## Render demand
-
-`scene.services.render` owns continuous-render holds and the last 16 idle
-request reasons for one attachment. `holdContinuousRender(id)` and
-`releaseContinuousRender(id)` are idempotent per owner; the last release
-requests one settling frame. `governorRequestRender(reason)` forwards a
-one-shot request even while another owner holds continuous rendering.
-The tools call `install()` after scene consumers have registered their holds.
-
-The governor drives `engine.render` on every engine. Cesium implements
-`setContinuous` with its scene's `requestRenderMode` and disables automatic
-simulation-time renders with `maximumRenderTimeChange = Infinity`. Engine
-internals request their own scene directly and never import the governor.
-Layer service helpers take their attached engine as the final argument;
-attachment-bound callbacks can capture `renderGovernorFor(engine)` directly.
-Destroying the scene clears its holds and makes the captured service inert.
-A parked engine gets a fresh service when reattached.
-
-## World overlays
-
-`scene.services.overlay` owns one attachment's world labels and cards. It
-keeps its sources, collision domains, paint lanes, canvases, frame listeners,
-observers, timers and accessible action subscribers. `init()` installs its
-DOM inside `engine.host.container`; the detection blend surface stays beside
-the card root so it can blend against the scene.
-
-Publish with `setEntries(sourceId, entries, options)`, `setVisible(sourceId,
-visible)` and `clearSource(sourceId)`. Read painted rectangles with
-`getPaintRect(sourceId, entryId)` and register custom painters with
-`registerPaintLane(laneId, painter, options)`. `subscribeActions(listener)`
-provides the accessible mirror; `activateAction(owner, key)` rejects an old
-host's actions. The shell reconnects these operations on every attachment.
-
-`worldOverlayFor(engine)` resolves the same service for standalone consumers.
-The module helper functions take the engine first. Retained layer models use
-`bindOverlayHost` with their attached-engine getter; injected hosts without a
-`forEngine` resolver keep their own operations. Publications can buffer before
-`init()`. Destruction is terminal, including before initialization; a parked
-engine needs fresh scene services. An old paint-lane handle cannot mutate its
-replacement. Font measurements are shared until the last live host releases
-them.
-
-`scene.services.trackedReadout` bridges the follow handle's label and selected
-ALPR or Local ADS-B card into this overlay. `init()` subscribes to that engine's
-follow changes and that attachment's context events; `refresh(entity)` republishes
-changed label text, and `activeId()` resolves the card for annotation placement.
-Positions stay live cached visual anchors. `trackedReadoutFor(engine)` resolves
-the service; destruction removes its listeners and clears only its own source.
-
-`scene.services.context` owns selection records and notifications. Layer publishers
-use `bindOverlayHost` with their current engine, or a context service captured by
-their display. It mirrors records to the page context slot and preserves the
-`gev:entity-selected`, `gev:entity-selection-cleared` and aircraft awareness event
-payloads for page consumers. A clear reaches the page only when that attachment
-owns the page's selected record. Readouts listen only to their scene's event target.
-Identical IDs in different scenes cannot share a card or clear one another's
-selection. Retired context services cannot publish into a replacement attachment.
-An engine handoff carries the page-selected record through the layer session.
-The incoming context adopts it only while the page still selects that record;
-a clear between attachments wins. Rebuilt markers replace the retained carrier
-in the incoming readout without announcing another page selection.
-Readout initialization reads the retained record without testing the outgoing
-carrier's visibility; layers rebuild their carriers after camera restoration.
-The page chrome and detection controller still have page lifetimes.
-
-## Render effects
-
-The optional `visualStyles`, `bloom` and `contactSonar` capabilities are
-available on Cesium and Navara through `engine.render`. Cesium implements
-styles, sharpening, borrowed bloom and the Anime Milky Way fade in
-`src/globe/cesium/postStages.js`; contact sonar is in `sonar.js` and
-`sonarCommands.js`. Cesium does not advertise `cloudCover`.
-
-`VisualEffects` drives transitions through the render contract. UI teardown
-stops animation and disables effects; engine destruction removes its stages
-and restores the borrowed bloom state. Sharpen intensity zero disables
-sharpening on both engines, following Cesium.
-
-## Wildlife privacy cells
-
-Wildlife privacy cells use one `cell` ground set for distinct bounds and taxon
-accents. The fill is 25% opaque and the 2 px outline is 80% opaque, matching
-Cesium's original ground geometry. Both drape on terrain and tiles and pass
-picks through to the badges. Wide views and detach release the set.
-
-## Batched line segments
-
-`engine.lines.createSegments({ id, widthPx, color, order })` groups independent
-straight segments in one batch. `replace(items)` copies pairs of Earth-fixed
-endpoints and optional per-item `widthPx`, `color` and `pickId`; `commit()`
-rebuilds the drawing once. Segments never connect to one another. `show()`
-and `destroy()` affect the whole batch; an empty replacement clears it.
-The batch shares `createLine`'s id namespace and `list()`, which includes its
-endpoint count and committed `pickIds` in item order.
-
-Cesium draws one synchronous primitive with per-instance colours and widths.
-Navara draws one ribbon mesh in the overlay after tone mapping, with scene
-depth and independent segment picks. Batches are solid and depth-tested;
-curved, dashed, transformed and depth-fail lines still use `createLine`.
-Infrastructure and cable references each use one batch for their visible
-stems, preserving Cesium's colours, widths, label winners and update cadence.
-Infrastructure excludes the whole stem batch while sampling its bases.
-
-### Choosing a primitive
-
-- **A position and an on-screen size:** a mover.
-- **A line at given heights, or one that moves or is restyled every frame**
-  (trails, orbits, a ring at the terrain height): a line.
-- **Anything that lies on the ground** and follows its relief:
-  - an area: `polygon`, or `disc` or `cell` when that is its shape (they
-    are exact and cheaper);
-  - a line on the ground: `corridor`, with `widthM` when its width is a
-    real width (an outline in metres) and `widthPx` otherwise.
-- Group items that change together into one set, and replace them in bulk.
-  A ground set rebuilds on commit. Small paths revealed each frame use
-  `dynamic: true`; corridor looks animate without a rebuild, and radial
-  fronts use `ground.createPulseField`.
-- **Pixels on the ground** (tiles, a raster, a photo): an imagery layer.
-  Fade it with `setAlpha`, and give a new raster to `setSource`.
-
-## Meshes: world triangles
-
-`engine.meshes.createMesh({ id, positions, indices, uv, image, color, show,
-depthTest, pickId })` draws indexed triangles on both sides. Positions are
-flat Earth-fixed xyz metres and indices name their vertices. Optional UVs run
-from (0, 0) at the image's bottom left to (1, 1) at its top right. The engine
-copies geometry arrays; the caller owns the canvas, image or video.
-
-`update(patch)` replaces only supplied fields. Repeating `image` uploads new
-canvas pixels; videos update on rendered frames. RGBA `color` multiplies the
-image, white by default. `show()` reads visibility and `show(boolean)` changes
-it. `depthTest` is `normal` or `always`; null `pickId` disables picking. Picks
-return the authored id and the mesh id as owner. `destroy()` is idempotent;
-`engine.meshes.list()` returns live ids in creation order.
-
-Cesium draws a synchronous Primitive with a flat material, no back-face
-culling and no depth writes. Colour, image and visibility changes retain the
-primitive; geometry, pick-id and depth-test changes replace it. The engine
-requests frames while the primitive or its image is preparing. Navara draws
-local coordinates relative to a double-precision world origin in its
-transparent scene pass after tone mapping, with scene depth and triangle
-picking. Their authored colours are blended in display space.
-Both engines own geometry, material and texture disposal. The fake engine
-keeps the same state and tests triangle intersections for picks.
-
-CCTV's `render/meshes.js` describes its live monitor quad and viewshed pyramid
-through this primitive. Its markers and outlines remain movers and lines.
-Obstruction probes use `engine.surface.raycast`; exclusions accept owned mesh,
-line and mover handles on Cesium and restore their visibility after the query.
-
-Data packs use one `src/scenes/dataPacks/display.js`: points on movers,
-straight raised paths on lines, raised polygons and image rectangles on
-meshes, and media markers with captions in a composed sprite. Polygon holes
-and authored vertex heights are retained. Shared triangulation uses `earcut`,
-with tests comparing its area to Cesium's polygon geometry. Images retain
-Cesium's one-degree rectangle grid. Scene detach releases drawn resources and
-pick targets; reattach redraws the retained decoded assets.
-
-Annotation drapes still use their existing renderers. Their bounded building
-classification volumes, animated fills and wire cages are not ordinary world
-triangles; they need a classification contract before that migration can
-preserve Cesium's behaviour.
-
-## Shared follow offsets and manual drawing
-
-`engine.camera.follow({ position, viewFrom, swingTo })` can swing from the
-initial follow frame to `swingTo`, an east/north/up offset in metres. Each
-frame turns at most 60 degrees and interpolates range, preserving Cesium's
-tracked-camera crossing guard. `handle.retarget({ swingTo })` changes only
-the pending swing; `null` cancels it. Stopping or replacing the follow, a
-camera command or engine destruction ends it. Share links read the current
-handle's target and label identity and the camera pose through the contract.
-
-`engine.input.acquirePointer()` returns an exclusive claim, or `null` if
-one is held. Pass it to `input.on(type, listener, { pointer: claim })` and
-call `claim.release()` when done. Other screen subscriptions yield, including
-picks that settle after ownership changes. Camera gestures stay enabled.
-Cesium suspends its stock select and track clicks and restores the original
-functions when the claim is released or the engine is destroyed.
-
-The Draw tool uses one `drawSurface.js` on every engine: a dashed geodesic
-line and a point mover set at the clicked heights. The dim, occluded band
-uses the selected colour as well as the visible band. Finished geometry still
-goes through the annotation board. Detaching the scene releases the claim,
-listeners and preview while retaining the chosen shape and colour. The
-page's pointer lease still arbitrates Draw against other tools.
-
-## How to add an engine
-
-Put the implementation in a new `src/globe/<name>/` folder. Keep SDK classes,
-shaders, resource disposal and SDK workarounds there. Use
-`src/globe/testing/fakeEngine.js` as the contract model, and
-`src/globe/contract.js` as the authoritative member and data-shape reference.
-Coordinates, colours, picks and display options crossing the boundary are plain
-data; displays do not receive native viewers or SDK types.
-
-Implement the required host, camera, picker, projector, frame, render, surface,
-input, credit, clock and map interfaces, plus all five drawing primitives:
-`movers`, `lines`, `ground`, `imagery` and `meshes`. `assertGlobeEngine(engine)`
-checks these required interfaces. `engineCapabilities(engine)` reports only the
-optional visualStyles, bloom, cloudCover and contactSonar groups. An optional
-group must be complete or absent. Do not advertise a capability with a no-op implementation. Match Cesium's behavior where the
-contract permits both engines to implement it.
-
-Run `createContractSuite(engine, { waitFrames, ... })` from
-`src/globe/testing/contractSuite.mjs`. Supply real pointer delivery, canvases and
-pixel reads for browser checks; keep the fake-engine tests as fast contract
-checks. Test ownership and repeated destruction as well as visible output.
-The browser harness is `scripts/qa-contract-suite.mjs`; use
-`--only=ground:,imagery:` for ground and imagery pixel checks.
-
-The application currently registers two kinds: adding another still requires
-registration in `ENGINE_KINDS`, scene construction/choice and the corresponding
-QA harnesses. `assertGlobeEngine` currently validates that registration. The
-folder and passing contract suite are the implementation boundary, not a claim
-that arbitrary engine folders are auto-discovered today. Layers and their
-fixtures should need no new drawing implementation.
-
-The layer manifest (`src/app/layers/renderers.js`) loads shared factories through
-`display`. Every valid engine implements all five primitives; the manifest has
-no per-kind primitive lists or `needs` declarations. `backends` supplies optional
-engine-specific display options, currently only wind's `flow`, loaded dynamically
-from its engine folder. A missing wind backend leaves the shared raster field
-available. Self-drawing layers and map overlays use the same contract and do not
-register supported engine kinds in the manifest.
-
-Run `src/app/layers/displayRehearsal.test.mjs`: it loads every manifest display
-on the fake engine with an unknown kind and empty extensions. Its small fixtures
-exercise attachment, drawing, hiding or release, and destruction; primitive
-registries, frame/camera/input subscriptions, follow state and service records
-must be clean before the engine itself is destroyed. New display entries need a
-fixture. Wildlife Sightings and the two map overlays are explicit skips because
-they have no display factory; their layer tests remain the coverage for those
-controllers. Native wind streamlines, DOM rasterization and GPU pixels are not
-covered by this rehearsal.
-
-`node scripts/check-import-directions.mjs` enforces SDK ownership for static
-imports, re-exports and literal dynamic imports, including package subpaths.
-Cesium packages belong in `src/globe/cesium/`; three, postprocessing and Navara
-packages belong in `src/globe/navara/`. Add the new SDK's ownership rule when
-registering it. Contract graphs cannot reach any engine, and the existing
-engines cannot reach one another. The temporary exact file/package exceptions
-in `scripts/package-boundaries.json` must have reasons and must still be used;
-the checker prints them. They are migration debt, not a pattern for new layers.
-Run package boundaries, formatting, the full unit suite and the coupling report
-as well; engine coupling counts may not grow.

docs/I18N.md

@@ -25,39 +25,17 @@ label.textContent = t(FEED_STATE_LABELS[state]);
 
 A module the server, tools or other portable code also imports must not load the catalogs: it imports `msg` from `src/i18n/marker.js`, which only marks the text, and the UI translates it with `t()` where it shows it. (Older modules keep a local `const msg = (text) => text`, which works the same.)
 
-Vue views call the same `t()` and `tn()`. The page's vue-i18n instance (`src/ui/i18n.js`), installed in every view, holds the active locale, and `t()`, `tn()` and the formatters read it from there, so a view that translates while rendering renders again when the locale changes. Views don't use vue-i18n's own `t`: English is the key, `context` picks an entry and plural forms follow `Intl.PluralRules`, which only Core's functions do.
-
 `msg()` exists for two reasons. `npm run i18n` finds messages only as string literals inside `t(…)`, `tn(…)` and `msg(…)`, so `t(FEED_STATE_LABELS[state])` alone tells it nothing. And a `t()` call at module load runs before the page has picked its language, so it would freeze the English.
 
 ## Markup
 
-Vue views translate in the template, so their text renders in the active locale:
-
-```vue
-<span>{{ t('Normal') }}</span>
-<button :title="t('Pin visual presets')">…</button>
-<option value="all">{{ t('All', { context: 'radio tag' }) }}</option>
-```
-
-Static page markup that no view renders (the loading screen in `index.html`, a host's own markup) opts in with attributes instead, and `npm run i18n` rejects them in a Vue template:
-
 ```html
 <span data-i18n>Normal</span>
 <button title="Pin visual presets" data-i18n-title>…</button>
 <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. `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 at boot and again after every language switch.
-
-## Switching language
-
-The language picker switches in place, without a reload. A view that calls `t()` while it renders follows by itself. Code that translates text and hands it on (to a store, a published view object, a layer's state, a DOM node) must word it again when the language changes:
-
-- **Present again.** `onLocaleChange(listener)` from `src/i18n/index.js` calls the listener after each change and returns the function that removes it; call that at teardown. The listener presents the view again from what it keeps, as `layerPanel.js` and `cockpitController.js` do.
-- **Keep the English, translate when presenting.** Store `msg()` text or a function that words it, not its translation: the voice control takes `update(part, { text: () => t('MIC') })`, the scene director's status and the SDR receiver's messages keep such functions, and `imagerySplit.js` takes its titles that way.
-- **Translated constants in a view** go in `computed`, not in a plain `const` set up once.
-
-A toast already on screen keeps its words.
+`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
 
@@ -88,16 +66,16 @@ An empty translation is reported, and so is one left as the English, plural form
 
 `npm run i18n` and `npm test` fail on UI text that is not marked:
 
-- **Markup:** element text without `data-i18n`, and `title`, `aria-label` or `placeholder` without the matching `data-i18n-*`. In a Vue template, static text or a static `title`, `aria-label` or `placeholder` (rather than `t()`), and any `data-i18n*` attribute.
+- **Markup:** element text without `data-i18n`, and `title`, `aria-label` or `placeholder` without the matching `data-i18n-*`.
 - **Code:** string literals that reach the page without `t()`, `tn()` or `msg()`: assigned to `textContent`, `title` and the like; passed to `setAttribute('title' | 'aria-label' | …)`, `createTextNode`, `showToast` and other notice helpers; assigned to a layer's `error`, `lastError`, `loadingLabel`, `statusMessage` or `status` (a plain `error = …` too); or kept in `label:`, `title:`, `status:` and similar properties. Not reported: declarations (`let status = …`), default values, ternary branches and lower-case codes (`'auth-failed'`). The full list is `JS_SINKS` in `scripts/i18n.mjs`.
 
 Fix it by marking the text. When the text must stay as it is, say so where it lives:
 
-| Case                                                                           | How                                                                      |
-| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
-| Codes, units, product names in markup (`0.9 dB`, `ADS-B · 1090`, `OpenSky`)    | `translate="no"` on the element; it covers everything inside, as in HTML |
-| Page markup whose text code sets through `t()` (a status that starts as `OFF`) | `data-i18n-runtime` on the element (not in a Vue template)               |
-| A literal in code that is not UI copy (a product name, sample data)            | `// i18n-ignore: <reason>` on the line or the line above                 |
+| Case                                                                        | How                                                                      |
+| --------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
+| Codes, units, product names in markup (`0.9 dB`, `ADS-B · 1090`, `OpenSky`) | `translate="no"` on the element; it covers everything inside, as in HTML |
+| Markup whose text code sets through `t()` (a status that starts as `OFF`)   | `data-i18n-runtime` on the element                                       |
+| A literal in code that is not UI copy (a product name, sample data)         | `// i18n-ignore: <reason>` on the line or the line above                 |
 
 Icons (`aria-hidden="true"`, Material Symbols), comments, CSS values and lowercase identifiers are skipped automatically, and so is `src/tools/`, whose text is written for AI clients rather than the page.
 
@@ -106,7 +84,6 @@ Icons (`aria-hidden="true"`, Material Symbols), comments, CSS values and lowerca
 | File                            | What it holds                                                                  |
 | ------------------------------- | ------------------------------------------------------------------------------ |
 | `src/i18n/index.js`             | `t`, `tn`, `msg`, the Intl formatters, markup translation, switching language  |
-| `src/ui/i18n.js`                | the page's vue-i18n instance: the active locale and the catalogs               |
 | `src/i18n/marker.js`            | `msg` alone, for modules the server or tools import (no catalogs)              |
 | `src/i18n/locale.js`            | shipped languages, their names, choosing the language at boot                  |
 | `src/i18n/locales/<code>.json`  | one catalog per language, keyed by English text                                |

docs/INFRASTRUCTURE-LAYERS.md

@@ -3,7 +3,7 @@
 `gods-eye-view/infrastructure` exports `createInfrastructureLayers(services)`.
 It returns fresh datacenter and dam layers in that order, with the existing IDs,
 appearance, label budgets and bundled public datasets. Importing the module or
-calling the factory does not load data, create an engine, or start the application.
+calling the factory does not load data, create a viewer, or start the application.
 The asset URLs resolve relative to the module; Vite rewrites them for production
 base paths. This browser source export expects a Vite-compatible asset build.
 
@@ -21,13 +21,7 @@ const layers = createInfrastructureLayers({
   governorRequestRender,
 });
 
-// Attach each layer to the current engine, then enable it when requested.
-for (const layer of layers) layer.init(null, { engine });
-await layers[0].enable();
-
-// On a scene switch, keep the parsed data and replace only its display.
-for (const layer of layers) layer.detachRenderer();
-for (const layer of layers) await layer.attachRenderer(null, { engine: nextEngine });
+// Register these layers with the existing data-layer manager and viewer.
 ```
 
 | Function | Arguments / responsibility |
@@ -41,39 +35,28 @@ for (const layer of layers) await layer.attachRenderer(null, { engine: nextEngin
 | `removeEntityContextsForLayer` | `(layerId)`; remove records owned by the layer on destruction or failed setup |
 | `governorRequestRender` | `(reason)`; request a frame through the existing render scheduler |
 
-Each returned session layer supports `init(null, { engine })`,
-`attachRenderer(null, { engine, signal })`, `detachRenderer()`, `enable()`,
-`disable()`, `update()`, `destroy()`, `getStats()`, `getLodDiagnostics()` and
-`getAnalystRecords(limit)`. The first argument is retained for lifecycle
-compatibility; drawing uses the engine passed in the options. Attach once per
-scene, detach before attaching another engine, and destroy when the session ends.
-Separate applications may use identical IDs with separate context/overlay hosts.
-Callbacks must remain usable through destruction.
+Each returned layer supports `init(viewer)`, `enable(viewer)`, `disable(viewer)`,
+`update(viewer)`, `destroy(viewer)`, `getStats()`, `getLodDiagnostics()` and
+`getAnalystRecords()`.
+Use the same viewer for the instance's entire lifetime. Each viewer/context/overlay
+host permits one live instance per layer ID; destroy an old instance before
+replacing it. Separate applications may use identical IDs with separate hosts.
+Callbacks must be ready before enable and remain usable through destruction.
 
-`src/layers/infrastructure/index.js` owns the parsed dataset, shared in-flight
-load, enabled intention and selection across scene switches. Enable loads on
-first use. Disable hides the drawing and clears selection but retains parsed
-data. Detach destroys scene resources and retains the dataset and selected ID;
-reattach redraws enabled data and restores selection when no other selection
-owns the context. The attachment signal cancels that scene's wait, not the
-session's fetch. Destroy aborts the fetch, discards late results and releases
-both data and drawing.
+Disable retains the loaded dataset for reuse and clears selection and listeners.
+Concurrent enables share one load. Destroy is permanent, aborts pending fetches,
+discards late results, and clears the owned data source, context records, overlays,
+input handler and listeners. The layer never creates an application context store,
+overlay host, viewer, or render scheduler. The consumer must resolve one compatible
+Cesium installation shared with its viewer; it must not bundle separate copies.
 
-`src/layers/infrastructure/render/display.js` draws the same records on every
-engine: point movers for tips and pins, lines for stems, ground polygons for
-footprints and ground corridors for paths. It owns the LOD walk, surface-height
-refresh, picks, context handles and overlay publications. Destruction releases
-its primitives and frame, camera and input subscriptions. The layer never
-creates an overlay host, engine or render scheduler and does not import Cesium.
-
-`gods-eye-view/infrastructure/geojson` exports the overlay publication,
-selection, label and error helpers in `src/data/localGeojsonCore.js`; it no
-longer exports `createLocalGeoJsonLayer`. `gods-eye-view/infrastructure/lod`
-exports the LOD policy helpers. The package exports do not import standalone
-application globals.
+`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.
+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,352 datacenter features and 704 dam features. The session
-splits multipart geometries using Cesium's stable repeated-id suffixes on every
-engine. Feature, mover and stem counts are different measurements. These files
-and licenses are independent of the renderer implementation.
+Their input counts are 4,351 datacenter features and 704 dam features. Cesium may
+expand multipart geometries into multiple entities; entity and stem counts are
+different measurements. This change does not refresh or relicense the datasets.

docs/KNOWN-ISSUES.md

@@ -10,24 +10,6 @@ For the roadmap and open backlog, see the repository issue tracker.
 
 ## Open
 
-### Wildlife grid relies on the iNaturalist UTFGrid cell schema
-
-Status: Open (guarded fallback)
-
-The `/v1/grid/{z}/{x}/{y}.grid.json` endpoint is documented in the v1 and v2
-API docs (“Grid Tiles UTFGrid”), but the documented response only defines the
-UTFGrid `grid`, `keys` and `data` members; the per-cell records are not
-specified. Its 64×64 UTFGrid shape, keys and cell records
-are validated in full at the allow-list proxy. A schema change or unavailable
-tile retains its last good cells for at most one hour; a cold unavailable grid
-uses sampled observations with the same badges and screen buckets, without
-claiming complete worldwide coverage. Tests use
-synthetic fixtures with the locally inspected tile's exact structure. Retest
-and update the schema guard before accepting an upstream shape change. Grid
-and observation calls share the paced queue, provider budget and 429 cooldown;
-ordinary tile failures do not block observation queries.
-
-
 ### Street traffic can be slow/uneven when panning across dense city blocks
 Status: Open (partially mitigated)
 
@@ -89,9 +71,9 @@ Status: Open (owner-accepted 2026-07-08, documented)
   a few stragglers take one more poll.
 - **Born-grounded first poll:** a contact first seen on the ground with no altitude
   data renders at the geoid for ≤1 poll until its floor cell warms.
-- Verify floor-placement behavior with `scripts/qa-floor-verify.mjs` against a
-  running local app; set `QA_BASE_URL` when it is not on the default port
-  (`http://localhost:4173`).
+- Full context, improvement ideas, and the verification oracle
+  (`scripts/qa-floor-verify.mjs`):
+  `docs/superpowers/reports/2026-07-08-height-datum-handover.md`.
 
 ---