@uipath/skills 1.195.0 → 1.196.0

package/skills/uipath-agents/references/lowcode/agent-definition.md

@@ -163,7 +163,7 @@ Runtime note: attachments cannot be supplied via `uip` CLI. Test from Studio Web
 
 | Field | Value |
 |-------|-------|
-| `storageVersion` | Managed by `uip agent migrate` — do not edit |
+| `storageVersion` | Managed by `uip agent refresh` — do not edit |
 | `isConversational` | `false` (autonomous agents) |
 | `showProjectCreationExperience` | `false` |
 | `targetRuntime` | `"pythonAgent"` |
@@ -291,7 +291,7 @@ Agent/
 │       └── feature.json                    # Written by uip agent memory
 ```
 
-The `memory` command updates `features/{FeatureName}/feature.json` and `.agent-builder/agent.json`. Run `uip agent validate --output json`, then `uip agent migrate --output json` after memory changes so generated bindings stay current.
+The `memory` command updates `features/{FeatureName}/feature.json`. Run `uip agent refresh --output json`, then `uip agent validate --output json` after memory changes so generated bindings stay current.
 
 For the full memory workflow and generated shape, see [capabilities/memory/memory.md](capabilities/memory/memory.md).
 
@@ -307,24 +307,25 @@ Agent/
 │       └── resource.json                   # One file per resource
 ```
 
-The `validate` command reads these files, resolves `referenceKey` for solution tools, and generates `.agent-builder/agent.json` which inlines all resources. The root `agent.json` should not contain a `resources` field.
+The `validate` command reads these files and resolves `referenceKey` for solution tools. The root `agent.json` should not contain a `resources` field.
 
 ### `folderPath` semantics
 
-`folderPath` (or `channel.properties.folderName` for escalations / `action.app.folderName` for guardrail escalations) carries the literal `Folder` field returned by `uip solution resource list` — the same rule for both local (`Source: "Local"`) and external (`Source: "Remote"`) resources:
+`folderPath` (or `channel.properties.folderName` for escalations / `action.app.folderName` for guardrail escalations) carries the literal `Folder` field returned by `uip solution resources list` — the same rule for both local (`Source: "Local"`) and external (`Source: "Remote"`) resources:
 
 | `location` | `folderPath` value | Source |
 |---|---|---|
-| `"solution"` | Typically `"solution_folder"` (the in-solution declared folder) | `Folder` field from `uip solution resource list` |
-| `"external"` | Literal Orchestrator folder, slash-separated (e.g., `"Shared/Sales"`) | `Folder` field from `uip solution resource list` |
+| `"solution"` | Typically `"solution_folder"` (the in-solution declared folder) | `Folder` field from `uip solution resources list` |
+| `"external"` | Literal Orchestrator folder, slash-separated (e.g., `"Shared/Sales"`) | `Folder` field from `uip solution resources list` |
 
-The author writes the value verbatim into `resource.json` (or into the guardrail action under `agent.json`); `uip agent migrate` propagates it into `bindings_v2.json` as `folderPath` (App resources translate `folderName` → binding `folderPath`). Connection (Integration Service) resources are exempt — bound by `connection.id`, no `folderPath`. See [critical-rules.md](critical-rules.md) Rule 11 and [solution-resources.md](solution-resources.md) § Bindings.
+The author writes the value verbatim into `resource.json` (or into the guardrail action under `agent.json`); `uip agent refresh` propagates it into `bindings_v2.json` as `folderPath` (App resources translate `folderName` → binding `folderPath`). Connection (Integration Service) resources are exempt — bound by `connection.id`, no `folderPath`. See [critical-rules.md](critical-rules.md) Rule 11 and [solution-resources.md](solution-resources.md) § Bindings.
 
 For each resource type's full schema, see the relevant capability file:
 
 - Tool resources (`$resourceType: "tool"`) — [capabilities/process/process.md](capabilities/process/process.md), [capabilities/integration-service/integration-service.md](capabilities/integration-service/integration-service.md)
 - Context resources (`$resourceType: "context"`) — [capabilities/context/context.md](capabilities/context/context.md)
 - Escalation resources (`$resourceType: "escalation"`) — [capabilities/escalation/escalation.md](capabilities/escalation/escalation.md)
+- MCP server resources (`$resourceType: "mcp"`) — [capabilities/mcp/mcp.md](capabilities/mcp/mcp.md)
 
 ## Common Edits
 
@@ -332,21 +333,21 @@ For each resource type's full schema, see the relevant capability file:
 
 1. Edit `agent.json` → `messages[0].content`
 2. Rebuild `messages[0].contentTokens` — single `simpleText` entry for prompts with no variables
-3. Validate: `uip agent validate --output json`
-4. Migrate: `uip agent migrate --output json`
+3. Refresh: `uip agent refresh --output json`
+4. Validate: `uip agent validate --output json`
 
 ### Change User Message Template
 
 1. Edit `agent.json` → `messages[1].content`
 2. Rebuild `messages[1].contentTokens` — tokenize `{{input.fieldName}}` as `variable`, surrounding text as `simpleText`
-3. Validate, then migrate
+3. Refresh, then validate
 
 ### Add an Input Field
 
 1. Add to `agent.json` → `inputSchema.properties` (and `.required` if mandatory)
 2. Mirror in `entry-points.json` → `entryPoints[0].input.properties` (and `.required`)
 3. Update `messages[1].content` and `contentTokens` if the field should appear in the user message
