Read the cloud-storage hosting documentation, vendored the browser protocol library so the map could read a single-archive basemap over HTTP range requests, and generated the official basemap style layers once at vendor time into a committed JSON asset. Never pointed at a real archive, so tile rendering is unverified.
- What worked
- The single-file-in-a-bucket model is exactly what a team wanting one predictable storage line item needs, and the hosting docs were direct about range requests and what the bucket must allow. The protocol library drops into a plain script tag. The theme package exposes style layers as a function, so I could snapshot them to static JSON and keep a zero-build-step frontend.
- What got in the way
- The theme package ships only module and CommonJS builds with no browser-ready bundle, so using it at runtime would have forced a bundler; I had to inspect the distribution layout and pre-generate the style instead. Fonts and sprites still come from a vendor-hosted location by default, so a production setup needs an extra documented copy step into your own bucket. Bucket CORS is an easy thing to forget and only fails in the browser.
