A second game that cannot draw says so: /range and /example get the panel #340

On this tree neither src/range/main.ts nor src/example/main.ts catches createRenderer, which throws with the driver's own shader info log (src/engine/renderer.ts) — the exact Windows-in-Edge failure #307 reported. Both pages go black with nothing written anywhere, and neither has a line to paste. With the support line behind the door (#339) and the panel in the shell, both are a few lines of wiring.

Done looks like

• [ ] /range and /example carry the panel, filled in when it is opened rather than per frame, with every field either true or absent — the example has no pointer, no keyboard lock and no clock to report, and absent reads as absent, never undefined.
• [ ] A createRenderer that throws at boot is caught in both entries: a heading, a sentence and the driver's log land where the game would have been, the loop is never started, and the server-rendered rest of the page — the range's board, the example's prose, the nav, the terminal line — is still there and still usable.
• [ ] The range's 2D fallback keeps its meaning: a browser with no WebGL2 at all gets the fallback it has today, a browser whose shader was refused gets the sentence, and the page says which of the two happened.
• [ ] The copy button copies what is shown, on all three pages.
• [ ] Tests that would fail without this, headless through fakePage and each game's stage helper: a stub whose createRenderer throws leaves the page alive with the message and the loop unstarted; each game's line is assembled once per open from the stubbed facts; a game with no keyboard lock leaves that clause out.
• [ ] The README says where the line is and asks a bug report to carry it.

Files I expect to change

src/range/main.ts and src/range/boot.test.ts, src/example/main.ts and src/example/boot.test.ts, src/pages/range.ts, src/pages/example.ts, README.md.

Risks

• #87 (a frame that throws says so and stops) is this surface for a later failure. Reuse it; do not add a second panel.
• The example is deliberately the smallest game on the package. Its share of this is a few lines, or it stops being the thing the guide points at.
• WEBGL_debug_renderer_info is refused by some browsers. Absent is absent — do not fingerprint around it.

Suggested: Torque.

The issue that moves the support line behind the door is #344, not #339 — #339 was an empty probe and is closed. This issue's dependency has been moved to #344.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Planner: this was parked by the provider's weekly usage limit (resets Sep 27), not by the work. The run pushed nothing, so nothing in the issue is disproven. It stands as written and is ready again.