-4. Validate, then migrate
+4. Refresh, then validate
 
 ### Add a File Input Field (`job-attachment`)
 
@@ -355,26 +356,26 @@ For each resource type's full schema, see the relevant capability file:
 3. Mirror both in `entry-points.json` → `entryPoints[0].input.properties` and `.definitions`
 4. Reference in the user message with `{{input.<fieldName>}}` if the agent should see file metadata
 5. To let the agent **read contents**, add a file-handling built-in tool — see [capabilities/built-in-tools/built-in-tools.md](capabilities/built-in-tools/built-in-tools.md)
-6. Validate, then migrate
+6. Refresh, then validate
 
 ### Add an Output Field
 
 1. Add to `agent.json` → `outputSchema.properties`
 2. Mirror in `entry-points.json` → `entryPoints[0].output.properties`
-3. Validate, then migrate
+3. Refresh, then validate
 
 ### Add a File Output Field (`job-attachment`)
 
 1. Add the field as `{ "$ref": "#/definitions/job-attachment" }` in `agent.json` → `outputSchema.properties`
 2. Add the canonical `job-attachment` block to `outputSchema.definitions`
 3. Mirror both in `entry-points.json` → `entryPoints[0].output.properties` and `.definitions`
-4. Validate, then migrate
+4. Refresh, then validate
 
 ### Change Model Settings
 
 1. Edit `agent.json` → `settings.model`, `.temperature`, `.maxTokens`, or `.maxIterations`
 2. Discover valid model identifiers with `uip agent model list` and select per [model-selection-guide.md](model-selection-guide.md) — the tenant is the source of truth (availability and GA/preview status vary per tenant). Keep `maxTokens` ≤ the model's `MaxTokens` cap.
-3. Validate, then migrate
+3. Refresh, then validate
 
 ### Capability-Adding Edits
 
@@ -385,4 +386,4 @@ For edits that add a new tool, context, or escalation, see the capability regist
 | File | Managed By |
 |------|------------|
 | `flow-layout.json` | Studio Web |
-| `.agent-builder/*` | Generated by `uip agent migrate` and Studio Web — do not edit by hand |
+| `entry-points.json`, `bindings_v2.json` | Regenerated by `uip agent refresh` and Studio Web — do not edit by hand |

package/skills/uipath-agents/references/lowcode/capabilities/built-in-tools/analyze-attachments.md

@@ -96,8 +96,8 @@ Schema is canonical — copy verbatim. Only `id` (fresh UUID) and optionally `de
    }
    ```
 
-4. **Validate** with `uip agent validate "<AGENT_NAME>" --output json` (read-only). Confirm `MigrationPending`, `Validated`.
-5. **Migrate** with `uip agent migrate "<AGENT_NAME>" --output json`. Confirm `MigrationApplied`, `StorageVersion`.
+4. **Refresh** with `uip agent refresh "<AGENT_NAME>" --output json`. Regenerates `entry-points.json` and `bindings_v2.json`.
+5. **Validate** with `uip agent validate "<AGENT_NAME>" --output json` (read-only). Confirm `Validated`.
 6. **Bundle and upload** with `uip solution bundle` then `uip solution upload --output json` (with user consent).
 7. **Test** from Studio Web or via Orchestrator job invocation — `uip` CLI cannot supply attachments at run time.
 

package/skills/uipath-agents/references/lowcode/capabilities/built-in-tools/batch-transform/impl-json.md

@@ -80,7 +80,7 @@ Studio Web forwards the user's CSV upload to the tool — no schema wiring. Othe
 
 | Check | How |
 |---|---|
-| Agent project shape (agent.json, resources, bindings) | `uip agent validate --output json` (canonical; auto-runs migrations + writes `.agent-builder/`) |
+| Agent project shape (agent.json, resources, bindings) | `uip agent validate --output json` (canonical; run `uip agent refresh` first to regenerate `entry-points.json` and `bindings_v2.json`) |
 | Smoke run | `uip solution upload . --output json`, invoke from Studio Web with a 10–20 row CSV before the full workload |
 
 The repo's coder-eval suite uses a shared static checker at `tests/tasks/uipath-agents/builtin_tool/check_builtin_tool.py` covering all four `toolType` values (`analyze-attachments`, `load-attachments`, `deep-rag`, `batch-transform`). It is shared test tooling, not a runtime requirement for this skill.

package/skills/uipath-agents/references/lowcode/capabilities/built-in-tools/built-in-tools.md

@@ -1,6 +1,6 @@
 # Built-In Tools Capability
 
-Built-in tools are pre-built agent tools that ship with the platform. They share a wire shape (`$resourceType: "tool"`, `type: "internal"`) and a fixed input/output schema per tool. Unlike process or Integration Service tools, built-in tools are self-contained at the agent level — no solution-level files, no `uip solution resource refresh`.
+Built-in tools are pre-built agent tools that ship with the platform. They share a wire shape (`$resourceType: "tool"`, `type: "internal"`) and a fixed input/output schema per tool. Unlike process or Integration Service tools, built-in tools are self-contained at the agent level — no solution-level files, no `uip solution resources refresh`.
 
 For process tools (RPA / agent / API / agentic), see [../process/process.md](../process/process.md). For Integration Service tools, see [../integration-service/integration-service.md](../integration-service/integration-service.md).
 
