@uipath/skills 1.195.1 → 1.196.0

package/skills/uipath-rpa/references/tenant-library-search-guide.md

@@ -8,23 +8,27 @@ The tenant feed is authoritative for org-published libraries. Do NOT search the
 
 ## CLI surface
 
-One command, one global filter:
+`uip or libraries list`. Returns a curated `Data: [{ Key, Title, Version, Authors }]` (pass `--all-fields` for the full DTO). `Key` is `PackageId:Version` and is always populated. `Title` can be `null`.
 
 ```bash
-uip resource libraries list --limit 500 --output json
-```
+# Server-side name search (contains-match), single keyword:
+uip or libraries list --search Excel --output json
 
-Returns `Data: [{ Key, Title, Version, Authors }]`. `Key` is `PackageId:Version` and is always populated. `Title` can be `null`.
+# Full scan, then filter/rank client-side:
+uip or libraries list --limit 500 --output json
+```
 
 | Flag | Purpose |
 |------|---------|
+| `-s, --search <term>` | Server-side name contains-match. Single term only — for multi-keyword OR or `Authors` matching, use `--output-filter`. |
+| `--feed-id <id>` | Target a specific feed by ID. Defaults to the tenant feed. |
 | `--limit <N>` | Items per call (default 50). Use 500 to cover most tenants in one call. |
 | `--offset <N>` | Pagination offset. Use only if `Data.length == --limit`. |
 | `--sort-by "<field> <asc\|desc>"` | Sort. Default `Id desc`. |
-| `--output-filter "<JMESPath>"` | Global filter, evaluated client-side after the API returns. |
-| `-t, --tenant <name>` | Override default tenant. |
+| `--all-fields` | Return the full library DTO instead of the curated subset. |
+| `--output-filter "<JMESPath>"` | Client-side filter, evaluated after the API returns. Use for multi-keyword OR, `Authors` matching, or null-`Title` guarding. |
 
-There is **no `--search` flag** and **no `--feed-id` flag** on `libraries list`. Filter via `--output-filter`.
+`--search` is the simplest path for a single name keyword. Use `--output-filter` (below) when you need multi-keyword OR, `Authors`-field matching, or a null-`Title` guard.
 
 ## JMESPath filter recipe
 
@@ -32,12 +36,12 @@ There is **no `--search` flag** and **no `--feed-id` flag** on `libraries list`.
 
 ```bash
 # Single keyword
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && contains(Title, 'Excel')]" \
   --output json
 
 # Multi-keyword OR
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && (contains(Title, 'Common') || contains(Title, 'Shared'))]" \
   --output json
 ```
@@ -49,7 +53,7 @@ For case-insensitive matching, lowercase the keyword in the filter and the field
 For orgs that publish libraries with cryptic Titles but a stable `Authors` value, filter on `Authors` instead of `Title`:
 
 ```bash
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Authors != null && contains(Authors, '<OrgName>')]" \
   --output json
 ```
@@ -58,7 +62,7 @@ Combine `Title` and `Authors` filters with `||` when the org uses both conventio
 
 ## Procedure
 
-1. **Auth preflight.** Run a benign call once: `uip resource libraries list --limit 1 --output json`. If `Result == "Failure"` with an auth-related message, surface it and switch to the manual fallback (below). Do NOT retry silently.
+1. **Auth preflight.** Run a benign call once: `uip or libraries list --limit 1 --output json`. If `Result == "Failure"` with an auth-related message, surface it and switch to the manual fallback (below). Do NOT retry silently.
 2. **Extract keywords** from the source (user prompt, plan tasks, surrounding workflow names). Cap at 6:
    - Org-prefix terms: `Common`, `Shared`, `Utils`, `Helpers`, `<Company>` if known
    - Capability terms: `Excel`, `SAP`, `ServiceNow`, `Salesforce`, `Email`, `PDF`, `SharePoint`, `Outlook`, `Citrix`, etc. — drawn from the activities the project will use
@@ -81,7 +85,7 @@ Combine `Title` and `Authors` filters with `||` when the org uses both conventio
    > 3. **Provide names manually** — name libraries to install even if not yet deployed; flag as `[VERIFY DEPLOYMENT]`
    > 4. **Pause and re-authenticate to a different tenant** — if libraries live elsewhere
 
-6. **Record the user's selection.** For each accepted library, run `uip rpa packages install --packages '[{"id": "<PackageId>", "version": "<Version>"}]' --output json` to add it to `project.json`. Verify after install with `uip rpa validate --output json`.
+6. **Record the user's selection.** For each accepted library, run `uip rpa packages install --packages 'id=<PackageId>,version=<Version>' --output json` to add it to `project.json`. Verify after install with `uip rpa validate --output json`.
 
 ## Skip when
 
@@ -103,8 +107,8 @@ If `uip` is unauthenticated, ask the legacy question:
 ## Anti-patterns
 
 1. **Searching the local filesystem first.** Tenant is authoritative; local matches do not indicate org adoption.
-2. **Using `--search`.** That flag does not exist on `uip resource libraries list`. Filter via `--output-filter`.
-3. **Using `--feed-id`.** That flag does not exist on `uip resource libraries list` (it does on `uip or packages list` — different command). The libraries command always targets the default tenant feed.
+2. **Using `--search` for multi-keyword OR or `Authors` matching.** `--search` is a single-term server-side name contains-match only. For OR across keywords or matching on `Authors`, use `--output-filter`.
+3. **Passing `--feed-id` without a reason.** It defaults to the tenant feed — only set it to target a non-default feed.
 4. **Calling `contains(Title, ...)` without `Title != null` guard.** Tenants commonly hold packages with null Title — the call fails fast with `Invalid type: contains() expected ... received type null`.
 5. **Listing all libraries with no `--limit` bump, or paginating past the end.** Default 50 truncates large tenants and silently misses candidates. Use `--limit 500` for a one-shot scan; paginate via `--offset` only if `Data.length == 500`. If `Data.length < --limit` on a paginated call, you have seen the entire feed — stop searching, do not run more filtered queries hoping for hidden matches.
 6. **Auto-installing a candidate.** Library installation modifies `project.json` and project compilability — always confirm via `AskUserQuestion` before invoking `packages install`.

package/skills/uipath-rpa/references/testing-guide.md

@@ -160,7 +160,7 @@ Three commands attach different data source types to a test case. All three regi
 #### `test-data add-variation` — File-based (JSON)
 
 ```bash
