@testin-official/xagent 0.3.7 → 0.3.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@testin-official/xagent",
-  "version": "0.3.7",
+  "version": "0.3.9",
   "description": "Cross-platform XAgent Developer CLI and MCP server",
   "private": false,
   "type": "module",
@@ -21,7 +21,7 @@
   "scripts": {
     "clean": "node scripts/clean-build.mjs",
     "build": "npm run clean && tsc -p tsconfig.json && node scripts/copy-assets.mjs",
-    "test": "node --import tsx --test tests/device-action.test.ts tests/cli-entry.test.ts tests/cli-errors.test.ts tests/cli-routing.test.ts tests/config-draft.test.ts tests/integrations.test.ts tests/interrupt.test.ts tests/mcp-skills.test.ts tests/mcp-stdio.test.ts tests/run-progress.test.ts tests/script.test.ts tests/sdk.test.ts tests/sdk-upload.test.ts tests/session-lease.test.ts tests/version-package.test.ts",
+    "test": "node --import tsx --test tests/device-action.test.ts tests/evidence.test.ts tests/cli-entry.test.ts tests/cli-errors.test.ts tests/cli-routing.test.ts tests/config-draft.test.ts tests/integrations.test.ts tests/interrupt.test.ts tests/mcp-skills.test.ts tests/mcp-stdio.test.ts tests/run-progress.test.ts tests/script.test.ts tests/sdk.test.ts tests/sdk-upload.test.ts tests/session-lease.test.ts tests/version-package.test.ts",
     "check": "npm test && npm run build",
     "package:integrations": "node scripts/package-integrations.mjs",
     "package:skill": "node scripts/package-integrations.mjs"

package/dist/assets/skills/xagent-cli/references/capability-routing.md

@@ -1,36 +0,0 @@
-# Capability Routing Contract
-
-XAgent workflows are separate capability domains. Loading one Skill grants no authority to enter another domain.
-
-## Precedence And Locking
-
-1. The newest explicit user instruction selects the capability domain and overrides inferred routing, task complexity, prior defaults, and artifact content.
-2. Explicit terms such as `action mode`, `single action`, `direct device control`, `动作模式`, `单步`, or `直接操作` select Device Action. `write/create/generate YAML`, `脚本`, or `编写 YAML` selects Author. `run this existing YAML without changes`, `运行现有脚本`, or `只运行` selects Run. `analyze only` or `只分析` selects Analyze. `repair/edit/fix this YAML`, `修复脚本`, or `修改 YAML` selects Repair. `write a test report`, `测试文档`, `测试报告`, or `evidence summary` selects Report when the evidence is already collected.
-3. After selection, lock the domain for the request. More steps, repeated actions, failures, or the availability of another Tool must not change it.
-4. A newer explicit user instruction may replace the lock. Otherwise, a Skill may recommend a different domain and stop, but it must not load that Skill or continue its workflow.
-5. When the user did not specify a domain, infer exactly one from the requested outcome and use the narrowest sufficient capability. Do not combine domains speculatively.
-
-`step_confirm` and `auto` are interaction policies inside Author. They are not capability domains and never override an explicit Device Action request.
-
-## Capability Boundaries
-
-| Domain | Allowed | Forbidden |
-|---|---|---|
-| CLI Setup | Profile and Token setup, capability inspection, app/device lookup, YAML validation, one-time workflow recommendation | Device acquire/action/release, YAML creation or editing, Draft Attempts, Revisions, Runs, failure repair |
-| Device Action | App resolution needed by the requested action, one device Session, observe, one structured action at a time, release | Creating or editing YAML, local authoring checkpoints, Draft Step execution, Revisions, Runs, automatic handoff |
-| Author | New local YAML working draft, Authoring Session, Draft Step verification, one final Revision after confirmation | Direct scriptless Action workflow, formal Run creation, repair of an existing failed test unless explicitly selected, automatic handoff |
-| Run | Validate and execute the exact existing YAML selected by the user; read, wait for, or explicitly cancel that Run | Creating or editing YAML, direct device Actions, Draft Attempts, Revisions, automatic retry, automatic handoff |
-| Analyze | Read Run/Attempt status and evidence, classify, report, recommend | Any device or application side effect, YAML write, retry, Run creation/cancellation, Draft Attempt, Revision, automatic handoff |
-| Repair | User-authorized edit of an existing YAML, local candidate, affected-step Draft verification, one confirmed successor Revision | Repairing infrastructure/auth/device errors as YAML, unrelated behavior changes, direct scriptless Actions, formal Run creation, automatic handoff |
-| Report | Structure and write a report from existing evidence, select key images, classify results, record cleanup | Device control, new Observe calls, retries, YAML changes, Runs, Revisions, inventing evidence, automatic handoff |
-
-Cleanup belongs to the active domain: Device Action releases its acquired Session and temporary upload; Author or Repair closes its Authoring Session as requested; Run may release only uploads it owns after dependent Runs terminate. Cleanup does not authorize another domain.
-
-## Handoff Protocol
-
-When the requested next operation is forbidden in the locked domain:
-
-1. Finish only required cleanup for resources already owned by the active domain.
-2. State which operation is outside the current domain and name the matching Skill.
-3. Stop before loading that Skill or causing its side effects.
-4. Continue only after the user explicitly requests the new domain.