fix: validate passphrase on empty-vault unlock (prevent lockout)

[saurabhhhcodes]

Real fix for #837.

unlockCredentials() accepted any passphrase when the vault was initialized (salt present) but empty (no verification token and no credentials), caching the wrong derived key and permanently locking the user out on the next save. Now the unlock path validates against a persisted verification token; a partially-initialized vault auto-creates that token so future unlocks are verifiable. Adds a regression test.

Closes #837

[github-actions]

🚀 Thank You for Contributing to Late-Meet

Please ensure that:

• the issue was assigned to you before opening this PR
• the PR references the related issue
• your changes follow repository contribution guidelines
• the project builds successfully before submission

Unassigned, duplicate, or low-quality PRs may be closed.

Thank you for contributing 💙

[github-actions]

👋 Thank you @saurabhhhcodes for your contribution to Late-Meet!

⚠️ Warning: You are not currently assigned to the linked issue #837. Please request assignment on that issue before submitting a PR.

Please review any automated suggestions or code review comments that may appear below! We will review your PR as soon as possible!

---

Please consider starring the repository ⭐ to show your support!

[coderabbitai]

Warning

Review limit reached

@saurabhhhcodes, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0abb2708-5a9c-4950-b5d2-3f75170b2da8

📥 Commits

Reviewing files that changed from the base of the PR and between d216444 and 8f3fc47.

📒 Files selected for processing (2)

• src/utils/credentials.test.ts
• src/utils/credentials.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[saurabhhhcodes]

🔔 Friendly ping @shouri123 — this real fix has passing CI and references an approved GSSoC issue. Ready for review/merge. Thanks!

[saurabhhhcodes]

🔔 Friendly ping @shouri123 — this real fix has passing CI and references an approved GSSoC issue. Ready for review/merge. Thanks!