wunderspec 0.129.3__tar.gz → 0.129.5__tar.gz

{wunderspec-0.129.3 → wunderspec-0.129.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: wunderspec
-Version: 0.129.3
+Version: 0.129.5
 Summary: Protocol specifications as Python code
 Author: Igor Konnov, Thomas Pani
 License-File: LICENSE
@@ -18,6 +18,12 @@ Description-Content-Type: text/markdown
 
 # Wunderspec
 
+[![PyPI](https://img.shields.io/pypi/v/wunderspec.svg)](https://pypi.org/project/wunderspec/)
+[![Lint](https://github.com/wunderspec/wunderspec/actions/workflows/lint.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/lint.yml)
+[![Build](https://github.com/wunderspec/wunderspec/actions/workflows/build.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/build.yml)
+[![Run Examples](https://github.com/wunderspec/wunderspec/actions/workflows/run-examples.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/run-examples.yml)
+[![Convert to TLA+](https://github.com/wunderspec/wunderspec/actions/workflows/convert-to-tla.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/convert-to-tla.yml)
+
 Wunderspec is a Python DSL for writing and checking executable specifications.
 
 Distributed systems often fail due to unforeseen issues: message reordering,
@@ -29,21 +35,24 @@ they become production incidents.
 
 This is **the open-core distribution**.
 
-> 📋 **Cheatsheet:** the [Wunderspec cheatsheet](https://github.com/wunderspec/wunderspec/blob/main/docs/user-references/cheatsheet.html)
-> summarizes the DSL and CLI on a single page — keep it open while you work.
+> 📋 **Wunderspec in 5 minutes:** the [Wunderspec in Five Minutes][five-minutes]
+> gives you a quick overview of the core concepts.
+
+> 📋 **Cheatsheet:** the [Wunderspec cheatsheet][cheatsheet]
+> summarizes the DSL and CLI in a few pages — keep it open while you work.
 
 ## 1. Wunderspec in Action
 
-Follow Bob in [his Wunderspec adventure](https://github.com/wunderspec/wunderspec/blob/main/docs/user-stories/bobs_log.md). There,
-Bob writes a specification of a write-ahead log, finds a bug, replays the
-counterexample and fixes the specification.
+Follow Bob in [his Wunderspec adventure][bobs_log].  There, Bob writes a
+specification of a write-ahead log, finds a bug, replays the counterexample and
+fixes the specification.
 
 ## 2. Installation
 
-Using [uv](https://docs.astral.sh/uv/):
+Using [uv][]:
 
 ```sh
-uv add wunderspec
+uv tool install wunderspec
 ```
 
 After installation, the CLI is available:
@@ -52,6 +61,13 @@ After installation, the CLI is available:
 wunderspec --help
 ```
 
+If you want to add Wunderspec as a dependency, just type:
+
+```sh
+uv add wunderspec
+uv sync
+```
+
 ## 3. Features
 
 This open-core package includes the features marked ✅ in the **Open Core**
@@ -74,14 +90,19 @@ commands are not included in this package.
 
 ## 4. Release Provenance
 
-- Release tag: `v0.129.3`
-- Source commit: `b21d0bd6cd54d3e259e418626727410c4875ac0b`
+- Release tag: `v0.129.5`
+- Source commit: `8561aecba08feb12e97117b0c7632ad83e9d8076`
 
-See [tests/README.md](https://github.com/wunderspec/wunderspec/blob/main/tests/README.md)
-for the development test log captured at release time.
+See [tests/README.md][] for the development test log captured at release time.
 
 ## 5. License
 
 Wunderspec is distributed under the Functional Source License, Version 1.1, with
-an Apache 2.0 future license (FSL-1.1-ALv2). See
-[LICENSE](https://github.com/wunderspec/wunderspec/blob/main/LICENSE).
+an Apache 2.0 future license (FSL-1.1-ALv2). See [LICENSE][].
+
+[cheatsheet]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-references/cheatsheet.html
+[Wunderspec in Five Minutes]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-references/wunderspec-one-pager.md
+[bobs_log]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-stories/bobs_log.md
+[uv]: https://docs.astral.sh/uv/
+[tests/README.md]: https://github.com/wunderspec/wunderspec/blob/main/tests/README.md
+[LICENSE]: https://github.com/wunderspec/wunderspec/blob/main/LICENSE

wunderspec-0.129.5/README.md

@@ -0,0 +1,92 @@
+![Wunderspec](https://raw.githubusercontent.com/wunderspec/wunderspec/main/assets/design/png/wunderspec-readme-header-dark-1200x480.png)
+
+# Wunderspec
+
+[![PyPI](https://img.shields.io/pypi/v/wunderspec.svg)](https://pypi.org/project/wunderspec/)
+[![Lint](https://github.com/wunderspec/wunderspec/actions/workflows/lint.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/lint.yml)
+[![Build](https://github.com/wunderspec/wunderspec/actions/workflows/build.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/build.yml)
+[![Run Examples](https://github.com/wunderspec/wunderspec/actions/workflows/run-examples.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/run-examples.yml)
+[![Convert to TLA+](https://github.com/wunderspec/wunderspec/actions/workflows/convert-to-tla.yml/badge.svg)](https://github.com/wunderspec/wunderspec/actions/workflows/convert-to-tla.yml)
+
+Wunderspec is a Python DSL for writing and checking executable specifications.
+
+Distributed systems often fail due to unforeseen issues: message reordering,
+race condition, stale observations, retry behavior, crashes and restarts,
+network outages, vibe code. Adding more example tests is often not enough to
+find these bugs before they make it to production. Specifications written in
+Wunderspec surface these issues early, so that teams find design flaws before
+they become production incidents.
+
+This is **the open-core distribution**.
+
+> 📋 **Wunderspec in 5 minutes:** the [Wunderspec in Five Minutes][five-minutes]
+> gives you a quick overview of the core concepts.
+
+> 📋 **Cheatsheet:** the [Wunderspec cheatsheet][cheatsheet]
+> summarizes the DSL and CLI in a few pages — keep it open while you work.
+
+## 1. Wunderspec in Action
+
+Follow Bob in [his Wunderspec adventure][bobs_log].  There, Bob writes a
+specification of a write-ahead log, finds a bug, replays the counterexample and
+fixes the specification.
+
+## 2. Installation
+
+Using [uv][]:
+
+```sh
+uv tool install wunderspec
+```
+
+After installation, the CLI is available:
+
+```sh
+wunderspec --help
+```
+
+If you want to add Wunderspec as a dependency, just type:
+
+```sh
+uv add wunderspec
+uv sync
+```
+
+## 3. Features
+
+This open-core package includes the features marked ✅ in the **Open Core**
+column. Premium-only command names stay visible for discoverability, but those
+commands are not included in this package.
+
+| Feature                       | Open Core | Premium |
+| ----------------------------- | :-------: | :-----: |
+| Symbolic expression evaluator |    ✅     |   ✅    |
+| `wunderspec lint`             |    ✅     |   ✅    |
+| `wunderspec run`              |    ✅     |   ✅    |
+| `wunderspec replay`           |    ✅     |   ✅    |
+| `wunderspec convert`          |    ✅     |   ✅    |
+| `wunderspec check`            |    ✅     |   ✅    |
+| `wunderspec with-tlc`         |    ✅     |   ✅    |
+| `wunderspec with-apalache`    |    ✅     |   ✅    |
+| `wunderspec fuzz`             |    ❌     |   ✅    |
+| `wunderspec rust`             |    ❌     |   ✅    |
+| `wunderspec lean`             |    ❌     |   ✅    |
+
+## 4. Release Provenance
+
+- Release tag: `v0.129.5`
+- Source commit: `8561aecba08feb12e97117b0c7632ad83e9d8076`
+
+See [tests/README.md][] for the development test log captured at release time.
+
+## 5. License
+
+Wunderspec is distributed under the Functional Source License, Version 1.1, with
+an Apache 2.0 future license (FSL-1.1-ALv2). See [LICENSE][].
+
+[cheatsheet]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-references/cheatsheet.html
+[Wunderspec in Five Minutes]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-references/wunderspec-one-pager.md
+[bobs_log]: https://github.com/wunderspec/wunderspec/blob/main/docs/user-stories/bobs_log.md
+[uv]: https://docs.astral.sh/uv/
+[tests/README.md]: https://github.com/wunderspec/wunderspec/blob/main/tests/README.md
+[LICENSE]: https://github.com/wunderspec/wunderspec/blob/main/LICENSE

{wunderspec-0.129.3 → wunderspec-0.129.5}/docs/user-references/cheatsheet.html

@@ -547,15 +547,13 @@
             </div>
             <div class="desc">Boolean equality / inequality</div>
           </div>
-          <div class="item">
-            <div class="sig">Ite(cond, then_expr, else_expr)</div>
-            <div class="desc">If-then-else expression; all three arguments are expressions</div>
-          </div>
           <div class="item">
             <div class="alt">
+              <span class="sig">Ite(cond, then_expr, else_expr)</span>
+              <span class="sep">or</span>
               <span class="sig">p.if_(cond).else_(q)</span>
-            </div>
-            <div class="desc">Method-chain form of <span class="sig">Ite(cond, p, q)</span></div>
+	    </div>
+            <div class="desc">If-then-else expression; all three arguments are expressions</div>
           </div>
         </div>
       </section>
@@ -575,13 +573,17 @@
             <div class="sig">x == y   x != y   x &lt; y   x &lt;= y   x &gt; y   x &gt;= y</div>
             <div class="desc">Comparison operators; return <span class="sig">BoolExpr</span></div>
           </div>
+          <div class="item">
+            <span class="sig">Set(lo, ..., hi)</span>
+            <div class="desc">Inclusive integer set <span class="sig">{lo, …, hi}</span>; distinct from list <span class="sig">Range(start, end)</span></div>
+          </div>
           <div class="item">
             <div class="alt">
-              <span class="sig">Interval(lo, hi)</span>
-              <span class="sep">or</span>
-              <span class="sig">lo.upto(hi)</span>
+                <span class="sig">Ints</span>
+                <span class="sep">or</span>
+                <span class="sig">UnsignedInts</span>
             </div>
-            <div class="desc">Inclusive integer set <span class="sig">{lo, …, hi}</span>; distinct from list <span class="sig">Range(start, end)</span></div>
+            <div class="desc">All signed / unsigned integers (infinite sets)</div>
           </div>
         </div>
       </section>
@@ -594,16 +596,16 @@
         </header>
         <div class="content">
           <div class="item">
-            <div class="sig">Set(1, 2, 3)</div>
-            <div class="desc">New set with the given elements</div>
+            <div class="sig">Set(2, 5, 8, 8)</div>
+            <div class="desc">New set with the given elements, duplicates ignored</div>
           </div>
           <div class="item">
-            <div class="sig">Set(1, ..., 4)</div>
-            <div class="desc">Shorthand: <span class="sig">Set(1, 2, 3, 4)</span></div>
+            <div class="sig">Set(lo, ..., hi)</div>
+            <div class="desc">Inclusive integer set <span class="sig">{lo, …, hi}</span></div>
           </div>
           <div class="item">
             <div class="sig">Set(E)</div>
-            <div class="desc">Empty set whose elements have type <span class="sig">E</span></div>
+            <div class="desc">Empty set whose elements have sort <span class="sig">E</span></div>
           </div>
           <div class="item">
             <div class="alt">
@@ -746,12 +748,12 @@
         </header>
         <div class="content">
           <div class="item">
-            <div class="sig">List(1, 2, 3)</div>
-            <div class="desc">New list with the given elements in order</div>
+            <div class="sig">List(2, 3, 3, 4)</div>
+            <div class="desc">New list with the given elements in order, duplicates allowed</div>
           </div>
           <div class="item">
             <div class="sig">List(E)</div>
-            <div class="desc">Empty list with elements of type <span class="sig">E</span></div>
+            <div class="desc">Empty list with elements of sort <span class="sig">E</span></div>
           </div>
           <div class="item">
             <div class="sig">Range(start, end)</div>
@@ -835,7 +837,7 @@
           </div>
           <div class="item">
             <div class="sig">M[key]</div>
-            <div class="desc">Look up value for <span class="sig">key</span></div>
+            <div class="desc">Look up value for <span class="sig">key</span> (<span class="sig">key</span> must exist)</div>
           </div>
           <div class="item">
             <div class="sig">M.insert(k, v)</div>
@@ -1069,6 +1071,49 @@ class Flag:
         </div>
       </section>
 
+      <!-- Temporal -->
+      <section class="card" data-title="temporal always eventually enabled weakfair strongfair liveness safety action_expr forall exists fairness">
+        <header>
+          <h2>Temporal expressions</h2>
+          <span class="hint">TemporalExpr — used in @temporal properties</span>
+        </header>
+        <div class="content">
+          <div class="item">
+            <div class="sig">Always(P)</div>
+            <div class="desc">□P — <span class="sig">P</span> holds in every state of the execution</div>
+          </div>
+          <div class="item">
+            <div class="sig">Eventually(P)</div>
+            <div class="desc">◇P — <span class="sig">P</span> holds in some future state</div>
+          </div>
+          <div class="item">
+            <div class="sig">AndT(t1, t2)   OrT(t1, t2)   NotT(t)   ImpliesT(t1, t2)</div>
+            <div class="desc">Temporal connectives; Boolean arguments are lifted to <span class="sig">TemporalExpr</span></div>
+          </div>
+          <div class="item">
+            <div class="sig">Enabled(my_action, arg)</div>
+            <div class="desc">True if <span class="sig">my_action</span> can fire; requires <span class="sig">@action(inline=False)</span></div>
+          </div>
+          <div class="item">
+            <div class="sig">Enabled(action_expr)</div>
+            <div class="desc">Direct action-expression form of <span class="sig">ENABLED A</span></div>
+          </div>
+          <div class="item">
+            <div class="sig">WeakFair(my_action, arg, vars=("x",))</div>
+            <div class="desc">WF — if action is continuously enabled it must eventually fire</div>
+          </div>
+          <div class="item">
+            <div class="sig">StrongFair(my_action, arg, vars=("x",))</div>
+            <div class="desc">SF — if action is enabled infinitely often it must eventually fire</div>
+          </div>
+          <div class="item">
+            <div class="sig">Forall(WeakFair(send, p, vars=("msgs",)) for p in PROCS)</div>
+            <div class="desc">Temporal quantification over a parameter set</div>
+          </div>
+        </div>
+      </section>
+
+
       <!-- State machine -->
       <section class="card" style="grid-column:span 12" data-title="state machine action context one_of alternatives split assume cache Param StateVar PARAMETER StateFieldType UPSERT direct assignment nested editing atomic">
         <header>
@@ -1277,48 +1322,6 @@ InChan = SubMachine(Data="Message", chan="cin")
         </div>
       </section>
 
-      <!-- Temporal -->
-      <section class="card" data-title="temporal always eventually enabled weakfair strongfair liveness safety action_expr forall exists fairness">
-        <header>
-          <h2>Temporal expressions</h2>
-          <span class="hint">TemporalExpr — used in @temporal properties</span>
-        </header>
-        <div class="content">
-          <div class="item">
-            <div class="sig">Always(P)</div>
-            <div class="desc">□P — <span class="sig">P</span> holds in every state of the execution</div>
-          </div>
-          <div class="item">
-            <div class="sig">Eventually(P)</div>
-            <div class="desc">◇P — <span class="sig">P</span> holds in some future state</div>
-          </div>
-          <div class="item">
-            <div class="sig">AndT(t1, t2)   OrT(t1, t2)   NotT(t)   ImpliesT(t1, t2)</div>
-            <div class="desc">Temporal connectives; Boolean arguments are lifted to <span class="sig">TemporalExpr</span></div>
-          </div>
-          <div class="item">
-            <div class="sig">Enabled(my_action, arg)</div>
-            <div class="desc">True if <span class="sig">my_action</span> can fire; requires <span class="sig">@action(inline=False)</span></div>
-          </div>
-          <div class="item">
-            <div class="sig">Enabled(action_expr)</div>
-            <div class="desc">Direct action-expression form of <span class="sig">ENABLED A</span></div>
-          </div>
-          <div class="item">
-            <div class="sig">WeakFair(my_action, arg, vars=("x",))</div>
-            <div class="desc">WF — if action is continuously enabled it must eventually fire</div>
-          </div>
-          <div class="item">
-            <div class="sig">StrongFair(my_action, arg, vars=("x",))</div>
-            <div class="desc">SF — if action is enabled infinitely often it must eventually fire</div>
-          </div>
-          <div class="item">
-            <div class="sig">Forall(WeakFair(send, p, vars=("msgs",)) for p in PROCS)</div>
-            <div class="desc">Temporal quantification over a parameter set</div>
-          </div>
-        </div>
-      </section>
-
       <!-- Imperative flow -->
       <section class="card" data-title="flow with_flow if else return end imperative conditional">
         <header>

wunderspec-0.129.5/docs/user-references/wunderspec-five-minutes.md

@@ -0,0 +1,114 @@
+# Wunderspec in Five Minutes
+
+Since nobody has time to read docs, here is a one-page summary of what you want
+to know about Wunderspec. For more details, see the [Cheatsheet][cheatsheet].
+
+**States and actions**. The most important definitions are annotated with
+`@state` and `@action`. Wunderspec uses these definitions to define a *state
+machine*.  This state machine starts in a state defined with
+`@action(init=True)` and evolves via one or more actions labeled with `@action`.
+Normally, the top-level actions are grouped with an action called `step`. All
+actions are atomic -- either an action executes (when all assumptions are met),
+and its effects are applied, or it doesn't execute at all. For a simple example,
+see the [sloppy counter][sloppy_counter].
+
+**Assumptions and assignments**. Actions normally contain assumptions about
+the current state and assignments to the next state. Here is a typical example
+from the [ledger][ledger]:
+
+```python
+@action
+def start_transaction(c: Context[LedgerState], company: Annotated[Expr, str]):
+    s = c.state
+    c.assume(s.pending_seq_no[company] == -1)
+    s.pending_seq_no[company] = s.registered_seq_no[company]
+    s.registered_seq_no[company] += 1
+```
+
+The Wunderspec transpiler collects the assumptions and assignments, when the
+Python code is executed. They are used to define the state machine.
+
+**Every variable of a state machine may be assigned at most once in an action**.
+Use local Python variables to compute intermediate values.
+
+**Value generation**. State machines in Wunderspec often use
+non-deterministically generated values. These values are produced with `with
+c.one_of(...)`. We can see an example in the [sloppy counter][sloppy_counter]:
+
+```python
+@action
+def step(c: Context[SloppyCounterState]):
+    with c.one_of(cpus(c.state), "cpu") as cpu:
+        increment(c, cpu)
+```
+
+In the code above, `cpu` receive a value from the set `cpus(c.state)`.  The
+second argument to `one_of` is a convenient alias for the intermediate
+representation and generated code. When it's omitted, the name is generated
+automatically. Wunderspec commands interpret this construct differently:
+
+ - `wunderspec run` generates values randomly,
+ 
+ - `wunderspec check` generates values systematically to explore all possible
+ executions,
+
+ - `wunderspec with-apalache` produces values with the SMT solver Z3.
+
+**Control non-determinism.** Wunderspec does not have explicit processes,
+threads, processors, or other computing devices. Instead, is uses control
+non-determinism to model choice of actions. Non-deterministic choice is done
+with `with c.alternatives(...)`. For example, he is how [simple
+WAL][simple_wal1] defines `step` with alternatives:
+
+```python
+@action
+def step(c: Context[KvStoreState]):
+    run, crash = c.alternatives("Run", "Restart")
+    with run:
+        kv_step(c)
+    with crash:
+        s = c.state
+        s.pc = Val(PC.Start)
+        s.pending = Command.Nop()
+        s.kv_mem = s.KEYS.map_to(lambda _: Val(0))
+```
+
+In the above code, the call to `c.alternatives` introduces two branching
+alternatives, "Run" and "Restart". Wunderspec commands interpret these
+alternatives differently:
+
+ - `wunderspec run` chooses one of the alternatives randomly,
+ 
+ - `wunderspec check` explores all possible alternatives systematically,
+
+ - `wunderspec with-apalache` explores the alternatives symbolically.
+
+Similar to `c.alternatives`, we have a special version `c.split(condition)` that
+introduces two alternatives, one where `condition` holds and another where it
+doesn't hold.
+
+**Properties.** Properties are the targets for analysis tools. Wunderspec
+currently has three kinds of properties:
+
+ - state `@invariant` is a Boolean condition over a state that must hold in all
+ states reachable from the initial states. All tools check state invariants. If
+ they find a state that violates the invariant, they report a counterexample
+ execution.
+ 
+ - state `@example` is a Boolean condition over a state that maybe holds in some
+ execution of the state machine. Tools report one or more executions that lead
+ to a state that satisfies the example.
+ 
+ - `@temporal` properties must hold in all executions. They are typically used
+ to check complex safety properties and liveness properties. Currently, only
+ `with-tlc` and `with-apalache` check temporal properties.
+ 
+ **Immutability.** While the Wunderspec state machines mutate the state,
+ the expressions operate over immutable data structures. For the data
+ structures, see the [Cheatsheet][cheatsheet].
+ 
+ 
+[sloppy_counter]: https://github.com/wunderspec/wunderspec/blob/main/examples/sloppy_counter.py
+[ledger]: https://github.com/wunderspec/wunderspec/blob/main/examples/ledger.py
+[simple_wal1]: https://github.com/wunderspec/wunderspec/blob/main/examples/simple_wal1.py
+[cheatsheet]: https://wunderspec.com/cheatsheet

{wunderspec-0.129.3 → wunderspec-0.129.5}/examples/payment.py

@@ -15,6 +15,7 @@ from wunderspec import (
     Exists,
     Expr,
     Field,
+    Forall,
     List,
     Map,
     Param,
@@ -394,12 +395,12 @@ def type_invariant(s: PaymentState) -> BoolExpr:
 
 @invariant
 def no_overdraft(s: PaymentState) -> BoolExpr:
-    return accounts(s).forall(lambda account: s.balance[account] >= 0)
+    return Forall(s.balance[account] >= 0 for account in accounts(s))
 
 
 @invariant
 def no_double_charge(s: PaymentState) -> BoolExpr:
-    return s.Txn.forall(lambda txn: event_count(s, txn, CHARGED) <= Val(1))
+    return Forall(event_count(s, txn, CHARGED) <= Val(1) for txn in s.Txn)
 
 
 @invariant

{wunderspec-0.129.3 → wunderspec-0.129.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "wunderspec"
-version = "0.129.3"
+version = "0.129.5"
 description = "Protocol specifications as Python code"
 authors = [
     {name = "Igor Konnov"},

{wunderspec-0.129.3 → wunderspec-0.129.5}/tests/README.md

@@ -6,9 +6,9 @@ public distribution to keep the package focused. The full development
 
 ## Release Provenance
 
-- Release tag: `v0.129.3`
-- Source commit: `b21d0bd6cd54d3e259e418626727410c4875ac0b`
-- Test log captured at: `2026-06-16T07:26:42Z`
+- Release tag: `v0.129.5`
+- Source commit: `8561aecba08feb12e97117b0c7632ad83e9d8076`
+- Test log captured at: `2026-06-16T19:14:56Z`
 - `make test` exit code: `0`
 
 ## Full Test Log From the Development Repository
@@ -124,5 +124,5 @@ tests/test_tla.py ...................................................... [ 94%]
 tests/test_tlc_trace.py ....                                             [ 98%]
 tests/test_trace_output.py .........................                     [100%]
 
-====================== 2343 passed, 11 skipped in 25.63s =======================
+====================== 2343 passed, 11 skipped in 22.31s =======================
 ```

{wunderspec-0.129.3 → wunderspec-0.129.5}/uv.lock

@@ -1781,7 +1781,7 @@ wheels = [
 
 [[package]]
 name = "wunderspec"
-version = "0.129.3"
+version = "0.129.5"
 source = { editable = "." }
 dependencies = [
     { name = "executing" },

{wunderspec-0.129.3 → wunderspec-0.129.5}/wunderspec/__init__.py

@@ -144,7 +144,7 @@ from .random_walk import state_view
 from .source_tracking import enable_source_tracking
 from .submachine import SubMachine
 
-__version__ = "0.129.3"
+__version__ = "0.129.5"
 
 __all__ = [
     # Constructor functions

{wunderspec-0.129.3 → wunderspec-0.129.5}/wunderspec/cli.py

@@ -500,19 +500,23 @@ def main() -> None:
 
     convert_parser = subparsers.add_parser(
         "convert",
-        help="Convert a Wunderspec module to another format",
+        help="Convert Wunderspec to TLA+ or Quint to Wunderspec",
+        description=(
+            "Convert a Wunderspec .py module to TLA+ .tla, "
+            "or a Quint .qnt module to Wunderspec .py."
+        ),
     )
     convert_parser.add_argument(
         "--from",
         dest="source",
         required=True,
-        help="Source Python file containing the Wunderspec module",
+        help="Source specification file: Wunderspec .py or Quint .qnt",
     )
     convert_parser.add_argument(
         "--to",
         dest="output",
         required=True,
-        help="Output file path (e.g., output.tla)",
+        help="Output file path: .tla for Wunderspec input, .py for Quint input",
     )
     convert_parser.add_argument(
         "--defs",
@@ -524,7 +528,9 @@ def main() -> None:
         "--instance",
         default=None,
         help="Name of a partially specialized state object in the source module "
-        "(e.g., proto5). Generates an MC*_<Base> wrapper with fixed constants and INSTANCE.",
+        "(e.g., proto5). Applies only to Wunderspec-to-TLA+ conversion; "
+        "ignored for Quint input. Generates an MC*_<Base> wrapper with fixed "
+        "constants and INSTANCE.",
     )
     convert_parser.add_argument(
         "--text-width",