chore(release): v1.8.0

The audit-drain day's whole output. Two things a user notices immediately:
a Wasm component with more than one export could not be loaded at all, and
`(doc reduce)` printed nothing.

- **Multi-export components load.** Every component fixture in this project
  and in zwasm exported exactly one function, so `(:require ["x.wasm" :as x])`
  — the headline feature — had only ever been exercised on single-function
  components. Fixed in zwasm v2.4.1, which this release pins.
- **`(doc reduce)` prints something.** So do `assoc`, `conj`, `first`, `apply`,
  `=` and 320 others. The generated metadata table covered 246 of 685
  `clojure.core` publics and none of the ~290 native primitives, so `find-doc`
  and `apropos` searched a third of core while answering as though they had
  searched all of it. Now 572 of 684.
- **`clojure.core.reducers`** lands, 31 of 32 probed expressions
  byte-identical to JVM Clojure.
- **`wasm/run` is bounded on output and wall clock**, not just fuel. Measured,
  a guest could force ~64 GB of host memory and roughly 18 hours of runtime
  inside the default fuel budget, because fuel counts instructions and neither
  bytes-per-instruction nor time-per-instruction is fixed.
- **A one-shot component resource handle was already invalid when returned**,
  and could silently name a different resource on reuse.
- **`clojure.pprint` stops publishing 49 internal formatter helpers**;
  `clojure.set` gains its arglists and stops answering `nil` where Clojure
  throws.

MINOR rather than PATCH: `clojure.core.reducers`, `:max-output-bytes` and
`:timeout-ms` are new surface. The pprint/data privatisations remove names that
upstream never published and nothing could portably have used.

Bumps build.zig.zon (`cljw --version` now reports 1.8.0) and refreshes handover.

Author: chaploud

.dev/handover.md

@@ -13,44 +13,19 @@
   `1ecc7a8a` (zwasm main; carries #157 component export index space + #158/#159
   the WASI capture cap — both load-bearing for cljw, unlike the v2.4.0 tag it
   replaced. Tagging zwasm is user-only, its ADR-0156). Latest release:
-  **v1.7.0** (2026-08-04; the component marshaller could kill the host on
-  guest data — bare `@intCast` = a ReleaseSafe panic; `result` lifts as
-  `[:ok v]`/`[:err e]` per ADR-0135 am2, replacing a throw that DISCARDED the
-  err payload; `*file*` lands). v1.6.0 earlier the same day carried four
-  hang/abort fixes. CHANGELOG is the release-history SSOT.
-- **First task on resume**: **release v1.8.0** + the four distribution repos.
-  Nothing blocks it: zwasm v2.4.1 is cut (user-granted) and `.zwasm` is pinned
-  to that tag. 26 commits since v1.7.0, all green, nothing half-landed.
+  **v1.8.0** (2026-08-04; multi-export components load, `wasm/run` gains
+  output + wall-clock bounds, `clojure.core.reducers` lands, and `(doc reduce)`
+  finally prints something). CHANGELOG is the release-history SSOT.
+- **First task on resume**: the remaining distribution repos —
+  `cw-playground`, `cw-serverless-demo`, `cw-arcade` (the homebrew tap is done
+  as part of the v1.8.0 release).
   NOTE on history hygiene: commit `673b082b`'s message describes only the
   gate-parity fix, but its diff ALSO carries the zwasm tag re-pin, `wasm/run`'s
   `:timeout-ms` axis and D-570's discharge — they were in the tree when the
