@uipath/skills 1.199.0 → 1.200.0

package/skills/uipath-rpa/references/legacy/environment-setup.md

@@ -1,78 +0,0 @@
-# Phase 0: Environment Readiness
-
-**Goal:** Establish the project root and verify the project is a legacy framework project before any other operations.
-
-**Key difference from modern (`uip rpa`):** The `uip rpa-legacy` CLI is standalone — it does **not** require Studio Desktop to be running. It resolves dependencies from NuGet directly and uses UiRobot for execution.
-
----
-
-## Step 0.1: Establish Project Root
-
-All `uip rpa-legacy` commands require a `<project-path>` argument pointing to the folder containing `project.json` (or the `project.json` file itself).
-
-```bash
-# Check if project.json exists in the CWD
-ls {cwd}/project.json
-```
-
-If the CWD is not the project root:
-- Locate the project root by finding `project.json`: `Glob: pattern="**/project.json"`
-- Ask the user where their project is located if multiple `project.json` files are found
-
-Store the project root path and use it consistently as `{projectRoot}` throughout all subsequent operations.
-
----
-
-## Step 0.2: Verify Legacy Project
-
-Read `project.json` and confirm this is a legacy framework project:
-
-```
-Read: file_path="{projectRoot}/project.json"
-```
-
-**Check these fields:**
-
-| Field | Legacy Value | Notes |
-|-------|-------------|-------|
-| `targetFramework` | `"Legacy"` | May be absent in very old projects (pre-2021), which implies Legacy |
-| `expressionLanguage` | `"VisualBasic"` (most common) or `"CSharp"` | Determines expression syntax in XAML |
-| `studioVersion` | Typically `< 23.x` | Older Studio versions |
-| `dependencies` | Classic package versions (no modern package IDs) | Very old projects (pre-2021) may have lower versions like ≤ 22.x |
-
-**If `targetFramework` is `"Windows"` or `"Portable"`**, this is a modern project — use the `uipath-rpa` skill instead.
-
-**If `targetFramework` is absent**, check the `studioVersion` and `dependencies` fields. Old projects without explicit `targetFramework` are Legacy by default.
-
----
-
-## Step 0.3: Authentication (If Needed)
-
-Some operations (cloud-based NuGet feeds, Orchestrator assets) may require authentication:
-
-```bash
-uip login
-```
-
-This opens a browser-based login flow. Authentication is typically needed only for:
-- Projects that use private NuGet feeds requiring authentication
-- `build` commands that push packages to Orchestrator
-- Accessing Orchestrator resources (assets, queues) during `debug` execution
-
-For most local development tasks (validate, edit, find-activities), authentication is **not required**.
-
----
-
-## Step 0.4: Package Restore
-
-After creating or modifying `project.json` dependencies, packages must be restored before `find-activities` or `type-definition` will work.
-
-**Trigger restore** by running validate on the project directory:
-
-```bash
-uip rpa-legacy validate "{projectRoot}" --output json
-```
-
-This resolves NuGet packages from configured feeds. After this completes, `find-activities` and `type-definition` will have access to the package assemblies.
-
-**If `find-activities` returns "No assemblies resolved from package dependencies"**, run validate first to trigger restore.

package/skills/uipath-rpa/references/legacy/project-structure.md

