@uipath/solution-tool 1.195.0 → 1.197.0-preview.59

package/dist/services/auth-helper.d.ts

@@ -7,4 +7,7 @@ export interface SolutionAuthContext {
 export declare function getSolutionAuthContext(options: {
     tenant?: string;
     loginValidity?: number;
+    /** Pin auth to this exact `.uipath/.auth` path (forwarded to
+     *  `getAuthContext`) instead of resolving from `process.cwd()`. */
+    envFilePath?: string;
 }): Promise<SolutionAuthContext>;

package/dist/services/deploy-activate-service.d.ts

@@ -11,6 +11,8 @@ export interface ActivateDeploymentOptions {
      * `--tenant` flag flows through here; library callers usually omit it.
      */
     tenant?: string;
+    /** Pin auth to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
     /** Timeout in seconds for activation polling. Default 360. */
     timeout?: number;
     /** Milliseconds between activation status polls. Default 5000. */

package/dist/services/deploy-list-service.d.ts

@@ -21,6 +21,8 @@ export type SortDirection = "Ascending" | "Descending";
 export interface ListDeploymentsOptions {
     /** Override the active tenant for auth + folder-lookup. The CLI's deprecated `--tenant` flag flows through here. */
     tenant?: string;
+    /** Pin auth (+ folder lookup) to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
     /** Filter by parent folder path (e.g., `"Shared"`). Post-fetch substring match. */
     folderPath?: string;
     /** Filter by parent folder key (GUID). Alternative to {@link folderPath}. */

package/dist/services/deploy-run-service.d.ts

@@ -1,5 +1,7 @@
 /** Discriminator for {@link DeployFailure}; library callers can ignore the tag and read `.message`/`.instructions`. */
 export type DeployFailureReason = "auth_failed" | "folder_resolution_failed" | "config_file_not_found" | "config_file_read_failed" | "config_file_parse_failed" | "install_request_failed"
+/** Personal Workspace deploy via AS auto-deploy failed (publish first, then retry). */
+ | "personal_workspace_deploy_failed"
 /** Recovery: deployment completed but flagged "Needs Setup" — manual config required before activation. */
  | "needs_setup_to_activate"
 /** Recovery: deployment completed, ready to activate — auto-activation didn't run. */
@@ -21,6 +23,8 @@ export type DeployFailureReason = "auth_failed" | "folder_resolution_failed" | "
 export interface DeployOptions {
     /** Override the active tenant for auth + folder-lookup. The CLI's deprecated `--tenant` flag flows through here. */
     tenant?: string;
+    /** Pin auth (+ folder lookup) to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
     /** Name for the deployment (`uip solution deploy run -n`). */
     deploymentName: string;
     /** Package name to deploy. */
@@ -50,16 +54,30 @@ export interface DeployOptions {
 }
 export interface DeploySuccess {
     ok: true;
-    /** "DeploymentSucceeded" — the canonical terminal success status. */
+    /**
+     * Tenant path: `"DeploymentSucceeded"` after polling reaches terminal.
+     * PW path: `"DeploymentStarted"` — the AS auto-deploy endpoint returns
+     * at request acceptance, before terminal state is observable.
+     */
     status: string;
-    deploymentKey: string | null | undefined;
-    pipelineDeploymentId: string;
+    /** Tenant only — populated from Pipelines install result. PW returns no key. */
+    deploymentKey?: string | null;
+    /** Tenant only — Pipelines deployment id. Undefined for PW (no Pipelines call). */
+    pipelineDeploymentId?: string;
     /** Allows `null` so `"InstanceId": null` reaches JSON output when the SDK reports null. */
     instanceId?: string | null;
     folderName: string;
     folderPath: string;
-    /** "SuccessfulActivate" | "Skipped" | "NoInstance" — short canonical token. */
+    /** "SuccessfulActivate" | "Skipped" | "NoInstance" — short canonical token. PW path emits `"Auto"`. */
     activationStatus: string;
+    /** PW only — server-assigned auto-name (`AutoDeploy-<solution>`). */
+    deploymentName?: string;
+    /** PW only — package name as deployed. */
+    packageName?: string;
+    /** PW only — package version as deployed. */
+    packageVersion?: string;
+    /** PW only — future-tense human guidance ("Check status with..."). */
+    nextSteps?: string;
 }
 export interface DeployFailure {
     ok: false;

package/dist/services/deploy-uninstall-service.d.ts

@@ -9,6 +9,8 @@ export interface UninstallDeploymentOptions {
      * `--tenant` flag flows through here; library callers usually omit it.
      */
     tenant?: string;
+    /** Pin auth to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
     /** Timeout in seconds for uninstall polling. Default 360. */
     timeout?: number;
     /** Milliseconds between uninstall status polls. Default 5000. */

package/dist/services/folder-helper.d.ts

@@ -18,4 +18,7 @@ export declare function resolveParentFolder(options: {
     personalWorkspace?: boolean;
     tenant?: string;
     loginValidity?: number;
+    /** Pin folder-lookup auth to this exact `.uipath/.auth` path, forwarded to
+     *  `resolvePersonalWorkspace`/`resolveFolder` so it matches the deploy auth. */
+    envFilePath?: string;
 }): Promise<string | undefined>;

package/dist/services/pack-command-service.d.ts

@@ -19,6 +19,5 @@ export declare class PackCommandService {
      */
     executeAsync(solutionPath: string, options: PackCommandOptions): Promise<ToolResult>;
     private ensurePackagerAsync;
-    private readFileAsUint8Array;
     private createPackOptions;
 }

package/dist/services/pack-service.d.ts

@@ -1,13 +1,3 @@
-import "@uipath/packager-tool-apiworkflow";
-import "@uipath/packager-tool-bpmn";
-import "@uipath/packager-tool-case";
-import "@uipath/packager-tool-connector";
-import "@uipath/packager-tool-flow";
-import "@uipath/packager-tool-functions";
-import "@uipath/packager-tool-webapp";
-import "@uipath/packager-tool-workflowcompiler";
-import "@uipath/resource-builder-tool";
-import "@uipath/tool-agent";
 import type { PackCommandOptions } from "../models/pack-command-types";
 export type { PackCommandOptions };
 /**

package/dist/services/packages-list-service.d.ts

@@ -22,6 +22,8 @@ export type ListPackagesFailureReason = "auth_failed" | "list_request_failed";
 export interface ListPackagesOptions {
     /** Override the active tenant for auth. The CLI's deprecated `--tenant` flag flows through here. */
     tenant?: string;
+    /** Pin auth to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
     /** Max packages to fetch. Default `DEFAULT_PAGE_SIZE`. */
     limit?: number;
     /** Column to sort by. Default `"publishDate"`. */

package/dist/services/personal-workspace-deploy.d.ts

@@ -0,0 +1,28 @@
+import type { SolutionAuthContext } from "./auth-helper";
+export interface PersonalWorkspaceDeployResult {
+    deploymentName: string;
+    packageName: string;
+    packageVersion: string;
+    folderFQN: string;
+}
+/**
+ * Deploy a Personal-Workspace-feed solution package via the Automation
+ * Solutions auto-deploy endpoint.
+ *
+ * The tenant `deploy run` path (Pipelines `deploy-from-package`) resolves the
+ * package from the tenant feed and cannot see a PW-feed package. This path
+ * uses the feed-aware `POST /api/deployments/deploy` endpoint instead:
+ *  - the PW folder key scopes both the package lookup and the deploy (header
+ *    `X-UIPATH-FolderKey`);
+ *  - `overwrites: []` lets the server apply the package's default resource
+ *    configuration (no caller-side overwrite computation);
+ *  - the endpoint auto-names the deployment `AutoDeploy-<solution>` and
+ *    auto-activates — matching Studio Web's PW autoDeploy behavior.
+ */
+export declare function deployToPersonalWorkspace(auth: SolutionAuthContext, params: {
+    packageName: string;
+    packageVersion: string;
+}, options?: {
+    tenant?: string;
+    loginValidity?: number;
+}): Promise<PersonalWorkspaceDeployResult>;

package/dist/services/personal-workspace-resolver.d.ts

@@ -25,4 +25,4 @@ export interface ResolvedPersonalWorkspace {
  * @param options - tenant and login validity for API authentication
  * @returns Resolved Personal Workspace `{ key, name }`
  */
-export declare function resolvePersonalWorkspace(options?: Pick<CreateApiClientOptions, "tenant" | "loginValidity">): Promise<ResolvedPersonalWorkspace>;
+export declare function resolvePersonalWorkspace(options?: Pick<CreateApiClientOptions, "tenant" | "loginValidity" | "envFilePath">): Promise<ResolvedPersonalWorkspace>;

package/dist/services/publish-service.d.ts

@@ -1,8 +1,12 @@
 /** Discriminator for {@link PublishFailure}; library callers can ignore the tag and read `.message` / `.ok`. */
-export type PublishFailureReason = "auth_failed" | "file_not_found" | "not_a_zip" | "file_read_failed" | "upload_failed" | "upload_version_conflict" | "upload_network" | "poll_timeout" | "poll_failed" | "poll_aborted" | "publish_failed";
+export type PublishFailureReason = "auth_failed" | "file_not_found" | "not_a_zip" | "file_read_failed" | "personal_workspace_resolution_failed" | "upload_failed" | "upload_version_conflict" | "upload_network" | "poll_timeout" | "poll_failed" | "poll_aborted" | "publish_failed";
 export interface PublishOptions {
     /** Override the active tenant for auth resolution. The CLI's deprecated `--tenant` flag flows through here. */
     tenant?: string;
+    /** Pin auth to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
+    /** Upload into the current user's Personal Workspace feed instead of the tenant feed. */
+    personalWorkspace?: boolean;
     /** Wait until the published package reaches a terminal state. Default `false`. */
     wait?: boolean;
     /** Timeout in seconds for the poll loop when `wait` is true. Default `360`. */
@@ -16,14 +20,19 @@ export interface PublishOptions {
 }
 export interface PublishSuccess {
     ok: true;
-    /** Package name as published. */
-    packageName: string;
-    /** Package version (semver). */
-    packageVersion: string;
-    /** Orchestrator's stable key for this exact version (uuid). */
+    /** Orchestrator's stable key for this exact version (uuid). Always populated. */
     packageVersionKey: string;
-    /** Terminal state when `wait: true` (`"Ready"`/`"Active"`), else the upload's immediate state. Plain string to keep `.d.ts` off the private pipelines-sdk enum. */
-    state: string;
+    /**
+     * Package name as published. Optional because PW publish enriches metadata
+     * via a follow-up `packagesGetVersion` call that can briefly 404 due to
+     * feed indexing lag — when that happens, the upload is still authoritative
+     * but the human-readable name is absent.
+     */
+    packageName?: string;
+    /** Package version (semver). Optional for the same reason as `packageName`. */
+    packageVersion?: string;
+    /** Terminal state when `wait: true` (`"Ready"`/`"Active"`), else the upload's immediate state. Optional for the same reason. */
+    state?: string;
 }
 export interface PublishFailure {
     ok: false;
@@ -39,5 +48,14 @@ export type PublishResult = PublishSuccess | PublishFailure;
  * solution feed and optionally polls to a terminal state. Returns a tagged
  * {@link PublishResult} for expected failures; re-throws only on unexpected
  * SDK errors. Does not touch `OutputFormatter` / `processContext`.
+ *
+ * Two upload paths:
+ *  - **Tenant feed (default)**: `PipelinesApi.pipelinesPackageUpload` —
+ *    returns a full DTO including packageName/version/state. The CI service
+ *    principal is authorized for this endpoint; do not unify on the AS path.
+ *  - **Personal Workspace** (`personalWorkspace: true`): `PackagesApi.packagesUpload`
+ *    with `locationKey` set to the PW folder key — returns a packageVersionKey
+ *    GUID only. A follow-up `packagesGetVersion` enriches metadata best-effort
+ *    (can 404 on indexing lag — handled gracefully).
  */
 export declare function publishSolutionAsync(packagePath: string, options?: PublishOptions): Promise<PublishResult>;

package/dist/services/resource-refresh-service.d.ts

@@ -3,6 +3,8 @@ export type ResourceRefreshFailureReason = "solution_not_found" | "not_a_solutio
 export interface ResourceRefreshOptions {
     /** Minimum minutes before token expiration to trigger a refresh. Default `10` (matches the CLI's `--login-validity`). */
     loginValidity?: number;
+    /** Pin auth to this exact `.uipath/.auth` path. */
+    envFilePath?: string;
 }
 export interface ResourceRefreshSuccess {
     ok: true;
@@ -23,7 +25,7 @@ export interface ResourceRefreshFailure {
 }
 export type ResourceRefreshResult = ResourceRefreshSuccess | ResourceRefreshFailure;
 /**
- * Programmatic core of `uip solution resource refresh`: re-scans every project's
+ * Programmatic core of `uip solution resources refresh`: re-scans every project's
  * `bindings_v2.json` and syncs resource declarations into the solution, importing
  * from Orchestrator when a match exists and virtualizing the rest. Returns a tagged
  * {@link ResourceRefreshResult}; re-throws only on unexpected errors. Mirrors

package/dist/services/solution-packager-helpers.d.ts

@@ -0,0 +1,25 @@
+import type { IFileSystem } from "@uipath/filesystem";
+import { type ISolutionPackager, type SolutionPackOptions } from "@uipath/solution-packager/node";
+import { LogLevel } from "@uipath/solutionpackager-tool-core";
+/**
+ * Shared building blocks for the solution packager command services
+ * (`pack`, `restore`). Both run the same SDK packager with the same auth
+ * connection and log-level mapping; keeping that logic here avoids duplicating
+ * it across the per-command services.
+ */
+/** Create a node solution packager wired to the CLI logger and telemetry. */
+export declare function createSolutionPackager(): Promise<ISolutionPackager>;
+/**
+ * Read a solution file as a `Uint8Array`. `IFileSystem.readFile` may hand back
+ * a `Buffer`/array depending on the backend, so coerce it before passing the
+ * bytes to the packager.
+ */
+export declare function readSolutionFileAsUint8Array(fs: IFileSystem, filePath: string): Promise<Uint8Array>;
+/** Map the CLI logger level to the packager SDK log level (defaults to Error). */
+export declare function resolveSdkLogLevel(): LogLevel;
+/**
+ * Attach the authenticated cloud connection to the packager options when a
+ * session is available. No-op when the user is not logged in (the packager
+ * then runs against public feeds only).
+ */
+export declare function applyAuthConnection(options: SolutionPackOptions, loginValidity?: number): Promise<void>;

package/dist/services/sync-resources-from-bindings.d.ts

@@ -66,6 +66,14 @@ export interface RcsMatch {
         path?: string;
     };
 }
+/**
+ * Find a resource in RCS by key (UUID). RCS's `SearchFolderEntities` endpoint
+ * has no key-based filter — only `name`/`entityTypes`/`entitySubTypes`. We
+ * paginate all resources of this kind and filter locally by key, exiting
+ * early on the match. Used for connections, whose binding carries the UUID
+ * directly via `bindingKey`.
+ */
+export declare function findResourceByKeyInRcs(builder: ISolutionBuilder, kind: string, expectedKey: string, folderPath?: string, propagateErrors?: boolean): Promise<RcsMatch | undefined>;
 /**
  * Page through RCS for a given (kind, name) and collect every match. Returns
  * an empty array on lookup error (logged as a warning). Callers decide what

package/dist/templates/AGENTS.md

@@ -45,10 +45,12 @@ You must manage membership via the CLI, never by editing the manifest. All these
 |---|---|
 | Create a solution | `uip solution init <name>` |
 | Register an existing subfolder of the solution dir as a project (no copying — use after scaffolding *inside* the solution dir, e.g. `uip rpa create-project --location <solution-dir>`) | `uip solution project add <project-path> [<solution-file>]` |
-| Add a project from outside the solution — copies the folder at `<path>` into the solution dir and registers it (`<path>` is a local filesystem path) | `uip solution project import --source <path>` |
+| Add a project from outside the solution — copies the folder at `<path>` into the solution dir and registers it (`<path>` is a local filesystem path) | `uip solution project import <path>` |
 | Unregister a project (does not delete the project files on disk) | `uip solution project remove <project-path> [<solution-file>]` |
 | List projects in the solution | `uip solution project list` |
 
+The `uip ... init` scaffolders (`agent init`, `maestro flow init`, `maestro bpmn init`, `maestro case init`, `api-workflow init`) **auto-register** the new project when run inside a solution directory — they walk up for the enclosing `.uipx` and add it to `Projects[]` automatically, so a separate `project add` is not needed. Pass `--skip-solution-registration` to scaffold standalone without registering; the output's `Data.SolutionRegistration.Status` is then `OptedOut`. The full set of `Status` values is: `Registered` / `AlreadyRegistered` (added in this run / already present), `NotInSolution` (no enclosing `.uipx` found), `OptedOut` (`--skip-solution-registration` passed), `Skipped` (a candidate solution was found but registration was not safe to attempt — e.g. multiple `.uipx` in one directory, or the project sits outside the solution dir), and `Failed` (manifest read/parse/write error).
+
 ## Project Types
 
 A solution can contain multiple projects of different types. The table below lists each project type and the `uip` command that scaffolds a fresh one (or marks the row when no scaffolding command exists).
@@ -64,13 +66,13 @@ A solution can contain multiple projects of different types. The table below lis
 | `Agent` | LLM agent project — **low-code** (configured via `agent.json`; no Python) or **coded** (Python: LangGraph / LlamaIndex / OpenAI Agents). Both subtypes share `ProjectType: "Agent"`; the discriminator is `agent.json#type`. | `uip agent init <path>` (low-code) · `uip codedagent new [name]` (coded — see the `uipath-agents` skill for the full flow) | `uipath-agents` |
 | `AppV2` | Coded App — web application | `uip codedapp init <path>` | `uipath-coded-apps` |
 | `Function` | UiPath Function (JS / TS / Python) | `uip functions new [name]` | none |
-| `Api` | API Workflow project | no CLI scaffolding | none |
+| `Api` | API Workflow project | `uip api-workflow init <name>` | none |
 | `Connector` | Integration Service connector | no CLI scaffolding — use `uip is connectors` to list / get / export existing connectors | none |
 | `WebApp` | Legacy low-code UiPath App (the coded variant is `AppV2`) | no CLI scaffolding | none |
 
 All skill should be installed by running the command: `uip skills install`. The general-purpose `uipath-platform` skill covers what isn't in a type-specific skill.
 
-The type lives in either `project.uiproj` (top-level `ProjectType`) or `project.json` (`designOptions.outputType`, falling back to top-level `ProjectType` when `outputType` is absent — read or write either field). After scaffolding, register the project with the solution: `uip solution project import --source <path>`. If you pass an unknown type to that command, it rejects with the exhaustive accepted list — trust that error over this table.
+The type lives in either `project.uiproj` (top-level `ProjectType`) or `project.json` (`designOptions.outputType`, falling back to top-level `ProjectType` when `outputType` is absent — read or write either field). The `init` scaffolders above auto-register when run inside a solution directory (unless `--skip-solution-registration` is passed). For other scaffolders, register the project with the solution after scaffolding: use `uip solution project add <project-path> [<solution-file>]` when the project already lives inside the solution directory (registers in place, no copy), or `uip solution project import <path>` to copy a project from outside the solution dir into it and register it. If you pass an unknown type to those commands, they reject with the exhaustive accepted list — trust that error over this table.
 
 ## End-to-End Lifecycle
 
@@ -83,6 +85,13 @@ uip login
 #    Non-interactive (CI / CD) with client credentials:
 uip login --client-id <ID> --client-secret <SECRET> --tenant <TENANT>
 
+# 1a. (Optional) Restore project dependencies before packing. Resolves NuGet
+#     deps (including authenticated Orchestrator feeds) so pack can compile.
+#     Useful in CI: login -> restore -> pack. Takes <solutionPath> only; it
+#     does not produce a package. Pack also restores internally, so this is an
+#     optimization, not a requirement.
+uip solution restore .
+
 # 2. Pack the solution into a .zip. Two positional args:
 #    <solutionPath>  — solution dir (containing .uipx) or a .uis file
 #    <output-path>   — directory where the .zip is written (required unless --dry-run)
@@ -121,11 +130,15 @@ uip solution deploy list
 ```bash
 uip solution deploy run --skip-activate ...                      # leaves "Inactive (Ready to activate)"
 uip solution deploy activate <deployment-name>     # activate later
-uip solution deploy uninstall <deployment-name>    # remove the deployment + its resources
+uip solution deploy uninstall <deployment-name> --yes   # remove the deployment + its resources (--yes required; the CLI never prompts)
 ```
 
 `uninstall` and `activate` take the deployment name as a **positional** argument (no `--name` flag). `status` takes the **pipeline deployment ID** (the GUID returned by `deploy run`), also positional.
 
+## Package Signing
+
+`solution pack` can sign each packed project `.nupkg` with a code-signing certificate. Signing is opt-in: add `--signing-certificate-path <cert.pfx>` to the pack command. The certificate password (`--signing-certificate-password`) is optional — passing it as `env.VAR` (e.g. `env.SIGNING_PASSWORD`) is recommended, though an inline value also works. An optional timestamp server is set with `--signing-timestamp-server <url>`.
+
 ## Studio Web (Browser Editing)
 
 Studio Web is a separate target from the Orchestrator deploy chain — it hosts a browser-based collaborative editor for solutions. The `solution upload` command pushes the local solution there and returns a `DesignerUrl` to open the solution in a browser; this is independent of `pack` / `publish` / `deploy` and does *not* produce a runtime-deployable artifact.
@@ -134,7 +147,7 @@ Studio Web is a separate target from the Orchestrator deploy chain — it hosts
 uip solution upload .                      # upload solution dir to Studio Web as a new solution; returns DesignerUrl
 uip solution upload . --force              # force-replace the existing Studio Web solution referenced by .uipx (destroys cloud version history)
 uip solution download <solution-id>        # round-trip a Studio Web solution back to disk
-uip solution delete <solution-id>          # remove a solution from Studio Web
+uip solution delete <solution-id> --yes    # remove a solution from Studio Web (--yes required; the CLI never prompts)
 ```
 
 `upload` accepts a solution directory, a `.uipx` file, or a `.uis` file. It probes Studio Web for the bundled `SolutionId` first: if the cloud has no solution with that id, the upload imports as new; if a solution with that id already exists, the upload is refused unless `--force` is passed. Forcing replaces the cloud project in place and **wipes its Studio Web version history**, so use `--force` deliberately. To upload a copy as an unrelated cloud solution instead of overwriting, scaffold a fresh solution with `uip solution init` (or remove the `SolutionId` from the local `.uipx`) and re-run upload.
@@ -146,15 +159,15 @@ Each project declares the resources it needs (assets, queues, buckets, processes
 After editing a project's bindings, or after `solution project import` (which doesn't auto-sync resources), reconcile the solution-level inventory:
 
 ```bash
-uip solution resource refresh     # re-scan every project, sync new / removed resources
+uip solution resources refresh     # re-scan every project, sync new / removed resources
 ```
 
-`solution resource refresh` creates new resources for bindings not yet in the solution and imports from Orchestrator when a matching resource already exists.
+`solution resources refresh` creates new resources for bindings not yet in the solution and imports from Orchestrator when a matching resource already exists.
 
 Inspect the current solution inventory:
 
 ```bash
-uip solution resource list        # everything declared in this solution
+uip solution resources list        # everything declared in this solution
 ```
 
 ## Deployment Configuration
@@ -196,6 +209,8 @@ The CLI talks about the same resource types Orchestrator does:
 - **Connections** — Integration Service connections to external systems (Salesforce, ServiceNow, …).
 - **Processes / Releases** — published packages bound to a folder.
 - **Triggers** & **Webhooks** — event-, time-, or queue-based job firing; outbound HTTP notifications.
+- **Entities** — Data Service tables. Add or bind with kind `Entity`.
+- **ChoiceSets** — enumerations used by entity fields. Add with kind `ChoiceSet`.
 
 Resources outside a solution are managed under the orchestrator tool, which exposes per-type subgroups (`uip or assets …`, `uip or queues …`, `uip or buckets …`, `uip or bucket-files …`, `uip or libraries …`, `uip or queue-items …`, `uip or triggers …`, `uip or webhooks …`). Run `uip or --help` for the live list. Example:
 
@@ -251,9 +266,9 @@ Adjacent groups commonly used alongside solutions:
 |---|---|
 | `Not authenticated` / 401 | `uip login`, then re-run |
 | Command targets the wrong tenant | `uip login tenant set <tenant>`; verify with `uip login status` |
-| Pack succeeds but publish 409s | Version conflict — bump the version (`uip solution pack . ./out -v <new-version>`) or delete the colliding version with `uip solution packages delete <package-name> <version>` (only if intentional) |
+| Pack succeeds but publish 409s | Version conflict — bump the version (`uip solution pack . ./out -v <new-version>`) or delete the colliding version with `uip solution packages delete <package-name> <version> --yes` (only if intentional; `--yes` required) |
 | `deploy run` fails on a resource conflict | `uip solution deploy config link config.json <resource> --name <existing> --folder-path <path>` to map to the existing one, or change `conflictFixingAction` via `config set` |
-| `Resource not found` after deploy | `uip solution resource refresh` to re-sync from each project's `bindings_v2.json`; if still missing, the resource was never declared in any project |
+| `Resource not found` after deploy | `uip solution resources refresh` to re-sync from each project's `bindings_v2.json`; if still missing, the resource was never declared in any project |
 | Output looks empty | You may have redirected stderr — confirmations and errors go there. Re-run without `2>` |
 
 ---