Both iOS fallbacks appended only to the view's own state, so when listUsers
failed the profile existed in the database but in no list the app shows -
and creating it again failed on the duplicate name. Kotlin already did this.
changeActiveUser shows its own alert, so the resync path was reporting the
same failure twice; use changeActiveUser_ and report it once.
Merging keepActiveUser into apiCreateActiveUser changed a signature that two Kotlin
docs quote. spec/api.md still described the old parameters and said the command sets
the profile as active, full stop; product/flows/onboarding.md quoted the old signature
one step above the line this branch had already updated to mention the flag. The iOS
spec table was fixed in the previous commit and these were missed - the same drift on
the other platform.
Both iOS call sites now use listUsersAsync, which is what changeActiveUserAsync_ uses
a few lines later; the synchronous listUsers blocks whatever executor the Task is on,
and SwiftUI infers that as the main actor.
Not compiled: the Kotlin changes here are markdown only, and the Swift ones cannot be
built on this machine.
Narasimha-sc