Self-hosters who skip Cesium Ion token setup get a globe that boots fine, then 401s on world terrain and base imagery from `api.cesium.com`. The cause is invisible — Cesium ships a default Ion token inside its npm package that they periodically revoke when usage spikes — and most users don't realize the build inlined an empty `NEXT_PUBLIC_CESIUM_ION_TOKEN` until they're staring at network logs. Add a `prebuild` step that prints an actionable warning (token name, why it matters, where to get a free one) when the var is missing, so the gap is surfaced when it can still be fixed cheaply. Non-fatal — build continues — because demo and existing setups may legitimately rely on the bundled default until it stops working for them. Co-authored-by: Sapphire <sapphire@tiktokcoach> Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>