fix: correct phone verification success notification

[cursor]

Summary

After updating phone verification and invalidating the user store, the success toast used the new phoneVerification value with inverted copy, so Verify showed "unverified" and Unverify showed "verified".

Align the phone path with the email path (!$user.phoneVerification ? 'unverified' : 'verified') so the toast matches the post-update state.

Fixes #1392

Test plan

• Open a user with both email and phone in Auth
• Verify phone → toast says verified
• Unverify phone → toast says unverified
• Email verify/unverify still reports correctly

  

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Teams feature lets you group users with membership management and role permissions

[greptile-apps]

Greptile Summary

Corrects the phone verification success notification so it describes the refreshed verification state consistently with the email verification path.

• Negates the refreshed phoneVerification value when selecting “verified” or “unverified” copy.
• Leaves the underlying verification update and user-store invalidation behavior unchanged.

Confidence Score: 5/5

The PR appears safe to merge, with the corrected phone notification matching the established email verification behavior.

The change only corrects success-message selection after the user data is invalidated and refreshed, without altering verification state, authorization, or persistence behavior.

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/auth/user-[user]/updateStatus.svelte	Corrects the phone verification toast’s conditional to report the post-update state; no actionable defects identified.

_{Reviews (1): Last reviewed commit: "fix: correct phone verification success ..." | Re-trigger Greptile}