Skip to content

docs(app-test-cases): refresh Maestro feature-compat — local + cloud both on v2.5.1#359

Merged
jjackson merged 1 commit into
mainfrom
emdash/avd-yt6cu
May 19, 2026
Merged

docs(app-test-cases): refresh Maestro feature-compat — local + cloud both on v2.5.1#359
jjackson merged 1 commit into
mainfrom
emdash/avd-yt6cu

Conversation

@jjackson
Copy link
Copy Markdown
Owner

Summary

Refreshes the "cloud emulator's bundled Maestro (1.36-ish per its CLI banner)" note in skills/app-test-cases/SKILL.md:262. The AMI has been on Maestro v2.5.1 since the 2026-05-12-2142 bake (pinned in infra/mobile-ami/scripts/30-maestro.sh in ace-web). This session also upgraded local Maestro from v2.3.0 → v2.5.1 to match.

The lag table is preserved as drift-prevention reference (re-baseline if versions ever diverge again) and the leep visibilityPercentage origin story is kept for context — but flagged as historically inactive on the current AMI.

Follow-up to #358 (probe1 timeout fix). With this PR:

  • Local Maestro: v2.5.1 (upgraded this session)
  • Cloud AMI Maestro: v2.5.1 (deployed 2026-05-12)
  • Both pinned to the same dadb-1.2.10 line, no protocol drift

Test plan

  • unzip -l ~/.maestro/lib/maestro-client.jar | grep .apk confirms maestro-app.apk + maestro-server.apk still at root in v2.5.1 (driver-extract path unaffected)
  • maestro --version returns 2.5.1
  • No code changes — docs only

🤖 Generated with Claude Code

…both on v2.5.1

The "cloud emulator's bundled Maestro (1.36-ish per its CLI banner)"
note was stale — the AMI has been on Maestro v2.5.1 since the
2026-05-12-2142 bake (pinned in infra/mobile-ami/scripts/30-maestro.sh
in ace-web). Local was just upgraded to v2.5.1 to match.

Lag table preserved as drift-prevention reference (re-baseline if
versions ever diverge again) and the leep visibilityPercentage origin
story is kept for context — but flagged as historically inactive on
the current AMI.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jjackson jjackson merged commit 3f70aec into main May 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant