fix(crypto): open encrypted note after setting a passphrase from the unlock prompt

[kodinkod]

Summary

Fixes a bug where clicking a locked encrypted note (.md.age), being prompted to set a password, setting it, and then having the note silently fail to open — nothing happened.

Clicking a .md.age note while the vault is locked calls requireUnlock (src/stores/crypto.ts), which registers a pending promise and opens the crypto panel. When that panel opens in setup / set-passphrase mode (this device isn't enrolled yet, or no passphrase is set), the user sets a password rather than unlocking.

Both crypto_setup and crypto_set_passphrase auto-unlock the vault on the Rust side, but only the store's unlock() resolved the pending promise. So after a successful setup the form's onDone closed the panel, closePanel rejected the pending promise as if it were a user cancel, and openNote bailed out silently — the note never opened.

The fix resolves the pending unlock from setup and setPassphrase too (once a status refresh confirms the vault is unlocked), via a shared resolvePendingUnlock helper now also used by unlock.

Related issues

Type of change

• Bug fix
• New feature
• Documentation
• Refactor / chore
• Breaking change

How was this tested?

• npm run lint passes
• npm run build passes (tsc && vite build, exit 0)
• cargo fmt --check && cargo clippy — not run (no Rust changes)
• cargo test — not run (no Rust changes)
• Traced the affected flow: setup/set-passphrase now resolve the requireUnlock promise so openNote proceeds to note_read instead of treating the panel close as a cancel

Screenshots / recordings

Contributor License Agreement

• I have read the Mycel CLA and I agree to it for this and all my future contributions.
• My contribution is my original work, or I have clearly identified any third-party material and its license.

🤖 Generated with Claude Code

https://claude.ai/code/session_01M2CsK2HG7jUuJBVi94t7Jk

---

Generated by Claude Code

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}