-uip rpa test-data add-variation --test-case-path "<TEST_CASE_FILE>" --data-variation-path "<DATA_FILE>" --project-dir "<PROJECT_DIR>" --output json --use-studio
+uip rpa test-data add-variation --test-case-path "<TEST_CASE_FILE>" --data-variation-path "<DATA_FILE>" --project-dir "<PROJECT_DIR>" --output json
 ```
 
 | Parameter | Required | Description |
@@ -172,7 +172,7 @@ Parses fields from the JSON file and creates one argument per field with matchin
 
 **Example:**
 ```bash
-uip rpa test-data add-variation --test-case-path "TestProcessInvoice.cs" --data-variation-path ".variations/InvoiceData.json" --project-dir "C:\MyProject" --output json --use-studio
+uip rpa test-data add-variation --test-case-path "TestProcessInvoice.cs" --data-variation-path ".variations/InvoiceData.json" --project-dir "C:\MyProject" --output json
 ```
 
 #### `test-data add-queue` — Orchestrator Test Data Queue
@@ -180,7 +180,7 @@ uip rpa test-data add-variation --test-case-path "TestProcessInvoice.cs" --data-
 > **Prerequisite:** Use the **uipath-platform** skill to discover queue details (name, ID, folder) before calling this command.
 
 ```bash
-uip rpa test-data add-queue --test-case-path "<TEST_CASE_FILE>" --queue-name "<QUEUE_NAME>" --folder-path "<FOLDER>" --queue-id <ID> --project-dir "<PROJECT_DIR>" --output json --use-studio
+uip rpa test-data add-queue --test-case-path "<TEST_CASE_FILE>" --queue-name "<QUEUE_NAME>" --folder-path "<FOLDER>" --queue-id <ID> --project-dir "<PROJECT_DIR>" --output json
 ```
 
 | Parameter | Required | Description |
@@ -194,7 +194,7 @@ Creates an `IDictionary<string, object>` argument named after the queue (camelCa
 
 **Example:**
 ```bash
