jssm 5.162.11 → 5.162.12

package/dist/deno/README.md

@@ -18,10 +18,10 @@ Please edit the file it's derived from, instead: `./src/md/readme_base.md`
 
 
 
-* Generated for version 5.162.11 at 7/12/2026, 8:54:54 AM
+* Generated for version 5.162.12 at 7/12/2026, 10:09:04 AM
 
 -->
-# jssm 5.162.11
+# jssm 5.162.12
 
 [**Try the live editor**](https://stonecypher.github.io/jssm-viz-demo/graph_explorer.html) ·
 [Documentation](https://stonecypher.github.io/jssm/docs/) ·
@@ -333,7 +333,7 @@ That decision shows up everywhere downstream:
   or run `npm run benny` against your own machine.
 
 - **More thoroughly tested than any other JavaScript state-machine
-  library.**  8,623 tests at 100.0% line coverage
+  library.**  8,640 tests at 100.0% line coverage
   ([report](https://coveralls.io/github/StoneCypher/jssm)), plus
   fuzz testing via `fast-check`, with parser test data across ten natural
   languages and Emoji.
@@ -467,11 +467,11 @@ If your contribution is missing here, please open an issue.
 
 <br/>
 
-***8,623 tests***, run 97,921 times.
+***8,640 tests***, run 98,037 times.
 
-- 7,721 specs with 100.0% coverage
-- 902 fuzz tests with 56.6% coverage
-- 10,907 TypeScript lines - 0.8 tests per line, 9.0 generated tests per line
+- 7,737 specs with 100.0% coverage
+- 903 fuzz tests with 56.5% coverage
+- 10,946 TypeScript lines - 0.8 tests per line, 9.0 generated tests per line
 
 [![Actions Status](https://github.com/StoneCypher/jssm/workflows/Node%20CI/badge.svg)](https://github.com/StoneCypher/jssm/actions)
 [![NPM version](https://img.shields.io/npm/v/jssm.svg)](https://www.npmjs.com/package/jssm)

package/dist/deno/jssm.d.ts

@@ -1104,6 +1104,12 @@ declare class Machine<mDT> {
      *  {@link Machine.transition}, so it fires no hooks, mutates no machine
      *  state, and touches no `data`.  A state with no probabilistic exits
      *  (a terminal, or a forced-only `~>` state) ends the walk.
+     *
+     *  Terminality is checked before the first transition and after every
+     *  transition.  A terminal start therefore completes with length zero even
+     *  when `max_steps` is zero, and a terminal reached on the final permitted
+     *  transition is completed rather than step-capped.
+     *
      *  @param start - State to begin the walk from.
      *  @param max_steps - Maximum transitions before the walk is step-capped.
      *  @param exit_memo - Per-run-set cache of {@link Machine.probable_exits_for}
@@ -1126,7 +1132,9 @@ declare class Machine<mDT> {
      *  current state, each ending at a terminal or after `max_steps`.  In
      *  `steady_state` mode yields exactly one walk of `max_steps` steps.  This
      *  is the lazy engine behind {@link Machine.stochastic_summary}; the
-     *  fsl-stochastic panel drives it across animation frames.
+     *  fsl-stochastic panel drives it across animation frames.  A walk already
+     *  at a terminal is reported as terminated with length zero, including when
+     *  `max_steps` is zero.
      *
      *  Passing `seed` reseeds the machine for reproducible runs.  Unlike
      *  {@link Machine.stochastic_summary}, the generator does NOT restore the
@@ -1149,6 +1157,10 @@ declare class Machine<mDT> {
      *  per-run `path_lengths`, `terminal_reached`, and `capped`; `steady_state`
      *  mode runs one long walk and omits those fields.
      *
+     *  Monte-Carlo runs count as `terminal_reached` when they start at a
+     *  terminal or reach one on the final permitted transition.  Terminal
+     *  starts contribute zero to `path_lengths`, even when `max_steps` is zero.
+     *
      *  Timing (`after`) decorations and data-guard conditions are not modeled
      *  by this sampler; it walks the probabilistic graph topology.
      *  @param opts - {@link JssmStochasticOptions}.  `runs` defaults to the