@field/cascade 0.5.2 → 0.7.0

package/CHANGELOG.md

@@ -2,6 +2,97 @@
 
 Notable changes to Cascade. Newest first.
 
+## 0.7.0 — 2026-09-12
+
+### Removed
+
+- **The dynamic executor.** `cascade run` had a second execution path: when the
+  deterministic runtime declined a graph, the CLI built a Studio `Graph`,
+  compiled each node with esbuild and cooked it through the class-based
+  scheduler. About 160 lines of second implementation, with behaviour that
+  differed from the one every other surface uses.
+
+  Removed on a measurement: all nine graphs across six sketches either render
+  through the deterministic runtime or are refused by the runtime's own
+  `runtime/preflight-environment` for declaring `runsOn: 'browser'`. 72 nodes,
+  none dynamic. A graph with no definition-v1 nodes is now refused by name
+  rather than run through the other path.
+
+  Nothing in the CLI reads the class registry any more, so
+  `registerStandardNodes()` is gone from the runner and the bundled CLI no
+  longer carries the class-based standard library.
+
+### Added
+
+- **`cascade.geo.FromRects`** and `rectsToGeometry`. `rects` was a declared core
+  type with no consumers; it converts to geometry as one closed polygon per
+  rect, with the tag preserved as a primitive string attribute. Raster rects
+  need their frame height, and the node refuses rather than guessing it — an
+  unflipped raster rect renders mirrored and plausible.
+- **A `files` capability on the CLI host.** Declaring `files` previously got a
+  node `undefined`, which pushed authors towards an undeclared `node:fs` import
+  — the invisible version of the thing declarations exist to make visible.
+  Reads resolve inside the project, writes are confined to `.cascade-cache/`.
+- **Stage output reaches the operator.** A stage could log and nobody could read
+  it: `stderr` was consulted only on failure and `stdout` only for its last
+  line. `cascade run --verbose` now forwards both.
+- **`--strict`** fails `validate` and `check` when a node names a module with no
+  file, and the summary says how many were unresolved rather than reporting
+  "passed" directly under the list.
+
+### Fixed
+
+- **Scrubbing no longer kills the cook it is waiting for.** The timeline marked
+  time-dependent nodes dirty *before* its own already-cooking guard, so every
+  scrubbed frame aborted the cook in flight and then deferred — a graph slower
+  than the mouse never finished one. The coalescing that was already there is
+  what makes leaving the running cook alone correct.
+- **A cancelled cook is no longer logged as a failure.** The node's state was
+  already right; only the console was lying, several times a second, which
+  buries the real failure when one arrives.
+
+## 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