fix(maestro): repair recent existing test flows - #6172
Draft
EdgeClaws wants to merge 13 commits into
Draft
Conversation
The tag was C000029 but the flow is C000029a; a C000029a tag-filtered run silently skipped it. Match the tag to the test ID. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
EdgeClaws
force-pushed
the
qa/maestro-recent-test-fixes
branch
from
August 21, 2026 22:17
b4a24cf to
f995b79
Compare
This was referenced Aug 21, 2026
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.
Direct review and merge PR from current EdgeApp/develop. This is the single branch for the recent net repairs to existing Maestro tests and the YAML-only GraalJS state-persistence repair.
Commit order:
Validation completed: git diff --check and YAML parsing for every changed flow/helper. No device run was performed for this reconstruction.