Add comprehensive cargo target directory debugging

The cargo build succeeds but no target directory is found. This adds extensive
debugging to understand where cargo is placing build artifacts.

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

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

Author: Qard

.github/workflows/CI.yml

@@ -159,12 +159,23 @@ jobs:
                 exit 1
               }
               echo "===== Checking build output ====="
+              echo "Current cargo environment:"
+              echo "CARGO_TARGET_DIR: ${CARGO_TARGET_DIR:-not set}"
+              echo "PWD: $(pwd)"
+              echo "Listing current directory:"
+              ls -la
               echo "Finding all files in target directory:"
               find target -type f 2>/dev/null || echo "No target directory found"
+              echo "Finding all hidden target directories:"
+              find . -name ".target*" -type d 2>/dev/null || echo "No hidden target dirs"
+              echo "Finding target dirs anywhere:"
+              find . -name "target" -type d 2>/dev/null || echo "No target dirs found"
               echo "Looking for WASM files specifically:"
               find . -name "*.wasm" -type f 2>/dev/null || echo "No WASM files found"
               echo "Looking for any files with 'fix-python-soname' in name:"
               find . -name "*fix-python-soname*" -type f 2>/dev/null || echo "No fix-python-soname files found"
+              echo "Checking if there's a target in parent directory:"
+              ls -la ../target 2>/dev/null || echo "No parent target directory"
               echo "Checking target structure:"
               ls -la target/ 2>/dev/null || echo "No target directory"
               ls -la target/wasm32-wasip1/ 2>/dev/null || echo "No wasm32-wasip1 directory"