release(0.1.5): bump versions, finalize CHANGELOG, fail loud on missing platform binaries (R20, Z2)

Versions bumped to 0.1.5 in every authoritative location:

- workspace `Cargo.toml` (`[workspace.package].version`, the
  `wickra-core` path dependency pin).
- `bindings/python/pyproject.toml`.
- `bindings/node/package.json` (main + all six `optionalDependencies`
  pins).
- All six per-platform `bindings/node/npm/<target>/package.json`
  templates.

CHANGELOG: the accumulated `[Unreleased]` block is promoted to
`[0.1.5] - TBD` (date left for the user to set at tag time); the new
`[Unreleased]` header sits empty above it; the compare link table is
extended with `[0.1.5]: …compare/v0.1.4...v0.1.5` and the
`[Unreleased]` link is repointed to `…compare/v0.1.5...HEAD`.

Wiki refresh for 0.1.5 (R20 + Z2):

- `Home.md` version pin table updated; the Quickstart-Node hint replaces
  the "spam filter holding back Windows" caveat with "0.1.5 is the
  first release in which `npm install wickra` works end-to-end on
  Windows" (npm Support released the name on 2026-05-22).
- `Quickstart-Node.md`'s Windows caveat is rewritten to explain the
  history (`0.1.1`–`0.1.4` of `wickra-win32-x64-msvc` are burned) and
  the resolution (0.1.5+ installs cleanly).
- `Quickstart-Rust.md` version mention bumped.
- `Warmup-Periods.md` note bumped + corrected: every Node and WASM
  class — single- and multi-output — now exposes `warmupPeriod()` after
  R3 (this branch), not only the single-output ones.

`release.yml` `publish_dir` no longer silently swallows a
second-attempt platform-package publish failure with a `::warning::`
and `return 0`. A real failure (after the existing 30s retry) now
emits an `::error::` and fails the job. The original mask is exactly
what allowed the `wickra-win32-x64-msvc@0.1.1–0.1.4` spam-filter
rejections to land four times in a row without anyone noticing (audit
finding R20). Failing loud means the next regression of this shape is
caught at the release run, not by a Windows user trying to
`require('wickra')`.

This commit does NOT push, tag, or trigger a release — the user
publishes the 0.1.5 tag themselves once the manual npm-republish
smoke test confirms `wickra-win32-x64-msvc@0.1.5` accepts publish on
the freshly-released name.

Cargo.lock

@@ -1941,7 +1941,7 @@ dependencies = [
 
 [[package]]
 name = "wickra"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "approx",
  "criterion",
@@ -1952,7 +1952,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-core"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "approx",
  "proptest",
@@ -1962,7 +1962,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-data"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "approx",
  "csv",
@@ -1989,7 +1989,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-node"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "napi",
  "napi-build",
@@ -1999,7 +1999,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-python"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "numpy",
  "pyo3",
@@ -2008,7 +2008,7 @@ dependencies = [
 
 [[package]]
 name = "wickra-wasm"
-version = "0.1.4"
+version = "0.1.5"
 dependencies = [
  "console_error_panic_hook",
  "js-sys",