From e8e3f5544ac680b0e7bb5ade924b61f6202731ba Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 24 Aug 2026 10:17:53 +0000
Subject: [PATCH] Version Packages

---
 .changeset/calm-planners-trace.md    |  8 --------
 packages/devtools/CHANGELOG.md       | 13 +++++++++++++
 packages/devtools/package.json       |  2 +-
 packages/effect-machine/CHANGELOG.md |  8 ++++++++
 packages/effect-machine/package.json |  2 +-
 5 files changed, 23 insertions(+), 10 deletions(-)
 delete mode 100644 .changeset/calm-planners-trace.md

diff --git a/.changeset/calm-planners-trace.md b/.changeset/calm-planners-trace.md
deleted file mode 100644
index 88ca820..0000000
--- a/.changeset/calm-planners-trace.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@typeonce/effect-machine": minor
-"@typeonce/effect-machine-devtools": minor
----
-
-Add planner-backed simulation sessions to the web visualizer. Machine and event inputs are rendered as fields from their Effect schemas, including type and constraint metadata, nested objects, arrays, unions, enums, literals, booleans, strings, and numbers. Browser constraints provide immediate feedback, while authoritative Effect Schema failures are mapped back to their fields. Each isolated step uses the real Effect Machine planner and shows selected branches, concrete topology changes, raised and emitted events, planned commands, completion, and output as a structured trace.
-
-Expose `Machine.inputEventSchemas` so inspection tools can describe or construct valid public events without reaching into the opaque event protocol. Planning evaluates synchronous statechart callbacks but does not commit commands or start runtime activities. Schema and planning failures remain visible beside the machine topology.
diff --git a/packages/devtools/CHANGELOG.md b/packages/devtools/CHANGELOG.md
index bec4421..315d5e1 100644
--- a/packages/devtools/CHANGELOG.md
+++ b/packages/devtools/CHANGELOG.md
@@ -1,5 +1,18 @@
 # @typeonce/effect-machine-devtools
 
+## 0.24.0
+
+### Minor Changes
+
+- eda432c: Add planner-backed simulation sessions to the web visualizer. Machine and event inputs are rendered as fields from their Effect schemas, including type and constraint metadata, nested objects, arrays, unions, enums, literals, booleans, strings, and numbers. Browser constraints provide immediate feedback, while authoritative Effect Schema failures are mapped back to their fields. Each isolated step uses the real Effect Machine planner and shows selected branches, concrete topology changes, raised and emitted events, planned commands, completion, and output as a structured trace.
+
+  Expose `Machine.inputEventSchemas` so inspection tools can describe or construct valid public events without reaching into the opaque event protocol. Planning evaluates synchronous statechart callbacks but does not commit commands or start runtime activities. Schema and planning failures remain visible beside the machine topology.
+
+### Patch Changes
+
+- Updated dependencies [eda432c]
+  - @typeonce/effect-machine@0.24.0
+
 ## 0.23.0
 
 ### Minor Changes
diff --git a/packages/devtools/package.json b/packages/devtools/package.json
index ad93fd5..274f001 100644
--- a/packages/devtools/package.json
+++ b/packages/devtools/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@typeonce/effect-machine-devtools",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Local development tools for Effect Machine",
   "author": "Sandro Maglione",
   "repository": {
diff --git a/packages/effect-machine/CHANGELOG.md b/packages/effect-machine/CHANGELOG.md
index 065ebbf..b0a9198 100644
--- a/packages/effect-machine/CHANGELOG.md
+++ b/packages/effect-machine/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @typeonce/effect-machine
 
+## 0.24.0
+
+### Minor Changes
+
+- eda432c: Add planner-backed simulation sessions to the web visualizer. Machine and event inputs are rendered as fields from their Effect schemas, including type and constraint metadata, nested objects, arrays, unions, enums, literals, booleans, strings, and numbers. Browser constraints provide immediate feedback, while authoritative Effect Schema failures are mapped back to their fields. Each isolated step uses the real Effect Machine planner and shows selected branches, concrete topology changes, raised and emitted events, planned commands, completion, and output as a structured trace.
+
+  Expose `Machine.inputEventSchemas` so inspection tools can describe or construct valid public events without reaching into the opaque event protocol. Planning evaluates synchronous statechart callbacks but does not commit commands or start runtime activities. Schema and planning failures remain visible beside the machine topology.
+
 ## 0.23.0
 
 ### Patch Changes
diff --git a/packages/effect-machine/package.json b/packages/effect-machine/package.json
index 04487f1..3ff82cf 100644
--- a/packages/effect-machine/package.json
+++ b/packages/effect-machine/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@typeonce/effect-machine",
-  "version": "0.23.0",
+  "version": "0.24.0",
   "description": "Schema-first state machines and statecharts for Effect",
   "author": "Sandro Maglione",
   "repository": {