@uipath/skills 1.203.1-preview.1177 → 1.203.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/skills",
-  "version": "1.203.1-preview.1177",
+  "version": "1.203.1",
   "description": "UiPath agent skills for Claude Code, Codex, Cursor, Copilot, Gemini and OpenCode — RPA, UI automation, UI testing, coded agents/apps/workflows, and troubleshooting. Distributed as the UiPath Claude Code plugin.",
   "author": {
     "name": "UiPath"

package/skills/uipath-maestro-bpmn/references/operate/CAPABILITY.md

@@ -32,19 +32,10 @@ These actions may contact UiPath services or external systems.
    migrate, and cursor movement require a clear user decision for that action.
 3. **Validate before operate** - do not upload, publish, debug, or run until Author validation is complete or the user
    explicitly accepts known draft warnings.
-<<<<<<< HEAD
 4. **Refresh package metadata before cloud actions** - run `uip maestro bpmn refresh <project-path> --output json`;
    `Data.WrittenFiles` names what was stale. Never use the deprecated `update-metadata` - it does not materialize
    `Intsvc.*` connection bindings. Stale `bindings_v2.json`, `entry-points.json`,
    `operate.json`, or `package-descriptor.json` can break import or runtime even when the BPMN source is correct.
-=======
-4. **Refresh package metadata before cloud actions** - after source validation,
-   run `uip maestro bpmn refresh <project-path> --output json`
-   (the deprecated `uip maestro bpmn update-metadata <file.bpmn> --dry-run` checks drift
-   without writing). Stale `bindings_v2.json`, `entry-points.json`,
-   `operate.json`, or `package-descriptor.json` can break import or runtime
-   even when the BPMN source is correct.
->>>>>>> 0770c04c1 (docs(bpmn): make refresh the single documented metadata contract)
 5. **Keep source and package ownership clear** - fix process structure, variables, mappings, events, and documented non-IS
    extensions in `.bpmn`; rerun CLI generation/enrichment for generated package JSON and Integration Service metadata.
 6. **Default publish wording to Studio Web upload unless the user explicitly asks for Orchestrator deployment** - keep deploy semantics explicit.

package/skills/uipath-maestro-bpmn/references/shared/local-metadata-regeneration-guide.md

@@ -2,16 +2,14 @@
 
 Use this guide when BPMN source changed and local package metadata must be refreshed or verified before packaging, upload, debug, publish, or deploy.
 
-<<<<<<< HEAD
 **Do NOT apply it to an Integration Service draft or boundary handoff.** When the task is to author a local BPMN draft and hand connector enrichment to the CLI (no upload/pack yet), `entry-points.json`, `bindings_v2.json`, `operate.json`, and `package-descriptor.json` stay CLI-owned — do not hand-author or pre-generate them. Author only the `.bpmn` source shape plus a `.md` notes file **inside the project directory** naming the CLI-owned blockers. The regeneration workflow below reaches such a project only once its connectors are enriched.
-=======
+
 The BPMN `refresh` command is the authoritative local source-to-derived-state
 boundary. It requires exactly one project-root `.bpmn` file
 and atomically regenerates the complete package metadata set. The command is
 offline and provider-neutral: it does not log in, discover a tenant, invoke a
 connector, or resolve an account. It consumes only identities already authored
 into the supported BPMN contract.
->>>>>>> b77a95d33 (feat(bpmn): derive package metadata with refresh)
 
 ## Ownership
 
@@ -81,23 +79,17 @@ Do not derive metadata from stale package files first. Use existing generated fi
 ## Safe Local Workflow
 
 1. Edit `.bpmn` first.
-<<<<<<< HEAD
 2. Check the source itself: well-formed XML, diagrams, entry point IDs,
    variables, mappings, binding references. Do not run `uip maestro bpmn
    validate` yet — it cross-checks `entry-points.json` against the source, so it
    reports the pre-refresh state as an error whenever an edit renamed a start
    event. Run it after step 3.
 3. Regenerate package metadata from the BPMN source:
-=======
-2. Run local validation for XML, diagrams, entry point IDs, variables, mappings, binding references, and package metadata drift.
-3. After validation succeeds, regenerate derived metadata:
->>>>>>> b77a95d33 (feat(bpmn): derive package metadata with refresh)
 
    ```bash
    uip maestro bpmn refresh <project-path> --output json    # regenerate + materialize IS connection bindings
    ```
 
-<<<<<<< HEAD
    `refresh` materializes `Intsvc.*` connection bindings (including triggers)
    and validates before writing. It needs `project.uiproj` — without one it
    exits `BpmnRefreshFailed` / `RetryWillNotFix`; for a bare `.bpmn`, write the
@@ -105,21 +97,12 @@ Do not derive metadata from stale package files first. Use existing generated fi
    stale and `Data.UnchangedFiles` the ones already current, so a drift answer
    needs no separate command. Never fall back to the deprecated
    `update-metadata`.
-=======
-   A successful response reports `Status`, `ProjectPath`, `BpmnFile`,
-   `WrittenFiles`, and `UnchangedFiles`.
-
-   Use `refresh` — it materializes `Intsvc.*` connection bindings (including
-   triggers) and validates before writing. The deprecated
-   `uip maestro bpmn update-metadata <file.bpmn>` (with `--dry-run` for a
-   drift check) only rewrites the BPMN-derived fields and does **not** materialize
-   connection bindings.
->>>>>>> 0770c04c1 (docs(bpmn): make refresh the single documented metadata contract)
 
    If CLI unavailable for a local-only synthetic project, write the minimal
    placeholder-safe shape (see below) before continuing.
 
-4. Verify the project directory now contains the full metadata set:
+4. Run `uip maestro bpmn validate <file.bpmn> --output json`, then verify the
+   project directory contains the full metadata set:
    `project.uiproj`, `operate.json`, `entry-points.json`, `bindings_v2.json`,
    and `package-descriptor.json`. Run refresh a second time only when checking
    idempotence; unchanged source must leave all four generated files unchanged.

package/skills/uipath-maestro-flow/references/author/greenfield.md

@@ -68,7 +68,7 @@ If not logged in and you need tenant nodes:
 
 ```bash
 uip login                                          # interactive OAuth (opens browser)
-uip login --authority https://alpha.uipath.com     # non-production environments
+uip login --authority "<AUTHORITY_URL>"            # non-default host (Automation Suite, dedicated)
 ```
 
 When you do need it, emit `uip login status --output json` as a parallel `Bash` inside T1.

package/skills/uipath-maestro-flow/references/author/plugins/inline-voice-agent/impl.md

@@ -247,7 +247,7 @@ Outbound needs no binding step — `inputs.from` names the trunk directly, so th
 | `flow pack` / `flow debug`: `Converted BPMN carries no agentDefinition for voice agent node(s) …` | Different failure from the row above — the agent directory is fine, but the CLI's bundled `@uipath/flow-converter` does not forward `voiceAgentDefinitions` to the BPMN serializer. Pack catches it rather than shipping a package that deploys and drops every call | `uip tools update` to a CLI whose converter supports voice, then re-pack. Nothing in the project can work around an old converter |
 | `registry get` reports the voice type not found | The installed CLI predates voice support (the types ship in its bundled registry, so this is a CLI-version problem, not a tenant one) | `uip tools update`; re-run `registry get` |
 | `uip conversational trunks …`: `unknown command 'trunks'` (and `uip conversational --help` lists no `trunks`) | The CLI predates the trunk commands. Independent of node support: the voice node types ship in the bundled registry, so authoring, `registry get`, and `validate` all work on a CLI whose `conversational` tool has no `trunks` | Tool packages resolve on the CLI's own `N.Nx` minor line, so `uip tools update` cannot pull a `trunks` that only exists on a later line — the CLI itself has to be on one that ships it (`uip --version`, and `which -a uip` when more than one is installed). A trunk's number and direction flags are also readable from the Phone numbers page. Note a tool's `-dev.<run>` number is a global CI counter, not a per-line one: a tool run number higher than the CLI's says nothing about which line it came from |
-| Call never connects on a tenant that packs and deploys fine | No SIP trunk provisioned, or the number lacks the direction your topology needs — not detectable from the CLI at author time | `uip conversational trunks list` to see whether the tenant has any trunk at all. Adding a number, enabling a direction on it, and releasing it are portal-only — send the user to `{baseUrl}/{orgName}/agents_/phone-numbers` (e.g. `https://alpha.uipath.com/conversationalagents/agents_/phone-numbers`). Raise it as an Open Question rather than re-authoring the flow |
+| Call never connects on a tenant that packs and deploys fine | No SIP trunk provisioned, or the number lacks the direction your topology needs — not detectable from the CLI at author time | `uip conversational trunks list` to see whether the tenant has any trunk at all. Adding a number, enabling a direction on it, and releasing it are portal-only — send the user to `{baseUrl}/{orgName}/agents_/phone-numbers` (e.g. `https://cloud.uipath.com/conversationalagents/agents_/phone-numbers`). Raise it as an Open Question rather than re-authoring the flow |
 | Call connects but the agent is silent / call drops immediately | Package built without the embedded `agentDefinition` (hand-rolled pack pipeline), or `settings.voice` removed after pack | Re-pack with the CLI; verify the staged `.bpmn` has `name="agentDefinition"` on the voice serviceTask |
 | Outbound call never dials | `from` is not a SIP trunk number on the tenant, or `to` is malformed, or the trunk exists but is not outbound-enabled | `uip conversational trunks list --direction outbound --output json`; use a number with `outboundEnabled: true` for `from`; `to` must be E.164 in a literal binding. Turning outbound *on* for an existing number is portal-only — the Phone numbers page, `{baseUrl}/{orgName}/agents_/phone-numbers` |
 | Inbound number rings but nothing runs | Trunk not bound, bound to a different process, or bound to an older build | `uip conversational trunks list --direction inbound --output json` — check `processName` and that `entryPoint` matches the trigger's `inputs.entryPointId`; re-run `trunks assign` (§ Bind an Inbound Phone Number) |

package/skills/uipath-maestro-flow/references/author/plugins/inline-voice-agent/planning.md

@@ -32,7 +32,7 @@ uip conversational trunks list --direction inbound  --output json   # inbound bi
 
   ```text
   {baseUrl}/{orgName}/agents_/phone-numbers
-  # e.g. https://alpha.uipath.com/conversationalagents/agents_/phone-numbers
+  # e.g. https://cloud.uipath.com/conversationalagents/agents_/phone-numbers
   ```
 
   It is org-scoped (no tenant segment) — build it from `uip login status --output json` (`Data.BaseUrl` + `Data.Organization`). There is no `trunks create`.

package/skills/uipath-maestro-flow/references/shared/cli-conventions.md

@@ -132,7 +132,7 @@ Log in interactively by running:
 
 ```bash
 uip login
-uip login --authority https://alpha.uipath.com    # non-production environments
+uip login --authority "<AUTHORITY_URL>"           # non-default host (Automation Suite, dedicated)
 ```
 
 ## 6. `--folder-key` requirement

package/version-manifest.json

@@ -1,5 +1,5 @@
 {
   "schemaVersion": 2,
-  "skillsVersion": "1.203.1-preview.1177",
+  "skillsVersion": "1.203.1",
   "targetCli": "^1.203.0"
 }