@uipath/skills 1.196.0 → 1.197.0

package/skills/uipath-maestro-bpmn/references/author/references/plugins/service-tasks/planning.md

@@ -1,31 +0,0 @@
-# Service Task Planning
-
-Use this reference when planning BPMN service tasks. For resource-specific wrappers, read [task-recipes/](../../task-recipes/) after choosing the BPMN element.
-
-## When to use
-
-- System work represented by `bpmn:serviceTask`.
-- UiPath extension-backed service shells.
-- Draft placeholders for connector, agent, RPA, API workflow, or create-and-wait queue calls.
-- Service work that needs retry, error mapping, input mapping, or output mapping.
-
-## Planning steps
-
-1. Confirm the BPMN element is actually a service task. Queue create, business rules, HITL, and call activity work use other BPMN task classes.
-2. Identify the service owner: model-authored shell, CLI-enriched connector, Orchestrator resource, or external dependency.
-3. Decide whether the task can be implemented now or must remain a draft placeholder.
-4. List required inputs, outputs, bindings, retry behavior, and boundary error paths.
-5. Declare variables before mapping task outputs.
-6. Plan resource bindings with placeholder-safe IDs only.
-7. Add diagram geometry and surrounding flows.
-
-## Model may draft
-
-- Standard `bpmn:serviceTask` wrappers.
-- Public-safe IDs, labels, mappings, retries, and boundary errors.
-- Documented non-Integration-Service `uipath:activity` shells.
-- Placeholders for CLI-owned service details.
-
-## Stop conditions
-
-Stop before upload/run when required service type metadata, resource binding, input schema, output schema, or executable context is missing.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/signals/impl.md

@@ -1,33 +0,0 @@
-# Signal Implementation
-
-This document defines the preserve-only boundary for BPMN signals.
-
-## Preserve-only implementation
-
-The model may preserve imported:
-
-- Root `bpmn:signal` definitions.
-- `bpmn:signalEventDefinition` references on start, intermediate, boundary, and end events.
-- Signal throw/catch sequence flows and event subprocesses.
-- Public-safe payload variable mappings.
-- Diagram shapes and edges.
-
-Do not generate new signal definitions, signal event definitions, signal
-throws, signal catches, or signal-based event subprocesses in new source.
-
-## CLI or operator-owned implementation
-
-The CLI or operator must resolve:
-
-- Any runtime subscription or cross-process signal binding outside standard BPMN XML.
-- Payload schemas that are generated by a runtime resource.
-- Tenant-specific channel, folder, or resource identifiers.
-- Correlation, idempotency, and fan-out expectations when multiple deployed instances can catch the signal.
-- Validation evidence that the deployed runtime supports the imported signal event shape.
-
-## Validation expectations
-
-- Imported signal event definitions still reference existing signal definitions.
-- Unrelated edits preserve imported signal XML and diagram geometry.
-- Any claim that an imported signal is executable has current runtime validation
-  evidence outside this model-authored XML.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/signals/planning.md

@@ -1,46 +0,0 @@
-# Signal Planning
-
-Signals are preserve-only for current Maestro BPMN authoring. Use this
-reference only when inspecting or preserving imported signal throw/catch
-behavior.
-
-## When to use
-
-- An imported or brownfield BPMN file already contains signal definitions or
-  signal event definitions.
-- The user asks why signal-based behavior is not regenerated.
-- You need to preserve imported signal XML while editing unrelated supported
-  process structure.
-
-## Planning steps
-
-1. Identify the existing signal definitions and event references.
-2. Preserve them unchanged unless the user explicitly asks to remove or replace
-   them.
-3. Route new behavior through supported message, timer, receive-task,
-   Integration Service, or gateway patterns instead of adding new signals.
-4. Report that signal regeneration is unsupported until current product and CLI
-   validation confirm it.
-
-## Executable boundary
-
-Do not generate new `bpmn:signal` definitions or
-`bpmn:signalEventDefinition` elements in new source.
-
-- Preserve-only: imported `bpmn:signal` definitions, signal event references,
-  local throw/catch topology, labels, variables, mappings, and diagram
-  geometry.
-- Unsupported for regeneration: runtime subscription registration,
-  cross-process correlation, payload schema versioning, tenant/folder/resource
-  identifiers, and any non-BPMN binding needed for deployed execution.
-
-## Model may draft
-
-- No new signal BPMN.
-- Only preservation of imported signal XML while applying unrelated supported
-  edits.
-
-## Stop conditions
-
-Stop before Operate when imported signal behavior is expected to execute and no
-current runtime validation evidence is available.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/start-end-events/impl.md

