…dpoint cp-7.71.1 cp-7.72.0 (#28098)

- fix: point DIGEST_API_URL to production endpoint (#28088)

## **Description**

<!-- 1. What is the reason for the change? The fallback URL for
`DIGEST_API_URL` was pointing at the development endpoint. -->
<!-- 2. What is the improvement/solution? Switch the hardcoded fallback
to the production endpoint so that builds without an explicit env var
hit production. -->

Switches the hardcoded fallback value for `DIGEST_API_URL` in
`AppConstants.ts` from the dev endpoint
(`digest.dev-api.cx.metamask.io`) to the production endpoint
(`digest.api.cx.metamask.io`).

Also moves the `@metamask/sdk-communication-layer` import to the top of
the file to follow alphabetical import ordering.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes:

## **Manual testing steps**

N/A

## **Screenshots/Recordings**

### **Before**

N/A

### **After**

N/A

## **Pre-merge author checklist**

- [x] 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).
- [x] I've completed the PR template to the best of my ability
- [x] I've included tests if applicable
- [x] I've documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] 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.

## **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.

<!-- Generated with the help of the pr-description AI skill -->

Made with [Cursor](https://cursor.com)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk: only changes a constant fallback URL and import ordering.
Main impact is that builds without `DIGEST_API_URL` will now call the
production digest service instead of the dev endpoint.
> 
> **Overview**
> Updates `AppConstants.DIGEST_API_URL` to default to the production
`https://digest.api.cx.metamask.io/api/v1` endpoint when the
`DIGEST_API_URL` env var is not set.
> 
> Also reorders the `DEFAULT_SERVER_URL` import to match expected import
ordering.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
9d584a4. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
[8603e1c](8603e1c)

Co-authored-by: Xavier Brochard <xavier.brochard@consensys.net>

This PR updates the change log for 7.71.1. (Hotfix - no test plan
generated.)

---------

Co-authored-by: metamaskbot <metamaskbot@users.noreply.github.com>
Co-authored-by: chloeYue <chloe.gao@consensys.net>

- Keep ## [7.71.1] hotfix + full ## [7.71.0] from stable.
- Footer: [Unreleased] v7.71.1...HEAD; [7.71.1] v7.71.0...v7.71.1; [7.71.0] unchanged.
- Normalize Predict withdraw bullet to ASCII apostrophe.

Made-with: Cursor

…ne (#27532)

Revert ASCII normalization for stable-merge conflict resolution.

Made-with: Cursor

# 🚀 v7.71.1 Testing & Release Quality Process

Hi Team,
As part of our new **MetaMask Release Quality Process**, here’s a quick
overview of the key processes, testing strategies, and milestones to
ensure a smooth and high-quality deployment.

---

## 📋 Key Processes

### Testing Strategy
- **Developer Teams:**
Conduct regression and exploratory testing for your functional areas,
including automated and manual tests for critical workflows.
- **QA Team:**
Focus on exploratory testing across the wallet, prioritize high-impact
areas, and triage any Sentry errors found during testing.
- **Customer Success Team:**
Validate new functionalities and provide feedback to support release
monitoring.

### GitHub Signoff
- Each team must **sign off on the Release Candidate (RC)** via GitHub
by the end of the validation timeline (**Tuesday EOD PT**).
- Ensure all tests outlined in the Testing Plan are executed, and any
identified issues are addressed.

### Issue Resolution
- **Resolve all Release Blockers** (Sev0 and Sev1) by **Tuesday EOD
PT**.
- For unresolved blockers, PRs may be reverted, or feature flags
disabled to maintain release quality and timelines.

### Cherry-Picking Criteria
- Only **critical fixes** meeting outlined criteria will be
cherry-picked.
- Developers must ensure these fixes are thoroughly reviewed, tested,
and merged by **Tuesday EOD PT**.

---

## 🗓️ Timeline and Milestones

1. **Today (Friday):** Begin Release Candidate validation.
2. **Tuesday EOD PT:** Finalize RC with all fixes and cherry-picks.
3. **Wednesday:** Buffer day for final checks.
4. **Thursday:** Submit release to app stores and begin rollout to 1% of
users.
5. **Monday:** Scale deployment to 10%.
6. **Tuesday:** Full rollout to 100%.

---

## ✅ Signoff Checklist

Each team is responsible for signing off via GitHub. Use the checkbox
below to track signoff completion:

# Team sign-off checklist
- [ ] Mobile Platform

This process is a major step forward in ensuring release stability and
quality. Let’s stay aligned and make this release a success! 🚀

Feel free to reach out if you have questions or need clarification.

Many thanks in advance

# Reference
- Testing plan sheet -
https://docs.google.com/spreadsheets/d/1tsoodlAlyvEUpkkcNcbZ4PM9HuC9cEM80RZeoVv5OCQ/edit?gid=404070372#gid=404070372

Merge origin/stable into release/7.72.0 after 7.71.1 landed on stable.

Conflict resolution:
- app/constants/ota.ts: keep release/7.72.0 OTA placeholder (vX.XX.X)
- CHANGELOG.md: integrate stable (7.71.1 hotfix + footer); no ## [7.72.0] on release line yet

Merge with Create a merge commit — do NOT squash.

Made-with: Cursor