git:20260807.55310d1 to git:20260811.3fd64fb

106 added, 40 removed. Audit C to C.

-

- - **(Studio Web + IntSvc only)** do not run local binding-sync/resource-refresh commands or edit solution catalogue files. Treat the connection and solution resources exposed by Studio Web as authoritative. If the host exposes a relevant ProxyTool, inspect its live schema before calling it and use only the fields and values that schema declares; never reconstruct the call from memory.

-

+

+ Author, validate, execute, and publish API Workflow JSON in Studio Web. Use `CreateProjects` for project creation, the Studio Web VFS for authoring, the embedded CLI for static validation and activity discovery, `RunProject` for approved execution, and the host publish bridge for publication.

-

- - User wants to **run, package, publish, or deploy** an API workflow through capabilities exposed by Studio Web

-

+

-

- - User wants to **debug or operate** an API workflow using Studio Web validation, run, lifecycle, connection, or diagnostic capabilities

-

+

+ ## Studio Web Capability Map

-

- 19. **Create API Workflow projects with the Studio Web project tool — never with a CLI init command.** Before creating a project, inspect the live ProxyTool schema for `proxy-tools-Solution` and its `CreateProjects` operation. Invoke that operation with the API Workflow project type using exactly the fields and enum values present in the current schema. Do not hardcode the request shape or tool parameters in the skill; the live schema is the contract.

+ Studio Web provides a browser sandbox, a virtual `/solution` filesystem, an embedded `uip` command, and live ProxyTools. Treat this map as the executable contract for Studio Web; shared references provide authoring context. For requests beyond this map, report the exact host capability gap and ask how the user wants to proceed.

- 19a. **Let Studio Web own project scaffolding and solution metadata.** Do not run `uip solution init`, `uip api-workflow init`, `uip login`, or any other local project-setup command. Do not search for, create, or edit a local `.uipx` file. After `CreateProjects` succeeds, inspect the project files exposed by the Studio Web workspace/VFS and edit the generated workflow entrypoint. If the creation tool or required project type is unavailable, report that capability gap instead of fabricating a local scaffold.

-

+ - **Project creation:** inspect the live `proxy-tools-Solution` / `CreateProjects` schema and invoke the API Workflow project type with exactly its declared fields and enum values.

+ - **Project files:** for the open project, use `CurrentProject.AbsolutePath`. After creation, verify the returned `/solution/<projectName>` directory with `LsDirectory` and edit `/solution/<projectName>/Workflow.json`. Treat the host-generated tree and metadata as authoritative.

+ - **Activity discovery:** use `ExecuteBashCommand` for `uip api-workflow registry resolve` / `stub` and read-only Integration Service discovery such as `uip is connectors list`, `activities list`, `connections list` / `ping`, and `resources list` / `describe`. Authentication comes from the active Studio Web session. Keep `--output json` whenever output is parsed.

+ - **Validation:** from the target project root, run `uip api-workflow validate Workflow.json --output json` until `Data.Status` is `Valid`.

+ - **Execution:** state concrete external side effects and require an explicit user yes. Then inspect `/skills/synthetic/proxy-tools-Api/SKILL.md`, inspect the live `RunProject` schema, invoke exactly its declared fields for the target project, and use the actual tool result as evidence.

+ - **Publication:** for an explicit approved publish request, optionally inspect `uip solution publish --help`, then run host-intercepted `uip solution publish` with supported flags. The active solution is implicit. Treat command success as request acceptance and verify final completion in Studio Web's Publish history.

-

- Validate and run through capabilities exposed by Studio Web, inspecting each live schema before calling it. Validation without external side effects may proceed autonomously; preserve the explicit-consent requirement before any run that can call a vendor system. Do not ask the user to establish a local CLI login or fall back to a local command when Studio Web does not expose the required capability; report the capability gap.

-

+ Authentication and tenant context are inherited from the active Studio Web session. Report authentication or capability failures as host-level blockers and retry after the relevant host state changes.

+

-

- Once the workflow is ready, use only the lifecycle tools exposed by Studio Web for packaging, publishing, deployment, and published-workflow operations. Inspect each tool's live schema before calling it. Do not substitute local solution, authentication, Orchestrator, Integration Service, or trace CLI commands when the corresponding Studio Web capability is absent; report the missing capability and ask how the user wants to proceed.

-

+

+ - **(Studio Web + IntSvc only)** treat the connection and solution resources exposed by Studio Web as authoritative. Use registry resolution, read-only `uip is` discovery, and relevant resource ProxyTools for authoring. Inspect each live ProxyTool schema immediately before invocation and pass exactly its declared fields and values.

+

-

- Fix run failures in category order — **Structure > Expression > Activity Config > Logic** — using diagnostics exposed by the Studio Web validation/run capability. Do not switch to a local CLI troubleshooting workflow or local authentication setup when a host capability is missing; report the capability gap.

-

+

+ - User wants to **run, publish, or manage the lifecycle of** an API workflow through capabilities exposed by Studio Web

+

-

+

