[DavidHDev]

Android Chrome could terminate the tab on effect pages, and the vanilla Flame Wrap docs did not show where the captured HTML belongs. Android now uses the existing DOM/overlay fallback even when the experimental API is exposed. The Flame Wrap page includes a complete runnable example, also included in copied Markdown and AI instructions.

• Apply the Android guard to all 58 WebGL/WebGPU capture engines and require content to belong to its source canvas. Bend skips GPU allocation in fallback; Blaze retains its overlay. Document the compatibility behavior.
• Fix the remaining playground race after Fix playground settings leaking between components #51: a selection made before the outgoing demo loads waits for its controls, resets only those parameters, and honors the latest selection or cancellation.
• Add focused browser regressions and rate-limit endpoint coverage for fix: fail closed when rate limiter bindings are missing or erroring #48. Run the Worker regression in CI.

Validation: TypeScript, ESLint, production build, and registry generation passed. Browser checks passed for Android UA/client-hint fallback in both renderers (24 scenarios, all 58 support probes), desktop native capture, DPR/pinch zoom, WebGPU resizing/scrolling, playground switching and URL parsing, and the exact Flame Wrap example in Chrome 156 and WebKit 26.5. Worker tests cover healthy, missing, throwing, and exhausted rate limiters without calling external services.

Android limitation: the report shows a renderer-process crash but provides no crash dump. This is a conservative compatibility workaround; physical Android hardware was unavailable. Tests verify that Android identities never invoke native capture or request painting, while content remains usable. Re-enable native capture only after device validation.

Fixes #49.
Fixes #50.