@typeonce/effect-machine-devtools 0.24.0 → 0.26.0

package/NOTICE

@@ -1,3 +1,7 @@
 Portions are adapted from the Effect project, which is distributed under the
 MIT License. See https://github.com/Effect-TS/effect and the source history for
 authorship and provenance.
+
+This product includes Eclipse Layout Kernel for JavaScript (elkjs), which is
+distributed under the Eclipse Public License 2.0. See
+https://github.com/kieler/elkjs for source and license information.

package/README.md

@@ -1,6 +1,6 @@
 # Effect Machine devtools
 
-`@typeonce/effect-machine-devtools` scans a local project for exported Effect Machine `.handle(...)` results and serves a live text-tree visualizer.
+`@typeonce/effect-machine-devtools` scans a local project for exported Effect Machine `.handle(...)` results and serves a live, statically laid-out statechart.
 
 The package is experimental and pre-1.0. Minor releases may change its command options, document schemas, and programmatic modules.
 
@@ -9,13 +9,13 @@ The package is experimental and pre-1.0. Minor releases may change its command o
 Core and devtools always release at the same version. Install matching versions:
 
 ```sh
-pnpm add @typeonce/effect-machine@latest effect@4.0.0-rc.111
+pnpm add @typeonce/effect-machine@latest effect@4.0.0-rc.112
 pnpm add --save-dev @typeonce/effect-machine-devtools@latest
 ```
 
 When pinning a release instead of using `latest`, use the same explicit version for both packages.
 
-The current release requires Node.js 22.19 or newer and Effect `4.0.0-rc.111`.
+The current release requires Node.js 22.19 or newer and Effect `4.0.0-rc.112`.
 
 ## Run the visualizer
 
@@ -62,26 +62,26 @@ Discovery parses source files without executing them. Evaluation then loads cand
 
 Run the devtools only against code you trust. The server has no authentication and binds to the loopback interface by default. Do not expose it on a public or untrusted network.
 
-## Inspection and simulation
+## Inspection and walkthroughs
 
-The visualizer shows topology, active initial paths, state annotations, events, transitions, branches, state updates, activities, source metadata, and diagnostics. The tree supports pointer and keyboard navigation, subtree expansion, related-state highlighting, and structured detail inspection.
+The visualizer shows topology as a read-only statechart with native horizontal and vertical scrolling, incremental zoom, and a fit-to-viewport overview. Machine tabs run across the top so the chart uses the rest of the viewport. States remain grouped inside their compound parents, while orthogonal routes connect each enabled transition without requiring a draggable canvas. State cards show projected value fields and invocations at a glance. A single click selects a state or transition, while a double click opens its dismissible inspector. State selection distinguishes incoming from outgoing relationships, and conditional branches with the same source and target share one topology edge while retaining their full details in the inspector.
 
-Simulation uses the same `Machine.planInitial` and `Machine.plan` semantics as the core package. Machine input and event payload controls are derived from their Effect schemas. Fields show their projected type, description, required or optional status, and constraints such as ranges, lengths, patterns, enum choices, and defaults. Supported controls include strings, numbers, booleans, enums, literals, nested objects, arrays, and unions. Browser constraints provide immediate feedback, then Effect Schema validates the complete value in the worker and reports failures beside the corresponding fields.
+The machine document includes projected value and output schemas for every state, plus the public machine and event input contracts. The browser renders those contracts as read-only field metadata: names, projected types, required or optional status, descriptions, ranges, lengths, patterns, and literal or enum values. It never asks for payload values merely to explore a static document.
 
-Start a session, send an enabled event, and inspect the resulting macrostep as structured microsteps. Events without payload fields run when clicked; events with input open a form first. The trace includes selected branches, before/after topology, exits, entries, state updates, raised events, emitted events, planned commands, completion, and output.
+Start a simulation to enter the document's captured configuration or its declared initial topology. Simulation mode turns transition edges into the control surface while state nodes remain read-only. Targetless transitions are rendered as self-loops, and runtime-resolved targets terminate at disabled dashed placeholders. Click an unambiguous available edge to advance directly; ambiguous branches open a compact picker at the click rather than guessing. Parallel regions stay active independently, compound states enter their declared initial child, and recorded shallow or deep history can be restored later in the same simulation.
 
-Each plan loads the exported machine in a fresh worker, decodes the portable session snapshot, and evaluates synchronous statechart callbacks. This supports conditional branches, parallel transitions, history, choices, state updates, reentry, and automatic stabilization. It also means synchronous code inside initial, transition, entry, exit, choice, history, and output callbacks runs during planning.
+Conditional branches, declinable transitions, automatic triggers, and invoke outcomes are shown as explicit choices rather than guessed. A runtime-resolved target or first use of an unrecorded history target remains visible but unavailable. Public event contracts are shown beside their choices, but values are not fabricated because no value can change a document-only decision reliably.
 
-The planner does not commit commands, start activities, invoke children, deliver `sendTo` events, or run returned Effects. Commands and emissions are shown in the trace instead. A worker is discarded after every request and a planning request is limited to ten seconds, but the devtools are still intended only for trusted projects.
+Every selected branch is retained in the immutable bottom timeline. Select an earlier step, then choose a different branch on the chart to truncate the old future and explore another path. The chart keeps candidate edges visible and reveals a new active configuration only when it falls outside the viewport.
 
-Simulation sessions use encoded snapshots and are tied to one source revision. A file change remounts the latest document; restart the simulation to use the new definition. Schema decoding and planning failures remain visible as diagnostics without discarding the topology.
+Simulations do not load project modules again, call resolvers or guards, apply state updates, run Effects, start invocations, deliver events, or commit commands. They are deliberately topology-only and side-effect-free. A file change remounts the latest document; restart the simulation to explore the new revision.
 
 ## Programmatic modules
 
-The first release publishes three programmatic modules:
+The package publishes three programmatic modules:
 
-- `DevToolsProtocol` defines the versioned worker, browser, and planner-session messages.
+- `DevToolsProtocol` defines the versioned discovery and browser registry messages.
 - `MachineDocument` defines and constructs the serializable inspection document.
-- `MachineSimulator` provides the conservative, document-only simulator for consumers that cannot load project code.
+- `MachineWalkthrough` provides immutable, document-only topology exploration with explicit choices, history, and time travel.
 
 The project inspector, registry, worker, and local server remain implementation modules. Their interfaces can change without becoming package-level compatibility commitments.