jssm 5.143.28 → 5.143.29

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.28 at 6/12/2026, 4:10:08 PM
+* Generated for version 5.143.29 at 6/12/2026, 4:39:23 PM
 
 -->
-# jssm 5.143.28
+# jssm 5.143.29
 
 [**Try the live editor**](https://stonecypher.github.io/jssm-viz-demo/graph_explorer.html) ·
 [Documentation](https://stonecypher.github.io/jssm/docs/) ·
@@ -250,6 +250,37 @@ observation point.
 returns `false`.  An unknown state throws.  Branching code can rely on the
 distinction.
 
+**Overlapping state groups** let a state belong to several groups at once -
+something a strict hierarchy can't express.  A group is declared with `&`,
+and the same `&name` then drives transitions, shared metadata, boundary
+hooks, and runtime queries:
+
+```javascript
+const req = sm`
+  &InProgress : [connecting sending receiving];
+  &Receiving  : [receiving draining];
+
+  idle 'send'    -> connecting 'open' -> sending 'reply' -> receiving;
+  receiving 'eof' -> draining 'done'  -> idle;
+
+  &InProgress 'abort' -> idle;        // a transition from every group member
+  on enter &Receiving do 'log_rx';    // boundary hook fires crossing in
+`;
+
+req.action('send');
+req.isIn('InProgress');     // true  - connecting is in &InProgress
+req.groupsOf('receiving');  // Set { 'InProgress', 'Receiving' }  - overlap
+```
+
+`receiving` is in **both** groups simultaneously - it is in-progress *and*
+receiving.  When two groups disagree about the same action, a CSS-like
+cascade decides: state-specific edges win, then the innermost (nearest)
+group, then the later-declared one.  Groups render as nested Graphviz
+clusters, or as bracketed chips on the node label where memberships
+genuinely overlap.
+
+See the cookbook's overlapping-groups recipes for fuller worked examples.
+
 
 
 <br/>
@@ -281,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,017 tests at 100.0% line coverage
+  library.**  7,227 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.
@@ -414,11 +445,11 @@ If your contribution is missing here, please open an issue.
 
 <br/>
 
-***7,017 tests***, run 81,861 times.
+***7,227 tests***, run 82,269 times.
 
-- 6,261 specs with 100.0% coverage
-- 756 fuzz tests with 83.5% coverage
-- 5,880 TypeScript lines - 1.2 tests per line, 13.9 generated tests per line
+- 6,469 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
 
 [![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)