ci: skip smart E2E selection for PRs targeting stable branch

[jvbriones]

Description

Extends the existing release/* skip logic in the Smart E2E Selection action to also skip AI-driven test selection when a PR targets stable. PRs to stable (like hotfixes) should always run the full E2E suite, same as release branches.

Changelog

CHANGELOG entry:

Related issues

Fixes:

Manual testing steps

Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I've followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I've included tests if applicable
• I've documented my code using JSDoc format if applicable
• I've applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Performance checks (if applicable)

• I've tested on Android
  • Ideally on a mid-range device; emulator is acceptable
• I've tested with a power user scenario
  • Use these power-user SRPs to import wallets with many accounts and tokens
• I've instrumented key operations with Sentry traces for production performance metrics
  • See trace() for usage and addToken for an example

For performance guidelines and tooling, see the Performance Guide.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

---

Note

Low Risk
Low risk CI-only change that extends existing release-branch exemptions to the stable branch; impact is limited to which E2E suites run and whether pr-not-ready-for-e2e is auto-applied.

Overview
Extends the existing release-branch CI behavior to the stable branch.

The smart-e2e-selection composite action now skips AI suite selection (falling back to running the full E2E suite) when the PR base ref is release/* or stable, and updates skip messaging accordingly. The auto-label workflow for pr-not-ready-for-e2e also ignores PRs targeting stable, and the E2E decision tree docs are updated to reflect these exemptions.

^{Reviewed by Cursor Bugbot for commit 0966726. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud