Add Rust-backed legacy recovery flow to Locker web

[ua741]

Summary

• add Legacy recovery APIs, models, and password-reset flow to rust/contacts
• expose the Legacy surface through the wasm bindings and ente-contacts-web
• add the Locker Legacy drawer and mobile-aligned owner/trusted-contact flows
• stop sending User-Agent from browser wasm requests to avoid the Firefox CORS failure

Validation

• cargo check --manifest-path rust/contacts/Cargo.toml
• cargo check --manifest-path web/packages/wasm/Cargo.toml
• cargo check --manifest-path mobile/packages/rust/rust/Cargo.toml
• yarn lint
• yarn workspace locker next build

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​electron-builder@​26.0.14
	npm/​clip-bpe-js@​0.0.6
	npm/​any-shell-escape@​0.1.1
	npm/​@​types/​auto-launch@​5.0.5
	npm/​compare-versions@​6.1.1
	npm/​chokidar@​4.0.3
	npm/​@​types/​node@​24.12.0
	npm/​cross-env@​10.1.0
	npm/​electron-log@​5.4.3
	npm/​comlink@​4.4.2
	npm/​concurrently@​9.2.1
	npm/​auto-launch@​5.0.6
	npm/​ajv@​8.17.1
	npm/​electron@​41.0.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		HTTP dependency: npm @electron/rebuild depends on https://github.com/electron/node-gyp#06b29aafb7708acef8b3669835c8a7857ebc92d2 Dependency: @electron/node-gyp@https://github.com/electron/node-gyp#06b29aafb7708acef8b3669835c8a7857ebc92d2 Location: Package overview From: ? → npm/electron-builder@26.0.14 → npm/@electron/rebuild@3.7.2 ℹ Read more on: This package | This alert | What are http dependencies? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Publish the HTTP URL dependency to a public or private package repository and consume it from there. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@electron/rebuild@3.7.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm clip-bpe-js is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: desktop/package.json → npm/clip-bpe-js@0.0.6 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/clip-bpe-js@0.0.6. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report