The globe's nerd stats are instruments in the scene

Owner decision 2026-10-06: the globe tells its numbers where they belong instead of in a table. instruments.js adds
one three.js group to globe.gl's scene and a DOM overlay of chips:
- the Sun: a ray and a bead over the subsolar point (with the irradiance), the day/night line, the golden hour and
  the three twilights, the declination, the noon and midnight meridian, and the analemma at this hour, its stretch to
  the next equinox or solstice brighter;
- a focused post's place: its horizon, its Sun's line and height, and its day lit on its latitude, with one chip for
  the place, the phase, the solar time, the elevation and the day's length;
- the tropics and polar circles (the axial tilt), the CDN ring, the view's centre and spread, and rings around the
  posts in view;
- a small orrery in the top left corner, re-anchored to the camera before each render, with the Earth–Sun distance,
  the seasons, the next equinox or solstice and the next perihelion or aphelion stacked under it;
- the frame rate as a ring around the globe; the rest (points, textures, countries, renderer) as a legend.

The chips are placed after each frame globe.gl draws, clear of each other, the moment's caption, the orrery and the
legend, and slide back inside the canvas at its edge; country names keep clear of them. Geometry changes only inside
a wake globe.js already made, so an idle globe still draws nothing. three.js's classes come from globe.gl's own
objects, looked for before each render until its globe is in the scene. A phone's banner draws the day/night line
and the subsolar point; full screen draws everything, and a globe built in the banner now moves its camera back when
opened full screen.

GlobePanel loses both tooltips and the one-second poll that read every post into a table; the Sun's rows stay as
screen-reader text, and a failed start says so. Seven keys only the tooltips used are gone.

GlobeTests (desktop with a located post written from Milano and pinned, in both themes and turned to the subsolar
point; a phone's banner, full screen and back; an idle globe drawing no frame) pass. Under SwiftShader the instruments
cost 1–3 ms of a ~50 ms frame and under 0.1 ms of script; FeedPerfTests' heaps are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

wwwroot/vendor/globe/SOURCES.md

@@ -27,3 +27,14 @@ few areas without a code (Kosovo, Somaliland, Northern Cyprus, …).
 
 The service worker leaves this folder out of the offline precache (`service-worker.published.js`): the feed page
 loads it the first time it shows the globe.
+
+**Before upgrading globe.gl**, check what the app relies on inside the bundle, since it never sees `window.THREE`:
+- **`wwwroot/js/instruments.js`** takes three.js's classes from objects globe.gl made (`classesOf`):
+  - the globe mesh, whose material is `globeMaterial()`, inside a `Group`;
+  - the graticules, a `LineSegments` with a `LineBasicMaterial`, added hidden;
+  - an empty `Mesh`, for `BufferGeometry` and `MeshBasicMaterial`;
+  - the camera's `Vector3`.
+
+  It also relies on the scene's `onBeforeRender` and `onAfterRender` running on every frame. If any of these change,
+  the instruments fall back to the ring and the legend, and the e2e `GlobeTests` fail on `built`.
+- **`wwwroot/js/globe.js`** relies on the texture class of the day map and on the globe material's shader chunks.