jssm 5.143.30 → 5.143.33

package/README.md

@@ -18,10 +18,10 @@ Please edit the file it's derived from, instead: `./src/md/readme_base.md`
 
 
 
-* Generated for version 5.143.30 at 6/12/2026, 5:04:41 PM
+* Generated for version 5.143.33 at 6/17/2026, 9:14:01 PM
 
 -->
-# jssm 5.143.30
+# jssm 5.143.33
 
 [**Try the live editor**](https://stonecypher.github.io/jssm-viz-demo/graph_explorer.html) ·
 [Documentation](https://stonecypher.github.io/jssm/docs/) ·
@@ -312,7 +312,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.**  7,228 tests at 100.0% line coverage
+  library.**  7,231 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.
@@ -445,11 +445,11 @@ If your contribution is missing here, please open an issue.
 
 <br/>
 
-***7,228 tests***, run 82,270 times.
+***7,231 tests***, run 82,273 times.
 
-- 6,470 specs with 100.0% coverage
-- 758 fuzz tests with 76.7% coverage
-- 6,610 TypeScript lines - 1.1 tests per line, 12.4 generated tests per line
+- 6,473 specs with 100.0% coverage
+- 758 fuzz tests with 76.8% coverage
+- 6,605 TypeScript lines - 1.1 tests per line, 12.5 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/cdn/instance.js

@@ -23486,7 +23486,7 @@ var constants = /*#__PURE__*/Object.freeze({
  *  Useful for runtime diagnostics and for embedding in serialized machine
  *  snapshots so that deserializers can detect version-skew.
  */
-const version = "5.143.30";
+const version = "5.143.33";
 
 // whargarbl lots of these return arrays could/should be sets
 const { state_name_chars, state_name_first_chars, action_label_chars } = constants;
@@ -26161,10 +26161,31 @@ class Machine {
         this.set_hook({ kind: 'exit', from, handler });
         return this;
     }
-    /** Register a hook that fires after leaving a specific state (post-exit).
-     *  @param from    - The state that was exited.
-     *  @param handler - Callback invoked after exit completes.
+    /** Register a hook that fires when a state's `after` timer elapses — the
+     *  delay-over companion to `a after 5s -> b;` style time transitions.  It
+     *  does NOT fire when the state is entered or left by ordinary dispatch;
+     *  use {@link hook_entry} / {@link hook_exit} for those.  (Versions through
+     *  5.143.28 also spuriously fired it on entering the state, the jssm side
+     *  of StoneCypher/fsl#1327.)
+     *  @param from    - The state whose `after` timer is being watched.
+     *  @param handler - Callback invoked when the timer fires, just before the
+     *                   timed transition is taken; informational — its outcome
+     *                   cannot reject the transition.
      *  @returns `this` for chaining.
+     *
+     *  @example
+     *    const m = sm`a after 1000 -> b; a -> c; c -> a;`;
+     *    let calls = 0;
+     *    m.hook_after('a', () => { calls += 1; });
+     *    m.go('c');
+     *    m.go('a');
+     *    // ordinary dispatch never fires it; only the timer elapsing does:
+     *    calls;  // => 0
+     *    m.clear_state_timeout();
+     *
+     *  @see hook_entry
+     *  @see hook_exit
+     *  @see set_state_timeout
      */
     hook_after(from, handler) {
         this.set_hook({ kind: 'after', from, handler });
@@ -26774,15 +26795,12 @@ class Machine {
                         data_changed = true;
                     }
                 }
-                // 2. after hook
-                if (this._has_after_hooks) {
-                    const ah = this._after_hooks.get(newStateOrAction);
-                    const outcome = abstract_hook_step(ah, hook_args);
-                    // there's no such thing as after not passing, so, omit the result pass check.
-                    // after hooks are post-exit and informational — their outcome never changes
-                    // data, so there's no data_changed branch here (it would be unreachable).
-                    _update_hook_fields(hook_args, outcome);
-                }
+                // 2. (removed) After hooks do NOT fire on dispatch.  They are the
+                // `after`-timer's companion (fsl#698: "delay over!") and fire only from
+                // the state-timeout path.  Through v5.143.28 a probe here keyed on
+                // newStateOrAction spuriously fired them on entering the hooked state —
+                // or on a same-named action — making one timer elapse read as two
+                // handler calls (StoneCypher/fsl#1327).
                 // 3. any transition hook
                 if (this._any_transition_hook !== undefined) {
                     const outcome = abstract_hook_step(this._any_transition_hook, hook_args);

package/dist/cdn/viz.js

@@ -23511,7 +23511,7 @@ var constants = /*#__PURE__*/Object.freeze({
  *  Useful for runtime diagnostics and for embedding in serialized machine
  *  snapshots so that deserializers can detect version-skew.
  */
-const version = "5.143.30";
+const version = "5.143.33";
 
 // whargarbl lots of these return arrays could/should be sets
 const { state_name_chars, state_name_first_chars, action_label_chars } = constants;
@@ -26186,10 +26186,31 @@ class Machine {
         this.set_hook({ kind: 'exit', from, handler });
         return this;
     }
-    /** Register a hook that fires after leaving a specific state (post-exit).
-     *  @param from    - The state that was exited.
-     *  @param handler - Callback invoked after exit completes.
+    /** Register a hook that fires when a state's `after` timer elapses — the
+     *  delay-over companion to `a after 5s -> b;` style time transitions.  It
+     *  does NOT fire when the state is entered or left by ordinary dispatch;
+     *  use {@link hook_entry} / {@link hook_exit} for those.  (Versions through
+     *  5.143.28 also spuriously fired it on entering the state, the jssm side
+     *  of StoneCypher/fsl#1327.)
+     *  @param from    - The state whose `after` timer is being watched.
+     *  @param handler - Callback invoked when the timer fires, just before the
+     *                   timed transition is taken; informational — its outcome
+     *                   cannot reject the transition.
      *  @returns `this` for chaining.
+     *
+     *  @example
+     *    const m = sm`a after 1000 -> b; a -> c; c -> a;`;
+     *    let calls = 0;
+     *    m.hook_after('a', () => { calls += 1; });
+     *    m.go('c');
+     *    m.go('a');
+     *    // ordinary dispatch never fires it; only the timer elapsing does:
+     *    calls;  // => 0
+     *    m.clear_state_timeout();
+     *
+     *  @see hook_entry
+     *  @see hook_exit
+     *  @see set_state_timeout
      */
     hook_after(from, handler) {
         this.set_hook({ kind: 'after', from, handler });
@@ -26799,15 +26820,12 @@ class Machine {
                         data_changed = true;
                     }
                 }
-                // 2. after hook
-                if (this._has_after_hooks) {
-                    const ah = this._after_hooks.get(newStateOrAction);
-                    const outcome = abstract_hook_step(ah, hook_args);
-                    // there's no such thing as after not passing, so, omit the result pass check.
-                    // after hooks are post-exit and informational — their outcome never changes
-                    // data, so there's no data_changed branch here (it would be unreachable).
-                    _update_hook_fields(hook_args, outcome);
-                }
+                // 2. (removed) After hooks do NOT fire on dispatch.  They are the
+                // `after`-timer's companion (fsl#698: "delay over!") and fire only from
+                // the state-timeout path.  Through v5.143.28 a probe here keyed on
+                // newStateOrAction spuriously fired them on entering the hooked state —
+                // or on a same-named action — making one timer elapse read as two
+                // handler calls (StoneCypher/fsl#1327).
                 // 3. any transition hook
                 if (this._any_transition_hook !== undefined) {
                     const outcome = abstract_hook_step(this._any_transition_hook, hook_args);