-uip rpa test-data add-queue --test-case-path "TestLoanApproval.cs" --queue-name "loan_applications" --folder-path "Shared" --queue-id 123 --project-dir "C:\MyProject" --output json --use-studio
+uip rpa test-data add-queue --test-case-path "TestLoanApproval.cs" --queue-name "loan_applications" --folder-path "Shared" --queue-id 123 --project-dir "C:\MyProject" --output json
 ```
 
 > **Critical:** Do NOT rename the auto-generated test data queue argument. If you change its name, data retrieval silently fails.
@@ -206,7 +206,7 @@ uip rpa test-data add-queue --test-case-path "TestLoanApproval.cs" --queue-name
 > 2. **Install the target entity into the project** if not already installed — `uip rpa data-fabric-entities install --add "<ENTITY_NAME>" --project-dir "<PROJECT_DIR>" --output json`. `test-data add-entity` requires the entity's generated type to exist in the project. See [cli-reference.md § Data Fabric Entities](cli-reference.md#commands----data-fabric-entities).
 
 ```bash
-uip rpa test-data add-entity --test-case-path "<TEST_CASE_FILE>" --entity-name "<ENTITY_NAME>" --entity-type-name "<ENTITY_TYPE>" --project-dir "<PROJECT_DIR>" --output json --use-studio
+uip rpa test-data add-entity --test-case-path "<TEST_CASE_FILE>" --entity-name "<ENTITY_NAME>" --entity-type-name "<ENTITY_TYPE>" --project-dir "<PROJECT_DIR>" --output json
 ```
 
 | Parameter | Required | Description |
@@ -219,7 +219,7 @@ Creates an argument of the entity type named after the entity (camelCase). Requi
 
 **Example:**
 ```bash
-uip rpa test-data add-entity --test-case-path "TestLoanApproval.cs" --entity-name "LoanApplication" --entity-type-name "LoanApplication" --project-dir "C:\MyProject" --output json --use-studio
+uip rpa test-data add-entity --test-case-path "TestLoanApproval.cs" --entity-name "LoanApplication" --entity-type-name "LoanApplication" --project-dir "C:\MyProject" --output json
 ```
 
 ### Data-Driven Testing Best Practices

package/skills/uipath-rpa/references/trigger-pattern-guide.md

@@ -97,7 +97,7 @@ Structural shape (placeholders in angle brackets — fill from `get-default-xaml
         <!-- One or more local trigger activities. Get full XAML via:
                uip rpa activities get-default-xaml \
                  --activity-class-name <FullClassName> \
-                 --project-dir "<PROJECT_DIR>" --use-studio --output json -->
+                 --project-dir "<PROJECT_DIR>" --output json -->
         <<TriggerPrefix>:<TriggerClassName> DisplayName="..." ... />
       </ui:TriggerScope.Triggers>
       <ui:TriggerScope.Action>
