refactor(core): backup success after I/O-related errors

[romanz]

In case the host is unavailable, #6651 will stop sending ButtonRequests.

This PR makes sure that show_backup_success() won't fail if there was an error during the backup process - so the success screen will be shown to the user.

Currently THP debug builds fail with an assertion if the FW tries to write again before the previous write was ACKed, so this PR makes sure that after an error no ButtonRequest will be sent after #6651 is merged.

Note: writing the secret to storage is not affected by this change, since it doesn't access the active context / button request handler.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a4a09f05-663a-46ef-aa06-cecda0161c8f

📥 Commits

Reviewing files that changed from the base of the PR and between 993dbad and 45c29c9.

📒 Files selected for processing (1)

• core/src/apps/management/reset_device/__init__.py

---

Walkthrough

The change modifies error-handling scope in a backup process by expanding the continue_on_errors("Backup in progress") suppression context. Previously, this error suppression applied only to the backup info generation conditional. The reorganization now places the backup info generation, master secret/storage writes, and backup-success UI all within the same error-suppression context, ensuring I/O-related errors during the backup block don't propagate to subsequent operations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	The description explains the purpose and context well, but lacks the structured template elements (PR setup, development status markers) required by the repository guidelines.	Add structured sections: assign yourself, add to Firmware project with Priority/Team/Sprint, and set appropriate development status (e.g., 'Needs Review').

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: moving backup success handling under error-suppression context to ensure UI displays even after I/O errors.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch romanz/2604/backup-success

Warning

Review ran into problems

🔥 Problems

Timed out fetching pipeline failures after 30000ms

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

en main(all)

model	device_test	click_test	persistence_test
T2T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3B1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3T1	test(all) main(all)	test(all) main(all)	test(all) main(all)
T3W1	test(all) main(all)	test(all) main(all)	test(all) main(all)

Latest CI run: 25156240778

[obrusvit]

utACK

The with continue_on_error(..) context extended to the whole perform_backup + show_backup_success interaction with writing to storage in between.