Release 0.1.3: full pipeline working end to end

CI is now green across all 20 jobs:
- Rust on Linux/macOS/Windows
- Python 3.9/3.11/3.12 on Linux/macOS/Windows
- Node 18/20 on Linux/macOS/Windows (Windows previously failed
  because ci.yml built the native module without --platform; fixed
  in the previous commit)
- WASM build
- Cross-library benchmark report

This tag re-publishes 0.1.3 across crates.io / PyPI / npm so a single
version covers every working binding. The release workflow's idempotent
publish steps mean re-runs are safe; the new code in this version is
just the build-script and loader changes that fixed CI.

Cargo.lock

@@ -1883,7 +1883,7 @@ dependencies = [
 
 [[package]]
 name = "wickra"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "approx",
  "criterion",
@@ -1894,7 +1894,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-core"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "approx",
  "proptest",
@@ -1904,7 +1904,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-data"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "approx",
  "csv",
@@ -1922,7 +1922,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-node"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "napi",
  "napi-build",
@@ -1932,7 +1932,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-python"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "numpy",
  "pyo3",
@@ -1941,7 +1941,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-wasm"
-version = "0.1.2"
+version = "0.1.3"
 dependencies = [
  "console_error_panic_hook",
  "js-sys",