-  gate went green and rode along. Not amended (already pushed); recorded here
-  so the CHANGELOG for v1.8.0 is written from the diff, not from that message.
-- **Unreleased on main** (21 commits since v1.7.0, 2026-08-04 audit-drain day —
-  CHANGELOG entry is owed by the next release):
-  **Gate**: the local full gate now runs `--serial-e2e`, the configuration CI
-  runs — it did not, and a serial-only EPIPE death in an e2e was therefore
-  invisible locally while failing every push (`gate_parity` + `epipe_head`
-  assert both halves).
-  **Wasm/component**: `wasm/run` gains `:timeout-ms` (D-570 — fuel is a ~760x
-  proxy for time, so the 1e9 default permitted ~18 h); multi-export components
-  load at all (zwasm #157); the
-  ADR-0135 marshalling table asserted in both directions over a 16-export
-  fixture; `result`/`variant` LOWER (they raised `feature_not_supported`);
-  one-shot `component-invoke`'s `own` result no longer names a destroyed table
-  (ADR-0159 am1) and a resource handle is bound to its component; `wasm/run`
-  output is capped (D-349 — ~64 GB was reachable).
-  **clj surface**: `clojure.core.reducers` bundled (31/32 oracle-identical);
-  `core_meta.clj` 291→628 rows, so `reduce`/`assoc`/`conj`/`first` are
-  documented and `find-doc` covers 84% of core not 36% (ADR-0181);
-  `clojure.set` → multi-arity `defn`, `(intersection)` now throws where it
-  answered nil; 49 pprint + 5 data internals privatised; 44 authored
-  `clojure.math` docstrings.
-  **Scaffolding**: `cleanup_orphans.sh` now exists (cited as live, did not);
-  `run_wasm_gate.sh` had been exiting 0 without running; new gates
-  `reference_clones` / `clj_attribution --gate` / `doc_coverage` /
-  `epipe_head` / `gate_parity`; NOTICE said three files where ten reproduce
-  upstream text. ADR-0180/0181, AD-058/059.
+  gate went green and rode along. Not amended (already pushed); the v1.8.0
+  CHANGELOG was written from the diff rather than that message.
+- **Unreleased on main**: nothing. v1.8.0 (2026-08-04) carried the whole
+  audit-drain day; CHANGELOG is the SSOT for what it contained.
 - **Forbidden**: bare `zig build test` without `-Dwasm`; bare `zig build` for a
   probe (use ReleaseSafe). The FULL gate runs `--serial-e2e`, ALONE; never a
   concurrent build during a gate. `.claude/**` edits + cross-repo publishes may

CHANGELOG.md

@@ -7,6 +7,65 @@ first stable `1.0.0` tag; pre-1.0 `alpha` / `rc` tags may still change surfaces.
 
 ## [Unreleased]
 
+## [1.8.0] - 2026-08-04
+
+**Upgrade if you use Wasm components, or if you use `doc` / `find-doc`.**
+A component with more than one export could not be loaded at all, and `doc` on
+most of `clojure.core` printed nothing.
+
+### Added
+
+- **`clojure.core.reducers`.** The full sequential surface — `r/map`,
+  `r/filter`, `r/remove`, `r/mapcat`, `r/flatten`, `r/take`, `r/take-while`,
+  `r/drop`, `r/reduce`, `r/fold`, `r/foldcat`, `r/cat`, `r/monoid`,
+  `r/append!` — with the curried one-arity forms. 31 of 32 probed expressions
+  are byte-identical to JVM Clojure; the one difference is set print order.
+  `fold` computes the same value as upstream's but never in parallel: there is
+  no ForkJoinPool here, so it takes the same single-reduce arm upstream itself
+  takes for lists, ranges and sets. Its docstring says so.
+- **`wasm/run` takes `:max-output-bytes` and `:timeout-ms`**, alongside the
+  existing `:fuel` and `:max-memory-pages`. Both default to finite values
+  (16 MiB per captured stream, 60 s); `0` or a negative value opts out.
+
+### Fixed
+
+- **A Wasm component with two or more exports failed to load.** Every fixture
+  in this project and in zwasm exported exactly one function, so
+  `(:require ["x.wasm" :as x])` — the headline feature — had only ever been
+  exercised on single-function components. Fixed in zwasm v2.4.1, which this
+  release pins.
+- **`wasm/run` could be made to exhaust host memory.** It buffered the guest's
+  stdout and stderr without limit, and the fuel budget does not bound that:
+  fuel counts instructions, and how many bytes an instruction writes is the
+  guest's choice. Measured, a guest could force ~64 GB before its fuel ran
+  out. Also had no wall-clock bound — the same guest could run for roughly 18
+  hours inside the default fuel budget.
+- **A resource handle from a one-shot `wasm/component-invoke` was already
+  invalid when you received it**, because the component was torn down before
+  the call returned. Handle numbers are per-instance table indices starting at
+  1, so passing it on could silently operate on a *different* resource. The
+  component now lives as long as the handle does, and a handle is bound to the
+  component that minted it.
+- **`result` and `variant` could not be passed INTO a component.** They lifted
+  out correctly, so the round-trip the mapping table describes was one-way.
+- **`(doc reduce)` printed nothing** — and so did `assoc`, `conj`, `first`,
+  `apply`, `=` and 320 others. The generated metadata table covered 246 of 685
+  `clojure.core` publics and none of the ~290 implemented as native
+  primitives, so `find-doc` and `apropos` were searching a third of core while
+  answering as though they had searched all of it. Now 572 of 684.
+- **`(clojure.set/intersection)` returned `nil`** where Clojure throws
+  `ArityException`, and no var in `clojure.set` reported `:arglists`.
+
+### Changed
+
+- **`clojure.pprint` no longer publishes 49 internal formatter helpers**
+  (`cl-tens`, `cl-roman`, `cl-under-1000`, …). Upstream keeps them private;
+  they were public here only because they were written as `defn`. `cl-format`
+  and the other six documented names are unaffected. Same for five
+  `clojure.data` internals and three contrib parser implementation details.
+- **`clojure.math` gained docstrings**, written for this runtime rather than
+  imported — upstream's all end in a `java.lang.Math` Javadoc URL.
+
 ## [1.7.0] - 2026-08-04
 
 **Upgrade if you load Wasm components.** An untrusted component could kill the

build.zig.zon

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