Validate Godot Android Amy.gd dictionary API - #10
Closed
linuxificator wants to merge 11 commits into
Closed
linuxificator wants to merge 11 commits into
linuxificator wants to merge 11 commits into
Conversation
linuxificator
changed the base branch from
feature/godot-android-raw-wire-poc
to
upstream/android-oboe
August 23, 2026 17:20
linuxificator
changed the base branch from
upstream/android-oboe
to
validation/godot-service-only-ci-base
August 23, 2026 17:22
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
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.
Fork-local validation PR for Stage 2. The Android Godot proof uses the shared Amy.gd high-level Dictionary API; Amy.gd itself owns the pure-Java AmyClient/LocalSocket transport to the independent :amy service. CI verifies there is no direct AmyClient/sendWire use in main.gd, no Android AmySynth GDExtension or native client library, exact Dictionary-to-wire output at runtime, and the separate service process. No upstream/Shorepine PR is created.