fix: ensure release includes all dependencies

- Change release workflow to use dotnet publish for Module (was using
  dotnet build which omits runtimes/ directory with native SQLite libs)
- Update install-remote.ps1 to recursively copy all directories from
  release archive (handles runtimes/, Functions/, future subdirs)
- Document pitfall in CLAUDE.md to prevent regression

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: lucaspimentel

.github/workflows/release.yml

@@ -41,7 +41,7 @@ jobs:
         run: dotnet publish src/PSCue.ArgumentCompleter/PSCue.ArgumentCompleter.csproj -c Release -r ${{ matrix.rid }} --self-contained -o dist/${{ matrix.rid }}/
 
       - name: Build Module
-        run: dotnet build src/PSCue.Module/PSCue.Module.csproj -c Release -o dist/${{ matrix.rid }}/
+        run: dotnet publish src/PSCue.Module/PSCue.Module.csproj -c Release -o dist/${{ matrix.rid }}/
 
       - name: Copy module files
         shell: pwsh

CLAUDE.md

@@ -254,6 +254,7 @@ public void TestLearningAccess()
 11. **PCD attempts Set-Location on non-existent path**: Always loop through ALL suggestions and verify existence before navigation. Never call `Set-Location` on paths that don't exist - show helpful error messages instead. This handles race conditions and stale database entries gracefully.
 12. **PCD tab completion behavior**: CompletionText must match native cd exactly - use .\ prefix for child directories, ..\ for siblings, and single quotes for spaces. ListItemText should be clean (no prefixes/separators/quotes). See module/Functions/PCD.ps1:183-228 for implementation.
 13. **Testing with non-existent paths**: Use `skipExistenceCheck: true` parameter in `PcdCompletionEngine.GetSuggestions()` when testing with mock/non-existent paths. Production code filters non-existent paths by default.
+14. **Release builds missing dependencies**: The release workflow (.github/workflows/release.yml) MUST use `dotnet publish` (not `dotnet build`) for PSCue.Module to include all dependencies, especially the `runtimes/` directory with native SQLite libraries. `dotnet build` only outputs primary assemblies, while `dotnet publish` creates a complete deployable package. The remote install script (install-remote.ps1) recursively copies all directories from the release archive to handle `runtimes/`, `Functions/`, and any future subdirectories.
 
 ## Documentation
 - **Implementation status**:

install-remote.ps1

@@ -207,11 +207,12 @@ try {
         }
     }
 
-    # Copy Functions directory if it exists
-    $FunctionsDir = Join-Path $ExtractDir "Functions"
-    if (Test-Path $FunctionsDir) {
-        Copy-Item -Path $FunctionsDir -Destination $InstallDir -Recurse -Force
-        Write-Info "  Installed: Functions/"
+    # Copy all directories from extracted archive (Functions, runtimes, etc.)
+    $DirectoriesToCopy = Get-ChildItem -Path $ExtractDir -Directory
+
+    foreach ($dir in $DirectoriesToCopy) {
+        Copy-Item -Path $dir.FullName -Destination $InstallDir -Recurse -Force
+        Write-Info "  Installed: $($dir.Name)/"
     }
 
     # Success!