Skip to content

Detect pending legacy profile convergence - #2

Draft
Howe829 wants to merge 1 commit into
release/0714from
BugFix/legacy-profile-convergence-status
Draft

Detect pending legacy profile convergence#2
Howe829 wants to merge 1 commit into
release/0714from
BugFix/legacy-profile-convergence-status

Conversation

@Howe829

@Howe829 Howe829 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Load the local DID document before reporting VNext legacy-upgrade completion.
  • Return completed only when foundation profile discovery no longer requires convergence.
  • Allow identities with legacy draft profiles to enter the existing root-signed convergence workflow.

Root cause

legacy_upgrade_status treated 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 -- --check
  • cargo test -p awiki-im-core identity_legacy_upgrade --locked — 12 focused tests passed
  • Android arm64 native SDK rebuilt successfully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant