@vention/vention-skills 0.10.28 → 0.10.30

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vention",
-  "version": "0.10.28",
+  "version": "0.10.30",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/README.md

@@ -1,6 +1,6 @@
 # Vention skills
 
-Version 0.10.28. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
+Version 0.10.30. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
 
 | Skill                       | What it does                                                                                                                         |
 | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vention/vention-skills",
-  "version": "0.10.28",
+  "version": "0.10.30",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "license": "MIT",
   "type": "module",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "vention",
-  "version": "0.10.28",
+  "version": "0.10.30",
   "description": "Vention skills for coding agents: write MachineLogic applications, build machine designs, and diagnose deployed machines.",
   "author": {
     "name": "Vention"

package/skills/vention-design/SKILL.md

@@ -3,7 +3,7 @@ name: vention-design
 description: Create, build and edit Vention machine designs and design graphs for agentic layout. Use when the user wants to start a new design, lay out an automation cell, add or reposition components in a Vention design, generate a machine layout from a description, add or place a floor plan image under a design, list a design's versions, or inspect an existing design graph. Trigger on MachineBuilder designs, design graphs, assembly graphs, extrusions, actuators, robot mounting, cell footprints, floor plans, or a machine-builder URL.
 license: MIT
 metadata:
-  version: "0.10.28"
+  version: "0.10.30"
   author: Vention
 ---
 

package/skills/vention-machine-logic/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic
 description: Write, edit, validate, and deploy MachineLogic Python applications for Vention machines with the machine-logic-sdk and the Vention CLI. Load it before writing or changing any Python that talks to a Vention machine, however short, since device names and version-specific SDK calls come from here. Use to program a Vention machine or MachineMotion controller, drive actuators, conveyors, robots, pneumatics, or digital I/O, change an existing application, build a state machine, debug from logs, or pull, push, or link with the Vention CLI (vention or vn). Trigger on MachineLogic, machine-logic-sdk, MachineMotion, MachineBuilder applications, the Vention CLI, or a directory holding .machine-code-app-directory-info.json. Printing what the machine or robot holds now (positions, taught targets, calibration, I/O) is a program: files on disk hold only as-designed values. Not for explaining an existing machine or its configuration in words when no program is asked for, nor for Python that never touches the machine.
 license: MIT
 metadata:
-  version: "0.10.28"
+  version: "0.10.30"
   machine-logic-sdk: ">=3.0,<4"
   author: Vention
 ---
@@ -75,9 +75,9 @@ It reads `requirements.txt` for `vention-state-machine`, `vention-storage`, and
 
 ## The shape of an application
 
-Write the code to `main.py` before you answer, every time the user asks for a program, a script or a readout — even a one-off, even a read-only one. Code that only appears in the reply cannot be type-checked, pushed, or run.
+Write the code to `main.py` before you answer, every time the user asks for a program, a script or a readout — even a one-off, even a read-only one. Code that only appears in the reply cannot be type-checked, pushed, or run. Before you answer, check the code you wrote against each behaviour the request states (starting position, button behaviour, counts, speeds, stop behaviour) and implement every one. When you leave one out on purpose, because a safety rule below forbids it or only the user knows a value, the reply names it, says why, and says what would let you add it. A value neither the request nor the configuration gives goes in a named constant the reply lists as the user's to fill in.
 
-`main.py` is the entry point named in `project.json`. Resolve devices once from the configuration, keep speeds in named constants at the top, and make the shutdown path unconditional.
+`main.py` is the entry point named in `project.json`. Resolve devices once from the configuration, keep speeds in named constants at the top, and make the shutdown path unconditional. It covers every way out: put anything after the device lookups that can fail (homing, scene lookups, loading a recipe) inside the `try`. In the `finally`, tell workers to issue no further commands, stop motion, join any worker still inside a device call with a timeout, then switch outputs off, so a late write cannot undo them. Give each step its own `try`/`except` so one failure does not skip the rest.
 
 ```python
 from machinelogic import Machine, MotionProfile, VentionException
@@ -147,11 +147,19 @@ print(f"cycle {cycle} took {elapsed:.1f} s")     # the work that was worth not b
 robot.wait_for_motion_completion()               # robots take no arguments
 ```
 
-Poll `state.move_in_progress` only when something has to be serviced mid-travel, such as a Stop or a timeout, and still finish on the wait: the flag can read False before the move has begun, so a polling loop alone may return before the axis arrives. `move_continuous_async` is the exception to all of it: it has no target to arrive at, so it ends at `stop()`, never at a wait.
+`move_continuous_async` is the exception to all of it: it has no target to arrive at, so it ends at `stop()`, never at a wait. When something has to be serviced mid-travel, such as the position, a Stop, or a deadline, run the wait on a worker (`asyncio.to_thread` in an asyncio application) and loop until it returns. Never loop on `state.move_in_progress` instead: it can read False before the move has begun, so the loop ends before the axis arrives. The SDK retries a wait past its timeout and can raise a `requests` error rather than a `VentionException`, and a wait cut short by `stop()` may raise too: once you have stopped the device, treat that as the stop, not a fault.
+```python
+axis.move_relative_async(250.0, profile)  # send the move before its wait starts
+arrival = ThreadPoolExecutor(max_workers=1).submit(axis.wait_for_move_completion, 20)  # concurrent.futures
+while not arrival.done():  # ends on arrival, however early the loop starts
+    print(axis.state.position)
+    time.sleep(0.1)
+arrival.result()  # re-raises what the wait raised
+```
 
 ## Reacting to an input edge
 
-Polling can straddle a pulse that opens and closes between two reads. `on_state_change` fires on every transition, on a background thread, so the process has to stay alive for the edges to land in:
+Polling can straddle a pulse that opens and closes between two reads. `on_state_change` fires on every update the controller sends, repeats included, on a background thread, so the process has to stay alive for the edges to land in:
 
 ```python
 from machinelogic.ivention.idigital_input import IDigitalInput
@@ -162,6 +170,8 @@ def on_edge(value: bool, digital_input: IDigitalInput) -> None:
 part_present.on_state_change(on_edge)
 ```
 
+When the request wants a Stop or Hold to act at once, it covers a press during a long move or a dwell, which a check between steps misses. Set a `threading.Event` from its `on_state_change` callback (`loop.call_soon_threadsafe(event.set)` in an asyncio application); the mid-travel loop above calls `stop()` on the moving device when it is set, and a dwell is `if stop_requested.wait(dwell_s):`, not `time.sleep(dwell_s)`. Register the callback before reading the input's current level, and start the motion only after that read finds it clear: a press between the read and the registration is lost, and registering fires nothing, so a button already held gives no edge and any state the callback keeps starts from that read. Whether an edge that lands while the cycle is busy or held counts is the request's to say: when every edge counts, latch it (a counter, a queue) rather than dropping it; when the request arms the input only at some point in the cycle, ignore edges before that point. When Stop must be followed by a fresh Start, discard any Start pressed before it so an old press cannot restart the cycle. A repeat is not an edge: keep the last value seen and count a rising edge only when it changes from False to True. Homing is motion too: check a held Stop or Hold before it, and where one must interrupt it, on SDK 3.2.0 and later use `home_async()` and the wait above so `stop()` can end it. Right before each command that starts motion, read the interlock's and the Hold's current level (`state.value`) rather than a flag your callback set: a queued event may not have run yet.
+
 ## Doing several things at once
 
 A plain sequence stays a plain synchronous script. When two or more things have to happen at the same time (two conveyors, a counter beside a cycle, a cycle that also listens for MQTT), run each as a task on one asyncio loop. The SDK has no coroutines: an `_async` method only sends the command and returns, and the waits block. Keep every blocking call off the loop, or it stalls every other task for as long as it blocks.

package/skills/vention-machine-logic-hmi/SKILL.md

@@ -3,7 +3,7 @@ name: vention-machine-logic-hmi
 description: Build or edit the custom operator HMI of a MachineLogic application, the React touch screen in customui/ that runs in MachineBuilder and on the MachineMotion pendant, wired to the application's Python process through vention-communication. Use when the user asks for an operator screen, a custom HMI or UI, a touch panel, start and stop buttons, live machine state on screen, or recipes an operator picks, for a Vention machine or inside a directory holding .machine-code-app-directory-info.json. Uses @vention/machine-ui, @vention/machine-apps-components and @vention/machine-logic-ui-sdk. Do not use for the no-code HMI Builder, or for the Python motion logic alone (that is vention-machine-logic).
 license: MIT
 metadata:
-  version: "0.10.28"
+  version: "0.10.30"
   author: Vention
 ---
 

package/skills/vention-machine-logic-hmi/examples/indexing-station-hmi/customui/package.json

@@ -15,9 +15,9 @@
     "@emotion/styled": "11.14.1",
     "@mui/material": "5.16.7",
     "@tabler/icons-react": "3.44.0",
-    "@vention/machine-apps-components": "1.30.25",
-    "@vention/machine-logic-ui-sdk": "0.47.4",
-    "@vention/machine-ui": "6.7.0",
+    "@vention/machine-apps-components": "1.30.26",
+    "@vention/machine-logic-ui-sdk": "0.47.5",
+    "@vention/machine-ui": "6.7.1",
     "react": "17.0.2",
     "react-dom": "17.0.2",
     "react-router-dom": "6.30.3",

package/skills/vention-machine-logic-hmi/examples/indexing-station-hmi/requirements.txt

@@ -1,5 +1,5 @@
 machine-logic-sdk==3.1.0
-vention-communication==0.15.35
-vention-state-machine==0.16.30
-vention-storage==0.20.13
+vention-communication==0.15.36
+vention-state-machine==0.16.31
+vention-storage==0.20.14
 uvicorn==0.35.0

package/skills/vention-monitoring/SKILL.md

@@ -3,7 +3,7 @@ name: vention-monitoring
 description: Diagnose deployed Vention machines from controller state, history, health, and activity data. Use when the user reports a machine that is down, faulted, offline, slow, or underperforming, asks why a cycle time regressed, wants to interpret MachineMotion event data or drive and brake status, asks about OEE or uptime, or wants to know which machine in a fleet needs attention. Trigger on a MachineMotion serial number plus any complaint.
 license: MIT
 metadata:
-  version: "0.10.28"
+  version: "0.10.30"
   author: Vention
 ---