doing · High priority

Minecraft Full Player HTML in Go

The full Go player renderer now has an SEO-isolated public canary on ?renderer=go, strict single- and dual-edition response validation, automatic PHP fallback, and live Command Center monitoring for standard, caped, and Bedrock profiles. Its HTML carries complete canonical, robots, Open Graph, Twitter, profile and structured image metadata. The canary includes accessible navigation, persistent themes, shared site metadata, a compact footer, profile tools, protected-versus-refreshable states, and a responsive 3D viewer backed by a server-rendered static skin preview when JavaScript or WebGL is unavailable. Static styling and viewer interactions now ship as versioned, cacheable assets instead of being repeated in every HTML response, while player-specific viewer URLs and names remain escaped data attributes. The viewer now closes the main PHP interaction gap with walk, stand and fly poses, animation and rotation controls, nametags, zoom, reset, and a same-origin PNG screenshot action. Its static body render is deferred unless WebGL fails, with a noscript fallback retained for non-JavaScript visitors; the critical head is preloaded while lower asset cards use native lazy loading and asynchronous decoding. A reversible dispatcher uses stable percentage bucketing for ordinary human profile views while keeping bots, refreshes, errors, language variants and explicit renderer=php requests on the PHP control. The first measured cohort is running at one percent. Aggregate outcomes now survive Go service restarts in a private systemd state directory, and Command Center holds the cohort until at least 100 genuine sampled views, 24 hours of observation, and zero safe fallbacks have been recorded. Observer probes remain separate from real visitors. Deploy-time checks independently enforce the PHP control, sampled dispatcher, persistence, and explicit canary paths.