@@ -13,7 +13,7 @@ For process tools (RPA / agent / API / agentic), see [../process/process.md](../
 
 1. **Built-in tools are not implicit.** Add them as `resources/{Name}/resource.json` with `type: "internal"` to make them callable. Without the resource file, the tool is unavailable.
 2. **`properties.toolType` is the discriminator** — fixed per built-in, kebab-lowercase. Copy from the per-tool walkthrough; do not invent.
-3. **No solution-level files.** Built-in tools need no `uip solution resource refresh`. Validate the agent and bundle.
+3. **No solution-level files.** Built-in tools need no `uip solution resources refresh`. Validate the agent and bundle.
 4. **Input/output schemas are fixed.** Do not edit them. Each tool's walkthrough lists the canonical schema.
 
 ## Resource Shape
@@ -50,8 +50,8 @@ For process tools (RPA / agent / API / agentic), see [../process/process.md](../
 ## Lifecycle
 
 1. **Author** the agent-level `resources/{ToolName}/resource.json` with the canonical shape from the per-tool walkthrough.
-2. **Validate** with `uip agent validate "<AGENT_NAME>" --output json` (read-only check).
-3. **Migrate** with `uip agent migrate "<AGENT_NAME>" --output json` — regenerates `.agent-builder/`.
+2. **Refresh** with `uip agent refresh "<AGENT_NAME>" --output json` — regenerates `entry-points.json` and `bindings_v2.json`.
+3. **Validate** with `uip agent validate "<AGENT_NAME>" --output json` (read-only check).
 4. **Bundle and upload** the solution. No solution-resource refresh needed.
 
 ## Tool Registry

package/skills/uipath-agents/references/lowcode/capabilities/built-in-tools/deeprag/impl-json.md

@@ -67,7 +67,7 @@ Studio Web forwards conversation attachments to the tool — no schema wiring. O
 
 | Check | How |
 |---|---|
-| Agent project shape (agent.json, resources, bindings) | `uip agent validate --output json` (canonical; auto-runs migrations + writes `.agent-builder/`) |
+| Agent project shape (agent.json, resources, bindings) | `uip agent validate --output json` (canonical; run `uip agent refresh` first to regenerate `entry-points.json` and `bindings_v2.json`) |
 | Smoke run | `uip solution upload . --output json`, invoke from Studio Web with a test PDF/TXT attachment |
 
 The repo's coder-eval suite uses a shared static checker at `tests/tasks/uipath-agents/builtin_tool/check_builtin_tool.py` covering all four `toolType` values (`analyze-attachments`, `load-attachments`, `deep-rag`, `batch-transform`). It is shared test tooling, not a runtime requirement for this skill.

package/skills/uipath-agents/references/lowcode/capabilities/context/context.md

@@ -10,7 +10,7 @@ Contexts feed retrievable information into an agent at runtime. Three variants e
 
 ## Variants
 
-| `contextType` | Backing | Solution-level auto-gen by `uip solution resource refresh`? | Walkthrough |
+| `contextType` | Backing | Solution-level auto-gen by `uip solution resources refresh`? | Walkthrough |
 |---|---|---|---|
 | `"index"` | ECS Context Grounding index (StorageBucket-backed) | Yes — auto-writes `index/<Name>.json` + `bucket/orchestratorBucket/<Bucket>.json` + 2 debug entries | [index.md](index.md) |
 | `"attachments"` | Runtime files passed to the agent | No (no solution resource needed) | [attachments.md](attachments.md) |

package/skills/uipath-agents/references/lowcode/capabilities/context/datafabric.md

@@ -39,7 +39,7 @@ No `indexName` and no `settings` for DataFabric contexts. The shape is entirely
 
 ## Solution-Level Files
 
-**Not auto-generated.** Solution-level resource generation for DataFabric contexts is not yet supported by `uip solution resource refresh` — the agent-level `resource.json` is written, but you must hand-author any solution manifests needed.
+**Not auto-generated.** Solution-level resource generation for DataFabric contexts is not yet supported by `uip solution resources refresh` — the agent-level `resource.json` is written, but you must hand-author any solution manifests needed.
 
 ## Gotchas
 

package/skills/uipath-agents/references/lowcode/capabilities/context/index.md

@@ -9,7 +9,7 @@ For other context variants, see [context.md](context.md).
 - Agent needs to retrieve from a knowledge base of indexed documents
 - The index already exists in Context Grounding and is backed by an Orchestrator storage bucket
 
-`uip solution resource refresh` emits an `index` binding into `bindings_v2.json`, resolves the backing storage bucket via ECS + Orchestrator, and writes all three artifacts automatically: `resources/solution_folder/index/<IndexName>.json`, `resources/solution_folder/bucket/orchestratorBucket/<BucketName>.json`, and two `debug_overwrites.json` entries (`kind: "index"`, `kind: "bucket"`). No manual solution-level authoring is required.
+`uip solution resources refresh` emits an `index` binding into `bindings_v2.json`, resolves the backing storage bucket via ECS + Orchestrator, and writes all three artifacts automatically: `resources/solution_folder/index/<IndexName>.json`, `resources/solution_folder/bucket/orchestratorBucket/<BucketName>.json`, and two `debug_overwrites.json` entries (`kind: "index"`, `kind: "bucket"`). No manual solution-level authoring is required.
 
 **Only `contextType: "index"` with a StorageBucket data source is supported.** `attachments` and `datafabricentityset` contexts, and indexes backed by GoogleDrive / OneDrive / Dropbox / Confluence, emit a warning from refresh and must be hand-authored.
 
@@ -24,7 +24,7 @@ Run `uip login status --output json`. If a solution and agent do not yet exist,
 ### Step 2 — Find the index (identity)
 
 ```bash
-uip solution resource list --kind Index --source remote --search "<INDEX_NAME>" --output json
+uip solution resources list --kind Index --source remote --search "<INDEX_NAME>" --output json
 ```
 
 Response wrapper: `{Result, Code: "ResourceList", Data: [...]}` — parse `.Data[]`.
@@ -41,15 +41,15 @@ When the same `Name` repeats across folders, pick by `Key`.
 ### Step 3 — Get the index configuration
 
 ```bash
-uip solution resource get <KEY> --output json
+uip solution resources get <KEY> --output json
 ```
 
-Response wrapper: `{Result, Code: "ResourceConfiguration", Data: {...}}`. `Data.spec` is the source-of-truth that `uip solution resource refresh` round-trips into `resources/solution_folder/index/<IndexName>.json` — confirm it before authoring.
+Response wrapper: `{Result, Code: "ResourceConfiguration", Data: {...}}`. `Data.spec` is the source-of-truth that `uip solution resources refresh` round-trips into `resources/solution_folder/index/<IndexName>.json` — confirm it before authoring.
 
 | `Data.spec` field | Confirms / Use as |
 |-------|------------------|
 | `dataSourceType` | MUST equal `"StorageBucket"`. Anything else (GoogleDrive / OneDrive / Dropbox / Confluence / Attachments) — refresh warns + skips. Hand-author solution-level files or escalate. |
-| `storageBucketReference.name` | Bucket display name. Refresh writes this as the bucket manifest's `name`. Optionally cross-check with `uip solution resource list --kind Bucket --source remote --search "<NAME>" --output json` to confirm the bucket is reachable. |
+| `storageBucketReference.name` | Bucket display name. Refresh writes this as the bucket manifest's `name`. Optionally cross-check with `uip solution resources list --kind Bucket --source remote --search "<NAME>" --output json` to confirm the bucket is reachable. |
 | `storageBucketReference.key` | Bucket GUID — refresh writes this verbatim as `key` in the bucket manifest and as `dependencies[].key` / `spec.storageBucketReference.key` in the index manifest. |
 | `storageBucketReference.folderKey` | Folder GUID containing the bucket. Matches the index's `FolderKey` from Step 2 (the bucket lives in the same folder as the index). |
 | `fileNameGlob` | File-extension filter on the index itself. Sanity-check — does not need to match the agent resource's `settings.fileExtension.value`. |
@@ -69,7 +69,7 @@ Wrapper-level `apiVersion` is `"ecs.uipath.com/v2"` — matches what refresh wri
   "name": "<ContextName>",              // display name; matches the folder under resources/
   "description": "",
   "contextType": "index",
-  "folderPath": "Shared/Knowledge",     // Literal Folder from `uip solution resource list`. Propagates verbatim into bindings_v2.json.
+  "folderPath": "Shared/Knowledge",     // Literal Folder from `uip solution resources list`. Propagates verbatim into bindings_v2.json.
   "indexName": "<IndexName>",           // MUST match the ECS index Name exactly (case-sensitive)
   "settings": {
     "retrievalMode": "semantic",        // "semantic" | "structured" | "deeprag" | "batchtransform"
@@ -99,7 +99,7 @@ Wrapper-level `apiVersion` is `"ecs.uipath.com/v2"` — matches what refresh wri
 
 ## Solution-Level Files
 
-For `contextType: "index"` with a StorageBucket-backed ECS index, `uip agent migrate` emits:
+For `contextType: "index"` with a StorageBucket-backed ECS index, `uip agent refresh` emits:
 
 ```json
 {
@@ -113,7 +113,7 @@ For `contextType: "index"` with a StorageBucket-backed ECS index, `uip agent mig
 }
 ```
 
-into `bindings_v2.json` at the agent project root. `folderPath` is propagated verbatim from the agent-level `resource.json`'s top-level `folderPath` field. `uip solution resource refresh` then:
+into `bindings_v2.json` at the agent project root. `folderPath` is propagated verbatim from the agent-level `resource.json`'s top-level `folderPath` field. `uip solution resources refresh` then:
 
 1. Calls ECS `GET ecs_/v2/indexes/AllAcrossFolders?$filter=Name eq '<IndexName>'&$expand=dataSource` — resolves the index GUID, folder key, and data source type. With the binding's `folderPath` set, refresh narrows multi-folder name collisions to the exact deployment.
 2. If `dataSource.@odata.type` is not `#UiPath.Vdbs.Domain.Api.V20Models.StorageBucketDataSource`, warns + skips (other data sources — GoogleDrive, OneDrive, Dropbox, Confluence, Attachments — are not yet wired).
@@ -212,14 +212,14 @@ All failures (index not found, ambiguous name match, non-StorageBucket data sour
 
 See § Agent-Level Resource Shape above for the full field reference, including the three variants (`index`/`attachments`/`datafabricentityset`) and per-`retrievalMode` settings (`citationMode` for `deeprag`, `webSearchGrounding` + `outputColumns` for `batchtransform`).
 
-### Step 5 — Validate and migrate
+### Step 5 — Refresh and validate
 
 ```bash
+uip agent refresh  "<AGENT_NAME>" --output json
 uip agent validate "<AGENT_NAME>" --output json
-uip agent migrate  "<AGENT_NAME>" --output json
 ```
 
-Validate is read-only. Migrate writes the binding. Confirm `Validated.resources` includes the context, then inspect the emitted binding:
+Refresh writes the binding. Validate is read-only. Confirm `Validated.resources` includes the context, then inspect the emitted binding:
 
 ```bash
 cat "<AGENT_NAME>/bindings_v2.json"
@@ -229,7 +229,7 @@ cat "<AGENT_NAME>/bindings_v2.json"
 ### Step 6 — Refresh solution resources
 
 ```bash
-uip solution resource refresh --output json
+uip solution resources refresh --output json
 ```
 
 Refresh resolves the index via ECS `$expand=dataSource`, locates its backing StorageBucket in Orchestrator, and writes:

package/skills/uipath-agents/references/lowcode/capabilities/escalation/escalation.md

@@ -2,14 +2,14 @@
 
 Walkthrough for adding an escalation resource that hands off agent control to a human via a deployed UiPath Action Center app (a web app of kind `workflow Action`). The agent pauses, creates a task on the app, and resumes when the human picks an outcome.
 
-The only channel type currently supported end-to-end by `uip solution resource refresh` is `actionCenter`. Other channel types (`email`, `slack`, `teams`) are recognised by the runtime but have no automatic solution-level resource generation and are out of scope for this skill.
+The only channel type currently supported end-to-end by `uip solution resources refresh` is `actionCenter`. Other channel types (`email`, `slack`, `teams`) are recognised by the runtime but have no automatic solution-level resource generation and are out of scope for this skill.
 
 ## When to Use
 
 - Agent needs human approval, review, or input mid-execution
 - A UiPath Action Center app of kind `Workflow Action` is already deployed in Orchestrator
 
-**Key pattern:** the skill writes only the agent-level `resources/{EscalationName}/resource.json`. `uip solution resource refresh` emits an App binding into `bindings_v2.json` and then hand-writes the four solution-level files (`app/workflow Action/`, `appVersion/`, `package/`, `process/webApp/`) plus two `debug_overwrites.json` entries (`kind: "app"`, `kind: "process"`) automatically. No manual solution-level authoring is required for `actionCenter` channels.
+**Key pattern:** the skill writes only the agent-level `resources/{EscalationName}/resource.json`. `uip solution resources refresh` emits an App binding into `bindings_v2.json` and then hand-writes the four solution-level files (`app/workflow Action/`, `appVersion/`, `package/`, `process/webApp/`) plus two `debug_overwrites.json` entries (`kind: "app"`, `kind: "process"`) automatically. No manual solution-level authoring is required for `actionCenter` channels.
 
 ## Discovery
 
@@ -20,7 +20,7 @@ Scaffold per [../../project-lifecycle.md § End-to-End Example](../../project-li
 ### Step 2 — Find the deployed Action Center app
 
 ```bash
-uip solution resource list --kind App --source remote --search "<APP_NAME>" --output json
+uip solution resources list --kind App --source remote --search "<APP_NAME>" --output json
 ```
 
 Filter the result for entries whose `Type` is `"Workflow Action"` (Coded / CodedAction types cannot back an escalation today). Each entry carries:
@@ -29,7 +29,7 @@ Filter the result for entries whose `Type` is `"Workflow Action"` (Coded / Coded
 |-----------------------|--------|
 | `Key` | `channel.properties.resourceKey` (also becomes the app resource's `key`) |
 | `Name` | `channel.properties.appName` (also propagates as binding `name`) |
-| `Folder` | `channel.properties.folderName` — literal Orchestrator folder (e.g., `"Shared/Approvals"`). `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. |
+| `Folder` | `channel.properties.folderName` — literal Orchestrator folder (e.g., `"Shared/Approvals"`). `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. |
 | `FolderKey` | folder GUID — used in `debug_overwrites.json` |
 
 `Key` gives you everything you need to identify the backing app, but `resource list` does not return `systemName` or `deployVersion` — both are required to fetch the action schema in Step 3. Query the Apps API once, filtered client-side by `id == <KEY>`, to extract them:
@@ -111,7 +111,7 @@ Use other `type` values (1=UserId, 2=GroupId, 4=AssetUserEmail, 5=StaticGroupNam
 
 > **Do not set `displayName` for `type: 3`.** The reference solution omits it; leaving it out results in cleaner rendering in Studio Web.
 
-**`channel.properties.folderName` must be the literal `Folder` from `uip solution resource list --kind App`** (e.g., `"Shared/Approvals"`). `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do NOT set it to `"solution_folder"` — escalation apps are always external.
+**`channel.properties.folderName` must be the literal `Folder` from `uip solution resources list --kind App`** (e.g., `"Shared/Approvals"`). `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do NOT set it to `"solution_folder"` — escalation apps are always external.
 
 Default `taskTitle` / `taskTitleV2` to a short human-readable label — e.g., `"Approval request"`. `taskTitle` is a string; `taskTitleV2` is a `contentTokens`-style object (see [../../agent-definition.md](../../agent-definition.md) § Messages).
 
@@ -164,7 +164,7 @@ Escalations hand off agent control to a human via a channel. Generate fresh UUID
       "properties": {
         "resourceKey": "<appId-guid>",              // from `action-apps?state=deployed` → `id`
         "appName": "<deploymentTitle>",             // from the same response → `deploymentTitle`
-        "folderName": "Shared/Approvals",           // literal Folder from `uip solution resource list --kind App`. uip agent migrate translates this to folderPath in the App binding inside bindings_v2.json.
+        "folderName": "Shared/Approvals",           // literal Folder from `uip solution resources list --kind App`. uip agent refresh translates this to folderPath in the App binding inside bindings_v2.json.
         "appVersion": 1,                            // from the same response → `deployVersion` (integer)
         "isActionableMessageEnabled": false,
         "actionableMessageMetaData": null
@@ -204,7 +204,7 @@ Escalations hand off agent control to a human via a channel. Generate fresh UUID
 
 ## Solution-Level Files
 
-**Solution-level files for Action Center escalations are auto-generated.** Unlike external process tools, you do NOT hand-write any solution-level files for an escalation. `uip solution resource refresh` scans agent projects for escalation resources, resolves each `properties.resourceKey` against the Apps API + `publish/versions` + Orchestrator `/odata/Releases` + `GetPackageEntryPointsV2`, and writes all four required files itself:
+**Solution-level files for Action Center escalations are auto-generated.** Unlike external process tools, you do NOT hand-write any solution-level files for an escalation. `uip solution resources refresh` scans agent projects for escalation resources, resolves each `properties.resourceKey` against the Apps API + `publish/versions` + Orchestrator `/odata/Releases` + `GetPackageEntryPointsV2`, and writes all four required files itself:
 
 - `resources/solution_folder/app/workflow Action/<deploymentTitle>.json`
 - `resources/solution_folder/appVersion/<title>.json`
@@ -221,17 +221,17 @@ The fourth file (`process/webApp/...`) backs the app resource's `dependencies[1]
 
 Use the full shape from § Agent-Level Resource Shape above. Generate fresh UUIDs for the top-level `id` AND the channel `id` — do not reuse.
 
-### Step 7 — Validate, migrate, and refresh solution resources
+### Step 7 — Refresh, validate, and refresh solution resources
 
 ```bash
+# Refresh — regenerates entry-points.json and bindings_v2.json.
+uip agent refresh "<AGENT_NAME>" --output json
+
 # Validate — read-only check of agent and resource.json.
 uip agent validate "<AGENT_NAME>" --output json
 
-# Migrate — applies pending schema migrations and writes bindings_v2.json.
-uip agent migrate "<AGENT_NAME>" --output json
-
-# Refresh — imports the App binding from bindings_v2.json into the solution.
-uip solution resource refresh --output json
+# Refresh solution resources — imports the App binding from bindings_v2.json into the solution.
+uip solution resources refresh --output json
 ```
 
 After refresh, confirm the four solution-level app files exist under `resources/solution_folder/`:
@@ -254,7 +254,7 @@ uip solution upload ./dist/<SOLUTION_NAME>.uis --output json
 
 See [../../critical-rules.md](../../critical-rules.md) Critical Rules. Escalation-specific gotchas:
 
-- `properties.folderName` MUST be the literal `Folder` from `uip solution resource list --kind App` (e.g., `"Shared/Approvals"`). `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do NOT use `"solution_folder"` — escalation apps are always external. See [../../critical-rules.md](../../critical-rules.md) Rule 11 and Anti-pattern 18.
+- `properties.folderName` MUST be the literal `Folder` from `uip solution resources list --kind App` (e.g., `"Shared/Approvals"`). `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do NOT use `"solution_folder"` — escalation apps are always external. See [../../critical-rules.md](../../critical-rules.md) Rule 11 and Anti-pattern 18.
 - `recipients` array MUST have at least one entry. Empty uploads but routes nowhere.
 - For `type: 3` (email) recipients, do NOT set `displayName`.
 - Generate fresh UUIDs for the top-level `id` AND each channel `id`.

package/skills/uipath-agents/references/lowcode/capabilities/guardrails/guardrails-recommend.md

@@ -206,7 +206,7 @@ Report per guardrail:
 - **Actionability issue** — describe the problem (e.g., "'Agent' is in selector.scopes but AllowedScopes for this validator is ['Llm', 'Tool'] — 'Agent' is not allowed; change scope to 'Llm' or 'Tool'") and the fix
 - **Relevance issue** — describe why the guardrail may not be appropriate and what to consider instead
 
-If the user asks to fix identified issues: apply corrections to `agent.json`, run `uip agent validate` to confirm the fix passes checks, then `uip agent migrate` to persist the regenerated `.agent-builder/`.
+If the user asks to fix identified issues: apply corrections to `agent.json`, run `uip agent refresh` to regenerate `entry-points.json` and `bindings_v2.json`, then `uip agent validate` to confirm the fix passes checks.
 
 ---
 

package/skills/uipath-agents/references/lowcode/capabilities/guardrails/guardrails.md

@@ -161,10 +161,10 @@ Creates a task in an Action Center app for human review.
 "action": {
   "$actionType": "escalate",
   "app": {
-    "id": "<Key from uip solution resource list --kind App>",
+    "id": "<Key from uip solution resources list --kind App>",
     "name": "<app Name>",
     "version": "0",
-    "folderName": "<Folder from uip solution resource list --kind App>"
+    "folderName": "<Folder from uip solution resources list --kind App>"
   },
   "recipient": {
     "type": 3,
@@ -176,11 +176,11 @@ Creates a task in an Action Center app for human review.
 | Field | Type | Required | Description |
 |-------|------|----------|-------------|
 | `$actionType` | `"escalate"` | Yes | Action discriminator |
-| `app.id` | string | Yes | App deployment ID — the `Key` field from `uip solution resource list --kind App` |
-| `app.name` | string | Yes | Action Center app name — the `Name` field from `uip solution resource list --kind App` |
+| `app.id` | string | Yes | App deployment ID — the `Key` field from `uip solution resources list --kind App` |
+| `app.name` | string | Yes | Action Center app name — the `Name` field from `uip solution resources list --kind App` |
 | `app.version` | string | Yes | Always `"0"` for solution-embedded apps |
 | `app.folderId` | string | No | Omit — not used by validate |
-| `app.folderName` | string | Yes | Literal Orchestrator folder — the `Folder` field from `uip solution resource list --kind App` (e.g., `"Shared"`, `"Shared/Approvals"`). `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. |
+| `app.folderName` | string | Yes | Literal Orchestrator folder — the `Folder` field from `uip solution resources list --kind App` (e.g., `"Shared"`, `"Shared/Approvals"`). `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. |
 | `app.appProcessKey` | string | No | Omit — only used in advanced scenarios |
 | `recipient.type` | integer | Yes | Recipient kind — see shapes below: 1=UserId, 2=GroupId, 3=UserEmail, 4=AssetUserEmail, 5=GroupName, 6=AssetGroupName, 7=ArgumentEmail, 8=ArgumentGroupName |
 | `recipient.*` | — | — | Remaining fields depend on `type` — see recipient shapes below |
@@ -242,7 +242,7 @@ Confirm the target validator is listed. Record the exact parameter `id` values a
 **Step 1 — Discover the app** using `--kind App` from the solution root:
 
 ```bash
-uip solution resource list --kind App --source remote --search "<app-name>" --output json
+uip solution resources list --kind App --source remote --search "<app-name>" --output json
 ```
 
 Filter results for `"Type": "Workflow Action"`. Use these three fields from the result:
@@ -253,7 +253,7 @@ Filter results for `"Type": "Workflow Action"`. Use these three fields from the
 | `Name` | `app.name` |
 | `Folder` | `app.folderName` (literal, e.g., `"Shared"`) |
 
-`app.version` is always `"0"` — that's a fixed value, not derived from the `resource list` row. `app.folderName` carries the literal `Folder` and `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do not use `FolderKey` for any `app.*` field.
+`app.version` is always `"0"` — that's a fixed value, not derived from the `resource list` row. `app.folderName` carries the literal `Folder` and `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Do not use `FolderKey` for any `app.*` field.
 
 If multiple entries share the same name in different folders, ask the user which deployment to use.
 
@@ -286,7 +286,10 @@ import os, sys, json, urllib.request, urllib.error
 key = sys.argv[1]
 base = f"{os.environ['UIPATH_URL']}/{os.environ['UIPATH_ORGANIZATION_ID']}/apps_/default/api/v1/default"
 hdr = {"Authorization": "Bearer " + os.environ["UIPATH_ACCESS_TOKEN"],
-       "X-Uipath-Tenantid": os.environ["UIPATH_TENANT_ID"], "Accept": "application/json"}
+       "X-Uipath-Tenantid": os.environ["UIPATH_TENANT_ID"], "Accept": "application/json",
+       # The Apps API gateway rejects the default "Python-urllib/x.y" User-Agent with 403.
+       # Send an explicit UA so this call doesn't false-fail (curl works because it sets one).
+       "User-Agent": "uipath-guardrail-verify"}
 def get(u):
     try:
         return json.load(urllib.request.urlopen(urllib.request.Request(u, headers=hdr)))
@@ -345,14 +348,14 @@ The check is **name-only** (types, `required` flags, `isList` are not checked);
 Run from the solution root:
 
 ```bash
-uip agent validate <AgentName> --output json
-uip agent migrate  <AgentName> --output json
-uip solution resource refresh  --output json
+uip agent refresh   <AgentName> --output json
+uip agent validate  <AgentName> --output json
+uip solution resources refresh   --output json
 ```
 
-- `validate` is a read-only check; regenerates `.agent-builder/agent.json`. Reports `MigrationPending: true` if migration is needed.
-- `migrate` generates `bindings_v2.json` with a `resource: "app"` binding for the escalation app. The binding carries both `name` (from `app.name`) and `folderPath` (translated from `app.folderName`).
-- `refresh` reads `bindings_v2.json`, fetches the app from the Resource Catalog Service using the joint `(name, folderPath)` key, and generates all 4 solution-level resource files (`app/workflow Action/`, `appVersion/`, `package/`, `process/webApp/`) plus the `debug_overwrites.json` entries for both the app and its code-behind process.
+- `refresh` regenerates `entry-points.json` and `bindings_v2.json` with a `resource: "app"` binding for the escalation app. The binding carries both `name` (from `app.name`) and `folderPath` (translated from `app.folderName`).
+- `validate` is a read-only check. Fails with `AgentValidationOutdated` if refresh is needed.
+- `solution resources refresh` reads `bindings_v2.json`, fetches the app from the Resource Catalog Service using the joint `(name, folderPath)` key, and generates all 4 solution-level resource files (`app/workflow Action/`, `appVersion/`, `package/`, `process/webApp/`) plus the `debug_overwrites.json` entries for both the app and its code-behind process.
 
 **Step 5 — Upload:**
 
@@ -813,7 +816,7 @@ PostExecution only — no content exists to check before the LLM generates outpu
 
 ### Example 8: Escalate PII Violations to Action Center — Multiple Tool Targets
 
-Escalates to an Action Center app when email or credit card PII is detected at the agent level. `app.id`, `app.name`, and `app.folderName` come from `uip solution resource list --kind App`.
+Escalates to an Action Center app when email or credit card PII is detected at the agent level. `app.id`, `app.name`, and `app.folderName` come from `uip solution resources list --kind App`.
 
 ```json
 {
@@ -980,9 +983,9 @@ Add the `guardrails` array at the agent.json root level alongside `settings`, `m
 7. **Do not use `filter` action on built-in validators** — `"$actionType": "filter"` is only supported on deterministic rules. All built-in validators (`pii_detection`, `intellectual_property`, `prompt_injection`, `user_prompt_attacks`, `harmful_content`) support only `block`, `log`, and `escalate`.
 8. **Do not use odd numbers or floats for `harmfulContentEntityThresholds`** — only `0`, `2`, `4`, `6` are valid severity values. Values like `3` or `2.5` cause validation errors.
 9. **Do not add a built-in validator without first running `uip agent guardrails list --output json`** — always fetch the list, verify the validator exists, and confirm `Status` is `"Available"`. Adding an `Unauthorised` or non-existent validator causes runtime failures.
-10. **Do not use Action Center apps with `Type: "VB Action"` or `Type: "Coded"` as escalation targets** — only entries with `Type: "Workflow Action"` can back a guardrail escalation. Always filter `uip solution resource list --kind App` results by this type.
+10. **Do not use Action Center apps with `Type: "VB Action"` or `Type: "Coded"` as escalation targets** — only entries with `Type: "Workflow Action"` can back a guardrail escalation. Always filter `uip solution resources list --kind App` results by this type.
 11. **Do not use `--kind Process` (Type: `"webApp"`) to find escalation apps** — those entries are code-behind processes, not app deployments. Their `Key` values are process release GUIDs, not app IDs. Always use `--kind App` with `Type: "Workflow Action"`.
-12. **Do not put `"solution_folder"` into `app.folderName`** — set it to the literal `Folder` from `uip solution resource list --kind App` (e.g., `"Shared/Approvals"`). `uip agent migrate` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Omit `app.folderId`. `FolderKey` from `resource list` is NOT used in any `app.*` field — it IS correct in `debug_overwrites.json` entries, where it maps the solution-embedded resource to its real runtime location.
+12. **Do not put `"solution_folder"` into `app.folderName`** — set it to the literal `Folder` from `uip solution resources list --kind App` (e.g., `"Shared/Approvals"`). `uip agent refresh` translates it to `folderPath` in the App binding inside `bindings_v2.json`. Omit `app.folderId`. `FolderKey` from `resource list` is NOT used in any `app.*` field — it IS correct in `debug_overwrites.json` entries, where it maps the solution-embedded resource to its real runtime location.
 13. **Do not hardcode the auth-file path for Apps API calls in guardrail setup.** `source <(grep = ...)` fails to export variables to the surrounding shell in some environments, and `~/.uipath/.auth` is wrong when the sandbox writes auth at the filesystem root. Use the HOME-robust prelude: `A="$HOME/.uipath/.auth"; [ -f "$A" ] || A="/.uipath/.auth"; set -a; source "$A"; set +a`.
 14. **Do not add a Tool-scoped guardrail before the tool is added to the agent** — every name in `selector.matchNames` must match an existing tool resource under `<AGENT_NAME>/resources/<ToolName>/resource.json`. A guardrail referencing a non-existent tool will be caught by `uip agent validate` and fail with an error. Always run `uip agent tool list` first (Step 2) and confirm target tools are present.
 15. **Do not skip action schema validation for escalation apps** — before writing a guardrail with `"$actionType": "escalate"`, fetch the app's action schema and verify all required inputs (8), outputs (3), and outcomes (2) are present by name. If any are missing, report `<APP_NAME> does not have the required action schema configuration for tool guardrails.` and do not proceed. See [§ Adding an escalation guardrail — Step 2](#adding-an-escalation-guardrail--step-by-step).
@@ -1090,14 +1093,14 @@ Quick template — built-in PII validator:
 ]
 ```
 
-### Step 5 — Validate and migrate
+### Step 5 — Refresh and validate
 
 ```bash
+uip agent refresh  "<AGENT_NAME>" --output json
 uip agent validate "<AGENT_NAME>" --output json
-uip agent migrate  "<AGENT_NAME>" --output json
 ```
 
-Confirm the guardrails appear in the validated output without errors. Migrate regenerates `.agent-builder/` so Studio Web sees the updated guardrails.
+Confirm the guardrails appear in the validated output without errors. Refresh regenerates `entry-points.json` and `bindings_v2.json` so Studio Web sees the updated guardrails.
 
 ## References