@@ -193,7 +193,7 @@ Per-package conventions (read each package's bundled `overview.md` for canonical
 
 - **O365 Mail** (`umm:` prefix family): `FilterExpression` as a string attribute. OData-like: `(parentFolderId=='INBOX')`, `(hasAttachments==`true`)`. AND uses `&amp;&amp;`; booleans use backticks. See [activity-docs/UiPath.MicrosoftOffice365.Activities/3.8/activities/overview.md](activity-docs/UiPath.MicrosoftOffice365.Activities/3.8/activities/overview.md).
 - **GSuite Gmail**: `Filter` as a structured child element with `LogicalOperator` + `Criteria` leaves, not a string. See [activity-docs/UiPath.GSuite.Activities/3.8/activities/NewEmailReceived.md](activity-docs/UiPath.GSuite.Activities/3.8/activities/NewEmailReceived.md).
-- **IS connector triggers** (Salesforce, Jira, Slack, …): authored as a structured filter tree, not a string. Discover the filterable field names via `uip is triggers describe "<connector>" "<OPERATION>" "<object>" --output json` → read `filterFields.fields[*].name`. The CLI compiles the tree into the runtime expression; do not pass the compiled form directly.
+- **IS connector triggers** (Salesforce, Jira, Slack, …): authored as a structured filter tree, not a string. Discover the filterable field names via `uip is triggers describe "<connector>" "<OPERATION>" "<object>" --output json` → read `Data.FilterFields[*].Name`. The CLI compiles the tree into the runtime expression; do not pass the compiled form directly.
 
 ## Lifecycle and Verification
 

package/skills/uipath-rpa/references/ui-automation-guide.md

@@ -14,7 +14,7 @@ Quick reference for UI automation in UiPath workflows — covers both coded work
 
 ## Pre-flight: Window Baseline
 
-Before configuring any target or writing any UIA workflow, list top-level windows **once** via `uip rpa uia snapshot inspect` to check whether the target app is open. Full flag reference: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`. Two outcomes:
+Before configuring any target or writing any UIA workflow, list top-level windows **once** via the UIA snapshot CLI to check whether the target app is open. Subcommand and flags: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`. Two outcomes:
 
 - **Target window present** → proceed directly to `uia-configure-target`; it will attach.
 - **Target window absent** → launch the app yourself, then proceed directly to `uia-configure-target`; the skill picks up the new window as part of its own capture.
@@ -46,7 +46,7 @@ When the source is a Test Manager test case, a PDD, or any written list of "Clic
 | Sense | Used in | What it is | Boundary / identity |
 |-------|---------|------------|---------------------|
 | **Capture screen** | XAML Multi-Screen Authoring (below), [uia-configure-target-workflows.md § Multi-Step UI Flows](uia-configure-target-workflows.md) | A distinct UI state that requires its own `uia-configure-target` pass because the app has to be advanced (via the `uip rpa uia interact` CLI) between captures. | Bounded by app advancement — everything captured before the next advance is one capture screen. |
-| **OR screen** | Object Repository CLI, `.objects/` layout, `Descriptors.<App>.<Screen>.<Element>`, [uia-configure-target-workflows.md](uia-configure-target-workflows.md) | A data-model entity in the Object Repository, registered via `create-screen` / matched via `get-screens`. | Identified by its window selector. |
+| **OR screen** | Object Repository CLI, `.objects/` layout, `Descriptors.<App>.<Screen>.<Element>`, [uia-configure-target-workflows.md](uia-configure-target-workflows.md) | A data-model entity in the Object Repository, registered and matched via the OR CLI. | Identified by its window selector. |
 | **Screen handle** (coded only) | "Screen Handle Affinity" under § For Coded Workflows | A runtime `UiTargetApp` returned by `uiAutomation.Open` / `Attach`, bound to one OR screen. | Element descriptors are valid only on the handle for their own OR screen. |
 
 **These senses are independent.** Multiple capture screens can map to one OR screen when they share a window selector (e.g., several URLs under the same browser tab if the window selector is URL-neutral). Conversely, one OR screen can produce many screen handles at runtime (one per `Open`/`Attach` call).
@@ -187,7 +187,7 @@ Before writing ANY target — whether C# (`uiAutomation.Open(...)`, `Descriptors
 2. **NEVER guess selector attributes** from HTML/DOM structure, element tag names, or CSS classes. Selectors are generated from the live application tree by probing elements — not from source code inspection.
 3. **ALWAYS follow the target configuration steps** from [uia-configure-target-workflows.md](uia-configure-target-workflows.md). Use the returned XAML/references exactly as provided. Do not modify selectors, content hashes, or reference IDs.
 4. **NEVER substitute external browser automation for UIA.** Do not use PowerShell, Selenium, Playwright, Chrome DevTools Protocol, raw DOM JavaScript, HTTP form posts, or `InvokeCode` to drive a browser/app when the user asked for a UiPath RPA automation. Use those tools only for non-UI setup, diagnostics, or data preparation; the visible application interaction must remain in UiPath UIA activities or coded `uiAutomation` calls backed by Object Repository descriptors.
-5. **Use UiPath UIA for exploration.** App/window discovery, UI probing, selector discovery, and target capture must use the UI Automation skills and `uip rpa uia` CLI flows (`uip rpa uia snapshot inspect`, `uia-configure-target`, `uip rpa uia interact`, Object Repository capture). Full flag reference: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`. Do not use Playwright, Selenium, DOM inspection, process lists, or ad hoc scripts to decide what UI targets/selectors to author.
+5. **Use UiPath UIA for exploration.** App/window discovery, UI probing, selector discovery, and target capture must use the UI Automation skills and the `uip rpa uia` CLI flows (the UIA snapshot CLI, `uia-configure-target`, the `uip rpa uia interact` CLI, Object Repository capture). Subcommands and flags: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`. Do not use Playwright, Selenium, DOM inspection, process lists, or ad hoc scripts to decide what UI targets/selectors to author.
 
 > This gate applies regardless of how simple the target seems. Even a `<webctrl tag='BODY' />` selector will fail validation without proper attributes. The cost of running target configuration is always lower than debugging hand-written selectors.
 
@@ -220,13 +220,50 @@ Procedure: [uia-configure-target-workflows.md § Multi-Step UI Flows](uia-config
 
 ---
 
+## Object Repository as a Published UI Library
+
+Selector breakage is the #1 maintenance cost in UI automation. A **UI Library** is a published library project whose Object Repository ships inside the `.nupkg` — descriptors defined once, consumed by every automation against the same application. Fix a descriptor once, bump the version, and all consumers inherit the fix.
+
+### Hierarchy and naming
+
+```
+Application (InvoicePortal)
+  └── Screen (LoginPage)
+      └── Element (UsernameField)
+```
+
+- Reference form: `App.Screen.Element` — `InvoicePortal.LoginPage.UsernameField`
+- Business-meaningful PascalCase element names: `SubmitOrderButton`, not `Button32`
+- One descriptor per distinct UI element; screens mirror the application's logical screens
+
+### Extract-and-publish pattern
+
+Precondition: the source project has captured descriptors (`.objects/` content). If it has none, capture targets first ([§ Configuring Targets](#configuring-targets-object-repository)) — there is nothing to promote, and hand-writing descriptors is forbidden.
+
+1. Develop the first process against its **local** Object Repository, configuring targets as usual ([§ Configuring Targets](#configuring-targets-object-repository)).
+2. Promote the reusable descriptors into a dedicated UI Library project — a library project ([library-authoring-guide.md](library-authoring-guide.md)) holding the shared Object Repository; pack and upload per [library-authoring-guide.md § Pack & Publish](library-authoring-guide.md). Concrete OR manipulation steps: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/`.
+3. **One UI Library per corporate application** (SAP, Salesforce, Workday) — an update to one app's selectors must not force re-deployment of another's.
+4. New automations against that application consume the UI Library from the start. Process-specific one-off descriptors stay in the local Object Repository.
+
+### Consumption
+
+Install the UI Library as a package dependency; its descriptors appear under **UI Libraries** in the Object Repository and are targetable like local descriptors. Coded workflows resolve them via [§ Finding Descriptors Step 2](#step-2--check-uilibrary-nuget-packages). Selector updates propagate by bumping the dependency version — no per-workflow changes.
+
+### Update rules — MANDATORY
+
+1. **Update descriptors in place — NEVER delete-and-re-add an element.** The element-to-activity link is identity-based; deleting the element severs it and every consumer activity bound to it breaks, even if a same-named element is re-created.
+2. **Version by SemVer** ([library-authoring-guide.md § Versioning](library-authoring-guide.md)): selector fix without renaming = patch; element/screen rename or restructure = breaking = major.
+3. **Promote accepted healing fixes.** When a selector recovery ([§ Runtime Selector Failure Recovery](#runtime-selector-failure-recovery)) is accepted in a workflow that consumes a shared UI Library, apply the fix in the UI Library and bump the version — do not re-fix the same selector consumer by consumer.
+
+---
+
 ## Running UI Automation Workflows
 
 **Always use `uip rpa debug start`** (not `uip rpa run`) when running workflows with UI automation. A debug session pauses on error instead of tearing down the application, leaving the UI state available for inspection.
 
 **Every debug run** must follow this procedure to prevent stale windows from accumulating or being reused in a dirty state:
 
-1. **Record the window baseline** — list top-level windows via `uip rpa uia snapshot inspect` and note which w-refs and titles are already present. Full flag reference: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`.
+1. **Record the window baseline** — list top-level windows via the UIA snapshot CLI and note which w-refs and titles are already present. Subcommand and flags: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`.
 2. **Run the workflow:**
    ```bash
    uip rpa debug start --file-path "<FILE>" --project-dir "<PROJECT_DIR>" --output json
@@ -236,8 +273,8 @@ Procedure: [uia-configure-target-workflows.md § Multi-Step UI Flows](uia-config
    ```bash
    uip rpa execution cancel --project-dir "<PROJECT_DIR>" --output json
    ```
-4. **List windows again** via `uip rpa uia snapshot inspect`.
-5. **Diff before vs after.** Any window present now that was NOT in the baseline was opened by the workflow. Close each such window via `uip rpa uia interact window` (see `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md` for the exact close-action flags).
+4. **List windows again** via the UIA snapshot CLI.
+5. **Diff before vs after.** Any window present now that was NOT in the baseline was opened by the workflow. Close each such window via the `uip rpa uia interact` CLI (see `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md` for the close subcommand and its flags).
 
 Skipping steps 4-5 causes the next run's open-if-not-open behavior to reuse a stale window in whatever state it was left in, or -- if the selector doesn't match -- to spawn a duplicate instance.
 

package/skills/uipath-rpa/references/uia-configure-target-workflows.md

@@ -36,9 +36,9 @@ Some UI elements only become visible after interacting with earlier elements (e.
 
 After registering an element in the Object Repository, advance to the next screen by interacting with it (or a sibling element) via the `uip rpa uia interact` CLI. Interact here **only to move the app to the next state you need to capture** — as many verbs as that legitimately takes (e.g. open a menu then click an item, or type then press Enter), never to map the app ahead of need or to verify behavior (see complete-then-advance above). Read `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`. Read it rather than improvising from `--help`. Do not use `interact` to read attributes and hand-write or edit a selector; selector construction and improvement are the configure-target flow's job.
 
-**Reuse refs from the current `uia-configure-target` capture — do not re-inspect.** The `uip rpa uia interact` CLI resolves element refs against the most recent snapshot in memory regardless of which CLI wrote it (the two write to different folders, but the snapshot is shared). Pass the same e-refs (`e28`, `e35`, etc.) directly to `uip rpa uia interact click`/`type`/`select`. Running `uip rpa uia snapshot inspect` just to re-mint refs for an unchanged UI is wasted work — the refs you have are still live.
+**Reuse refs from the current `uia-configure-target` capture — do not re-inspect.** The `uip rpa uia interact` CLI resolves element refs against the most recent snapshot in memory regardless of which CLI wrote it (the two write to different folders, but the snapshot is shared). Pass the same e-refs (`e28`, `e35`, etc.) directly to the interact subcommands. Re-running the UIA snapshot CLI just to re-mint refs for an unchanged UI is wasted work — the refs you have are still live.
 
-Re-inspect (or re-run `uip rpa uia snapshot capture`) only when the UI has actually advanced since the last capture; refs from a pre-advance snapshot will not resolve against the new state. Full flag reference: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`.
+Re-inspect (or re-capture via the UIA snapshot CLI) only when the UI has actually advanced since the last capture; refs from a pre-advance snapshot will not resolve against the new state. Subcommands and flags: `{PROJECT_DIR}/.local/docs/packages/UiPath.UIAutomation.Activities/references/cli-reference.md`.
 
 ### Capture Loop
 

package/skills/uipath-rpa/references/uia-prerequisites.md

@@ -36,7 +36,7 @@ uip rpa packages versions --package-id UiPath.UIAutomation.Activities --include-
 Install / upgrade (mutating — only after consent per the table above; substitute `<MIN_VERSION>` with the value declared at the top of this file):
 
 ```bash
-uip rpa packages install --packages '[{"id": "UiPath.UIAutomation.Activities", "version": "<MIN_VERSION>"}]' --project-dir "$PROJECT_DIR" --output json
+uip rpa packages install --packages 'id=UiPath.UIAutomation.Activities,version=<MIN_VERSION>' --project-dir "$PROJECT_DIR" --output json
 ```
 
 `packages install` accepts the beta version directly via the `version` field — no separate prerelease flag is needed once the version string is specified explicitly.

package/skills/uipath-rpa/references/validation-guide.md

@@ -55,7 +55,7 @@ PHASE 2 — build-clean (per-project, once per edit session):
 
 **Target the specific file:** `validate --file-path` validates only the file you changed (faster than whole-project). `build` is project-scoped (no `--file-path`); when it errors, the output names the offending file — re-run `validate --file-path` on it as part of Phase 2's fix loop.
 
-**5-attempt cap per loop** — 5 attempts for each file's Phase 1 `validate` loop; a separate 5 attempts for the Phase 2 `build` loop. After a loop exhausts its budget, present the remaining errors to the user. They may require domain knowledge or environment-specific fixes.
+**5-attempt cap per loop** — 5 attempts for each file's Phase 1 `validate` loop; a separate 5 attempts for the Phase 2 `build` loop. After a loop exhausts its budget, present the remaining errors to the user. They may require domain knowledge or environment-specific fixes. Each loop's counter resets when you start a new loop (e.g., new file, new user prompt, or resuming after user input).
 
 ### Rules
 
@@ -97,8 +97,8 @@ After reaching 0 validation errors AND a clean project-level build (Phase 2), ru
 ```bash
 # Run with default arguments (post-build, skip the redundant rebuild):
 uip rpa run --file-path "<FILE>" --skip-build --output json
-# Run with input arguments:
-uip rpa run --file-path "<FILE>" --skip-build --input-arguments '{"key": "value"}' --output json
+# Run with input arguments (repeat --input-arguments per key; = string, := raw JSON):
+uip rpa run --file-path "<FILE>" --skip-build --input-arguments key=value --output json
 # Run with verbose logging for debugging:
 uip rpa run --file-path "<FILE>" --skip-build --log-level Verbose --output json
 ```
@@ -137,7 +137,7 @@ C) <user-driven approach>
 ```
 Read: file_path="{projectRoot}/project.json"     -> check current dependencies
 
-Bash: uip rpa packages install --packages '[{"id": "UiPath.Excel.Activities"}]'```
+Bash: uip rpa packages install --packages id=UiPath.Excel.Activities```
 
 Omit `version` to automatically resolve the latest compatible version (preferred — gets newest docs and features). Only pin a specific version when you have a reason to (e.g., known compatibility constraint).
 

package/skills/uipath-rpa/references/xaml/canvas-layout-guide.md

@@ -391,7 +391,7 @@ States defined inline inside `Transition.To` need `<x:Reference>` registration a
 
 ## 5. Long Running Workflow (ProcessDiagram) Layout
 
-ProcessDiagrams use a **BPMN-style horizontal left-to-right** flow, distinct from Flowchart's vertical top-to-bottom.
+ProcessDiagrams use a **BPMN-style horizontal left-to-right** flow, distinct from Flowchart's vertical top-to-bottom. Package dependency, full node vocabulary, gateway patterns, suspend/resume: [long-running-workflow-guide.md](long-running-workflow-guide.md) — this section covers layout and ViewState only.
 
 ### Key Differences from Flowchart
 
@@ -411,6 +411,9 @@ ProcessDiagrams use a **BPMN-style horizontal left-to-right** flow, distinct fro
 | `upa:EventNode` | 40x40 | Circle | Start event (with `StartBehavior`) |
 | `upa:TaskNode` | 120x80 | Rectangle | Activity container (wraps Sequence) |
 | `upa:DecisionNode` | 60x60 | Diamond | True/False branching |
+| `upa:SwitchNode` | 60x60 | Diamond | Multi-way routing (`x:TypeArguments`) |
+| `upa:SplitNode` | 60x60 | Diamond | Parallel branch fan-out |
+| `upa:MergeNode` | 60x60 | Diamond | Parallel branch convergence |
 | `upa:EndNode` | 40x40 | Circle | End event (with `EndBehavior`) |
 | `upa:BoundaryNode` | 40x40 | Circle | Error handler attached to TaskNode |
 

package/skills/uipath-rpa/references/xaml/common-pitfalls.md

@@ -134,7 +134,7 @@ When `Text` contains literal `[k(...)]`, `[d(...)]`, or `[u(...)]` special-key t
 ```
 
 Alternatives:
-- Build the bracket characters with `Chr(91)` / `Chr(93)` so the string carries no literal `[` / `]`: `Text="["13700132" & Chr(91) & "k(enter)" & Chr(93)]"`.
+- Build the bracket characters with `ChrW(91)` / `ChrW(93)` so the string carries no literal `[` / `]`: `Text="["13700132" & ChrW(91) & "k(enter)" & ChrW(93)]"`.
 - Split the input: one `NTypeInto` for the digits, one `NKeyboardShortcuts` (or a second `NTypeInto`) for `[k(enter)]`.
 
 ## ActivityAction/ActivityFunc Initialization
@@ -344,15 +344,23 @@ Or omit `Default` entirely if the variable is assigned before its first read.
 
 The `Language` property on `InvokeCode` uses the `UiPath.Core.Activities.NetLanguage` enum, which has **only two valid values**: `VBNet` and `CSharp`.
 
-**Critical:** The project-level `expressionLanguage` in `project.json` uses `"VisualBasic"`, but InvokeCode's `Language` attribute requires `"VBNet"` instead. Do NOT use `"VisualBasic"` — it is not a valid `NetLanguage` value. `"CSharp"` is the same in both.
+**Critical:** The project-level `expressionLanguage` in `project.json` uses `"VisualBasic"`, but InvokeCode's `Language` attribute requires `"VBNet"` instead. Do NOT use `"VisualBasic"` or `"VB"` — neither is a valid `NetLanguage` value. `"CSharp"` is the same in both.
 
-**What happens:** Using `Language="VisualBasic"` passes Studio validation but fails at runtime:
+**What happens:** `Language="VisualBasic"` (or `"VB"`) passes Studio validation but fails at runtime:
 ```
 Failed to create a 'Language' from the text 'VisualBasic'.
 System.FormatException: VisualBasic is not a valid value for NetLanguage.
 ```
 
-**Prevention:** Omit the `Language` attribute entirely — InvokeCode infers it from the project's expression language. If you must set it explicitly, use `"VBNet"` (not `"VisualBasic"`) or `"CSharp"`. See `InvokeCode.md` in `../activity-docs/UiPath.System.Activities/` for full details.
+**Prevention:** Omit the `Language` attribute entirely — InvokeCode infers it from the project's expression language. If you must set it explicitly, use `"VBNet"` or `"CSharp"`.
+
+## `Chr()` / `Asc()` Break at Runtime in Modern Projects — Use `ChrW()` / `AscW()`
+
+`Chr(n)` / `Asc(c)` go through ANSI code page 1252, which .NET 6+ does not register. For `n ≥ 128` they throw `System.NotSupportedException: No data is available for encoding 1252` at runtime — after passing both `validate` and `build`. Use `ChrW(n)` / `AscW(c)` (Unicode, no code page) instead, or the BCL `Convert.ToChar(n)` / `CInt(c)`.
+
+`Chr`/`ChrW`/`Asc`/`AscW` live in `Microsoft.VisualBasic`, which is not auto-imported — `BC30451: 'ChrW' is not declared` means you must add `Microsoft.VisualBasic` to both `NamespacesForImplementation` and `ReferencesForImplementation`. The `Convert.*` BCL forms avoid this.
+
+`ContinueOnError=True` silently swallows the runtime exception (workflow looks successful, output is wrong/empty) — set it to `False` while debugging.
 
 ## HTTP Request Activity Complexity
 
@@ -422,7 +430,7 @@ Also remove the `xmlns:uiascb` namespace declaration from the root `<Activity>`
 `FieldObject Name` values are connector-specific and schema-driven. Never guess. Always read:
 
 ```bash
-uip is resources describe <connector-key> <operation-name> --operation Create --output json
+uip is resources describe <connector-key> <object-name> --operation Create --output json
 cat ~/.uipath/cache/integrationservice/<connector-key>/_static/<operation>.Create.json
 ```
 
@@ -463,6 +471,10 @@ Activity tag names rarely match Studio display names. Guessing the tag from the
 | Delete File | `ui:DeleteFile` | `ui:DeleteFileX` |
 | Wait | `ui:Wait` | `Delay` (MWF primitive — no prefix) |
 
+### `InvokeProcess` vs `StartProcess`
+
+To launch a local executable (`.exe`/`.cmd`/`.bat`), use `ui:StartProcess` (property `FileName` + `Arguments`). `ui:InvokeProcess` runs an Orchestrator process/package (property `ProcessName`) and has **no `FileName`** — reaching for one means you picked the wrong activity. Don't work around it with `Shell()`, `Process.Start`, or `InvokeCode`; for PowerShell use `InvokePowerShell<T>`.
+
 ### Tag Verification Gate
 
 Before writing any `<prefix:Tag>` not already in the file:
@@ -902,7 +914,7 @@ All nodes in a Flowchart/ProcessDiagram must be registered as children of the co
 </Flowchart>
 ```
 
-The same registration rules apply to `<upa:ProcessDiagram>` and its node types (`EventNode`, `TaskNode`, `DecisionNode`, `EndNode`, `BoundaryNode`).
+The same registration rules apply to `<upa:ProcessDiagram>` and its node types (`EventNode`, `TaskNode`, `DecisionNode`, `SwitchNode<T>`, `SplitNode`, `MergeNode`, `SubProcessNode`, `EndNode`, `BoundaryNode`).
 
 ### Other Gotchas