@xevy/skills 0.1.45 → 0.1.46

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -2,7 +2,7 @@
2
2
  "name": "xevy",
3
3
  "displayName": "Xevy",
4
4
  "description": "Native /xevy:* SDLC workflow commands driven through the Xevy MCP server. Analyze, plan, execute, fix, and move-to-qa run locally by default and accept --cloud for the server Web Agent. Merge stays local; merge-pull-request evaluates and lands the remote PR.",
5
- "version": "0.1.45",
5
+ "version": "0.1.46",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.45",
3
+ "version": "0.1.46",
4
4
  "description": "Install Xevy agent skills and secure per-agent MCP transports for Cursor, Claude Code, Codex, and other coding agents.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -34,11 +34,11 @@ For file transfer, use absolute paths and chunks of at most 192 KiB. Download wi
34
34
  3. Queue bounded actions with the current generation: focus, launch a supported application, click, drag, scroll, type, or press a key. Use observations to choose the next dependent action.
35
35
  4. Read each command until a terminal result, then take a fresh screenshot and check the expected app result. For a transaction, verify its final state, such as the saved file, submitted record, or visible deletion confirmation. Native input success establishes that the action executed; business success requires observed application evidence.
36
36
  5. A timeout or lost acknowledgement leaves the result uncertain. Inspect command status and the desktop before retrying a write. Resume from the observed state; avoid repeating a submit, payment, send, or delete whose outcome is unresolved.
37
- 6. After the final screenshot, queue `desktop.release {}` when you used native desktop input and wait for its terminal result. This releases the desktop focus lease so another agent can act. Browser tabs remain independent during the lease. Then call `computer_complete_operation` using the same `operationId`, current generation, and `completed`, `submitted`, `deleted`, or `failed`. Summarize the app result actually verified. Stop owned control when finished.
37
+ 6. After the final desktop observation, queue `desktop.release {}` when you used native desktop input and wait for its terminal result. This releases the desktop focus lease so another agent can act. Browser tabs remain independent during the lease. Then call `computer_complete_operation` using the same `operationId`, current generation, and `completed`, `submitted`, `deleted`, or `failed`. Summarize the result actually verified. Stop owned control when finished.
38
38
 
39
39
  Use the actual tool argument names and response envelope. Queue `const {command} = await computer_action({computerId, sessionId, generation, action: 'desktop.snapshot', payload: {}, operationId, summary: 'Verify the test record'})`, then read `await computer_command({computerId, commandId: command.id})`. The action response is `{command: {...}}`; take the ID from its nested `command`, while MCP clients parse the response's JSON text content. Read each action's current payload schema before constructing inputs.
40
40
 
41
- Only after observing the final screenshot and terminal operation commands, record the verified result with:
41
+ Only after reading terminal operation commands and the relevant final evidence, record the verified result with:
42
42
 
43
43
  ```javascript
44
44
  computer_complete_operation({
@@ -53,6 +53,8 @@ computer_complete_operation({
53
53
 
54
54
  The completion argument is `outcome`; command responses expose execution `status`.
55
55
 
56
+ For desktop changes, a later `desktop.snapshot` or `desktop.windows` result can establish the final state. For browser changes, use a later `browser.snapshot`, `browser.inspect`, or `browser.tabs` result. `desktop.release` and `browser.disconnect` do not invalidate that evidence. A successful `shell.run`, `file.uploadCommit`, or `file.uploadCancel` can complete a technical operation; an unfinished upload cannot. `file.stat` and `file.readChunk` can prove read-only file operations. A terminal failed or blocked command can support `failed`. Use `submitted` or `deleted` only after observing the application outcome, and verify shell or file writes separately when their effect matters.
57
+
56
58
  Keep a stable `operationId` for one outcome across clicks, waits, retries, and screenshots. Use summaries such as “Save the test customer in the CRM” or “Export the monthly worksheet.” Start a new operation for a distinct transaction. Native audit segments retain cumulative counts per segment; the logical activity groups distinct segments and a separate verified completion. Record errors and blocked outcomes honestly.
57
59
 
58
60
  ## Blocks, data, and evidence