chore(release): target v1.13.4

Smell-audited: 1: the version is chosen, not bumped, and the release workflow
distinguishes those two cases explicitly.

release.yml's contract: a `.version` that has NEVER shipped is released
VERBATIM; one that HAS shipped makes the push a patch, taking the first free
patch in the series. `1.13.2` has shipped, so a plain merge would have cut
v1.13.3. Naming 1.13.4 here is the deliberate act the workflow reserves for a
chosen version, so preflight releases it as-is.

Also records the test-tier migration under Changed. It ships no runtime
behaviour change, but it moves where a contributor finds behaviour tests: 24
bash e2e scripts became clojure.test suites under test/clj/suites/, run by
cljw itself, and 781 process spawns left the gate. What stays in bash is the
CLI surface and anything needing the process.

Smoke green 12/0 in 427s — the version string is compiled in, so this
invalidates the Zig cache and pays the full test-binary rebuild.

Author: BuddhiLW

CHANGELOG.md

@@ -7,6 +7,15 @@ first stable `1.0.0` tag; pre-1.0 `alpha` / `rc` tags may still change surfaces.
 
 ## [Unreleased]
 
+### Changed
+
+- **Behaviour tests move to a cljw-native tier.** 24 bash e2e scripts that
+  spent one `cljw` process per assertion became `clojure.test` suites under
+  `test/clj/suites/`, run by cljw itself — 781 process spawns out of the gate,
+  and the suites re-run over an nREPL with no rebuild. What stays in bash is
+  the CLI surface (exit code, stderr, argv) and anything that needs the
+  process itself. No runtime behaviour changes.
+
 ### Added
 
 - **`clojure.walk/macroexpand-all` now works.** It previously threw

build.zig.zon

@@ -1,6 +1,6 @@
 .{
     .name = .cljw,
-    .version = "1.13.2",
+    .version = "1.13.4",
     .fingerprint = 0x1869d207073beffa,
     .minimum_zig_version = "0.16.0",
     .dependencies = .{