@@ -1,206 +0,0 @@
-# Legacy Project Structure
-
-Understanding the layout and configuration of a legacy UiPath RPA project.
-
----
-
-## Directory Layout
-
-```
-{projectRoot}/
-├── project.json              # Project metadata and dependencies
-├── Main.xaml                 # Entry point workflow
-├── *.xaml                    # Additional workflows (flat or in folders)
-├── Workflows/                # (Optional) Sub-folder for organized workflows
-├── Data/                     # (Optional) Input/output data files
-├── .screenshots/             # (Optional) Studio screenshot captures
-├── .settings/                # (Optional) Studio settings profiles
-└── .tmh/                     # (Optional) Test Manager data
-```
-
-**Notable absences compared to modern projects:**
-- No `.local/docs/packages/` — no auto-generated activity documentation
-- No `.codedworkflows/` — no coded automation support
-- No `.objects/` — no Object Repository
-- No `.project/JitCustomTypesSchema.json` — no JIT custom types
-
----
-
-## Creating a project.json from Scratch
-
-### Minimal Template
-
-Start with this — only `UiPath.System.Activities` is required. Add other packages as needed.
-
-```json
-{
-  "name": "MyProject",
-  "description": "",
-  "main": "Main.xaml",
-  "dependencies": {
-    "UiPath.System.Activities": "[24.10.8]"
-  },
-  "schemaVersion": "4.0",
-  "studioVersion": "25.10.0.0",
-  "projectVersion": "1.0.0",
-  "expressionLanguage": "VisualBasic",
-  "targetFramework": "Legacy",
-  "runtimeOptions": {
-    "autoDispose": false,
-    "isPausable": true,
-    "isAttended": false,
-    "requiresUserInteraction": true,
-    "supportsPersistence": false,
-    "workflowSerialization": "DataContract",
-    "excludedLoggedData": ["Private:*", "*password*"],
-    "executionType": "Workflow"
-  },
-  "designOptions": {
-    "projectProfile": "Developement",
-    "outputType": "Process"
-  },
-  "entryPoints": [
-    {
-      "filePath": "Main.xaml",
-      "uniqueId": "00000000-0000-0000-0000-000000000000",
-      "input": [],
-      "output": []
-    }
-  ]
-}
-```
-
-### Package Selection Guide
-
-**Add packages based on what the workflow needs.** Only `UiPath.System.Activities` is required — everything else is optional.
-
-| Need | Package | Latest Legacy Version |
-|------|---------|----------------------|
-| **Core (always include)** | `UiPath.System.Activities` | **24.10.8** |
-| UI automation (click, type, selectors) | `UiPath.UIAutomation.Activities` | **25.10.28** |
-| Excel (read/write, macros, CSV) | `UiPath.Excel.Activities` | **2.24.4** |
-| Email (SMTP, IMAP, POP3, Outlook) | `UiPath.Mail.Activities` | **1.24.18** |
-| HTTP/REST/SOAP/JSON/XML | `UiPath.WebAPI.Activities` | **1.21.1** |
-| Testing and assertions | `UiPath.Testing.Activities` | **25.10.1** |
-| PDF (read text, OCR, merge, split) | `UiPath.PDF.Activities` | **3.25.2** |
-| Office 365 (Graph API) | `UiPath.MicrosoftOffice365.Activities` | **2.9.13** |
-| Word documents | `UiPath.Word.Activities` | **1.20.3** |
-| PowerPoint presentations | `UiPath.Presentations.Activities` | **1.14.2** |
-| Database (SQL queries) | `UiPath.Database.Activities` | **1.10.1** |
-| Windows Credential Manager | `UiPath.Credentials.Activities` | **2.1.0** |
-| FTP/SFTP file transfer | `UiPath.FTP.Activities` | **2.4.0** |
-| Encryption/hashing (AES, HMAC, PGP) | `UiPath.Cryptography.Activities` | **1.6.1** |
-| Python script execution | `UiPath.Python.Activities` | **1.10.0** |
-| Java method invocation | `UiPath.Java.Activities` | **1.3.1** |
-| Document Understanding/OCR | `UiPath.IntelligentOCR.Activities` | **6.27.3** |
-| Forms (FormIo/HTML) | `UiPath.Form.Activities` | **2.0.8** |
-| Terminal emulation (3270/5250/VT) | `UiPath.Terminal.Activities` | **2.9.0** |
-| Google Suite (Gmail, Drive, Sheets) | `UiPath.GSuite.Activities` | **2.8.28** |
-| NLP (sentiment, translation) | `UiPath.Cognitive.Activities` | **2.2.4** |
-| StudioX scenario templates | `UiPath.ComplexScenarios.Activities` | **1.5.1** |
-| OmniPage OCR engine | `UiPath.OmniPage.Activities` | **1.22.2** |
-| Persistence (long-running workflows) | `UiPath.Persistence.Activities` | **1.8.1** |
-| Mobile automation (iOS/Android) | `UiPath.MobileAutomation.Activities` | **25.10.0** |
-| SAP BAPI function calls | `UiPath.SAP.BAPI.Activities` | **3.0.4** |
-
-**Example:** A workflow that reads Excel, sends email, and calls a REST API needs:
-```json
-"dependencies": {
-  "UiPath.System.Activities": "[24.10.8]",
-  "UiPath.Excel.Activities": "[2.24.4]",
-  "UiPath.Mail.Activities": "[1.24.18]",
-  "UiPath.WebAPI.Activities": "[1.21.1]"
-}
-```
-
-### Packages Can Be Added Later
-
-You don't need all packages upfront. Add them to `dependencies` as you discover what the workflow needs.
-
-**Important:** `find-activities` only searches packages listed in `dependencies`. If you add a package to project.json, re-run `find-activities` to discover its activities.
-
-### Searching for Packages
-
-When the known packages above don't cover a need, search configured NuGet feeds:
-
-```bash
-uip rpa-legacy find-package --query "barcode" --limit 10 --output json
-```
-
-This searches all configured feeds (UiPath official + any custom feeds) by name and description. Add the discovered package to `dependencies`, then `find-activities` will index it.
-
-### Arbitrary .NET Packages
-
-Any NuGet package can be added to `dependencies` for custom .NET classes, methods, and types. Examples:
-- `CsvHelper` — advanced CSV parsing
-- `ClosedXML` — .xlsx manipulation without COM
-- `HtmlAgilityPack` — HTML parsing
-
-Use these via `InvokeCode` with the appropriate namespace imports.
-
-**Avoid adding packages already bundled with Studio** (e.g., `Newtonsoft.Json`) — version conflicts can cause runtime issues.
-
----
-
-## project.json Key Fields
-
-| Field | Description |
-|-------|-------------|
-| `name` | Project name (used as package ID when packaged) |
-| `main` | Entry point XAML file (relative path) |
-| `dependencies` | NuGet package dependencies with version constraints |
-| `expressionLanguage` | `"VisualBasic"` (most legacy) or `"CSharp"` |
-| `targetFramework` | `"Legacy"` for .NET Framework 4.6.1 projects |
-| `designOptions.outputType` | `"Process"` (standalone) or `"Library"` (reusable) |
-| `studioVersion` | Studio version that created the project |
-
-### Version Constraints
-
-| Syntax | Meaning |
-|--------|---------|
-| `[1.2.3]` | Exact version 1.2.3 |
-| `[1.2.3, )` | Minimum version 1.2.3 |
-| `[1.0, 2.0)` | Range: >= 1.0, < 2.0 |
-
----
-
-## Library Project Template
-
-To create a **Library** project (reusable workflows published as a NuGet package), set `outputType` to `"Library"`:
-
-```json
-{
-  "name": "Acme.Finance.InvoiceUtilities",
-  "description": "Reusable invoice processing workflows",
-  "dependencies": {
-    "UiPath.System.Activities": "[24.10.8]"
-  },
-  "schemaVersion": "4.0",
-  "studioVersion": "25.10.0.0",
-  "projectVersion": "1.0.0",
-  "expressionLanguage": "VisualBasic",
-  "targetFramework": "Legacy",
-  "runtimeOptions": {
-    "autoDispose": false,
-    "isPausable": true,
-    "isAttended": false,
-    "requiresUserInteraction": false,
-    "supportsPersistence": false,
-    "workflowSerialization": "DataContract",
-    "excludedLoggedData": ["Private:*", "*password*"],
-    "executionType": "Workflow"
-  },
-  "designOptions": {
-    "projectProfile": "Developement",
-    "outputType": "Library"
-  }
-}
-```
-
-**Key differences from Process projects:**
-- **No `main` field** — libraries have no entry point
-- **No `entryPoints` array** — all workflows are callable individually
-- **`outputType: "Library"`** — published as activity package, not deployed as process
-- Workflows marked **Public** become activities when consumed; **Private** workflows are internal helpers
-
-For full library design guidance (naming, versioning, patterns), see [project-organization-guide.md](./project-organization-guide.md).

