Shared planar layer composition

Complete ordering for media, labels and supported styles

Development SDK 0.3.0-dev.8823863c (core 8823863c2fc779e8784df36860a73bf41fb431f3) passes the same 7-check, 12-phase script on Native and browser main thread/Worker at DPR1/2. This is local development delivery; devices, external platforms and formal releases remain pending.

The shared Mercator view has zero pitch/roll and no terrain/extrusion. Raster media, backgrounds, icons/text, heat and existing line/fill effects use complete layer order. Existing addLayer/moveLayer/setStyle methods remain; probe commonPlanarLayerComposition. Globe, tilt, terrain and custom line-animation/media combinations keep their existing restrictions.

Reordering and compatible diff retain stable layer/source identities, caches and in-flight resources. Invalid candidates retain the previous actual frame. Materials are prepared as a full batch; limits fail instead of truncating fragments. Current and parent textures share 512 fragments, 128 media layers and 64 MiB deduplicated texture budgets. An additional 64 MiB vertex budget covers live and staged candidates with RAII release. The previous 4096 image-edge/32 MiB source limits, 1024 tile edges and joint symbol/heat/line budgets remain. Queries follow shared layer order and original identities with existing conservative footprints, not texture-alpha picking.

The complete public script uses original nonuniform PNG, PBF glyphs and blue/green fade tiles. Opaque raster center/nonuniform probes and solid overlays compare hosts strictly. Existing translucent heat/line effects retain Native SRGB linear-space blending versus browser UNORM channel-space blending; per-channel differences remain, while position, order, occlusion, queries and DPR are checked. Reordering, unchanged invalid/diff frames, asynchronous child arrivals and a real 2000 ms fade retain text/icon overlays and queries. Localhost3306 is a screenshot barrier; drivers wait actual 750 ms/1600 ms without a script fake clock.

The complete HTML/CSS/JavaScript example runs from the downloaded SDK/web directory through an HTTP server. Both buttons and the click handler are included; it has no acceptance-barrier dependency.