release: cljw 1.2.1 — the *cider-error* buffer (analyze-last-stacktrace) + *e parity

Smell-audited: 1: version bump + CHANGELOG + the D-548 recurrence record;
the feature shipped in eafc4fd (ADR-0170 am1). Pre-tag verification on
this tree: smoke green; three full-gate runs each 401/402 with ONLY the
ledger-tracked D-548(a) roaming SIGABRT failing — at its two RECORDED
abort sites (delay_once_under_concurrency 2026-07-02, the cancel section
2026-06-25), 20/20 standalone green, 8x-parallel stress 1/8 vs the
ledger's own pre-change 3/8 baseline, and CI (the release platform)
green on the feature commit — the documented pre-existing host-load
race, not an am1 regression (full record in the D-548 row).

Author: chaploud

.dev/debt.yaml

@@ -1069,7 +1069,13 @@ active:
     last_reviewed: "2026-06-25"
   - id: "D-548"
     status: |-
-      open (2026-07-02). Low-core concurrency exposure, surfaced by the first nightly
+      open (2026-07-02). RECURRED 2026-07-14 during the v1.2.1 pre-tag full gates
+      (Mac local, serial-e2e, TWICE in a row): (a) future_promise_delay exit 134;
+      20× standalone all PASS; the A/B check vs the ledger's own pre-am1 baseline —
+      8× parallel stress — reproduced 1/8 exit 134 vs the recorded 3/8, so the
+      ADR-0170 am1 throw-path change did NOT worsen it (rate at/below baseline;
+      the race predates am1 by 3 weeks and ships in released 1.1.0/1.2.0).
+      Low-core concurrency exposure, surfaced by the first nightly
       FULL gate on the hosted 3-vCPU macos-15 runner (runs 28571235224 + 28574985879):
       (a) e2e_phase14_future_promise_delay — a ROAMING case SIGABRTs the ReleaseSafe
       binary (exit 134): run 28574985879 aborted delay_once_under_concurrency; run

CHANGELOG.md

@@ -5,6 +5,35 @@ All notable changes to ClojureWasm are documented here. The format follows
 [SemVer](https://semver.org/). SemVer compatibility guarantees start at the
 first stable `1.0.0` tag; pre-1.0 `alpha` / `rc` tags may still change surfaces.
 
+## [1.2.1] - 2026-07-14
+
+Patch release: the `*cider-error*` buffer works — CIDER renders numbered
+causes with stack frames, phase-aware routing, and Show/Hide frame filters
+against cljw, instead of "[no stack trace available]".
+
+### Added
+
+- **nREPL `cider/analyze-last-stacktrace` op** (+ the bare alias) — analyzes
+  the session's `*e` on demand: one cause per `ex-cause` chain link with
+  class / message / printed ex-data / error phase / stack frames
+  (innermost-first, with `clj` / `repl` / `project` / `dup` flags and
+  navigable `file-url` for on-disk frames). CIDER's rich error buffer and
+  its compile-phase inline overlays activate automatically.
+
+### Fixed
+
+- **`*e` is now set for every caught REPL error** — Clojure parity:
+  compiler-class errors (an unresolved symbol, a syntax error) previously
+  left `*e` untouched; now `(ex-message *e)` works after any error, in both
+  the CLI REPL and nREPL sessions.
+- **`(throw (ex-info …))` carries a stack trace** — the live call stack is
+  stamped on the thrown value, so user throws render frames like runtime
+  errors (both backends).
+- **nREPL use-after-free** — the 1.2.0 re-architecture fed the per-message
+  scratch-owned request source into evals whose products outlive the
+  message; long editor sessions could see corrupted strings. The source is
+  now copied to the persistent arena.
+
 ## [1.2.0] - 2026-07-13
 
 Minor release: the nREPL server is rebuilt to full base-protocol fidelity —

build.zig.zon

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