feat(LWD): call addAddress in broadcast instead of recipient

[dilaouid]

✅ Checklist

• npx changeset was attached.
• Covered by automatic tests.
• Impact of the changes:
  • addAddress is not called in the Recipient step anymore but during the Broadcast

📝 Description

Changes the placement of addAddress of the RecentAddressStore
Not called in Recipient step but when the tx is broadcasted successfully

❓ Context

• JIRA or GitHub link:

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.
• Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

4 Skipped Deployments

Project	Deployment	Review	Updated (UTC)
ledger-live-github-bot	Ignored		Jan 2, 2026 10:49am
native-ui-storybook	Ignored		Jan 2, 2026 10:49am
react-ui-storybook	Ignored		Jan 2, 2026 10:49am
web-tools	Ignored		Jan 2, 2026 10:49am

[github-actions]

⚠️ E2E tests are required

Changes detected require e2e testing before merge (even before asking for any review).

🖥️ Desktop

-> Run Desktop E2E

• Select "Run workflow"
• Branch: feat/change-add-address-placement
• Device: nanoSP or stax

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud