Perf: defer Windows VC++ runtime probe to init failure path (#54)

Skips the registry probe during module import; only runs it as a diagnostic if native sodium_init() throws on Windows. Reduces cold-start overhead.

Author: MariusStorhaug

src/functions/private/Initialize-Sodium.ps1

@@ -19,7 +19,14 @@
         if (-not $script:Supported) { throw 'Sodium is not supported on this platform.' }
         if ($script:SodiumInitialized) { return }
 
-        $initializationResult = [PSModule.Sodium]::sodium_init()
+        try {
+            $initializationResult = [PSModule.Sodium]::sodium_init()
+        } catch {
+            if ($IsWindows) {
+                $script:Supported = Assert-VisualCRedistributableInstalled -Version '14.0' -Architecture $script:ProcessArchitecture
+            }
+            throw
+        }
         if ($initializationResult -lt 0) {
             throw 'Sodium initialization failed.'
         }

src/main.ps1

@@ -36,8 +36,6 @@ switch ($true) {
 $assemblyPath = Join-Path -Path $PSScriptRoot -ChildPath "libs/$runtimeIdentifier/PSModule.Sodium.dll"
 Import-Module $assemblyPath -ErrorAction Stop
 
-if ($IsWindows) {
-    $script:Supported = Assert-VisualCRedistributableInstalled -Version '14.0' -Architecture $processArchitecture.ToString()
-} else {
-    $script:Supported = $true
-}
+# Optimistically mark supported; Initialize-Sodium will run the Windows VC++ runtime check lazily only if native init fails.
+$script:Supported = $true
+$script:ProcessArchitecture = $processArchitecture.ToString()