The Cesium camera port moves into render/cesium/camera.js, with the
listener list and position conversion shared from common.js. It now
covers flights (flyTo, flyToBounds, cancelFlight, flying), lookAt and
release, command hooks, and a flightEnd event for the flights it starts.
A flight's end that Cesium raises inside one of the port's own calls is
delivered once Cesium's call returns, so its callback sees the flight
let go of. A flight Cesium declines to start, mid scene-mode morph,
ends as cancelled instead of never settling.
Flight traces run in Node on the recorder's headless camera with a
virtual clock; the browser harness keeps the instant traces.
The startup fly-in, landmark and viewport flights, share-link restore
and the shell's camera state now go through the port. camera.js and
sharelink.js leave the Cesium allow-list.
The first camera-family slice. The camera port's events move into a
shared module (render/camera/events.js) that the stub and the Cesium
port both use: listener lists, delivery with errors reported, and the
contract's per-listener `changed` measure.
The Cesium port gains:
- camera.on: `changed` measured per listener on every tick, where Cesium
measures its single threshold (the counts match Cesium's own at each
threshold); moveStart and moveEnd relayed from Cesium's camera;
- camera.viewRectangle, in degrees (now in CESIUM_CHECKS);
- lon and lat in pose, and NaN where Cesium has no cartographic position.
Code that still holds the viewer reaches the renderer through
rendererOf(viewer); the application renderer binds it on create and
unbinds on destroy.
The HUD reads its telemetry from the camera port and no longer imports
Cesium (off the allow-list). The share link writes the hash from the
pose. Its restore path stays on the viewer's camera for a later slice.
Behaviour changes:
- The share link listens to `changed` at its own 0.5 threshold, not at
whatever global threshold layers had set, and also to moveEnd, so the
hash always catches up with where the camera comes to rest.
- The HUD's and share link's camera callbacks run from the port's single
relay, ahead of other moveStart/moveEnd listeners, and a throw in one
is reported to the renderer's error listeners instead of escaping from
Cesium's render.