+ - User wants to **debug or operate** an API workflow using Studio Web validation, execution, lifecycle, connection, or diagnostic capabilities

+

+

+ 19. **Create API Workflow projects with the Studio Web project tool.** First distinguish an explicit request for a new project from a request to add workflow content to the current project. For a new project, inspect the live `proxy-tools-Solution` / `CreateProjects` schema and invoke the API Workflow project type using exactly the fields and enum values it declares.

+ 19a. **Continue from the project returned by Studio Web.** Verify `/solution/<projectName>` with `LsDirectory`, then edit `/solution/<projectName>/Workflow.json`; alternatively, open that project before using `CurrentProject.AbsolutePath`. Preserve the host-generated project tree and metadata. When the creation operation, project type, or generated tree is unavailable, report the exact capability gap.

+

+

+ 2. **Start minimal, iterate to correct.** Add one activity at a time. Run the offline static validator after each addition. Fix what breaks and repeat. Start runtime execution after the explicit consent required by rule 21.

+ 3. **Validate statically, execute through the host.** `uip api-workflow validate` is the autonomous offline pre-flight. After explicit consent, use the live `proxy-tools-Api` / `RunProject` host operation to verify runtime behavior, expressions, connections, and side effects. See rules 20–21.

+

+

+ 5. **String literals in `Assign.set` / `Response` / If `when` MUST be wrapped as `"${'literal'}"`** — a JS string inside an expression. Studio Web's designer normalizes unwrapped values to `"${literal}"` on save, so use single quotes inside the expression: `"set": { "tier": "${'PLATINUM'}" }`. Numbers, booleans, and references like `${$context.variables.X}` need no extra wrapping. (Response payloads have a related but distinct constraint — see rule 15.) **Scope:** this rule applies to Assign / Response / If / variable contexts. Connector `bodyParameters` / `queryParameters` / `pathParameters` use BARE literals; `${'...'}` there is read as an expression and the field is cleared on save. See rule 16 and [references/connector-activity-discovery.md#field-shape-rules-flat-keys-bare-literals-renamed-export-hub-prefix](references/connector-activity-discovery.md#field-shape-rules-flat-keys-bare-literals-renamed-export-hub-prefix). See [references/troubleshooting.md](references/troubleshooting.md#studioweb-roundtrip-pitfalls).

+

+

+ **Static coverage:** malformed JSON; unknown `activityType` values; per-activity required keys; missing activity metadata (warnings); invalid evaluation settings; duplicate or empty-named variables; and empty task lists. **Runtime coverage:** resource and connection IDs, expression evaluation, designer normalization, and real connector behavior. After explicit consent, verify runtime coverage through the schema-inspected `RunProject` host operation.

+

+

+ - **On-disk is authoritative.** Every Studio Web designer save can re-trigger normalization passes that may corrupt the Response shape. After each designer roundtrip, run the offline static validator. When runtime revalidation is needed, obtain the explicit consent required by rule 21, invoke `RunProject`, inspect the Response, and re-apply the single-expression workaround when needed. Until the designer fix ships, treat the file on disk as the source of truth.

+

+

+ 21. **Start each Studio Web run after an explicit user "yes."** Once static validation passes, state the concrete external side effects and ask whether to run now or skip. On approval, read `/skills/synthetic/proxy-tools-Api/SKILL.md`, inspect the live `RunProject` schema immediately before invocation, and call it with exactly the declared fields for the target project. Use the actual tool result as execution evidence. When `RunProject` is unavailable, report the exact host capability gap.

+

+

+ 17. **Map runtime inputs directly from the live `RunProject` schema.** When a required input is absent or ambiguous, report the schema gap and ask the user for the needed value or host capability.

+ 18. **Interpret execution from the actual `RunProject` result and its live contract.** Keep `--output json` for embedded discovery and static-validation commands whose output is parsed.

+

+

+ From the target project directory, run `uip api-workflow validate Workflow.json --output json`, fixing and re-validating until `Data.Status` is `Valid`. Then state concrete external side effects and ask for explicit consent. On approval, inspect `/skills/synthetic/proxy-tools-Api/SKILL.md` and the live `RunProject` schema, then invoke `RunProject` using exactly its declared fields. Report validation or execution capability gaps with the exact host result.

+

+

+ For an explicit publish request, optionally inspect `uip solution publish --help`, obtain publish approval, and invoke host-intercepted `uip solution publish` for the active solution with supported flags: `--description`, `--release-notes`, `--version`, `--location`, `--location-name`, and `--personal-workspace`. Command success means Unified Build accepted the request and started background packaging. Verify the terminal status in Studio Web's Publish history. Use schema-inspected host capabilities for other lifecycle and published-workflow operations.

+

+

+ Fix failures in category order — **Structure > Expression > Activity Config > Logic**. Use the embedded static validator autonomously, read-only `uip is` discovery for connection diagnosis, and consent-gated `RunProject` invocations for runtime diagnosis. Inspect each live schema immediately before invocation and report the exact host result or capability gap.

+

+

## Quick Start (CREATE from scratch in Studio Web)

