redesign how it works as four numbered steps with highlighted commands

read the archive size in the intro from /api/map instead of hardcoding it

pin the space on the profile

serve the page with bun html imports, tailwind, and split server and client modules

publish the yellow atlas design with bun s3 documentation

launch the self-hosted global map with live transfer stats

enable private http caching and asset revalidation

measure initial and navigation map idle times

expose upstream range timing for map performance checks

document successful live s3 verification

validate archive version on upstream range reads

add private bucket pmtiles map served by bun

initial commit