Detect pending legacy profile convergence - #2
Draft
Howe829 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Root cause
legacy_upgrade_statustreated every VNext device state as completed. Identities that still carried legacy draft foundation profiles therefore skipped the existing convergence path and later failed device approval because those profiles are read-only.Impact
VNext identities with canonical profiles remain a fast completed path. Legacy draft profiles now resume the existing idempotent convergence flow while preserving authority and device identity.
Validation
cargo fmt --all -- --checkcargo test -p awiki-im-core identity_legacy_upgrade --locked— 12 focused tests passed