1. Inspect the live ProxyTool schema for `proxy-tools-Solution` and `CreateProjects`.

- 2. Call `CreateProjects` for an API Workflow project using only schema-declared parameters and values; never guess or hardcode the request shape.

- 3. Inspect the files generated in the Studio Web workspace/VFS, open the generated workflow entrypoint, and add user activities after `WorkflowStart` inside the root sequence.

- 4. Validate and run only through capabilities exposed in Studio Web. Preserve the explicit-consent rule before any run that can invoke a vendor system or create external side effects.

- 5. When packaging or publishing is requested, use the available Studio Web lifecycle tool after inspecting its live schema. If none is exposed, report the capability gap rather than falling back to local CLI setup.

-

+ 2. Call `CreateProjects` for an API Workflow project using the schema-declared parameters and enum values.

+ 3. Verify the returned `/solution/<projectName>` directory, then edit `/solution/<projectName>/Workflow.json` and add user activities after `WorkflowStart` inside the root sequence.

+ 4. Set the embedded command working directory to `/solution/<projectName>`. Run `uip api-workflow validate Workflow.json --output json` until valid. State side effects and ask for explicit consent; on approval, inspect `/skills/synthetic/proxy-tools-Api/SKILL.md` and invoke the live `RunProject` operation with exactly its schema-declared fields.

+ 5. When publication is explicitly requested, optionally inspect `uip solution publish --help`, obtain approval, and run host-intercepted `uip solution publish` for the active solution with supported bridge flags. Treat acceptance as background work and verify completion in Studio Web's Publish history.

+

-

- - **Do NOT** run `uip solution init`, `uip api-workflow init`, or any local setup command in Studio Web. Inspect and call the live `proxy-tools-Solution` / `CreateProjects` schema instead.

- - **Do NOT** search for, create, or edit `.uipx` solution metadata in Studio Web; the host owns that metadata.

- - **Do NOT** hand-assemble a replacement project when `CreateProjects` is unavailable. Report the missing capability so the user can choose how to proceed.

- - **Do NOT** use successful local validation, packaging, or publication as evidence that a project was created correctly in Studio Web. The `CreateProjects` result and host-exposed project tree are authoritative.

-

+

+ - **Use the freshly inspected `proxy-tools-Solution` / `CreateProjects` schema** for every explicit new-project request.

+ - **Use the successful `CreateProjects` result and host-exposed project tree as creation evidence.**

+ - **Preserve the host-generated project tree and solution metadata** while authoring `/solution/<projectName>/Workflow.json`.

+ - **Report an unavailable creation capability or project type as an exact host gap** and ask how the user wants to proceed.

+

-

- - `Not authenticated` / `Organization ID not available` → do not ask the user to run `uip login`. Use an exposed Studio Web authentication or connection capability after inspecting its live schema; if none exists, report the host-level authentication blocker and do not retry.

-

+

+ - `Not authenticated` / `Organization ID not available` → inspect any exposed Studio Web authentication or connection capability through its live schema. Report the host-level authentication blocker and retry after the Studio Web session or tenant state changes.

+

-

+

- > **Studio Web reference scope.** Keep the shared references available for JSON authoring, troubleshooting, and CLI operations that Studio Web exposes, including validation and `uip api-workflow registry resolve` / `stub` for connector discovery. A reference documents the complete API Workflow surface; it does not grant permission to run every listed command in this host. Project creation must use the live `proxy-tools-Solution` / `CreateProjects` schema, and the Studio Web rules above still prohibit local init, login, solution-metadata, and lifecycle fallbacks.

-

+ > **Studio Web reference scope.** Use the shared references for JSON authoring, troubleshooting, static validation, `uip api-workflow registry resolve` / `stub`, read-only Integration Service discovery, and the host-intercepted active-solution publish bridge. Apply the Studio Web capability map above and inspect live host schemas for project, runtime, resource, and lifecycle operations.

+

+

+ | [references/cli-reference.md](references/cli-reference.md) | Studio Web capability map: embedded authoring commands, schema-inspected `RunProject`, and approved host-intercepted active-solution publication |

+

+

+ | [assets/templates/connector-call-example.json](assets/templates/connector-call-example.json) | **Http kind** — HTTP Request curated activity (`call: "UiPath.Http"`) for arbitrary REST calls. Generated by `registry stub` against the catfacts URL and compatible with the Studio Web designer. Validate it through the embedded static validator and, after explicit consent, execute it through schema-inspected `RunProject`. |

+

+

+ - **After static validation and explicit consent, execute through the freshly inspected `proxy-tools-Api` / `RunProject` operation and use its actual result as evidence.** See rules 20–21.

+

+

+ | [references/operating-published-workflows.md](references/operating-published-workflows.md) | Operate and diagnose published workflows through live Studio Web capabilities; report unavailable job, log, trace, or lifecycle surfaces and hand off deeper platform investigation |

+

+

+ | [assets/templates/solution-connection-resource-template.json](assets/templates/solution-connection-resource-template.json) | **Studio Web resource reference.** Inspect the relevant host resource capability and use its declared fields for connection-resource authoring. |

+