fix(ci): standardize Appium Playwright JSON report filename

[cmd-ob]

Description

Standardize the Playwright JSON file inside each Appium CI artifact to playwright-report.json, matching the default results-file-pattern in the upcoming playwright-test-health-report github-tools action (MetaMask/github-tools#262).

Suite/shard identity stays in the artifact name (playwright-json-report-{test-suite-name}); only the inner zip filename is fixed. New Appium smoke tags can be added without changing the daily report workflow config.

Changelog

CHANGELOG entry: null

Related issues

Refs: Follow-up to Appium JSON artifact upload — prepares for github-tools playwright-test-health-report (MetaMask/github-tools#262).

Manual testing steps

N/A — CI-only change. Post-merge verification on main:

• Confirm Appium jobs still upload playwright-json-report-* artifacts.
• Open an artifact zip and verify the JSON file is named playwright-report.json (not {suite-name}.json).

Screenshots/Recordings

Before

N/A — CI workflow change only.

After

N/A — CI workflow change only.

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

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.

Made with Cursor

[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.

[github-actions]

🔍 Smart E2E Test Selection

• Selected E2E tags: None (no tests recommended)
• Selected Performance tags: None (no tests recommended)
• Risk Level: low
• AI Confidence: 95%

click to see 🤖 AI reasoning details

E2E Test Selection:
The PR contains exactly 2 changed files:

1. .github/workflows/run-appium-e2e-workflow.yml: Changes the PLAYWRIGHT_JSON_OUTPUT_FILE environment variable from a dynamic path tests/test-reports/playwright-json/${{ inputs.test-suite-name }}.json to a fixed filename tests/test-reports/playwright-json/playwright-report.json. The suite identity is preserved in the artifact name prefix (playwright-json-report-*). This is a pure CI infrastructure fix for the GitHub tools playwright-test-health-report integration — it only affects how the JSON report file is named/uploaded, not what tests run or how they execute.

2. tests/playwright.smoke-appium.config.ts: Updates a single comment line to reflect the new fixed filename behavior. This is a comment-only change with zero functional impact.

Neither change affects:

• Any app source code
• Any E2E test logic, selectors, page objects, or flows
• Any test execution behavior
• Any performance-sensitive code paths

This is a pure CI reporting infrastructure fix. No E2E test tags need to be run to validate this change, as it only affects artifact upload paths in the CI workflow.

Performance Test Selection:
No app code changes were made. The PR only modifies CI workflow artifact upload paths and a comment in the Playwright config. There is no impact on any performance-sensitive code paths, rendering, or user flows.

View GitHub Actions results

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.28%. Comparing base (9cc924c) to head (165d1a2).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #31756   +/-   ##
=======================================
  Coverage   83.28%   83.28%           
=======================================
  Files        5750     5755    +5     
  Lines      149002   149088   +86     
  Branches    34819    34854   +35     
=======================================
+ Hits       124092   124170   +78     
- Misses      16553    16556    +3     
- Partials     8357     8362    +5     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.