@uipath/skills 1.196.0 → 1.197.0

package/skills/uipath-api-workflow/references/troubleshooting.md

@@ -294,7 +294,12 @@ These are issues that surface only when a workflow is opened or run in **StudioW
   uip is connections ping <alternate-uuid> --output json
   # If Code: "ConnectionPing" — use this UUID in the workflow
   ```
-- **What NOT to do:** do NOT proceed with the failing UUID and "flag for follow-up." A workflow authored against a non-pinging connection will 401 in cloud regardless of how correct the JSON is. If neither the filtered nor unfiltered listing yields a working UUID, abort and tell the user to re-authenticate (`uip is connections edit <uuid>` opens an OAuth browser flow) or create a fresh connection in the StudioWeb UI.
+  If the unfiltered listing is also empty, the connection may live in another folder — both listings are folder-scoped. Search every folder before giving up:
+  ```bash
+  uip is connections list --all-folders --output json
+  # Each row carries Folder / FolderKey. Take an Enabled Id, then ping it.
+  ```
+- **What NOT to do:** do NOT proceed with the failing UUID and "flag for follow-up." A workflow authored against a non-pinging connection will 401 in cloud regardless of how correct the JSON is. Do NOT conclude "no connection exists" from an empty filtered or unfiltered listing — run `--all-folders` first. Only if the filtered, unfiltered, AND `--all-folders` listings all fail to yield a working UUID should you abort and tell the user to re-authenticate (`uip is connections edit <uuid>` opens an OAuth browser flow) or create a fresh connection in the StudioWeb UI.
 - **See also:** [connector-activity-discovery.md — Step 2](connector-activity-discovery.md#step-2--verify-a-vendor-connection-intsvc-kind-only) for the full discovery+fallback flow.
 
 ### IntSvc kind activity output read at the root returns `undefined`
@@ -432,7 +437,7 @@ These are issues that surface only when a workflow is opened or run in **StudioW
   Also check that `bindings_v2.json`'s `"key"` matches `Workflow.json`'s `connectionId` matches the missing resource file's intended `"key"` — same UUID across all three.
 - **Fix (preferred — two CLI commands):**
   ```bash
-  # 1. Generate bindings_v2.json from Workflow.json (pure local; no auth needed):
+  # 1. Generate bindings_v2.json from Workflow.json (local for connections; queries IS for resource picker fields):
   uip api-workflow bindings sync --workflow <path-to-Workflow.json> --output json
 
   # 2. Sync catalogue + debug overwrites via @uipath/resource-builder-sdk (requires uip login):
@@ -564,7 +569,7 @@ These are issues that surface only when a workflow is opened or run in **StudioW
 
 ### `Failed to parse <solution>.uipx`
 - **Cause:** Solution file is malformed JSON
-- **Fix:** Re-create with `uip solution new <name>` and re-add projects via `uip solution project add`
+- **Fix:** Re-create with `uip solution init <name>` and re-add projects via `uip solution project add`
 
 ### Generated `operate.json` or `package-descriptor.json` mismatch
 - **Cause:** Stale files committed by hand or from an older CLI version
@@ -572,7 +577,18 @@ These are issues that surface only when a workflow is opened or run in **StudioW
 
 ### `.nupkg` produced but missing workflow files
 - **Cause:** Workflow JSON not located in the project directory the packager scanned
