Offer classic and Godot games from one shared entrance - #6
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Visitors now enter through a shared chooser at
/, with the full React game at/classic/and the standalone Godot prototype at/seed/. The chooser describes each game's scope, technology, origins, and the contributions of TechLuddite, Gemini, Claude, and Codex. Neither game starts automatically.This includes the previously local React observatory redesign and Godot fabrication-room implementation, their regression tests, cross-version navigation, and a single Pages deployment containing both games. Classic save keys are preserved; Godot uses an independent browser save. Release verification checks the deployed chooser, classic HTML, Godot HTML/data, and WASM availability against the deployed commit.
Godot performance remains an open issue. The ambient-audio source leak was fixed, but the user reported continued excessive resource use and requested shutdown.
docs/PERFORMANCE-HANDOFF.mdrecords the evidence, local shutdown constraint, and required testing from another machine. The chooser prominently marks the prototype's unresolved performance status.Validation: GitHub Actions passed TypeScript checks, 128 classic simulation tests, 23 Godot checks and a scene smoke test, both builds, 12 chooser/classic browser tests, and 8 Godot tests across Chromium and Firefox. Desktop and mobile chooser screenshots were reviewed. The remote Godot browser suite uses a virtual display and an explicitly enabled Mesa software graphics device. No local servers, browsers, or game engines were restarted. Passing CI does not resolve the outstanding laptop performance investigation.