fix(test): ensure useEncryption hook and test share same crypto module instance

In Vitest's jsdom environment, a static import inside a hook (captured
at module evaluation time) and a dynamic import() inside a test body
can resolve to different module instances. When vi.stubGlobal patches
crypto after static imports have already been evaluated, the hook's
closed-over decryptContent has a stale crypto reference (no .subtle),
while the test's dynamic import() gets the patched one.

Fix: use vi.mock + vi.importActual so both the test's enc() helper
and the hook's internal decryptContent are guaranteed to come from
the same module instance, with the same crypto reference.

Author: SamoTech

src/__tests__/useEncryption.test.ts

@@ -3,6 +3,14 @@ import { renderHook, act } from '@testing-library/react'
 import { useEncryption } from '@/hooks/useEncryption'
 import type { DecryptedNote } from '@/types/note'
 
+// Hoist the actual implementation so both the test helpers and the hook's
+// internal static import share the same module instance and the same
+// crypto.subtle reference — avoiding stale-closure issues in jsdom.
+vi.mock('@/lib/crypto', async () => {
+  const actual = await vi.importActual<typeof import('@/lib/crypto')>('@/lib/crypto')
+  return actual
+})
+
 function makeNote(overrides: Partial<DecryptedNote> = {}): DecryptedNote {
   return {
     id: 'note-1',