@field/cascade 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -2,6 +2,69 @@
 
 Notable changes to Cascade. Newest first.
 
+## 0.6.0 — 2026-09-10
+
+All three items from a user's first day with the npm package.
+
+### Added
+
+- **`cascade.math.*` — arithmetic as nodes.** `Binary` (add, subtract,
+  multiply, divide, power, modulo, min, max, atan2), `Unary` (abs, negate,
+  floor, ceil, round, sqrt, sign, sin, cos, tan, asin, acos, exp, log, radians,
+  degrees, fract), `Clamp`, `Mix` and `Compare`.
+
+  The maths already existed as expressions — every parameter field takes
+  `sin($T)`, `clamp`, `lerp`, `fit`. So these are not a second way to compute
+  but a second way to *place* a computation: an expression is private to one
+  parameter, and a value you want to look at, reuse, or wire into three places
+  has to be a node.
+
+  Grouped with an operation to pick rather than one node per operation, which
+  is Houdini's form and would be about twenty-five nodes. Inputs are `any` and
+  every operation is component-wise with scalar broadcast, so multiplying a
+  `vec2` by a scalar and adding two `vec3`s both work. There is no `Fit`:
+  `cascade.core.Remap` already is one.
+
+  Division and modulo by zero give zero rather than `Infinity`, and `sqrt` of a
+  negative gives zero rather than `NaN` — a non-finite number flows into a
+  position and the geometry silently vanishes, which is a blank frame with no
+  error anywhere.
+
+- **Connections can be made backwards.** A drag or click may begin on an
+  unconnected input pin and end on an output; the endpoints are normalised
+  before the connection is built, so variadic fan-in, the `Input` node a subnet
+  auto-creates, and multi-select fan-in all behave identically in either
+  direction. A *connected* input keeps the disconnect gesture.
+
+### Fixed
+
+- **The node search panel no longer closes when the search narrows to one
+  result.** The pointer had not left it — the panel shrank away from underneath
+  a stationary cursor, which fired `mouseleave` at the exact moment you were
+  about to click the thing you searched for. Leave-to-close now applies only
+  while the panel is being browsed by hover, not once you have typed.
+
+## 0.5.2 — 2026-09-10
+
+### Fixed
+
+- **The load warm-up no longer reports false errors.** A node's ports are
+  created by running its code, so on load a connection into a node that has
+  never executed has no port to attach to, and Studio cooks the graph
+  repeatedly until the wiring settles. Early passes reached nodes whose
+  upstream edge had not bound, those nodes ran with `undefined` on that input
+  and threw their own "nothing wired to my image input", and a later pass then
+  succeeded — leaving a correct graph and a log full of errors that never
+  cleared. Reported against the `volume-field` sketch by someone who had
+  verified from the cache files that the render was in fact right.
+
+  The scheduler now distinguishes an input that is *pending* from one that is
+  *missing*: a node with an unbound inbound edge is held back as not-ready
+  rather than cooked and failed. Once the warm-up stops making progress the
+  graph says so, and an edge that still has not bound is treated as unbindable
+  — so a genuinely unwired node errors as it always did, rather than silently
+  never cooking.
+
 ## 0.5.1 — 2026-09-09
 
 - Prepared the 0.5 browser-player release for npm, with updated README and