@swmansion/argent 0.27.1-next.20 → 0.27.1-next.21

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.
Files changed (8) hide show
  1. package/dist/cli-cmds.mjs +254 -54
  2. package/dist/client.js +224 -47
  3. package/dist/installer.mjs +17 -7
  4. package/dist/mcp-server.mjs +234 -51
  5. package/dist/tool-args.generated.d.ts +1 -1
  6. package/dist/tool-server.cjs +721 -571
  7. package/package.json +1 -1
  8. package/skills/argent-create-flow/references/live-authoring.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@swmansion/argent",
3
- "version": "0.27.1-next.20",
3
+ "version": "0.27.1-next.21",
4
4
  "mcpName": "io.github.software-mansion/argent",
5
5
  "description": "MCP server for iOS Simulator and Android Emulator control",
6
6
  "license": "Apache-2.0",
package/skills/argent-create-flow/references/live-authoring.md CHANGED
@@ -268,7 +268,7 @@ Run `flow-execute` on the complete YAML with the absolute project root. For a fr
268
268
 
269
269
  `flow-execute` takes exactly one flow source: `name`, for a flow saved under `.argent/flows/`, or `flow_path`, an absolute path to any flow `.yaml`.
270
270
 
271
- Over `argent link` or `ARGENT_TOOLS_URL`, `run:` fragments work when they are under `project_root`, under its `.argent/flows/`, or beside the flow file. Keep fragments there. These steps do not work over a link, in the flow or in a fragment that it reaches: `script:`, `snapshot:`, and a `tool:` step that takes a file (such as `screenshot-diff`, `reinstall-app`, or `flow-execute`) or records a flow.
271
+ Over `argent link` or `ARGENT_TOOLS_URL`, `run:` fragments work when they are under `project_root`, under its `.argent/flows/`, or beside the flow file. Keep fragments there. `snapshot:` steps work in the flow and in its fragments, and the baselines stay in the project. With `updateBaselines: true`, the client writes each new baseline when the run ends. A `baseline not written` line in the report means that the client did not save that baseline: fix the reason in the line and run again. These steps do not work over a link, in the flow or in a fragment that it reaches: `script:`, and a `tool:` step that takes a file (such as `screenshot-diff`, `reinstall-app`, or `flow-execute`) or records a flow.
272
272
 
273
273
  The tool-server checks the flow and its fragments before the first step. The error lists each step that does not work over a link, and each `run:` step whose fragment the client could not send, with the reason. A fragment that does not exist fails its `run:` step when the step runs. Run a flow that needs these steps with no link and no `ARGENT_TOOLS_URL`, on the computer that runs the tool-server.
274
274