feat(seedless-onboarding): add dataType support for secret data items

[huggingbot]

Explanation

The metadata service now supports a dataType column for categorizing secret data (PrimarySrp, ImportedSrp, ImportedPrivateKey). This enables clients to distinguish between different types of backed-up secrets

Changes include:

• Add dataType parameter to insert operations
• Add updateSecretDataItem and batchUpdateSecretDataItems for updating existing items
• Update fetchAllSecretData to return storage metadata (itemId, dataType) alongside secret data
• Refactor SecretMetadata to separate local metadata from storage-level metadata

References

https://consensyssoftware.atlassian.net/browse/SL-350

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

---

Note

Adds dataType and storage metadata support with migrations. Introduces breaking API changes.

• Implement EncAccountDataType end-to-end: addNewSecretData now requires dataType; payload still writes type for backward compatibility
• New storage metadata on SecretMetadata: itemId, dataType, createdAt (TIMEUUID), storageVersion; plus compare, compareByTimestamp, and matchesType
• Update fetch path to return/storage-align items, prioritize PrimarySrp, and sort via TIMEUUID timestamps; validate first item is primary SRP
• Add runMigrations (with internal dataType migration) and setMigrationVersion; persist migrationVersion and SeedlessOnboardingMigrationVersion enum
• Replace removed APIs: drop parseSecretsFromMetadataStore, fromBatch, sort, and version getter; fromRawMetadata now requires storageMetadata
• Add TIMEUUID utilities and mapping from EncAccountDataType to SecretType; re-export EncAccountDataType
• Bump @metamask/toprf-secure-backup to ^1.0.0

^{Written by Cursor Bugbot for commit 7184599. This will update automatically on new commits. Configure here.}

[huggingbot]

May I know are there any major difference between #storageVersion and #version?
If not we can remove either one of them.

removed version entirely and kept storageVersion here. This should work for old clients too because we're not using version in our logic at all

[huggingbot]

do we need to also update SocialBackupsMetadata?

[huggingbot]

Should we move this logic to SecretMetadata class? wdyt?

fixed here

Misclicked.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​toprf-secure-backup@​0.11.0 ⏵ 1.0.0			+1	-1

View full report