@vention/vention-skills 0.10.10 → 0.10.12

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "vention",
-  "version": "0.10.10",
+  "version": "0.10.12",
   "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.10. Skills for coding agents that work with Vention machines, packaged as one plugin, `vention`, in the `vention-skills` marketplace.
+Version 0.10.12. 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.10",
+  "version": "0.10.12",
   "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.10",
+  "version": "0.10.12",
   "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.10"
+  version: "0.10.12"
   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.10"
+  version: "0.10.12"
   machine-logic-sdk: ">=3.0,<4"
   author: Vention
 ---
@@ -246,9 +246,9 @@ Each example is a standalone `main.py` whose module docstring names the device n
 5. `vention push`, then run the application on the digital twin from MachineBuilder before any hardware run. One or two full cycles prove the cycle; each extra one costs a cycle time and shows nothing the first two did not. Run them at 100 % of the speed setting, chosen for that run: nothing on the twin can be hurt.
 6. Read the output with `vention logs` once the run ends, rather than following it while the cycles play. `vention logs` prints only the most recent lines, so a count of matching lines can stop rising before the run ends. Print each cycle's measured time. When the cycle time is unknown, sleep once for one cycle's estimate, read `vention logs` once for the measured time, then sleep once for the cycles left: a rounded-up guess for the whole run wastes the difference. Before that first sleep, read `vention logs` once a few seconds after starting the run, to see that the first cycle began: a run stuck before its first move would otherwise cost the whole sleep. Print a line before every call that can block for long, such as a home or a long move, not only after it, so a log that stops shows which call it stopped in. Never loop over `vention logs` waiting for a line to appear, and never end your turn while a background wait is running. MachineLogic failures name the device and the reason; read the log before proposing a change.
 7. Check a motion from the log, not by watching the twin: `print` the robot's joint angles or the axis position at each step, then compare them with what the step should reach. For a repeated or oscillating motion, such as a wave, print the joint angles at each end of the swing, so the log alone shows how far it moved and which joints moved.
-8. On the digital twin, an axis finishes homing only when the design places a target in front of its home sensor. Otherwise `home()` never returns, even past its timeout, because the SDK keeps retrying the request. Never delete the homing to get past this: the hardware needs it. Tell the user the twin cannot home that axis until its home sensor faces a target in the design, and ask whether to skip the home on the twin only.
+8. On the digital twin, `home()` can hang: it does not return, even past its timeout, because the SDK keeps retrying the request. The twin also reports an axis's end sensors as off at every position, so their state cannot tell you where the axis is. Never delete the homing to get past a hang: the hardware needs it. Stop the run, tell the user the home did not finish on the twin, and ask whether to skip the home on the twin only.
 9. Pressing the emergency stop on the digital twin's pendant does nothing, so skip that test there. Tell the user the e-stop path is untested until the first run on the real cell.
-9. Show the user the diff before pushing over an application they did not write in this session.
+10. Show the user the diff before pushing over an application they did not write in this session.
 
 ## Deploying to a real cell
 

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.10"
+  version: "0.10.12"
   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.14",
-    "@vention/machine-logic-ui-sdk": "0.45.9",
-    "@vention/machine-ui": "6.6.13",
+    "@vention/machine-apps-components": "1.30.15",
+    "@vention/machine-logic-ui-sdk": "0.45.10",
+    "@vention/machine-ui": "6.6.14",
     "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.30
-vention-state-machine==0.16.24
-vention-storage==0.20.8
+vention-communication==0.15.31
+vention-state-machine==0.16.25
+vention-storage==0.20.9
 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.10"
+  version: "0.10.12"
   author: Vention
 ---