- The map source controller waits for a base that loads as it is shown
(the globe engine's tilesetReady) before it takes the stack before it
down: one that fails throws there, so that stack and its imagery stay
and the error is reported, as from any failed switch. The Cesium map
engine has no tilesetReady, so its switches are unchanged.
- A failed default renderer load is tried again by the next call, and
the standalone page's early load does not report a failure nobody
awaited yet.
- The adapter ratchet's on-demand import rule refuses a default or an
empty destructuring.
- The stub boot check fails a layer whose manager answers false rather
than throwing, or that is not on (or off) afterwards; a field drawn
counts as drawn; the dev server is closed when the browser cannot
start.
- dev/stub-app/main.js starts the standalone application on the stub
renderer with only the contract's required members (?capabilities=all
gives it every capability) and steps its frames.
- npm run qa:stub-boot serves the application's own page with that entry,
and fails when any Cesium module or asset is requested (the stylesheet
the build's Cesium plugin links into every page is reported), on a page
or console error, or when a data layer fails to turn on or off. A feed's
failed response and the dev server client's own errors are reported;
--strict also fails a layer that drew nothing.
- The browser CI job runs it.
- RENDERER-CONTRACT.md and CURRENT-STATE.md describe the application on
the stub and the boot check.