fix(maestro): persist GraalJS state via output - #6171
Closed
EdgeClaws wants to merge 1 commit into
Closed
Conversation
This was referenced Aug 21, 2026
Author
|
Superseded by #6172, which now contains this unchanged YAML-only GraalJS state-persistence commit plus all current Maestro test repairs in one direct develop-based PR. |
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.
Scope
Isolates the GraalJS compatibility repair from the existing Maestro-test fixes.
Cross-command JavaScript state now uses Maestro
output.*instead of localvarassignments, covering the shared account/wallet helpers and affected existing flows.Verification
git diff --checkStack base for the clean Maestro-fixes review branch.