[P0] Rebaseline Electrobun roadmap/docs now that WGPU shipped upstream

[devallibus]

Summary

Electrobun's official March 4, 2026 WGPU release changes the assumptions in gametau's Electrobun docs and roadmap. The repo still describes GPUWindow/native GPU rendering as future upstream work, which is now stale.

Announcement:

• https://blackboard.sh/blog/wgpu-in-electrobun/

Why this matters

• The README and Electrobun decision doc currently frame native GPU support as not yet shipped upstream.
• That stale framing makes the current roadmap misleading.
• We need a new support plan that distinguishes what exists now from what is still unproven in gametau itself.

Suggested scope

• Update the README and Electrobun decision doc to reflect the March 4, 2026 release.
• Split Electrobun support into explicit tracks:
  • BrowserWindow / webview
  • BrowserWindow + <electrobun-wgpu> embedded GPU surface
  • pure GpuWindow
• Reclassify which existing Electrobun issues are still blocked vs newly actionable.

Acceptance criteria

• Public docs no longer describe Electrobun GPU support as a future upstream dependency.
• The roadmap clearly distinguishes shipped Electrobun capabilities from unimplemented gametau integration work.
• Existing Electrobun issue references are updated to the new baseline.

Related

• [Tracking] Monitor Electrobun upstream releases for GpuWindow availability #116
• [Design] RenderAdapter interface for non-DOM rendering paths #117
• [Design] Non-DOM InputAdapter for GPUWindow keyboard/mouse events #118
• Experimental Electrobun: auto-detect runtime in scaffold and examples before falling back to WASM #127

[devallibus]

Closed by #168. README/changelog wording is now rebaselined to the post-WGPU shipped state, and the remaining Electrobun work is tracked as release follow-up rather than upstream-blocked work.