@uipath/skills 1.199.0 → 1.200.0

package/skills/uipath-maestro-case/references/plugins/variables/io-binding/planning.md

@@ -2,7 +2,7 @@
 
 Trust the SDD. Emit inputs/outputs exactly as declared. Every SDD Outputs row carries `->` or `=`; preserve that operator and both operands through `tasks.md`. Bare `tasks.md` outputs come only from resolved-schema discovery, never from an SDD row. There is no `caseplan.json` yet — all validation happens during [implementation](impl-json.md).
 
-## SDD table to `tasks.md` projection (mandatory)
+## SDD Outputs table to `tasks.md` projection (mandatory)
 
 The SDD Outputs table has separate `Field`, `Type`, and `Binding / Value` columns, while `tasks.md` uses one canonical list item per row. Project each SDD row exactly once:
 
@@ -27,6 +27,24 @@ Treat `—` and blank `Field` cells on `=` rows as presentation-only placeholder
 
 Before the Phase 1 approval gate, reject any SDD Outputs row without `->` or `=`, and reject any `tasks.md` output item whose first token is `—`, `->`, or `=`. Every SDD-projected item must match `<field-path> -> <case-variable>` or `<case-variable> = <expression>`; `<top-level-field>` is reserved for schema-discovered items.
 
+## SDD Inputs table to `tasks.md` projection (mandatory)
+
+The SDD Inputs table has separate `Field`, `Type`, and `Binding` columns, exactly like the Outputs table above — but the `tasks.md` input item drops the `Type` column entirely. Project each SDD Inputs row to `<Field> <- <Binding>` or `<Field> = <Binding>` (operator comes from the Binding cell itself, per [Input/Output Notation](#inputoutput-notation) below); never carry the `Type` column into `tasks.md`:
+
+| SDD `Field` | SDD `Type` | SDD `Binding` | Canonical `tasks.md` item |
+|---|---|---|---|
+| `APIInput1` | `string` | `"literal-seed"` | `APIInput1 = "literal-seed"` |
+| `APIInput1` | `string` | `=vars.caseInput` | `APIInput1 = =vars.caseInput` |
+| `APIInput1` | `string` | `<- "Binding Matrix"."Echo literal".APIOutput1` | `APIInput1 <- "Binding Matrix"."Echo literal".APIOutput1` |
+
+```markdown
+<!-- INVALID: leaked the SDD Type column as a literal pipe segment -->
+- APIInput1 | string | <- "Binding Matrix"."Echo literal".APIOutput1
+
+<!-- VALID -->
+- APIInput1 <- "Binding Matrix"."Echo literal".APIOutput1
+```
+
 ## Discovering Input/Output Names
 
 1. **SDD per-task tables** — primary source. Each task lists input/output field names, types, and variable bindings.

package/skills/uipath-maestro-case/references/registry-discovery.md

@@ -195,13 +195,13 @@ Use the component type from the sdd.md to identify the **primary** cache file, t
 | CASE_MANAGEMENT | `caseManagement-index.json` |
 | CONNECTOR_ACTIVITY | `typecache-activities-index.json` |
 | CONNECTOR_TRIGGER | `typecache-triggers-index.json` |
-| PROCESS | `process-index.json` |
+| PROCESS | `processOrchestration-index.json` |
 | EXTERNAL_AGENT | *(not in cache)* |
 | TIMER | *(not in cache)* |
 
 For types marked "not in cache" (`EXTERNAL_AGENT`, `TIMER`), skip the cache lookup — these have no registry representation. `TIMER` → emit the `wait-for-timer` plugin shape. **`EXTERNAL_AGENT` has no generation plugin here — never write `type: external-agent`; model as `api-workflow` / `execute-connector-activity` per Rule 16.**
 
-**Cross-type fallback:** The sdd.md component type label is not always accurate — the actual registry resource may be stored under a different type. For example, an "RPA" process may appear in `process-index.json`, or an "AGENTIC_PROCESS" might be in `process-index.json` instead of `processOrchestration-index.json`. If the primary cache file yields no match, search the other cache files using the task's type-specific portable name, preserving the existing fallback behavior. **Exception: do not cross-type-fallback an `action` or `case-management` lookup.** An Action App ID is valid only from `action-apps-index.json`, and a child-case `entityKey` is valid only from `caseManagement-index.json`; a same-named process is not a compatible substitute for either task type.
+**Cross-type fallback:** The sdd.md component type label is not always accurate — the actual registry resource may be stored under a different type. For example, an "RPA" process may appear in `process-index.json`, or an "AGENTIC_PROCESS" might be in `process-index.json` instead of `processOrchestration-index.json`. If the primary cache file yields no match, search the other cache files using the task's type-specific portable name, preserving the existing fallback behavior. For `process` tasks the fallback is a hard gate before any unresolved/placeholder outcome — see [`plugins/tasks/process/planning.md` § Registry Resolution](plugins/tasks/process/planning.md#registry-resolution). **Exception: do not cross-type-fallback an `action` or `case-management` lookup.** An Action App ID is valid only from `action-apps-index.json`, and a child-case `entityKey` is valid only from `caseManagement-index.json`; a same-named process is not a compatible substitute for either task type.
 
 ### 2. Search by Name and Folder Path
 
@@ -272,7 +272,7 @@ After finding a match, map the **cache file type** (not the sdd.md component typ
 | Cache file | Task `type` | Identifier field |
 |---|---|---|
 | `agent-index.json` | `agent` | `entityKey` |
-| `process-index.json` | `process` | `entityKey` |
+| `process-index.json` | `rpa` | `entityKey` |
 | `api-index.json` | `api-workflow` | `entityKey` |
 | `processOrchestration-index.json` | `process` | `entityKey` |
 | `caseManagement-index.json` | `case-management` | `entityKey` |