@@ -1,59 +0,0 @@
-# Start, End, and Event Implementation
-
-This document defines the implementation boundary for BPMN events.
-
-## Model-owned implementation
-
-The model may edit:
-
-- `bpmn:startEvent`, `bpmn:endEvent`, `bpmn:intermediateCatchEvent`, `bpmn:intermediateThrowEvent`, and `bpmn:boundaryEvent`.
-- Standard event definitions such as timer, message, error, and terminate end events where supported.
-- Event IDs, names, `attachedToRef`, `cancelActivity`, incoming/outgoing flows, and BPMN DI.
-- Root `uipath:entryPointId` values for root starts.
-- `uipath:mapping` entries for event input/output movement.
-- Documented non-Integration-Service `uipath:event` shells such as Maestro message events.
-
-Message event boundaries:
-
-- Use `Maestro.ReceiveMessageEvent` for model-owned message starts, intermediate catches, and boundary waits when the message name and payload contract are known.
-- Use `Maestro.SendMessageEvent` for model-owned message throws and message end events when the message name and payload contract are known.
-- Use `Intsvc.EventTrigger` and `Intsvc.WaitForEvent` only through CLI enrichment because connector event metadata, bindings, trigger properties, and schemas are registry-backed.
-
-Boundary event flow rules:
-
-- A boundary event has no incoming flow.
-- A boundary event lists each exception/timeout sequence flow as its own
-  `bpmn:outgoing` child.
-- The attached activity lists only its normal incoming and outgoing flows. Do
-  not add boundary-event exception flows as normal activity incoming or
-  outgoing flows.
-- The exception sequence flow uses `sourceRef` equal to the boundary event ID
-  and `targetRef` equal to the recovery or review target.
-- Error boundary events must reference a declared root `bpmn:error`.
-- Add BPMN DI for the boundary event shape and for each outgoing exception
-  sequence flow.
-
-## CLI-owned or externally resolved implementation
-
-The CLI or operator must resolve:
-
-- Integration Service trigger and wait metadata.
-- Trigger property bindings and generated schemas.
-- Real connection, folder, queue, or external-system identifiers.
-- Cloud-side subscription, schedule, or correlation resources.
-
-## Validation expectations
-
-- Root runnable starts have unique entry point IDs.
-- Entry point variables reference the owning start event.
-- Event subprocesses have exactly one valid start event.
-- Boundary events attach to an activity in the same scope.
-- Boundary events have outgoing sequence flow children for their exception
-  paths, and the attached activity does not list those exception flows as
-  normal incoming/outgoing activity flows.
-- Message and error references resolve.
-- Every visible event and event flow has diagram geometry.
-
-Excluded event definitions from
-[supported-elements.md](../../supported-elements.md#current-generation-exclusions)
-are preserve-only for imported files.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/start-end-events/planning.md

@@ -1,37 +0,0 @@
-# Start, End, and Event Planning
-
-Use this reference when planning BPMN start events, end events, intermediate events, and boundary events.
-
-## When to use
-
-- Manual, timer, message, or trigger-driven starts.
-- Normal, terminate, error, or message ends.
-- Intermediate catch or throw events in the process body.
-- Boundary events attached to activities for timeout, error, or message paths.
-
-## Planning steps
-
-1. Identify whether the event starts work, waits for work, throws a notification, handles an exception, or finishes the process.
-2. Choose the BPMN event type and event definition before adding UiPath metadata.
-3. Determine scope: root process, subprocess, event subprocess, or activity boundary.
-4. Decide entry point status for root start events and list required entry variables.
-5. Plan event outputs and mappings to process variables.
-6. Record any runtime resource that needs CLI enrichment, especially connector-backed triggers or waits.
-7. Plan outgoing sequence flows, boundary escape paths, and end-state outputs.
-
-## Model may draft
-
-- Standard BPMN event elements and event definitions.
-- `uipath:entryPointId` for runnable root start events.
-- Public-safe IDs, labels, mappings, and diagram geometry.
-- Message or error definitions with synthetic names.
-- Boundary attachment and interrupting versus non-interrupting intent.
-
-## Stop conditions
-
-Stop before Operate when an event depends on unresolved connector metadata, trigger properties, dynamic schema, real message correlation contract, or private identifiers.
-
-Do not generate event definitions listed in
-[supported-elements.md](../../supported-elements.md#current-generation-exclusions)
-for new source. Preserve imported instances and report them as unsupported for
-regeneration.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/waits-triggers/impl.md

@@ -1,40 +0,0 @@
-# Wait and Trigger Implementation
-
-This document defines the implementation boundary for waits and triggers.
-
-## Model-owned implementation
-
-The model may edit:
-
-- Timer, message, and boundary event definitions.
-- Receive-task or event-based-gateway structures.
-- Entry point metadata for runnable starts.
-- Public-safe correlation variable names and mappings.
-- Non-Integration-Service message event shells when documented.
-
-Do not duplicate message-event concepts:
-
-- Plain BPMN message events describe process semantics.
-- `Maestro.ReceiveMessageEvent` and `Maestro.SendMessageEvent` are model-owned UiPath message-event shells.
-- Connector-backed waits and triggers use `Intsvc.WaitForEvent` or `Intsvc.EventTrigger` and require CLI enrichment.
-
-## CLI-owned or operator-owned implementation
-
-The CLI or operator must provide:
-
-- Integration Service trigger/wait context and schemas.
-- Schedule resource details when they are cloud-owned.
-- Real correlation identifiers, subscriptions, and binding resources.
-- Generated package files for executable triggers.
-
-## Validation expectations
-
-- Start triggers are valid entry points.
-- Intermediate waits have a path to resume or time out.
-- Boundary timers attach to valid activities.
-- Event schemas and output mappings resolve.
-- Connector-backed waits are enriched before upload/run.
-
-Excluded event definitions from
-[supported-elements.md](../../supported-elements.md#current-generation-exclusions)
-are preserve-only for imported files.

package/skills/uipath-maestro-bpmn/references/author/references/plugins/waits-triggers/planning.md

@@ -1,34 +0,0 @@
-# Wait and Trigger Planning
-
-Use this reference when planning process starts or pauses that wait for time, messages, schedules, or external events.
-
-## When to use
-
-- Timer starts or timer intermediate events.
-- Message or connector-backed starts.
-- Intermediate waits for messages or external connector events.
-- Timeout branches and boundary timers.
-
-## Planning steps
-
-1. Identify whether the wait begins the process, pauses the current path, or interrupts an activity.
-2. Choose timer, message, receive task, event-based gateway, or connector trigger shape.
-3. Define correlation inputs and outputs in public-safe terms.
-4. Plan timeout and cancellation behavior.
-5. Mark Integration Service trigger or wait enrichment as CLI-owned.
-6. Confirm whether the process may resume with stale data and how outputs update variables.
-
-## Model may draft
-
-- Standard timer, message, and boundary event structure.
-- Receive/wait task wrappers for non-connector message waits.
-- `uipath:event` shells for documented non-Integration-Service events.
-- Entry point IDs and variable mappings.
-
-## Stop conditions
-
-Stop before Operate when schedule, trigger properties, correlation contract, connector metadata, or dynamic event schema is unresolved.
-
-Do not generate signal, conditional, escalation, compensation, cancel, link,
-multiple, or parallel-multiple event definitions for new Maestro BPMN source.
-Preserve imported instances only.

package/skills/uipath-maestro-bpmn/references/author/references/supported-elements.md

@@ -1,123 +0,0 @@
-# Supported Elements
-
-Use this supported coverage map before choosing a BPMN wrapper or UiPath extension type. Treat anything outside this map, or listed in [Current generation exclusions](#current-generation-exclusions), as preserve-only unless a newer product contract says otherwise.
-
-## Modeling rule
-
-Pick the BPMN element first, then pick the UiPath execution recipe.
-
-- RPA workflows, agents, API workflows, and most async external executions are `bpmn:serviceTask`.
-- Queue item creation is `bpmn:sendTask`; create-and-wait queue work is `bpmn:serviceTask`.
-- Business rules are `bpmn:businessRuleTask`.
-- HITL is `bpmn:userTask`.
-- Agentic process and case-management process calls are `bpmn:callActivity`.
-- Integration Service waits are `bpmn:receiveTask` or event wrappers, and their executable metadata is CLI-owned.
-- Script work is `bpmn:scriptTask`; it is not a generic service task.
-
-## Standard BPMN coverage
-
-The model may author these standard BPMN structures when the process intent is clear and every visible element has BPMN DI.
-
-| Family | Supported elements |
-| --- | --- |
-| Events | `bpmn:startEvent`, `bpmn:endEvent`, `bpmn:intermediateCatchEvent`, `bpmn:intermediateThrowEvent`, `bpmn:boundaryEvent` |
-| Event definitions | none, message, timer, error, and terminate end events where valid for that event kind |
-| Gateways | `bpmn:exclusiveGateway`, `bpmn:inclusiveGateway`, `bpmn:parallelGateway`, `bpmn:eventBasedGateway` |
-| Tasks | `bpmn:task`, `bpmn:serviceTask`, `bpmn:sendTask`, `bpmn:receiveTask`, `bpmn:userTask`, `bpmn:businessRuleTask`, `bpmn:scriptTask` |
-| Containers | `bpmn:subProcess`, event subprocess when the start event type is supported, `bpmn:callActivity` |
-| Flow | `bpmn:sequenceFlow` with source, target, optional condition, optional default references on gateways |
-| Definitions and visual context | `bpmn:message`, `bpmn:error`, item definitions, data objects, data stores, text annotations, groups, pools, and lanes when required by the model |
-
-Visual-only elements such as pools, lanes, data objects, data stores, text annotations, and groups can describe the model but do not execute. Do not use them as substitutes for executable variables, mappings, or task payloads.
-
-## Current generation exclusions
-
-Do not generate these BPMN structures in new Maestro BPMN source. If they appear
-in imported or brownfield files, preserve them and report that the skill cannot
-safely regenerate or normalize them unless a current product contract and local
-CLI validation prove support.
-
-Planned, future, preview, and TBD support statuses are treated as unsupported
-for generation until they are confirmed by current tooling.
-
-| Family | Excluded from new generation |
-| --- | --- |
-| Gateways | `bpmn:complexGateway` |
-| Tasks and containers | `bpmn:manualTask`, `bpmn:adHocSubProcess`, `bpmn:transaction` |
-| Event definitions | `bpmn:conditionalEventDefinition`, `bpmn:signalEventDefinition`, `bpmn:escalationEventDefinition`, `bpmn:compensateEventDefinition`, `bpmn:cancelEventDefinition`, `bpmn:linkEventDefinition`, multiple event definitions, and parallel multiple event definitions |
-| Markers | Standard loop markers and compensation markers. Use only documented multi-instance parallel or sequential metadata for new loops. |
-
-Terminate is supported only for end events. Do not generate terminate starts,
-boundary events, intermediate catches, or intermediate throws.
-
-## UiPath extension coverage
-
-Use lower-case XML tags in authored examples: `uipath:activity`, `uipath:event`, and `uipath:mapping`.
-For copyable canonical shells, including the required nested
-`uipath:type value="..."` element, see
-[../../shared/wrapper-shells.md](../../shared/wrapper-shells.md). Do not use legacy
-`<uipath:activity type="...">` shorthand in new XML.
-For resource-backed tasks, `uipath:activity` identifies the wrapper type and
-resource context; task payload inputs and outputs belong in sibling
-`uipath:mapping version="v1"` elements.
-
-| Extension type | BPMN wrapper | XML tag | Ownership |
-| --- | --- | --- | --- |
-| `BPMN.Variables` | `bpmn:task` | `uipath:mapping` | Model-owned |
-| `BPMN.ScriptTask` | `bpmn:scriptTask` | `uipath:mapping` plus `uipath:scriptVersion` | Model-owned; parser executes as `Scp.Script` |
-| `Actions.HITL` | `bpmn:userTask` | `uipath:activity` | Model may draft shell; resource/form binding resolved by CLI or operator |
-| `Orchestrator.StartJob` | `bpmn:serviceTask` | `uipath:activity` | Model may draft shell; resource binding and schemas resolved by CLI or operator |
-| `Orchestrator.StartAgentJob` | `bpmn:serviceTask` | `uipath:activity` | Model may draft shell; agent binding and schemas resolved by CLI or operator |
-| `A2A.AgentExecution` | `bpmn:serviceTask` | `uipath:activity` | Model may draft shell; agent metadata resolved by CLI or operator |
-| `Orchestrator.ExecuteApiWorkflowAsync` | `bpmn:serviceTask` | `uipath:activity` | Model may draft shell; API workflow binding and schemas resolved by CLI or operator |
-| `Orchestrator.CreateQueueItem` | `bpmn:sendTask` | `uipath:activity` | Model may draft shell; queue binding resolved by CLI or operator |
-| `Orchestrator.CreateAndWaitForQueueItem` | `bpmn:serviceTask` | `uipath:activity` | Model may draft shell; queue binding and callback behavior resolved by CLI or operator |
-| `Orchestrator.BusinessRules` | `bpmn:businessRuleTask` | `uipath:activity` | Model may draft shell; rule binding and schemas resolved by CLI or operator |
-| `Orchestrator.StartAgenticProcess` | `bpmn:callActivity` | `uipath:activity` | Model may draft shell; called process binding resolved by CLI or operator |
-| `Orchestrator.StartAgenticProcessAsync` | `bpmn:callActivity` | `uipath:activity` | Model may draft shell; called process binding resolved by CLI or operator |
-| `Orchestrator.StartCaseMgmtProcess` | `bpmn:callActivity` | `uipath:activity` | Preserve or draft only with a dedicated case-management contract |
-| `Orchestrator.StartCaseMgmtProcessAsync` | `bpmn:callActivity` | `uipath:activity` | Preserve or draft only with a dedicated case-management contract |
-| `Maestro.ReceiveMessageEvent` | start, intermediate catch, or boundary message event | `uipath:event` | Model-owned when message name and public-safe payload contract are known |
-| `Maestro.SendMessageEvent` | intermediate throw or end message event | `uipath:event` | Model-owned when message name and public-safe payload contract are known |
-| `Maestro.CasePlanScheduler` | `bpmn:serviceTask` | `uipath:activity` | Preserve or draft only with a dedicated case-management contract |
-| `Maestro.CaseManagerGuardrails` | `bpmn:serviceTask` | `uipath:activity` | Preserve-only until documented |
-| `Maestro.CaseRulesEvaluator` | `bpmn:serviceTask` | `uipath:activity` | Preserve-only until documented |
-| `Intsvc.ActivityExecution` | `bpmn:sendTask` and supported event wrappers | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.HttpExecution` | `bpmn:sendTask` or intermediate throw | `uipath:activity` | After skeleton confirmation, request-and-continue plain connectionless HTTP may use [http-request.md](task-recipes/http-request.md); connector-authenticated or dynamic HTTP remains CLI-owned enrichment |
-| `Intsvc.UnifiedHttpRequest` | `bpmn:sendTask` or intermediate throw | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.AsyncExecution` | `bpmn:serviceTask` | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.SyncAgentExecution` | `bpmn:serviceTask` | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.AsyncAgentExecution` | `bpmn:serviceTask` | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.SyncWorkflowExecution` | `bpmn:serviceTask` | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.AsyncWorkflowExecution` | `bpmn:serviceTask` | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.EventTrigger` | message start event | `uipath:event` | CLI-owned enrichment |
-| `Intsvc.TimerTrigger` | timer start event | `uipath:activity` | CLI-owned enrichment |
-| `Intsvc.WaitForEvent` | `bpmn:receiveTask`, intermediate catch, or boundary message event | `uipath:event` | CLI-owned enrichment |
-
-## Script task runtime
-
-Script tasks execute JavaScript through Jint, not Node.js or a browser runtime.
-
-- Use `bpmn:scriptTask scriptFormat="JavaScript"`.
-- Put source in `bpmn:script` CDATA and include `uipath:scriptVersion`; prefer `v3`.
-- Inputs are exposed as named JavaScript variables after Maestro maps inputs into an `args` JSON body.
-- Available helpers are limited to `uipath.aggregate`, `uipath._aggregate`, `uipath._pipe`, and a no-op `console`.
-- There is a 64 MB memory limit and a 30 second execution timeout.
-- Do not use packages, filesystem, network, browser globals, or long-running async behavior.
-- For version `v2` and later the script may return any JSON value under `response`; older versions must return a JSON object.
-
-## Integration Service boundary
-
-For `Intsvc.*` elements, the model may author the surrounding BPMN shell,
-variables, mappings, error paths, diagram geometry, and a non-executable draft
-`uipath:type value="Intsvc.<Variant>"` shell with placeholder strings. The
-documented pass-2 exception is confirmed plain connectionless HTTP, which must
-follow [http-request.md](task-recipes/http-request.md). Connector-backed or
-dynamically schematized `Intsvc.*` work still requires the CLI to enrich connector key,
-operation/event metadata, connection binding, trigger property bindings,
-schemas, generated outputs, `bindings_v2.json`, and package metadata before
-upload or run.
-
-## Preservation boundary
-
-If an imported file contains extension types not listed here, preserve them and report that the skill cannot safely regenerate them. Do not delete unknown extensions unless the user explicitly asks for normalization.

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/README.md

@@ -1,29 +0,0 @@
-# Task Recipes
-
-Use these recipes after the BPMN skeleton is chosen. They describe how confirmed
-UiPath resource-backed work maps onto standard BPMN task classes during pass 2.
-Individual recipe files assume the pass-1 model is already selected; they are
-not process-modeling guidance.
-
-> Copyable minimal XML shell per wrapper: [../../../shared/wrapper-shells.md](../../../shared/wrapper-shells.md). Each recipe below describes when to use it and what fields are model- versus CLI-owned; copy the matching shell from `wrapper-shells.md` for the exact XML.
-
-| Need | BPMN element | Recipe |
-| --- | --- | --- |
-| Start an RPA process | `bpmn:serviceTask` | [rpa-job.md](rpa-job.md) |
-| Start a UiPath agent or A2A agent | `bpmn:serviceTask` | [agent-job.md](agent-job.md) |
-| Execute an API workflow | `bpmn:serviceTask` | [api-workflow.md](api-workflow.md) |
-| Implement confirmed request-and-continue plain HTTP | `bpmn:sendTask` | [http-request.md](http-request.md) |
-| Create a queue item | `bpmn:sendTask` | [queue.md](queue.md) |
-| Create and wait for a queue item | `bpmn:serviceTask` | [queue.md](queue.md) |
-| Execute a business rule | `bpmn:businessRuleTask` | [business-rule.md](business-rule.md) |
-| Create an Action Center human task | `bpmn:userTask` | [hitl.md](hitl.md) |
-| Call an agentic or case-management process | `bpmn:callActivity` | [call-activity.md](call-activity.md) |
-
-Rules:
-
-- Do not create Flow-style peer nodes in BPMN. Keep the BPMN element class visible in the XML.
-- Pass 1 still owns process modeling. Apply these recipes only after the BPMN
-  skeleton is chosen and the resource-backed node is ready for implementation.
-- Resource identity, folder binding, and dynamic schemas are resolved by CLI/operator unless this skill has a documented public-safe shell contract.
-- Keep resource names synthetic or placeholder-safe in examples.
-- Put routing logic on sequence flows and gateways after the task, not inside the resource recipe.

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/agent-job.md

@@ -1,36 +0,0 @@
-# Agent Job Recipe
-
-Agent wrappers are authored as `bpmn:serviceTask`, but the executable runtime
-contract depends on the process type reported by
-`uip or processes list --all-fields`, not the source project label. Some coded
-Python "agents" are published as `processType: "Function"` and are not the same
-runtime contract as low-code Agent Builder processes published as
-`processType: "Agent"`.
-
-| Agent deployment style | Wrapper shell | Notes |
-| --- | --- | --- |
-| Coded Python dependency published as `Function` | Use the process wrapper contract, not `StartAgentJob`, unless discovery documents a different wrapper | Resolve process identity, folder scope, input schema, and output schema before Operate. |
-| Low-code Agent Builder agent published as `Agent` | `Orchestrator.StartAgentJob` shell | Use resolved process identity fields, generated bindings, and current input/output schema metadata. Do not claim executable success from local XML validation alone. |
-| External A2A agent addressed by URL / skillId / authToken | `A2A.AgentExecution` | Studio Web renders this as an external A2A node and disables the Action dropdown. Do not use for folder-deployed agents — the canvas will treat the task as misconfigured. |
-| Integration Service external agent | `Intsvc.SyncAgentExecution`, `Intsvc.AsyncAgentExecution`, or legacy `Intsvc.AsyncExecution` | CLI must enrich connector resource key, connection binding, dynamic schemas, and operation metadata. |
-
-Common authoring mistake: assuming local validation or packaging proves the
-agent wrapper is executable. Validation checks structure and package shape; an
-authorized target-environment run is needed before claiming runtime behavior.
-Put the `JobArguments` input payload and `Process response` output payload as
-direct children of `uipath:activity`; do not put them in a sibling
-`uipath:mapping`.
-
-The model may draft:
-
-- Service task wrapper, variables, mappings, timeout/error paths, and validation gateways.
-- Public-safe prompt/input and output variable names.
-- A documented non-Integration-Service shell when resource metadata is known.
-
-CLI or operator must resolve:
-
-- Agent identity, version, folder binding, and generated resources.
-- Dynamic input and output schemas.
-- External-agent connector metadata for `Intsvc.*` variants.
-
-Add HITL review when agent output drives high-impact decisions or irreversible actions.

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/api-workflow.md

@@ -1,29 +0,0 @@
-# API Workflow Recipe
-
-The current supported implementation wrapper for confirmed API workflow
-invocation is `bpmn:serviceTask` with `Orchestrator.ExecuteApiWorkflowAsync`.
-
-Use these context fields:
-
-- `ReleaseKey` = Orchestrator process GUID from `uip or processes list`.
-- `FolderKey` = target folder GUID.
-- `FolderPath` = target folder path.
-- `Name` = process display name.
-
-Use `type="string"` on those context inputs. Do not rely on a lone display
-name when the wrapper requires resolved process and folder identity.
-
-The model may draft:
-
-- Service task wrapper and BPMN DI.
-- Request variables, response variables, status/error variables, and mappings.
-- Public-safe request body examples and boundary error paths.
-
-CLI or operator must resolve:
-
-- API workflow resource identity, folder binding, and generated package resources.
-- Solution-style `bindings_v2.json` entries for `uip solution resources refresh`.
-- Dynamic request and response schemas.
-- Fire-and-forget versus wait behavior when the product contract exposes that choice.
-
-Stop before Operate when workflow binding, schema, or wait behavior is unresolved.

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/business-rule.md

@@ -1,18 +0,0 @@
-# Business Rule Recipe
-
-The current supported implementation wrapper for confirmed business rule
-execution is `bpmn:businessRuleTask` with `Orchestrator.BusinessRules`.
-
-The model may draft:
-
-- Business rule task wrapper, incoming/outgoing flows, and BPMN DI.
-- Fact variables, result variables, diagnostics variables, and mappings.
-- A gateway after the rule task when rule output drives routing.
-- Retry, boundary error, or manual review paths when failures are recoverable.
-
-CLI or operator must resolve:
-
-- Rule identity, version, folder binding, and generated binding resources.
-- Dynamic input and output schemas.
-
-Do not represent a business rule as a generic service task in new XML unless preserving an imported file or matching an explicit product migration contract.

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/call-activity.md

@@ -1,56 +0,0 @@
-# Call Activity Recipe
-
-The current supported implementation wrapper for confirmed process calls
-exposed through Orchestrator process-orchestration resource types is
-`bpmn:callActivity`.
-
-Supported shells:
-
-- `Orchestrator.StartAgenticProcess`
-- `Orchestrator.StartAgenticProcessAsync`
-- `Orchestrator.StartCaseMgmtProcess`
-- `Orchestrator.StartCaseMgmtProcessAsync`
-
-The model may draft:
-
-- Call activity wrapper, mappings, boundary events, and BPMN DI.
-- Placeholder-safe called-resource intent when a documented contract exists.
-- Synchronous versus asynchronous routing as explicit process behavior.
-
-CLI or operator must resolve:
-
-- Called process identity, package/resource binding, and generated package metadata.
-- Dynamic input/output schemas.
-- Case-management details unless a dedicated case-management contract is available.
-
-Use subprocesses for inline local process structure. Use call activities when execution leaves the local BPMN scope.
-
-## Mapping shape
-
-Use normal activity mapping rules:
-
-- Inputs read declared process variables with `=vars.<variableId>`.
-- Outputs target declared `uipath:inputOutput` or `uipath:output` variable ids.
-- Boundary errors, retries, and error mappings use
-  [error-handling.md](../../../shared/error-handling.md).
-- If the called resource contract is unknown, leave the call activity as draft
-  intent instead of guessing input/output schemas.
-
-Minimal draft shell:
-
-```xml
-<bpmn:callActivity id="Call_ReviewProcess" name="Call Review Process">
-  <bpmn:extensionElements>
-    <uipath:activity version="v1">
-      <uipath:type value="Orchestrator.StartAgenticProcess" version="v1" />
-      <uipath:context>
-        <uipath:input name="process" type="resource" value="=bindings.Binding_ReviewProcess" />
-      </uipath:context>
-      <uipath:input name="payload" type="json" target="bodyField"><![CDATA[
-        {"requestId":"=vars.Var_RequestId"}
-      ]]></uipath:input>
-      <uipath:output name="status" type="string" var="Var_CallStatus" source="status" />
-    </uipath:activity>
-  </bpmn:extensionElements>
-</bpmn:callActivity>
-```

package/skills/uipath-maestro-bpmn/references/author/references/task-recipes/hitl.md

@@ -1,17 +0,0 @@
-# HITL Recipe
-
-The current supported implementation wrapper for confirmed Action Center human
-work is `bpmn:userTask` with `Actions.HITL`.
-
-The model may draft:
-
-- User task wrapper, variable mappings, boundary timer/error paths, and post-task gateways.
-- Public-safe form field names, outcome variable names, and decision routes.
-- Placeholder-safe assignment or routing intent when the user explicitly provides it.
-
-CLI or operator must resolve:
-
-- Real Action Center app/form, folder, queue, group, user, and notification metadata.
-- Dynamic form schemas and generated resources.
-
-No personal names, email addresses, tenant URLs, or exported form payloads should appear in authored examples.