chore(runway): cherry-pick test: upload Test Plan JSON file to artifacts (#29347)

- test: upload Test Plan JSON file to artifacts (#29337)

<!--
Please submit this PR as a draft initially.

Do not mark it as "Ready for review" until this PR meets the canonical
Definition of Ready For Review in `docs/readme/ready-for-review.md`.

In short: the template must be materially complete (not just section
titles
present), all status checks must be currently passing, and the only
expected
follow-up commits must be reviewer-driven.
-->

## **Description**
Fix broken Test Plan JSON link by uploading as GitHub Actions artifact
instead of gh-pages (which is blocked by branch protection).
Changes
- Replace gh-pages upload with actions/upload-artifact@v4 (unzipped)
- Update PR comment to link to build workflow for artifact access
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: null

## **Related issues**

Fixes:
https://consensyssoftware.atlassian.net/browse/MCRM-69
## **Manual testing steps**

```gherkin
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**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

<!--
Every checklist item must be consciously assessed before marking this PR
as
"Ready for review". A checked box means you deliberately considered that
responsibility, not that you literally performed every action listed.

Unchecked boxes are ambiguous: they are not an implicit "N/A" and they
are not
a silent "skip". See `docs/readme/ready-for-review.md` for the full
checklist
semantics.
-->

- [ ] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding

Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] 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](https://jsdoc.app/) format
if applicable
- [ ] I've applied the right labels on the PR (see [labeling

guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
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](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/edit-v2/401401446401?draftShareId=9d77e1e1-4bdc-4be1-9ebb-ccd916988d93)
to import wallets with many accounts and tokens
- [ ] I've instrumented key operations with Sentry traces for production
performance metrics
- See [`trace()`](/app/util/trace.ts) for usage and

[`addToken`](/app/components/Views/AddAsset/components/AddCustomToken/AddCustomToken.tsx#L274)
for an example

For performance guidelines and tooling, see the [Performance

Guide](https://consensyssoftware.atlassian.net/wiki/spaces/TL1/pages/400085549067/Performance+Guide+for+Engineers).

## **Pre-merge reviewer checklist**

<!--
Reviewer checklist items follow the same semantics as the author
checklist: an
unchecked box is ambiguous, a checked box means the reviewer consciously
assessed that responsibility. See `docs/readme/ready-for-review.md`.
-->

- [ ] 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.
[e741248](e741248)

Co-authored-by: sleepytanya <104780023+sleepytanya@users.noreply.github.com>

Author: runway-github[bot]

.github/workflows/build-rc-auto.yml

@@ -164,46 +164,15 @@ jobs:
           E2E_OPENAI_API_KEY: ${{ secrets.E2E_OPENAI_API_KEY }}
           E2E_GEMINI_API_KEY: ${{ secrets.E2E_GEMINI_API_KEY }}
 
-      - name: Upload test plan JSON to GitHub Pages
+      - name: Upload test plan JSON artifact
         if: always()
-        continue-on-error: true
-        run: |
-          VERSION="${{ needs.validate-and-find-pr.outputs.semver }}"
-          JSON_FILE="release-test-plan.json"
-
-          # Check if JSON file was generated
-          if [ ! -f "$JSON_FILE" ]; then
-            echo "No test plan JSON file found, skipping upload"
-            exit 0
-          fi
-
-          # Save JSON to temp
-          cp "$JSON_FILE" "/tmp/test-plan-${VERSION}.json"
-
-          # Configure git
-          git config user.name "github-actions[bot]"
-          git config user.email "github-actions[bot]@users.noreply.github.com"
-
-          # Fetch gh-pages branch or create it
-          git fetch origin gh-pages:gh-pages 2>/dev/null || echo "gh-pages doesn't exist yet"
-
-          # Switch to gh-pages
-          if git checkout gh-pages 2>/dev/null; then
-            echo "Switched to existing gh-pages branch"
-          else
-            git checkout --orphan gh-pages
-            git rm -rf . 2>/dev/null || true
-            git clean -fd 2>/dev/null || true
-          fi
-
-          # Create test-plans directory and copy JSON
-          mkdir -p test-plans
-          cp "/tmp/test-plan-${VERSION}.json" "test-plans/"
-
-          # Commit and push
-          git add test-plans/
-          git commit -m "Add test plan JSON for RC ${VERSION}" || echo "No changes to commit"
-          git push origin gh-pages
+        uses: actions/upload-artifact@v4
+        with:
+          name: test-plan-${{ needs.validate-and-find-pr.outputs.semver }}
+          path: release-test-plan.json
+          compression-level: 0
+          if-no-files-found: ignore
+          retention-days: 90
 
   slack-notification:
     name: Slack RC Notification

scripts/build-announce/test-plan-section.ts

@@ -199,10 +199,9 @@ export function buildTestPlanSection(testPlan: TestPlanResult): string {
   md += `---\n`;
   md += `*Generated by AI Test Plan Analyzer (${testPlan.model}) at ${testPlan.generatedAt}*\n\n`;
 
-  // JSON link for automation (version will be replaced by caller)
+  // JSON link - artifact is uploaded separately and available in the Actions run
   if (testPlan.version) {
-    const jsonUrl = `https://metamask.github.io/metamask-mobile/test-plans/test-plan-${testPlan.version}.json`;
-    md += `AI generated test plan (JSON): [test-plan-${testPlan.version}.json](${jsonUrl})\n\n`;
+    md += `AI generated test plan (JSON): Available as artifact \`test-plan-${testPlan.version}\` in the [build workflow](${process.env.BUILD_PIPELINE_URL || '#'})\n\n`;
   }
 
   return md;