release: v1.10.0 — the final release, on zwasm v2.5.0

Smell-audited: 1: the zwasm capability ledger's head + Pin section still
claimed v2.4.0 while build.zig.zon had been on v2.4.1 since 673b082 —
corrected in the same edit rather than layering a third version on top of
a stale record.

`.zwasm` pin v2.4.1 → **v2.5.0** (`278587f6`): full WASI 0.3 coverage plus
the 81 declared-but-unexported C-API symbols in `libzwasm.a`. Neither
reaches cljw's embedding surface — cljw drives Engine/Module/Instance
through Zig on the JIT-default `.auto` engine, not the C API — so this is
hygiene that lands the last release on zwasm's current stable, not a
behaviour follow. Verified: the five phase16 wasm e2e (ffi / component /
component_multiexport / engine_select / require_component) green on the
new pin, then the full gate 435/435.

Version 1.9.0 → 1.10.0. MINOR rather than PATCH because `repl` and `nrepl`
gain a `-cp` / `-A:alias` surface and `cljw repl` now rejects unknown
arguments it used to silently ignore — the same reasoning v1.9.0 used.

The CHANGELOG section says plainly that this is the final release and why,
and credits @BuddhiLW for the three reports it is mostly made of. The
zwasm ledger records that its watch duty ends here: cljw stops, zwasm
continues under separate maintainership.

Author: chaploud

.dev/zwasm_capabilities.md

@@ -2,12 +2,14 @@
 
 > **SSOT for "what does the zwasm we embed offer, and what has cljw adopted".**
 > cljw embeds **zwasm v2** (F-001, unavoidable). The dep is a **tag pin** —
-> **v2.4.0** (see § Pin), pinned 2026-08-03 — the external-consumer release,
-> none of which reaches cljw; prior v2.3.0 (2026-07-17) was the
-> WASI-0.3.0-official inventory sweep, v2.2.1 (2026-07-16) the binary-size
-> campaign, v2.2.0 (`cf5d20d7`, 2026-07-09)
-> the AOT-full-fidelity release (ADR-0203). zwasm is itself under active
-> co-development (`~/Documents/MyProducts/zwasm`) and its embedding API is
+> **v2.5.0** (see § Pin), pinned 2026-08-12, and this is cljw's **final** pin:
+> the runtime is no longer maintained (README), so this ledger stops tracking
+> zwasm's growth here. Prior pins: v2.4.1 (2026-08-04) the two cljw-found
+> component/output fixes, v2.4.0 (2026-08-03) the external-consumer release,
+> v2.3.0 (2026-07-17) the WASI-0.3.0-official inventory sweep, v2.2.1
+> (2026-07-16) the binary-size campaign, v2.2.0 (`cf5d20d7`, 2026-07-09)
+> the AOT-full-fidelity release (ADR-0203). zwasm continues under active
+> co-development (`~/Documents/MyProducts/zwasm`) and its embedding API keeps
 > *growing* — notably a **JIT-backed
 > engine** (the cljw north star, ROADMAP §9.0 gap area II × III). cljw has **adopted
 > the JIT as its default** (`.auto`, D-488 discharged); the remaining north-star step
@@ -45,9 +47,23 @@ a cljw-side shim.
 
 ## Pin
 
