Value Statement

Maestro E2E tests are currently flaky and intermittently failing, which causes otherwise valid PRs to break after merge and blocks auto-generated dependency upgrade PRs from bots. This creates unnecessary noise, slows down development velocity, and reduces confidence in CI signal quality.

The goal of this issue is to identify and fix flaky E2E tests, improve test robustness, and ensure the test suite provides stable and reliable validation for Maestro changes.

Definition of Done for Engineering Story Owner (Checklist)

• Flaky E2E tests are identified and fixed or reworked

• Maestro E2E test suite runs reliably across multiple CI runs

• PRs are no longer blocked by intermittent E2E failures

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.