You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR rebaselines the public Electrobun narrative after the upstream WGPU release and the milestone work that has already landed in gametau.
The immediate user-facing problem was that the repository still described Electrobun support in ways that were true before March 4, 2026 but are now stale. In practice that made the README and changelog lag the actual shipped product surface: scaffold/runtime auto-detection exists, create-gametau --desktop-shell electrobun exists, and the repo already contains BrowserWindow and GPUWindow example lanes.
Root cause
The original Electrobun evaluation language was written while WGPU support was still an upstream dependency and before the milestone work merged. The implementation moved forward through issues like #160, #161, #102, and PR #167, but the public docs still used older framing such as "experimental runtime" and "future upstream" style wording.
Fix
This diff updates the public-facing docs that are actually part of the GitHub repo history:
README.md now describes Electrobun as an explicit supported shell path rather than an abstract experimental provider path.
The Electrobun support section now distinguishes shipped functionality from remaining release follow-up work.
The roadmap text now points reviewers at the still-relevant follow-up items instead of upstream blockers that have already been passed.
CHANGELOG.md now records the earlier alpha/Electrobun work as historical context rather than current-state messaging.
I also aligned the local-only decision note in docs/ELECTROBUN-INTEGRATION-DECISION.md in my workspace, but /docs is ignored in this repository and is therefore not part of the reviewable GitHub diff.
Validation
This is a docs-only change. Validation for this PR was:
git diff --check
targeted repo searches to confirm the stale Electrobun wording was removed from the public docs touched here
Milestone context
Refs #159.
After reviewing the current implementation against the issue bodies, #99 and #127 also appear satisfied by already-merged work, but I left issue closure out of this PR so the review stays scoped to the doc rebaseline.
PR Review — claude-opus-4-6 (Claude Opus 4.6, 1M context)
Overall
Clean docs-only rebaseline. 8 additions, 6 deletions across 2 files. Every change replaces stale framing with language that matches the actual shipped state.
Verdict: Approve. No issues.
Changes reviewed
CHANGELOG.md — The v0.5.0 entry's "Experimental Electrobun runtime" phrasing is replaced with "Initial Electrobun runtime spike as an opt-in alpha path" and adds forward context noting this baseline was later expanded by v0.7.0. Accurate — the changelog now reads as historical context rather than current-state messaging.
README.md — 5 targeted edits:
"for experimental runtimes" → "for provider-backed runtimes such as Electrobun" — Correct. Electrobun is no longer experimental; it's a named, shipped provider path.
"Electrobun desktop bootstrap helpers (experimental)" → "...for explicit BrowserWindow and GPUWindow shell paths" — Removes the stale "experimental" label and adds specificity about what the adapter actually covers.
Roadmap status paragraph — Drops the generic "Update:" prefix and anchors to the March 6, 2026 date. Shifts framing from "Electrobun now ships..." (which reads as a changelog entry) to "As of [date], gametau ships..." (which reads as current state). The remaining work list correctly identifies it as gametau-internal follow-through, not upstream-blocked.
"What's not yet done" → "Remaining follow-up work" — Better tone. The old heading implied incompleteness; the new one frames it as planned next steps.
Roadmap section header "shipped → next steps" → "shipped → release follow-up" — More precise about where the work sits.
Observations
The PR body correctly notes that docs/ELECTROBUN-INTEGRATION-DECISION.md was aligned locally but isn't in the diff because /docs is gitignored. No action needed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR rebaselines the public Electrobun narrative after the upstream WGPU release and the milestone work that has already landed in
gametau.The immediate user-facing problem was that the repository still described Electrobun support in ways that were true before March 4, 2026 but are now stale. In practice that made the README and changelog lag the actual shipped product surface: scaffold/runtime auto-detection exists,
create-gametau --desktop-shell electrobunexists, and the repo already contains BrowserWindow and GPUWindow example lanes.Root cause
The original Electrobun evaluation language was written while WGPU support was still an upstream dependency and before the milestone work merged. The implementation moved forward through issues like
#160,#161,#102, and PR#167, but the public docs still used older framing such as "experimental runtime" and "future upstream" style wording.Fix
This diff updates the public-facing docs that are actually part of the GitHub repo history:
README.mdnow describes Electrobun as an explicit supported shell path rather than an abstract experimental provider path.CHANGELOG.mdnow records the earlier alpha/Electrobun work as historical context rather than current-state messaging.I also aligned the local-only decision note in
docs/ELECTROBUN-INTEGRATION-DECISION.mdin my workspace, but/docsis ignored in this repository and is therefore not part of the reviewable GitHub diff.Validation
This is a docs-only change. Validation for this PR was:
git diff --checkMilestone context
Refs
#159.After reviewing the current implementation against the issue bodies,
#99and#127also appear satisfied by already-merged work, but I left issue closure out of this PR so the review stays scoped to the doc rebaseline.