-- **TAG PIN — v2.4.0, pinned 2026-08-03.** `build.zig.zon`
-  `.zwasm` = `.url = "git+…/zwasm.git#v2.4.0"` + `.hash = "zwasm-2.4.0-FT1Fv9E0…"`,
-  resolved from GitHub. The external-consumer release: `-Dcompiler-rt`
+- **TAG PIN — v2.5.0, pinned 2026-08-12. FINAL.** `build.zig.zon`
+  `.zwasm` = `.url = "git+…/zwasm.git?ref=v2.5.0#278587f6"` +
+  `.hash = "zwasm-2.5.0-FT1Fv4KP…"`. Brings full **WASI 0.3** coverage (all
+  six proposals, 45/45 on the official `wasm32-wasip3` corpus across
+  macOS/Linux/Windows) and the 81 declared-but-unexported C-API symbols in
+  `libzwasm.a` (zwasm #161). **Neither reaches cljw's embedding surface**:
+  cljw drives Engine/Module/Instance through Zig on `.auto` (JIT-default,
+  D-488), not the C API, and its WASI use is the component/`wasm/run` path
+  the previous pins already served. So this is a hygiene follow that lands
+  cljw's last release on zwasm's current stable rather than a behaviour
+  change; no cljw-side delta is claimed. Verified: `zig build -Dwasm` +
+  the five phase16 wasm e2e (ffi / component / component_multiexport /
+  engine_select / require_component) green on the new pin, then the full
+  gate. Prior: **v2.4.1** (2026-08-04), the two fixes found FROM cljw —
+  component multi-export validation (#157) and the captured-run output
+  bound (#158/#159). Prior: **v2.4.0** (2026-08-03), the external-consumer
+  release: `-Dcompiler-rt`
   bundles Zig's compiler-rt into `libzwasm.a` for non-Zig linkers
   (zwasm #153/#154), and a DCE fix keeps the WasmGC cohort out of
   sub-3.0 builds (zwasm #150). **Neither reaches cljw, structurally**:
@@ -235,3 +251,11 @@ have surfaced it.
   catchable error rather than hiding it. Discharges half of D-404's "BLOCKED on
   a typed component FIXTURE" — the fixture now exists and is checked in; what
   remains is the engine accepting it.
+
+- **2026-08-12** — **PIN BUMP v2.4.1 → v2.5.0 (`278587f6`), the FINAL pin.**
+  User-directed, to land cljw's last release on zwasm's current stable. zwasm
+  2.5.0 is full WASI 0.3 coverage + the `libzwasm.a` C-API export fix; neither
+  touches cljw's Zig embedding surface, so this is hygiene rather than a
+  behaviour follow (five phase16 wasm e2e + the full gate green on it). This
+  ledger's watch duty ends here: cljw is no longer maintained, while zwasm
+  continues under separate maintainership.

CHANGELOG.md

@@ -7,6 +7,21 @@ first stable `1.0.0` tag; pre-1.0 `alpha` / `rc` tags may still change surfaces.
 
 ## [Unreleased]
 
+## [1.10.0] - 2026-08-12
+
+**The final release.** ClojureWasm is no longer maintained — a from-scratch
+Clojure runtime turned out to be more than one person can sustain, and this
+release exists so it stops at a working, fully-tested state rather than
+mid-stream. The code stays up under EPL-2.0; fork it and build on it, no
+permission needed. See the README for the full notice.
+
+Everything here is a fix, and three of the four were found by @BuddhiLW,
+who reported them with diagnoses and working branches — thank you. Each
+one's *class* was then swept, which is where the rest of the fixes came
+from. MINOR rather than PATCH because `repl` and `nrepl` gain a `-cp` /
+`-A:alias` surface, and `cljw repl` now rejects unknown arguments it used
+to ignore.
+
 ### Fixed
 
 - **A top-level `(do …)` that requires before it uses now works in every
@@ -55,6 +70,15 @@ first stable `1.0.0` tag; pre-1.0 `alpha` / `rc` tags may still change surfaces.
   to be classified and reach the shared classpath resolution, so a
   future subcommand cannot repeat the nREPL omission.
 
+### Changed
+
+- The embedded Wasm runtime is pinned to **zwasm v2.5.0** (was v2.4.1),
+  which brings full WASI 0.3 coverage and completes `libzwasm.a`'s C-API
+  exports. Neither reaches cljw's embedding surface — cljw drives
+  Engine/Module/Instance through Zig on the JIT-default `.auto` engine —
+  so this lands the final release on zwasm's current stable rather than
+  changing behaviour. zwasm continues under separate maintainership.
+
 ## [1.9.0] - 2026-08-05
 
 **Upgrade if you run untrusted code under `cljw.eval/with-budget`, parse

build.zig.zon

@@ -1,6 +1,6 @@
 .{
     .name = .cljw,
-    .version = "1.9.0",
+    .version = "1.10.0",
     .fingerprint = 0x1869d207073beffa,
     .minimum_zig_version = "0.16.0",
     .dependencies = .{
@@ -11,24 +11,28 @@
         // zwasm v2 embedding API (F-001 / D-037). `lazy` so the DEFAULT build +
         // gate never resolve it — only `-Dwasm` (b.lazyDependency) does.
         //
-        // PINNED to STABLE tag **v2.4.1** (2026-08-04). Unlike the pin-hygiene
-        // bumps before it, this one is load-bearing twice over — both fixes were
-        // found FROM cljw and neither was reachable by zwasm's own fixtures:
-        //   #157 a component with 2+ exports failed validation, so
-        //        `(:require ["x.wasm" :as x])` could only ever load a
-        //        single-function component — the headline feature, blocked.
-        //   #158/#159 a captured run had no output bound. Measured here: 64 MB
-        //        per 1e6 fuel, ~64 GB under the default fuel budget. `wasm/run`
-        //        passes `:max-output-bytes` (D-349).
+        // PINNED to STABLE tag **v2.5.0** (2026-08-11) — cljw's final pin.
+        // It brings full WASI 0.3 coverage (all six proposals, 45/45 on the
+        // official wasm32-wasip3 corpus across macOS/Linux/Windows) plus the
+        // 81 missing C-API symbols in `libzwasm.a` (#161). Neither changes
+        // cljw's embedding surface: Engine/Module/Instance on `.auto` (=
+        // JIT-default, D-488) is the same API it was at v2.2.0.
+        //
+        // The v2.4.1 pin before it was load-bearing twice over, both found
+        // FROM cljw and neither reachable by zwasm's own fixtures: #157 (a
+        // component with 2+ exports failed validation, so
+        // `(:require ["x.wasm" :as x])` could only load a single-function
+        // component — the headline feature, blocked) and #158/#159 (a captured
+        // run had no output bound: 64 MB per 1e6 fuel, ~64 GB under the default
+        // budget; `wasm/run` passes `:max-output-bytes`, D-349).
         //
         // Tag history: v2.4.0 (2026-08-03) external-consumer release
         // (`-Dcompiler-rt`, sub-3.0 DCE); v2.3.0 (2026-07-17) WASI-0.3.0 sweep;
         // v2.2.1 (2026-07-16) binary-size campaign; v2.2.0 (2026-07-09) AOT
-        // full fidelity. cljw's embedding surface (Engine/Module/Instance via
-        // `.auto` = JIT-default, D-488) is unchanged by all of them.
+        // full fidelity.
         .zwasm = .{
-            .url = "git+https://github.com/clojurewasm/zwasm.git?ref=v2.4.1#c45188a639aba8ee7298209539134a61643b2bd4",
-            .hash = "zwasm-2.4.1-FT1Fv0J0jQDowvbJuWRyBg6N0aX7lj52ldrm7T7HWzBr",
+            .url = "git+https://github.com/clojurewasm/zwasm.git?ref=v2.5.0#278587f608a7564d8f2dfa53f567aab70f661296",
+            .hash = "zwasm-2.5.0-FT1Fv4KPkgCaKsDmsn05BTYsoEhH7RCUreSX8a3mwFha",
             .lazy = true,
         },
     },