package/skills/uipath-rpa/references/legacy/test-data-guide.md

@@ -1,142 +0,0 @@
-# Test Data Creation Guide
-
-How to create test data files and UiPath types for legacy workflow testing.
-
----
-
-## Excel Test Data (COM-Compliant)
-
-### Using ExcelApplicationScope (Interop — .xls/.xlsx)
-
-Create a DataTable in code, then write it via Excel Interop:
-
-```xml
-<!-- Step 1: Build DataTable with InvokeCode -->
-<ui:InvokeCode Code="
-Dim dt As New DataTable()
-dt.Columns.Add(&quot;Name&quot;, GetType(String))
-dt.Columns.Add(&quot;Amount&quot;, GetType(Double))
-dt.Columns.Add(&quot;Date&quot;, GetType(String))
-dt.Columns.Add(&quot;Status&quot;, GetType(String))
-dt.Rows.Add(&quot;Invoice-001&quot;, 1500.50, &quot;2024-01-15&quot;, &quot;Active&quot;)
-dt.Rows.Add(&quot;Invoice-002&quot;, 2300.00, &quot;2024-02-20&quot;, &quot;Pending&quot;)
-dt.Rows.Add(&quot;Invoice-003&quot;, 890.25, &quot;2024-03-10&quot;, &quot;Closed&quot;)
-dt.Rows.Add(&quot;Invoice-004&quot;, 0, &quot;&quot;, &quot;Active&quot;)
-dt.Rows.Add(&quot;Invoice-005&quot;, -100.00, &quot;2024-12-31&quot;, &quot;Error&quot;)
-testData = dt" Language="VBNet">
-  <ui:InvokeCode.Arguments>
-    <scg:Dictionary x:TypeArguments="x:String, Argument">
-      <OutArgument x:TypeArguments="sd:DataTable" x:Key="testData">[dtTestData]</OutArgument>
-    </scg:Dictionary>
-  </ui:InvokeCode.Arguments>
-</ui:InvokeCode>
-
-<!-- Step 2: Write to Excel via ExcelApplicationScope -->
-<!-- Use ExcelApplicationScope + ExcelWriteRange (Interop) for .xls/.xlsx -->
-```
-
-### Test data design principles
-- Include edge cases: empty strings, zero values, negative numbers, special characters
-- Include null/DBNull values to test null handling
-- Mix data types per column to test type coercion
-- Include dates in multiple formats to test parsing
-- Include at least 5-10 rows for meaningful iteration testing
-
-### Using WriteCsvFile (Portable — no Excel needed)
-
-```xml
-<!-- Write CSV then optionally convert to Excel -->
-<ui:WriteCsvFile FilePath="[Path.Combine(Environment.CurrentDirectory, &quot;Data&quot;, &quot;test.csv&quot;)]"
-  DataTable="[dtTestData]" />
-```
-
----
-
-## Top 10 File Types
-
-| File Type | How to Create | Key Activity | Notes |
-|-----------|--------------|-------------|-------|
-| **Excel (.xls/.xlsx)** | `ExcelApplicationScope` + `ExcelWriteRange` | COM Interop | Use `.xls` for max legacy compat; `.xlsx` for modern |
-| **CSV (.csv)** | `WriteCsvFile` or `Write Text File` | Portable | Set `Delimitator` explicitly; specify `"UTF-8"` encoding |
-| **Text (.txt)** | `Write Text File` activity | System.IO | Use `Encoding="UTF-8"` for portability |
-| **JSON (.json)** | `Serialize JSON` + `Write Text File` | WebAPI package | Build JObject/JArray in InvokeCode, serialize, write |
-| **XML (.xml)** | Build XDocument in InvokeCode + `Write Text File` | System.Xml.Linq | Or use `Serialize XML` if available |
-| **PDF (.pdf)** | Export from Excel/Word scope, or HTML string + wkhtmltopdf | Requires source app | No native PDF creation activity in legacy |
-| **Word (.docx)** | `WordApplicationScope` + `Word Write Text` | COM Interop | Requires Word installed |
-| **HTML (.html)** | `Write Text File` with HTML string content | String building | Build HTML in InvokeCode or Assign |
-| **Email (.eml/.msg)** | `Save Mail Message` from mail activities | Mail package | Create MailMessage object first |
-| **Config (.xlsx)** | REFramework pattern: Config.xlsx with Settings/Constants/Assets sheets | Excel Interop | See `_REFRAMEWORK.md` for sheet structure |
-
-### Creating JSON test data
-
-```vb
-' InvokeCode — build JSON string
-Dim json As String = "{" & vbCrLf &
-  "  ""name"": ""Test User""," & vbCrLf &
-  "  ""amount"": 1500.50," & vbCrLf &
-  "  ""items"": [""A"", ""B"", ""C""]" & vbCrLf &
-  "}"
-output = json
-```
-
-### Creating XML test data
-
-```vb
-' InvokeCode — build XML string
-Dim xml As String = "<?xml version=""1.0"" encoding=""UTF-8""?>" & vbCrLf &
-  "<Invoices>" & vbCrLf &
-  "  <Invoice Id=""001"" Amount=""1500.50"" />" & vbCrLf &
-  "  <Invoice Id=""002"" Amount=""2300.00"" />" & vbCrLf &
-  "</Invoices>"
-output = xml
-```
-
----
-
-## Top 10 UiPath Types
-
-| Type | How to Create | Common Test Values | VB.NET Expression |
-|------|--------------|-------------------|-------------------|
-| **DataTable** | `Build Data Table` activity or InvokeCode | Headers + 5-10 rows, mixed types, nulls | `New DataTable()` |
-| **String** | `Assign` / literal | `"test"`, `""`, `Nothing`, special chars `<>&"` | `"value"` |
-| **Int32** | `Assign` / `CInt()` | `0`, `-1`, `Integer.MaxValue`, `Integer.MinValue` | `CInt("42")` |
-| **Boolean** | `Assign` | `True`, `False` | `True` |
-| **DateTime** | `Assign` / `DateTime.Parse()` | Today, epoch, future, `DateTime.MinValue` | `DateTime.Now` |
-| **Dictionary(Of String, Object)** | InvokeCode or `Assign` | Config-style key-value pairs, nested objects | `New Dictionary(Of String, Object)` |
-| **String()** (array) | `Assign` / `Split()` | Empty `{}`, single item, many items | `New String() {"a","b","c"}` |
-| **SecureString** | `Get Credential` or InvokeCode | Test password strings | `New NetworkCredential("","pass").SecurePassword` |
-| **MailMessage** | `Get Outlook Mail Messages` or InvokeCode | Email with To/Subject/Body/Attachments | `New System.Net.Mail.MailMessage()` |
-| **QueueItem** | `Get Transaction Item` from Orchestrator | SpecificContent dictionary, Priority, Deadline | Requires Orchestrator queue |
-
-### Creating a test Dictionary (Config-style)
-
-```vb
-' InvokeCode
-Dim config As New Dictionary(Of String, Object)
-config("MaxRetryNumber") = 3
-config("logF_BusinessProcessName") = "TestProcess"
-config("OrchestratorQueueName") = "TestQueue"
-config("ExcelFilePath") = "Data\Input\test.xlsx"
-output = config
-```
-
-### Creating a test DataTable with edge cases
-
-```vb
-' InvokeCode
-Dim dt As New DataTable()
-dt.Columns.Add("Name", GetType(String))
-dt.Columns.Add("Amount", GetType(Double))
-dt.Columns.Add("IsActive", GetType(Boolean))
-
-' Normal rows
-dt.Rows.Add("Alice", 100.50, True)
-dt.Rows.Add("Bob", 0, False)
-
-' Edge cases
-dt.Rows.Add("", -999.99, True)           ' Empty name
-dt.Rows.Add(DBNull.Value, DBNull.Value, DBNull.Value)  ' All nulls
-dt.Rows.Add("Special <>&""chars", 1E+15, True)  ' Special chars, large number
-
-testData = dt
-```