-- **Fix:** Verify workflow files are in the project folder declared in the solution `.uipx`, alongside `project.json`
+- **Fix:** Verify `Workflow.json` is in the project folder whose `project.uiproj` is declared in the solution `.uipx`
+
+### API workflow runs/deploys fine but does NOT appear or open in Studio Web
+- **Symptom:** The workflow runs under `uip api-workflow run`, the solution packs, publishes, and deploys as an API process — but after uploading the solution to Studio Web the API project is invisible / not editable. Importing it directly fails with `Failed to import new projects at the overwrite operations`.
+- **Cause:** The project uses the **runtime-only** shape — `project.json` + `workflows/WF_*.json`, no `.uiproj`. Studio Web's import (`isProjectFolder`) only recognizes a folder as a project when it contains a `.uiproj` file; a `project.json`-only folder is rejected as `invalid_project_folder`. Every runtime gate (validate / run / pack / publish / deploy) passes on this shape, so the defect surfaces only when a human opens Studio Web. This was the Woolworths private-preview RCA root cause. Root reason it happened: the project was hand-assembled instead of scaffolded with `uip api-workflow init`, which always produces the correct shape.
+- **Fix (preferred — re-scaffold):** For each broken `Type: "Api"` project, run `uip api-workflow init <newName>` inside the solution directory and copy the old main workflow's `document`/`do` content into the new `Workflow.json`. `init` writes the correct `project.uiproj` / `entry-points.json` / `bindings_v2.json` and registers the project in the `.uipx`. Then delete the old `project.json` folder (and its `.uipx` entry).
+- **Fix (in-place conversion)** when you must keep the existing folder/`Id` (SKILL.md rule 19a, [workflow-file-format.md](workflow-file-format.md#project-structure-studio-web-editable-contract)):
+  - Add `project.uiproj` (`ProjectType: "Api"`, `MainFile: "Workflow.json"`) and `entry-points.json` (`filePath: "content/Workflow.json"`, no leading slash, `type: "Api"`). Copy `bindings_v2.json` if present.
+  - Rename the main workflow to `Workflow.json` at the project root.
+  - Edit the `.uipx` `ProjectRelativePath` from `<folder>/project.json` → `<folder>/project.uiproj`, **preserving the project `Id` and `Type`**. Do NOT use `uip solution project remove`+`add` — it mints a new `Id`.
+  - Remove the stray `project.json` / `workflows/` (a mismatched `project.json` triggers `ProjectMetadataMismatchError`).
+  - Re-pack, then confirm the project opens in Studio Web (runtime/pack success alone does not prove it).
 
 ---
 
@@ -594,10 +610,10 @@ These are issues that surface only when a workflow is opened or run in **StudioW
 
 ## Validation Pitfalls
 
-### Not re-running after a fix
+### Not re-validating after a fix
 - **Symptom:** Reported "fixed" but errors remain
-- **Cause:** Skipped re-running `uip api-workflow run --no-auth` after applying a fix
-- **Fix:** ALWAYS re-run after every edit. The CLI is the only validator — there is no `uip api-workflow validate` command.
+- **Cause:** Skipped re-running the validators after applying a fix
+- **Fix:** ALWAYS re-run after every edit. Two validators: `uip api-workflow validate <Workflow.json>` (offline static — schema + semantic checks, autonomous) then `uip api-workflow run --no-auth` (runtime — catches expression/connection errors static analysis can't). See SKILL.md rules 20–21.
 
 ### Fixing in wrong order
 - **Symptom:** Fixing one error creates more errors; thrashing

package/skills/uipath-api-workflow/references/workflow-file-format.md

@@ -184,21 +184,39 @@ A `Sequence` task groups child tasks. Most workflows have a single root `Sequenc
 
 Child tasks execute in order. `$context` flows from one to the next via `export.as`.
 
-## Project Structure (Packaging Context)
+## Project Structure (Studio Web editable contract)
 
-When part of a UiPath solution, the workflow JSON sits in a project folder with `Type: "Api"` declared in the solution `.uipx`:
+An API workflow project that must open and edit in **Studio Web** ships a specific on-disk shape. **`uip api-workflow init <name>` generates this shape for you** (and registers the project in the solution `.uipx`) — use it for new projects instead of writing these files by hand. The layout below is the contract `init` produces and what `uip solution pack` reads via `project.uiproj`; it also documents what to recreate when converting a legacy `project.json` project:
 
 ```
 <solutionDir>/
-├── <solution>.uipx          # Lists all projects with their Type
-└── <projectFolder>/
-    ├── project.json         # Project metadata
-    ├── <main-workflow>.json # Your API workflow
-    └── <other-workflow>.json
+├── <solution>.uipx                 # Projects[].Type "Api", ProjectRelativePath "<projectFolder>/project.uiproj"
+└── <projectFolder>/                # created by `uip api-workflow init <projectFolder>`
+    ├── project.uiproj              # { "ProjectType": "Api", "Name": "...", "Description": null, "MainFile": "Workflow.json" }
+    ├── Workflow.json               # the API workflow — canonical fixed name, project root
+    ├── entry-points.json           # entryPoints[0]: filePath "content/Workflow.json", type "Api"
+    ├── bindings_v2.json            # IntSvc connector bindings ({"version":"2.0","resources":[]} when none)
+    └── .local/ProjectSettings.json # NOT written by init — Studio Web creates it on first open. Do not author by hand.
 ```
 
 `uip solution pack` auto-generates `operate.json` and `package-descriptor.json` during build — do NOT commit these.
 
+### Field rules (what Studio Web enforces)
+
+| File | Field | Rule |
+|------|-------|------|
+| `.uipx` | `Projects[].ProjectRelativePath` | MUST end with `/project.uiproj`. Pointing at `project.json` → folder isn't recognized as a project. |
+| `.uipx` | `Projects[].Type` | `"Api"`. |
+| `project.uiproj` | `ProjectType` | Exactly `"Api"` (capital A). Studio Web parses this with a strict enum — `"api"` is rejected with `InvalidUiprojFileError`. |
+| `project.uiproj` | `MainFile` | `"Workflow.json"`. Studio Web technically accepts any name, but the CLI packager + solution reconcile assume `Workflow.json`. |
+| `Workflow.json` | — | Must exist at project root (the file `MainFile` points to). |
+| `entry-points.json` | `entryPoints[0].filePath` | `"content/Workflow.json"` — relative, **no leading slash**. (`/content/...` is non-canonical.) |
+| `entry-points.json` | `entryPoints[0].type` | `"Api"`. (Studio Web's schema accepts any string here, but stay consistent.) `input`/`output` may be `null` or mirror the workflow's input/output JSON schema so the designer shows parameters. |
+
+> **Why this matters — the runtime shape is a trap.** A `project.json` + `workflows/WF_*.json` layout (no `.uiproj`) runs under `uip api-workflow run`, and packs/publishes/deploys as an API process — every runtime gate passes. But Studio Web's import only recognizes a folder as a project if it contains a `.uiproj` file (`isProjectFolder`); a `project.json`-only project is rejected as `invalid_project_folder` and never appears in Studio Web. Runtime success is NOT proof of Studio Web editability. Scaffold with `uip api-workflow init` — it can't produce the wrong shape (SKILL.md rule 19a).
+
+> **Standalone (CLI-only) projects** that never open in Studio Web — run purely via `uip api-workflow run` — don't need solution registration; `uip api-workflow init <name> --skip-solution-registration` still emits the same files but skips the `.uipx` wiring. The `.uiproj` contract is required the moment the project must be editable in Studio Web or shipped in a solution uploaded to Studio Web.
+
 ## Sources
 
 - CNCF Serverless Workflow Specification: https://github.com/serverlessworkflow/specification

package/skills/uipath-coded-apps/SKILL.md

@@ -1,7 +1,8 @@
 ---
 name: uipath-coded-apps
-description: "Always invoke for `app.config.json` or `action-schema.json` files. UiPath Coded Web Apps & Coded Action Apps via `uip codedapp` and `@uipath/uipath-typescript` SDK. Scaffold, build, debug, deploy. For .cs/XAML→uipath-rpa, Python→uipath-agents."
-allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion
+description: "UiPath Coded Apps — scaffold, build, run, and deploy Coded Web Apps and Coded Action Apps: React/TypeScript apps that call UiPath Cloud APIs via the `@uipath/uipath-typescript` SDK and ship to Automation Cloud (push/pull to Studio Web, pack, publish, deploy, OAuth-PKCE). Also generates live analytics & governance dashboards from a plain-language request, wired to tenant data via the Insights real-time API, with edit and deploy flows. For RPA→uipath-rpa, Python agents→uipath-agents, Maestro flows→uipath-maestro-flow, solution packaging→uipath-solution."
+when_to_use: "User wants to scaffold, build, push/pull, pack, publish, or deploy a Coded Web App or Coded Action App, or use the `@uipath/uipath-typescript` SDK inside one. Also dashboard requests: 'build me a dashboard', 'show agent health / error rate / KPIs / governance violations', 'generate an analytics or observability dashboard', edit an existing one (add/remove/change a widget, change time range, deploy), or fix/diagnose a dashboard that won't build (a metric that fails to compile, a bad SDK call, a broken widget). For RPA→uipath-rpa; Python agents→uipath-agents; Maestro flows→uipath-maestro-flow."
+allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, Task
 ---
 
 # UiPath Coded Apps
@@ -13,9 +14,12 @@ Build, debug, and deploy UiPath Coded Web Applications and Coded Action Apps usi
 - User wants to **build, debug, or deploy** a UiPath Coded Web App or Coded Action App
 - User asks about `uip codedapp` commands, `.uipath/` directory, `app.config.json`, or `action-schema.json`
 - User wants to **scaffold** a new React/Vue frontend for UiPath Cloud or an Action Center form
+- User wants to embed the **Document Understanding Validation Station** widget for human review of DU extraction results
 - User wants to **push/pull source** between local and Studio Web
 - User wants to use the `@uipath/uipath-typescript` SDK from a coded app
 - User wants to run the **full pipeline** (build → pack → publish → deploy)
+- User wants to **generate an agent-monitoring / analytics dashboard** from a natural-language description — e.g. "show agent health, error rates, invocation volume, latency, active agents, KPIs, governance metrics, or consumption trends"
+- User says "build/create/generate a dashboard", describes metrics to visualize, or asks for an agent observability, operations, or cost view
 
 ## App Types
 
@@ -28,7 +32,7 @@ Build, debug, and deploy UiPath Coded Web Applications and Coded Action Apps usi
 
 ## Critical Rules
 
-1. **Identify the app type before doing anything else.** Ask: *"Are you building a **Coded Web App** (custom frontend deployed to UiPath Cloud) or a **Coded Action App** (form for Action Center human task reviews)?"* The two paths diverge on scaffolding, redirect URI, and publish flag — do not guess.
+1. **Identify the app type before doing anything else.** Ask as a structured choice (Rule 18): **Coded Web App** — custom frontend deployed to UiPath Cloud · **Coded Action App** — form for Action Center human task reviews. The two paths diverge on scaffolding, redirect URI, and publish flag — do not guess.
 2. **Always check login status first.** Run `uip login status --output json` before any cloud command. If not logged in, run `uip login`.
 3. **Never skip the build step.** Run `npm run build` after scaffolding (to verify the scaffold compiles) and again before `pack` or `push` (to produce the deployable `dist/`). Verify `dist/` exists each time.
 4. **Pack → Publish → Deploy order is required.** Each step depends on the previous one producing its output.
@@ -43,7 +47,26 @@ Build, debug, and deploy UiPath Coded Web Applications and Coded Action Apps usi
 13. **Inspect the DF schema before writing analytics, filters, or seeds.** Run `uip df entities get <ENTITY_ID> --output json` to inspect fields and types. At runtime, use `entities.getById(<id>)` from the app's authenticated session. DF doesn't behave like a typical RDBMS; see [sdk/data-fabric.md](references/sdk/data-fabric.md) "Anti-shapes & gotchas".
 14. **Every list call returns ONE page — even with no options. There is no "give me everything" path.** Applies to `getAll`, `getAllRecords`, `queryRecordsById`, `getFileMetaData`, etc. `getAll()` with no options does NOT return all rows; the SDK sends no `pageSize` and the **server** applies its own cap, wrapped in a misleadingly-named `NonPaginatedResponse`. To list every row from a source that may exceed the cap, you MUST loop the cursor: `while (page.hasNextPage) { page = await getAll({ cursor: page.nextCursor }) }` and accumulate `items`. Reading `result.items.length` after a single call is almost always a bug. See [sdk/pagination.md](references/sdk/pagination.md).
 15. **Tables of dynamic data must paginate, not dump all rows in one scroll.** Page size 25–50 with next/prev/page-number controls and a "Showing X–Y of Z" summary. Top-N + "see all" is acceptable for explicitly summary panels (e.g., "Top 10 oldest"). Infinite-scroll-of-N-rows is unusable for operational dashboards. Applies to any table backed by any service (DF entities, Tasks, Jobs, Conversations, Process Instances, etc.). See [patterns.md](references/patterns.md) "Tabular Data".
-16. **When adding any new SDK method call, verify `VITE_UIPATH_SCOPE` already includes the required scope.** Write operations, action methods (`Jobs.stop`, `Tasks.complete`, `ProcessInstances.cancel`, etc.), or first use of a new service typically need broader scopes than read-only flows. Mismatched scopes fail silently with `401` / `403` on the first call. See [oauth-scopes.md](references/oauth-scopes.md) for the per-method scope table.
+16. **When adding any new SDK method call, verify the configured OAuth scope already includes the required scope** — both dashboards and web apps read the `scope` key from `uipath.json`. Write operations, action methods (`Jobs.stop`, `Tasks.complete`, `ProcessInstances.cancel`, etc.), or first use of a new service typically need broader scopes than read-only flows. Mismatched scopes fail silently with `401` / `403` on the first call. See [oauth-scopes.md](references/oauth-scopes.md) for the per-method scope table.
+17. **Never call `sdk.initialize()` in an action app.** That is web-app-only — it starts a PKCE OAuth redirect. Action apps run in Action Center's iframe with a host-injected session: construct `new UiPath()` (no args) and use it directly. See [create-action-app.md](references/create-action-app.md) `src/uipath.ts`.
+18. **Never make the user type magic phrases.** Whenever you ask the user to pick between known options (app type, build/edit/deploy intent, OAuth setup, deploy pinning), present a **structured choice** via the host coding agent's native question tool (selectable options) when one exists. Mechanics: one option per choice with a short bold label + one-line description of what picking it does; put the recommended option **first** and suffix its label "(Recommended)"; keep to **at most 4 options** (reserve one slot for an escape option like *Make changes* / *Cancel* when applicable). If there are 5+ candidates, or the host agent has no question tool, render a plain numbered list instead and accept the number or the option label as the answer. A free-text reply must always remain valid (e.g. a plan-change request) and takes precedence over the options. **Exception — never put a question in the same response as a long output:** plan-approval gates are free-text by design (the plan ends with "confirm or tell me what to change"); structured questions fire only on later, short turns. See `references/dashboards/plugins/build/impl.md`.
+
+## Disambiguation — Apps vs Dashboards
+
+**Route directly to Apps workflow** (sections below) when you see:
+`web app`, `action app`, `codedapp`, `app.config.json`, `action-schema.json`,
+`scaffold app`, `deploy app`, `pack`, `publish`, `push`, `pull`, `debug app`
+
+**Route directly to [references/dashboards/CAPABILITY.md](references/dashboards/CAPABILITY.md) when you see:**
+`dashboard`, `analytics`, `KPI`, `metrics`, `Insights`, `observability`,
+`admin console`, `report`, `chart`, `trend`, `governance report`, `agent metrics`
+
+**When intent is ambiguous** — ask "Which fits your goal?" as a structured choice (Rule 18):
+
+| Option | Description |
+|--------|-------------|
+| **Build or modify a Web App / Action App** | Scaffold a UI, form, or app that deploys to Automation Cloud |
+| **Generate a dashboard** | Analytics or admin view from a natural-language description |
 
 ## Task Navigation
 
@@ -55,6 +78,7 @@ Build, debug, and deploy UiPath Coded Web Applications and Coded Action Apps usi
 | **Push/pull code to Studio Web** | [references/file-sync.md](references/file-sync.md) |
 | **Package and deploy** | [references/pack-publish-deploy.md](references/pack-publish-deploy.md) |
 | **Full CLI command reference** | [references/commands-reference.md](references/commands-reference.md) |
+| **Embed the DU Validation Station widget** | [references/widgets/validation-station.md](references/widgets/validation-station.md) |
 | **OAuth scopes for SDK services** | [references/oauth-scopes.md](references/oauth-scopes.md) |
 | **SDK: Import paths & subpath exports** | [references/sdk/imports.md](references/sdk/imports.md) |
 | **SDK: Assets, Queues, Buckets, Processes, Jobs, Attachments** | [references/sdk/orchestrator.md](references/sdk/orchestrator.md) |
@@ -64,7 +88,12 @@ Build, debug, and deploy UiPath Coded Web Applications and Coded Action Apps usi
 | **SDK: Conversational Agent** | [references/sdk/conversational-agent.md](references/sdk/conversational-agent.md) |
 | **SDK: Agent Feedback** | [references/sdk/feedback.md](references/sdk/feedback.md) |
 | **SDK: Pagination** | [references/sdk/pagination.md](references/sdk/pagination.md) |
+| **SDK: Agents & Agent Memory (Insights RTM)** | [references/sdk/agents.md](references/sdk/agents.md) |
+| **SDK: Agent Traces (Insights RTM)** | [references/sdk/traces.md](references/sdk/traces.md) |
+| **SDK: Governance — policy evaluations (Insights API)** | [references/sdk/governance.md](references/sdk/governance.md) |
+| **SDK: Agent Governance Decisions — runtime compliance (Insights RTM)** | [references/sdk/governance-traces.md](references/sdk/governance-traces.md) |
 | **UI Patterns (polling, BPMN, HITL, text overflow, table pagination)** | [references/patterns.md](references/patterns.md) |
+| **Generate an admin dashboard from NLP** | [references/dashboards/CAPABILITY.md](references/dashboards/CAPABILITY.md) |
 
 ## CLI Setup
 
@@ -92,18 +121,32 @@ Authenticate before any cloud command:
 uip login status --output json         # check if logged in
 uip login                              # interactive OAuth (opens browser)
 uip login --authority https://alpha.uipath.com   # non-production environments
+
+# Client-credentials (headless/CI) — MUST include Apps.Read Apps.Write or publish's
+# "Registering coded app" step fails with 401 even though package upload succeeds.
+# OR.Default alone is NOT sufficient — it covers Orchestrator but not the Apps service.
+uip login \
+  --client-id <id> \
+  --client-secret <secret> \
+  --organization <org> \
+  --tenant <tenant> \
+  --scope "OR.Folders OR.Execution OR.Administration Apps.Read Apps.Write" \
+  --authority https://alpha.uipath.com   # omit --authority for production
 ```
 
-## Environment Variables
+> **The `uip login` session scope is separate from the app's runtime OAuth scopes.** The scopes in `uipath.json` are what the *deployed app* requests at runtime (see [oauth-scopes.md](references/oauth-scopes.md)). The `--scope` on `uip login` above is what the *CLI session* needs to call the Apps registration API during `uip codedapp publish`. `uip codedapp publish` does two things: uploads the package (needs Orchestrator scopes) **and** registers the coded app (needs `Apps.Read Apps.Write`). Omitting the Apps scopes lets the upload succeed but silently 401s the registration.
+
+## SDK Config (web app)
+
+The web app initializes the SDK with `new UiPath()` (no config). At runtime the SDK reads `clientId`, `scope`, `orgName`, `tenantName`, `baseUrl`, and `redirectUri` from `<meta name="uipath:*">` tags. During local dev `@uipath/coded-apps-dev` injects those tags from `uipath.json` (committed) — the single config source, holding `clientId`, `scope`, `orgName`, `tenantName`, `baseUrl`, and `redirectUri` (the Vite dev URL for local). In production the UiPath platform injects the same tags directly.
+
+To change any of these values, edit `uipath.json`.
+
+## CLI Environment Variables
 
 | Variable | Used By | Description |
 |----------|---------|-------------|
-| `VITE_UIPATH_CLIENT_ID` | Web App SDK | OAuth Client ID from External Application |
-| `VITE_UIPATH_SCOPE` | Web App SDK | Space-separated OAuth scopes |
-| `VITE_UIPATH_ORG_NAME` | Web App SDK | UiPath organization slug |
-| `VITE_UIPATH_TENANT_NAME` | Web App SDK | UiPath tenant name |
-| `VITE_UIPATH_BASE_URL` | Web App SDK | Must use API subdomain (see below) |
-| `UIPATH_PROJECT_ID` | push / pull | Studio Web project ID |
+| `UIPATH_PROJECT_ID` | `uip codedapp push` / `uip codedapp pull` | Studio Web project ID |
 
 **Base URL by environment:**
 
@@ -117,7 +160,7 @@ uip login --authority https://alpha.uipath.com   # non-production environments
 
 **Do NOT pause between steps to ask "should I continue?" — execute the full pipeline. Only stop if you need auth credentials or an app name.**
 
-1. **Auth** — `uip login status --output json`. If not logged in, ask the user for their environment and run `uip login`.
+1. **Auth** — `uip login status --output json`. If not logged in, ask the user for their environment and run `uip login`. If using **client credentials** (headless/CI), always include `Apps.Read Apps.Write` in `--scope` — required by the Apps service registration inside `uip codedapp publish`. `OR.Default` alone covers Orchestrator (package upload) but not Apps registration; omitting them causes a silent 401 on the second half of publish.
 2. **Build** — `npm run build`. Verify `ls dist/`.
 3. **Pack** — `uip codedapp pack dist -n <name> --version <version>`. Produces `.uipath/<name>.<version>.nupkg`. Bump version if previously published.
 4. **Publish** — `uip codedapp publish` (add `-t Action` for action apps). Verify `cat .uipath/app.config.json`.