package/skills/uipath-rpa/references/legacy/validation-and-fixing.md

@@ -1,154 +0,0 @@
-# Phase 3: Validate & Fix Loop
-
-Detailed procedures for validating legacy workflows, analyzing project quality, and fixing errors iteratively.
-
----
-
-## Step 3.1: Validate
-
-Use `uip rpa-legacy validate` to check a XAML file or entire project for compilation errors. Accepts XAML file path, project.json path, or project folder.
-
-```bash
-# Validate a specific file (use during iteration — per activity)
-uip rpa-legacy validate "{projectRoot}/Main.xaml" --output json
-
-# Validate entire project (use as FINAL step before completing)
-uip rpa-legacy validate "{projectRoot}" --output json
-```
-
-**Workflow:**
-- **During iteration:** validate per-file after each activity edit (faster, focused feedback)
-- **Before completing:** validate the entire project to catch cross-file issues
-- Run after **every** XAML edit — do not batch multiple edits without validation
-
----
-
-## Step 3.2: Categorize and Fix Errors
-
-**Fix order:** Package → Structure → Type → Activity Properties → Logic. Always fix in this order — higher-category fixes often resolve lower-category errors automatically.
-
-### 1. Package Errors — Missing namespace, unknown activity type, unresolved assembly
-
-**The legacy CLI does not have `install-or-update-packages`.** When a missing package is detected:
-1. Identify the missing package from the error message
-2. Check the [activity reference docs](./activity-docs/_INDEX.md) to confirm the correct package name
-3. **Ask the user** to install the package manually in Studio:
-   - Studio → Manage Packages → search for the package → Install
-   - Or edit `project.json` dependencies directly (advanced — must match NuGet version constraints)
-4. Re-validate after the package is installed
-
-### 2. Structural Errors — Invalid XML, malformed elements, missing closing tags
-
-- `Read` the XAML around the error location → `Edit` to fix XML structure
-- Cross-check against [xaml-basics-and-rules.md](./xaml-basics-and-rules.md) for correct element nesting and namespace declarations
-- Common issues: unclosed elements, mismatched namespace prefixes, duplicate `x:Name` attributes
-
-### 3. Type Errors — Wrong property type, invalid cast, type mismatch
-
-- **Always use `type-definition`** to discover exact enum values and type members — do not guess
-  ```bash
-  uip rpa-legacy type-definition "{projectRoot}" --type "EnumTypeName" --output json
-  ```
-- Example: InvokeCode `Language` property accepts `VBNet` (not `VisualBasic`, not `VB`)
-- Common fixes: wrong `x:TypeArguments`, missing namespace prefix (`sd:DataTable` vs `x:String`), VB vs C# expression syntax mismatch
-- Consult activity reference docs for behavioral context, but rely on `type-definition` for exact values
-
-### 4. Activity Properties Errors — Unknown properties, misconfigured settings
-
-- **Always use `find-activities --include-type-definitions`** to discover exact property names
-  ```bash
-  uip rpa-legacy find-activities "{projectRoot}" --query "activity name" --include-type-definitions --output json
-  ```
-- Activity reference docs describe behavior but may not list exact CLR property names — the CLI output is authoritative
-- Common issues: properties that exist in modern but not legacy versions, misspelled property names, wrong enum values
-
-### 5. Logic Errors — Wrong behavior, incorrect expressions, business logic issues
-
-- `Read` the XAML to understand current flow → `Edit` to correct
-- Verify expression syntax matches project language (VB.NET vs C#)
-- Consult [activity-docs/_PATTERNS.md](./activity-docs/_PATTERNS.md) for VB.NET expression patterns
-- Use `uip rpa-legacy debug` for runtime validation if static checks pass
-
----
-
-## Step 3.3: Iteration Loop
-
-```
-REPEAT:
-  1. Run: uip rpa-legacy validate "{projectRoot}/{file}.xaml" --output json
-  2. IF 0 errors → EXIT loop (success)
-  3. IF errors exist:
-     a. Categorize by type (Package/Structure/Type/Properties/Logic)
-     b. Fix highest-category errors first
-     c. Apply fix using Read + Edit tools
-  4. IF error cannot be auto-resolved:
-     a. Document the error for the user
-     b. Suggest manual fix steps
-     c. Continue fixing other errors
-UNTIL: 0 errors OR all remaining errors require user action
-```
-
-**When stuck on one error:** Consider deferring to the user if it's a configuration detail (missing package, credential setup, connection string). Inform the user clearly about what needs to be done.
-
----
-
-## Step 3.4: Package (Optional)
-
-If a deployable `.nupkg` artifact is needed, package the project after validation passes:
-
-```bash
-uip rpa-legacy pack "{projectRoot}" -o "{outputDir}" --output json
-```
-
-Not required for debugging — legacy RPA can be debugged directly without packaging.
-
----
-
-## Step 3.5: Smoke Test with Debug (Optional)
-
-**Always validate before debugging** — don't debug a file with compilation errors.
-
-```bash
-# Basic smoke test
-uip rpa-legacy debug "{projectRoot}/Main.xaml" -i '{"in_TestMode": true}' --timeout 60
-
-# Programmatic: capture result to file, suppress streaming logs
-uip rpa-legacy debug "{projectRoot}/Main.xaml" -i '{"in_TestMode": true}' --result-path /tmp/result.json --log-level error
-```
-
-**Reading results:**
-- Exit code 0 → success: check `Data.Output` for out-argument values
-- Exit code 1 → failure: check `Data.Error` for diagnostics:
-  - `Error.ActivityDisplayName` + `Error.XamlFile` → locate the problem
-  - `Error.ExceptionType` + `Error.Message` → understand it
-  - `Error.StackTrace` → full call chain
-  - `Data.ErrorLog` → all error-level log entries for context
-
-**Fix-and-retry:** edit XAML → validate → debug again.
-
-**Caution:** `debug` performs real actions (clicks, emails, file writes). Only use when safe.
-
-For test data creation (Excel files, CSV, JSON, common UiPath types), see **[test-data-guide.md](./test-data-guide.md)**.
-
----
-
-## Common Error Scenarios
-
-### Wrong enum value
-**Symptom:** "Cannot create unknown type" or "is not a member of" for an enum property.
-**Fix:** `uip rpa-legacy type-definition "{projectRoot}" --type "EnumTypeName" --output json`. Example: InvokeCode `Language` accepts `VBNet` and `CSharp` — not `VisualBasic` or `VB`.
-
-### Activity class name not found
-**Symptom:** Unknown activity type or missing namespace.
-**Fix:** `uip rpa-legacy find-activities "{projectRoot}" --query "..." --output json`, add xmlns + assembly ref.
-
-### Multiple errors after batch editing
-**Symptom:** Many errors after writing multiple activities at once.
-**Fix:** Revert to last good state. Re-add one activity at a time, validating after each.
-
-### Activity docs don't match XAML property names
-**Symptom:** Properties from reference docs don't work in XAML.
-**Fix:** `find-activities --include-type-definitions` for exact CLR property names from compiled assemblies.
-
-### Stuck on unfamiliar problem
-**Escalation:** `uip docsai ask "..."` → `WebSearch` (UiPath Forum, Stack Overflow, GitHub) → ask user.