@uipath/skills 1.195.0 → 1.196.0

package/skills/{uipath-solution → uipath-planner}/assets/templates/flow-sdd-template.md

@@ -23,7 +23,7 @@
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §3 Nodes Inventory + §7 Integrated Components |
 | **Tasks file** | `<FLOW_NAME_KEBAB>-tasks.md` |
-| **Generated by** | uipath-solution v<VERSION> |
+| **Generated by** | uipath-planner |
 | **Generation date** | <YYYY-MM-DD> |
 
 ---
@@ -31,7 +31,7 @@
 <!--
 EMIT THIS BLOCK ONLY when Execution autonomy: autonomous.
 Skip entirely in interactive mode (decisions were checkpoint-reviewed).
-See sdd-generation-guide.md Phase 3 Step 3a for the format spec.
+See sdd-generation-guide.md Phase 3 Step 2 item 3 for the format spec.
 Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 -->
 ## Decisions Made
@@ -48,7 +48,7 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.
-See sdd-generation-guide.md Phase 3 Step 3 for the format spec.
+See sdd-generation-guide.md Phase 3 Step 2 item 4 for the format spec.
 -->
 ## Action Required — SME Review Items
 
@@ -233,7 +233,7 @@ flowchart LR
 ### Orchestrator Deployment Target
 
 - [ ] Studio Web (default)
-- [ ] Orchestrator (requires `uipath-platform` skill)
+- [ ] Orchestrator (`.uipx`-wrapped solution → `uipath-solution`; non-solution single package → `uipath-platform`)
 
 ---
 

package/skills/{uipath-solution → uipath-planner}/assets/templates/rpa-sdd-template.md

@@ -22,9 +22,9 @@
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
 | **SDD scope** | <single-product \| solution> |
-| **Project list section** | <§10 \| §3 \| Project Inventory> |
+| **Project list section** | <§11 \| §10 + §11 \| Project Inventory> |
 | **Tasks file** | `<PROCESS_NAME_KEBAB>-tasks.md` |
-| **Generated by** | uipath-solution v<VERSION> |
+| **Generated by** | uipath-planner |
 | **Generation date** | <YYYY-MM-DD> |
 
 ---
@@ -32,7 +32,7 @@
 <!--
 EMIT THIS BLOCK ONLY when Execution autonomy: autonomous.
 Skip entirely in interactive mode (decisions were checkpoint-reviewed).
-See sdd-generation-guide.md Phase 3 Step 3a for the format spec.
+See sdd-generation-guide.md Phase 3 Step 2 item 3 for the format spec.
 -->
 ## Decisions Made
 
@@ -50,7 +50,7 @@ See sdd-generation-guide.md Phase 3 Step 3a for the format spec.
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.
-See sdd-generation-guide.md Phase 3 Step 3 for the format spec.
+See sdd-generation-guide.md Phase 3 Step 2 item 4 for the format spec.
 -->
 ## Action Required — SME Review Items
 
@@ -275,7 +275,7 @@ public enum <EnumName>
 
 ## 9. Application Inventory
 
-> **List all applications.** For SaaS integrations (Salesforce, Jira, etc.), flag `Integration Service — <CONNECTOR_SLUG>` in the Access Method column (e.g., `Integration Service — salesforce`) — the implementation plan will create a task to configure the connector, and §14 only needs `UiPath.IntegrationService.Activities` for all connectors combined. For email, specify the protocol (IMAP, O365 Graph API, Exchange/EWS, POP3) — do not default to O365. See the [Package Selection Guide](../../references/design/package-selection-guide.md) for the full Access Method → Package mapping.
+> **List all applications.** For SaaS integrations (Salesforce, Jira, etc.), flag `Integration Service — <CONNECTOR_SLUG>` in the Access Method column (e.g., `Integration Service — salesforce`) — the implementation plan will create a task to configure the connector, and §14 only needs `UiPath.IntegrationService.Activities` for all connectors combined. For email, specify the protocol (IMAP, O365 Graph API, Exchange/EWS, POP3) — do not default to O365. See the [Package Selection Guide](../../references/package-selection-guide.md) for the full Access Method → Package mapping.
 
 | # | Application | Interface | Access Method | Role | Interaction Pattern | Session Management |
 |---|---|---|---|---|---|---|
@@ -459,7 +459,7 @@ Sub-type reference:
 
 > **For Master Project:** specify the mode per sub-project if they differ. A Dispatcher may be XAML while a Performer with heavy data logic is Hybrid.
 >
-> **Before recommending Coded C#:** verify at least two checklist items from the [RPA Product Guide § Selection checklist before recommending Coded C#](../../references/design/rpa-product-guide.md#selection-checklist-before-recommending-coded-c) are true. "Cleaner control flow over a UI loop" is **not** a sufficient justification — XAML already has Try/Catch + Retry Scope + For Each over UIA activities. If the process body is >70% UI automation with minimal data shaping, recommend **XAML** or **Hybrid**.
+> **Before recommending Coded C#:** verify at least two checklist items from the [RPA Product Guide § Selection checklist before recommending Coded C#](../../references/rpa-product-guide.md#selection-checklist-before-recommending-coded-c) are true. "Cleaner control flow over a UI loop" is **not** a sufficient justification — XAML already has Try/Catch + Retry Scope + For Each over UIA activities. If the process body is >70% UI automation with minimal data shaping, recommend **XAML** or **Hybrid**.
 
 **Recommendation:** <XAML / Coded C# / Hybrid>
 
@@ -473,7 +473,7 @@ Sub-type reference:
 
 ## 14. Packages
 
-> **List required NuGet packages only.** For Master Project: one table per sub-project. Infer packages from §9 Application Inventory and the process steps using the [Package Selection Guide](../../references/design/package-selection-guide.md) — it contains the full Application-Type → Package matrix, Integration Service vs NuGet decision rules, and a selection checklist.
+> **List required NuGet packages only.** For Master Project: one table per sub-project. Infer packages from §9 Application Inventory and the process steps using the [Package Selection Guide](../../references/package-selection-guide.md) — it contains the full Application-Type → Package matrix, Integration Service vs NuGet decision rules, and a selection checklist.
 >
 > **Do NOT list Integration Service connectors in this table.** Integration Service connections are declared in §9 Application Inventory (Access Method = `Integration Service — <CONNECTOR_SLUG>`) and run on `UiPath.IntegrationService.Activities` — that package is the only §14 entry needed for them. See the Package Selection Guide's "Integration Service Connectors vs NuGet Packages" section for side-by-side examples.
 
@@ -509,7 +509,7 @@ Sub-type reference:
 | **Cross-platform / Windows-only** | <Windows Legacy / Windows / Cross-platform> |
 | **Recommended screen resolution** | <e.g., 1920×1080> (UI automation projects only) |
 | **Source repository** | <GIT_URL_OR_SME_REVIEW> |
-| **Shared libraries referenced** | <COMMA_SEPARATED_LIBRARY_NAMES_OR_NONE — from the Phase 1 Org Context question> |
+| **Shared libraries referenced** | <COMMA_SEPARATED_LIBRARY_NAMES_OR_NONE — from Step 2.5 Tenant Library Discovery> |
 
 ### Development & Production Hosts
 
@@ -593,12 +593,12 @@ Implementation tasks **do not live in this SDD** — they live in the planner's
 
 ### Terminal artefact — a packed `.uipx` solution
 
-The build is not finished when the project folder compiles. **The terminal artefact of an SDD-driven build is a packed `.uipx` solution**, not a bare project folder. After the implementation specialist (`uipath-rpa`, `uipath-agents`, etc.) reports its tasks complete, return to the **`uipath-solution` Operate half** and run:
+The build is not finished when the project folder compiles. **The terminal artefact of an SDD-driven build is a packed `.uipx` solution**, not a bare project folder. After the implementation specialist (`uipath-rpa`, `uipath-agents`, etc.) reports its tasks complete, load the **`uipath-solution`** skill and run:
 
 ```bash
 uip solution init <SOLUTION_NAME>
 uip solution project add <PROJECT_PATH> [--solution-file <SOLUTION_FILE>]    # repeat per project in the unified list
-uip solution resource refresh
+uip solution resources refresh
 uip solution pack <SOLUTION_DIR> <OUTPUT_DIR>
 ```
 
@@ -606,7 +606,7 @@ For a single-project build, the solution wrap is still required — `uip solutio
 
 For multi-project (Master Project) builds, run `uip solution project add` once per sub-project (Dispatcher / Performer / Reporting / Library / Test Automation) before `pack`.
 
-Full `uip solution` lifecycle: load `/uipath:uipath-solution` Operate half.
+Full `uip solution` lifecycle: load the `uipath-solution` skill.
 
 ---
 

package/skills/uipath-planner/references/multi-skill-patterns-guide.md

@@ -71,7 +71,7 @@ A request is **single-skill** when:
 3. uipath-solution     → publish and deploy to Orchestrator via `uip solution`
 ```
 
-`uipath-maestro-flow` follows the plan's `Solution scope` (SW or local); Orchestrator deploy of the wrapping solution requires `uipath-solution`.
+`uipath-maestro-flow` follows the plan's `Solution scope` (SW or local); Orchestrator deploy of the wrapping `.uipx` solution requires `uipath-solution`. For a non-solution single package (no `.uipx` wrapper), route the deploy step to `uipath-platform` instead.
 
 ## Pattern 5 — Agent that uses RPA processes as tools
 
@@ -86,7 +86,7 @@ A request is **single-skill** when:
 6. uipath-agents   → deploy
 ```
 
-## Pattern 8 — Build an AgentHub MCP server
+## Pattern 6 — Build an AgentHub MCP server
 
 **When it applies:** the request is to register an AgentHub MCP server that wraps a coded agent or uses Orchestrator-asset-backed auth that does not exist yet. Pure `uipath-mcp-servers` work — `uipath` / `command` / `platform` servers, `remote`/`swagger` with auth assets already in place, or any `is-activity` tool authoring against existing IS connections — is single-skill; go straight to `uipath-mcp-servers`.
 
@@ -118,7 +118,7 @@ When deriving tasks from an SDD, the planner picks a pattern based on the SDD's
 | Solution with Flow + RPA + Agents, components built fresh in this session | Pattern 2 expanded across all included products |
 | Solution with Flow consuming pre-published Orchestrator resources | Pattern 3 |
 | Solution overview SDD | Compose multiple patterns; respect cross-product integration order from §Cross-Project Data Flow |
-| API Workflow (single product) | API Workflow specialist + `uipath-solution` for deploy + testing |
+| API Workflow (single product) | `uipath-api-workflow` + `uipath-solution` for deploy + testing |
 | Agent with RPA tools in §3 Tools | Pattern 5 |
 
 Cross-project integration order (general rule): **dependencies before dependents**. Build callable resources (RPA processes, API Workflows, agents-as-tools) before the products that consume them (Flows, Cases, parent agents).

package/skills/uipath-planner/references/non-pdd-lane-guide.md

@@ -8,6 +8,10 @@ When the planner is invoked without an SDD (the entry guard found no `## Planner
 
 Bundle every unresolved question from the table below into **one** `AskUserQuestion` call. Do not ask one at a time; do not split across turns. If a question is already resolved from the user's request, omit it from the batch. If **all** are resolved, do not call `AskUserQuestion` at all and record the inferred values in the plan header with a one-line note in Decisions & Trade-offs.
 
+Question phrasing follows the rules in [pdd-driven-lane-guide.md → Step 5](pdd-driven-lane-guide.md#step-5--ui-element-targeting-only-when-9-contains-ui-applications): no internal jargon, no domain or app names in question text.
+
+If the entry guard classified a provided document as "Other context", read it before building the batch — any question its content answers counts as resolved, and the content feeds the plan.
+
 ### Skip-rules table (apply before building the batch)
 
 | Question | Skip when | Default if skipped |
@@ -15,7 +19,7 @@ Bundle every unresolved question from the table below into **one** `AskUserQuest
 | Q1 Generation approach | Request is simple and well-defined; the user is modifying an existing automation; or the task is single-skill single-step. | `simultaneous` |
 | Q2 Execution autonomy | Explore-first mode (the approval gate at plan time already scopes autonomy). | `autonomous` |
 | Q3 Project type fallback | Project type resolves via explicit naming, keyword signals, or filesystem (Step 3) — see "Project type" below. | `RPA workflow (XAML)` |
-| Q5 Solution scope (Flow only) | Plan does not load `uipath-maestro-flow`; OR the user already stated intent (e.g., "upload to Studio Web", "keep it local", "just build it"); OR the plan contains no generation skill. | Omit `Solution scope` field from the plan header entirely. |
+| Q4 Solution scope (Flow only) | Plan does not load `uipath-maestro-flow`; OR the user already stated intent (e.g., "upload to Studio Web", "keep it local", "just build it"); OR the plan contains no generation skill. | Omit `Solution scope` field from the plan header entirely. |
 
 The batch contains only the questions that survive the skip rules. Build the `AskUserQuestion` call as one tool invocation with one `questions` array entry per surviving item.
 
@@ -65,9 +69,9 @@ If the request is genuinely vague ("I want to build something with UiPath") AND
 > 3. **Flow** — visual node-based orchestration connecting multiple automations
 > 4. **Application** — custom UI deployed as a UiPath App
 
-If the user picks **RPA workflow**, record `Project type: XAML` and move on. **Never follow up with "XAML or C#?"** — that authoring-mode decision belongs to `uipath-rpa`, not the planner. Coded mode is set only when the user independently says "coded workflow" or ".cs file" (which rule 1 above already honors); never as a follow-up.
+If the user picks **RPA workflow**, record `Project type: XAML` and move on. **Never follow up with "XAML or C#?"** — that authoring-mode decision belongs to `uipath-rpa`, not the planner. Coded mode is set only when the user independently says "coded workflow" or ".cs file" (which rule 1 above already honors); never as a follow-up. **Never surface C# coded as a top-level recommendation for routine UI automation** — the coded fallback is an internal `uipath-rpa` decision.
 
-### Question 5 — Solution scope (Flow projects only)
+### Question 4 — Solution scope (Flow projects only)
 
 **Include this question in the Step 1 batch only when the plan loads `uipath-maestro-flow`.** For RPA / AI Agent / Application plans, omit the question entirely **and omit the `Solution scope` field from the plan header** — no other specialist reads it.
 
@@ -78,7 +82,7 @@ If the user picks **RPA workflow**, record `Project type: XAML` and move on. **N
 
 Record the answer in the plan header as `Solution scope: SW | local`. `uipath-maestro-flow` reads this field at runtime to decide whether to publish at the end.
 
-**Skip Q5** (and omit the field from the header) when:
+**Skip Q4** (and omit the field from the header) when:
 
 - The plan does not load `uipath-maestro-flow`.
 - The user's request already states the intent (e.g., "upload to Studio Web", "keep it local", "just build it") — record directly.
@@ -169,7 +173,7 @@ Option 2: parse the request fresh, run identity-matching against the old file (p
 
 ## Lane B budget
 
-Step 1 is **always one batched call** (Q1 + Q2 + optional Q3 in a single `AskUserQuestion`); Step 4 is one batched call when the plan has UI automation; resume adds one. The realistic floor is 0 calls and the realistic ceiling is 3.
+Step 1 is **always one batched call** (Q1 + Q2 + optional Q3/Q4 in a single `AskUserQuestion`); Step 4 is one batched call when the plan has UI automation; resume adds one. The realistic floor is 0 calls and the realistic ceiling is 3.
 
 | Scenario | `AskUserQuestion` calls |
 |---|---|
@@ -179,6 +183,6 @@ Step 1 is **always one batched call** (Q1 + Q2 + optional Q3 in a single `AskUse
 | Vague request, with UI automation | **2** (Step 1 batched — Q3 is part of the same batch — + Step 4 UI batch) |
 | Resume scenario | **+1** (continue/regenerate) |
 | Realistic maximum | **3** |
-| Hard cap (Critical Rule 3) | **5** |
+| Hard cap (per-phase prompt budget, Critical Rules) | **5** |
 
 The 5-call hard cap is defined in the planner's Critical Rules. If batching collapses the elicitation correctly, you should never approach it.

package/skills/uipath-planner/references/pdd-driven-lane-guide.md

@@ -2,23 +2,25 @@
 
 When the planner detects a Solution Design Document (SDD) at entry, it runs Lane A — read the SDD, derive tasks, hand off to specialists. This guide covers Lane A end-to-end.
 
-> Lane A is reached from the entry guard when the input file contains the marker heading `## Planner Handoff` (the load-bearing detection contract from `uipath-solution`). See SKILL.md for the entry guard logic.
+> Lane A is reached from the entry guard when the input file contains the marker heading `## Planner Handoff` or the `<!-- planner-handoff:v1 -->` marker (the load-bearing detection contract written by Phase D, or present in a hand-written SDD — either signal alone is sufficient). See SKILL.md for the entry guard logic.
 
 ## Step 1 — Read the SDD's Planner Handoff header
 
-The header appears immediately after `## Document History` in every SDD. Read these 6 fields:
+The header appears near the top of every SDD — immediately after `## Document History` in per-project SDDs, or as section 2 (right after Solution Overview) in a solution-overview SDD. Read these 6 fields:
 
 | Field | What the planner does with it |
 |---|---|
 | **Execution autonomy** | `interactive` → enter plan mode for task review before execution. `autonomous` → emit live tasks directly. |
 | **SDD scope** | `single-product` → one SDD file owns one task list. `solution` → one solution-overview SDD plus one per-project SDD; tasks span all projects. |
 | **Project list section** | Tells the planner where to find the unified project list (e.g., `§10` for RPA, `§3 + §7` for Flow, `Project Inventory` for solution overview). |
-| **Tasks file** | Where to write `<process>-tasks.md`. Solution-design proposes a path; planner respects it. |
-| **Generated by** | `uipath-solution v<VERSION>`. Used in the summary output to tell the user the SDD's provenance. |
+| **Tasks file** | Where to write `<process>-tasks.md`. Phase D proposes a path; Lane A respects it. |
+| **Generated by** | `uipath-planner`. Used in the summary output to tell the user the SDD's provenance. |
 | **Generation date** | `YYYY-MM-DD`. Shown to the user in the summary. |
 
 **Missing or malformed fields:** default `Execution autonomy` to `interactive` (safer), default `SDD scope` to `single-product`, infer `Project list section` from the template type, default `Tasks file` to `<sdd-basename-without-sdd>-tasks.md`. **Track each defaulted field** in a session-local list — Step 8 surfaces them in the user-facing summary so the human reviewer can correct the SDD before tasks are emitted. Do not silently swallow the defaults.
 
+**Autonomy override on resume:** if the user's resume message explicitly requests review or interactive handling, honour the message over the header's `Execution autonomy` value (do not re-ask).
+
 ## Step 2 — Check for an existing tasks.md
 
 If the file at `Tasks file` already exists (resume scenario), ask the user via `AskUserQuestion`:
@@ -71,14 +73,14 @@ Based on the project list, pick the matching pattern from [multi-skill-patterns-
 | RPA Master Project | Pattern 1 per sub-project, integrated via shared queues; cross-project deploy via `uipath-solution` (single `.uipx`) |
 | Flow with §7 Integrated Components that reference unbuilt resources | Pattern 2 |
 | Flow whose §7 integrated components are pre-existing | Pattern 3 |
-| Agent with RPA tools in §3 Tools | Pattern 7 |
+| Agent with RPA tools in §3 Tools | Pattern 5 |
 | Coded App | Coded App build + `uipath-solution` deploy + testing (when wrapped in `.uipx`); otherwise `uipath-coded-apps` self-deploys |
 | API Workflow | API Workflow build + `uipath-solution` publish + testing |
 | Solution scope | Compose patterns per project, sequenced by cross-product integration order (dependencies before dependents) |
 
 ## Step 5 — UI element targeting (only when §9 contains UI applications)
 
-If the SDD's §9 Application Inventory contains web / desktop / Citrix applications AND the plan loads `uipath-rpa` for a workflow that interacts with them, ask the Step 4 UI batch as a single `AskUserQuestion` call (3 questions, batched):
+If the SDD's §9 Application Inventory contains web / desktop / Citrix applications AND the plan loads `uipath-rpa` for a workflow that interacts with them, ask the UI batch as a single `AskUserQuestion` call (3 questions, batched):
 
 > *Question 1 — App type:* What kind of application are we automating?
 > 1. Web / browser app
@@ -94,6 +96,12 @@ If the SDD's §9 Application Inventory contains web / desktop / Citrix applicati
 > 2. **No, I'll open it first** — tell me when ready
 > 3. **Skip discovery for now** — scaffold with placeholder selectors
 
+Question phrasing rules (govern every user-facing question in any lane):
+
+1. **No internal jargon** (snapshot, hand-wire, AutomationId, selector candidate, autonomous capture, target configuration) — plain developer language only.
+2. **No domain or app names in question text** ("What kind of application", not "What kind of HR application") — domain lives in the plan header.
+3. **Never invent a third option for Q2** — the two canonical targeting options above are the contract.
+
 Skip individual questions per the rules:
 
 - **Skip Q1** if §9 names the app kind explicitly (web / desktop / Citrix in the Interface column).
@@ -102,6 +110,8 @@ Skip individual questions per the rules:
 
 Skip the entire batch if the plan does not include UI automation (pure data-processing, API-only, agent-only, flow-only).
 
+**Resumed session:** Q1 resolves from §9 Application Inventory; Q2 (targeting approach) and Q3 (app state) are session-bound and have no SDD field — re-ask them when the current conversation lacks their answers.
+
 Record the answers in the tasks.md header for traceability and for the implementation specialists to consume.
 
 ## Step 6 — Derive tasks
@@ -161,7 +171,7 @@ The planner's job is done. The main agent reads the live tasks (via TaskList) an
 | Scenario | `AskUserQuestion` calls |
 |---|---|
 | First run, no UI apps in §9 | **0** (plan-mode review uses EnterPlanMode, not AskUserQuestion) |
-| First run, UI apps in §9 | **1** (Step 4 batched UI questions, only when at least one of Q1/Q2/Q3 is unresolved) |
+| First run, UI apps in §9 | **1** (Step 5 UI batch, only when at least one of Q1/Q2/Q3 is unresolved) |
 | Resume run (existing tasks.md) | **1** (continue / regenerate) — plus 0-1 for UI batch if unresolved |
 | Maximum | **2** under any realistic scenario |
 

package/skills/uipath-planner/references/plan-and-tasks-format.md

@@ -90,7 +90,7 @@ Every task — in both file types — uses this exact structure. The fields belo
 | Field | Required | Notes |
 |---|---|---|
 | `Task T<N>` | yes | Sequential within the file. Renumber on regeneration. |
-| `<skill-name>` | yes | One of `uipath-rpa`, `uipath-platform`, `uipath-solution`, `uipath-agents`, `uipath-coded-apps`, `uipath-maestro-flow`, `uipath-maestro-case`, `uipath-human-in-the-loop`, `uipath-test`. The planner emits this skill in the live `TaskCreate` call. |
+| `<skill-name>` | yes | One of `uipath-rpa`, `uipath-platform`, `uipath-solution`, `uipath-agents`, `uipath-coded-apps`, `uipath-maestro-flow`, `uipath-maestro-case`, `uipath-api-workflow`, `uipath-mcp-servers`, `uipath-human-in-the-loop`, `uipath-test`. The planner emits this skill in the live `TaskCreate` call. |
 | `Identity` | yes | Stable tuple `<skill>:<project>:<subject>`. Used to match tasks across regenerations. **Parsing rule:** split on the first two colons only; `<subject>` may itself contain colons (typed-resource form `<kind>:<name>` for platform resources). Examples: `rpa:VendorInvoice_Performer:Process/CalculateTotal.xaml` (file-path subject), `platform:VendorInvoice:queue:VendorQueue` (typed-resource subject = `queue:VendorQueue`), `agents:InvoiceClassifier:tools/extract_amount.py` (file-path subject), `rpa:VendorInvoice:testing` (single-token subject). |
 | `Status` | yes | One of `[ ]` pending, `[~]` in_progress, `[x]` completed, `[!]` blocked. |
 | `Completed` | only when `[x]` | `YYYY-MM-DD by agent` or `YYYY-MM-DD by human`. The planner sets `agent` when its TaskUpdate flips the checkbox; `human` only when the user manually edits the file. |
@@ -203,7 +203,7 @@ The planner emits live tasks that mirror the file. Mapping rules:
 | `Blocked by:` | `addBlockedBy` (after all tasks are created) |
 | `Completed:` | `metadata.completed_by`, `metadata.completed_date` |
 
-**Rule G-8 applies (inherited from solution-design):** if any TaskCreate or TaskUpdate fails, log a single warning, continue without live tasks, and do not retry. The markdown plan / tasks file is the authoritative deliverable.
+**Rule G-8 applies (defined in [sdd-generation-guide.md](sdd-generation-guide.md) Phase 1 Step 0.5):** if any TaskCreate or TaskUpdate fails, log a single warning, continue without live tasks, and do not retry. The markdown plan / tasks file is the authoritative deliverable.
 
 ## Plan-mode integration
 

package/skills/{uipath-solution/references/design → uipath-planner/references}/product-selection-guide.md

@@ -40,7 +40,7 @@ A Solution is the correct primary when any of the following applies, even if a s
 - The PDD mentions **reusable components** that other automations consume (Library) AND a standalone process that uses them.
 - The PDD calls out a **dedicated test suite / regression pack** alongside the process being tested (Test Automation + the Process it validates).
 - The PDD describes **multiple independent streams** with no single runtime orchestrator (e.g., separate dispatchers feeding separate performers with no Flow tying them together).
-- The deliverable is intended to be **opened or edited in Studio Web**. SW ingests Solutions only — a bare project folder is not visible in either SW workspace tab. Even a single RPA Process targeted at SW must be wrapped in a Solution (`uip solution new` + `uip solution project import` + `uip solution upload`). Signals: "Studio Web", "SW", "upload to web", "browser editor", "cloud workspace edit".
+- The deliverable is intended to be **opened or edited in Studio Web**. SW ingests Solutions only — a bare project folder is not visible in either SW workspace tab. Even a single RPA Process targeted at SW must be wrapped in a Solution (`uip solution init` + `uip solution project import` + `uip solution upload`). Signals: "Studio Web", "SW", "upload to web", "browser editor", "cloud workspace edit".
 
 When any of the above applies, set the default primary to **Solution** and pre-compose the product list from the matched signals. Otherwise default to the highest single-product match.
 
@@ -276,7 +276,7 @@ Example unified project list for a Solution (Flow + RPA Library×2 + RPA Test Au
 
 ## Level 3 — Capability Add-ons
 
-These are capabilities added to the primary product, not standalone products. When detected, flag them in the appropriate template section. `uipath-planner` reads the flags from the SDD when it derives the task list and routes the work to the correct skill.
+These are capabilities added to the primary product, not standalone products. When detected, flag them in the appropriate template section. Lane A (task derivation) reads the flags from the SDD when it derives the task list and routes the work to the correct skill.
 
 ### HITL (Human-in-the-Loop)
 
@@ -309,7 +309,7 @@ These are capabilities added to the primary product, not standalone products. Wh
 - The primary product invokes a callable system-to-system integration
 - Input/output is structured JSON, not UI
 
-**How to flag:** In the primary product's template, list API Workflow invocations in the relevant section (Flow nodes, Agent tools, Case tasks). The planner picks this up and creates a per-API-Workflow task that routes to the API Workflow specialist.
+**How to flag:** In the primary product's template, list API Workflow invocations in the relevant section (Flow nodes, Agent tools, Case tasks). The planner picks this up and creates a per-API-Workflow task that routes to `uipath-api-workflow`.
 
 ## Template Mapping
 
@@ -342,11 +342,11 @@ For RPA projects in the Solution, use the RPA template once per RPA *group* —
 The solution overview SDD includes:
 
 1. Solution Overview (objective, business context)
-2. Project Inventory — the unified project list from Level 2.5 Part B
-3. Cross-Project Data Flow — how projects call each other (Flow → RPA, Agent tool → API Workflow, RPA Performer → Library)
-4. Shared Assets & Queues — assets, credentials, and queues referenced by more than one project
-5. Per-Project SDD Index — filename + one-line scope per project
-6. Planner Handoff — solution-level handoff header plus cross-project ordering notes (integrated components built before their consumers) for `uipath-planner` to consume. Do not include a task list here — the planner owns task generation.
+2. Planner Handoff — solution-level handoff header plus cross-project ordering notes (integrated components built before their consumers) for Lane A to consume. Position 2 keeps the header inside the first ~50 lines the Entry Guard reads — do not move it lower. Do not include a task list here — Lane A owns task generation.
+3. Project Inventory — the unified project list from Level 2.5 Part B
+4. Cross-Project Data Flow — how projects call each other (Flow → RPA, Agent tool → API Workflow, RPA Performer → Library)
+5. Shared Assets & Queues — assets, credentials, and queues referenced by more than one project
+6. Per-Project SDD Index — filename + one-line scope per project
 
 ## Gap Handling for Agent / Coded App
 

package/skills/{uipath-solution/references/design → uipath-planner/references}/rpa-product-guide.md

@@ -134,7 +134,7 @@ The skill that builds the workflows owns the final, detailed decision — this i
 
 **If the process is mostly UI with one non-trivial data step,** use **Hybrid**: XAML for orchestration + UI; one Coded Workflow invoked via `Invoke Workflow File` for the data step.
 
-For the full coded-vs-XAML decision flow, see [coded-vs-xaml-guide.md](../../../uipath-rpa/references/coded-vs-xaml-guide.md) in the `uipath-rpa` skill (architectural design only — final per-workflow decisions are made by the build skill).
+For the full coded-vs-XAML decision flow, load the `uipath-rpa` skill and consult its coded-vs-XAML reference (architectural design only — final per-workflow decisions are made by the build skill).
 
 ### Selection checklist before recommending Coded C#
 

package/skills/{uipath-solution/references/design → uipath-planner/references}/sdd-generation-guide.md

@@ -13,14 +13,14 @@ Before reading the PDD, ask the user how they want the interaction to work. Use
 > 1. **Autonomous** *(recommended)* — I will read the PDD, make all decisions, and generate the full SDD. I will only interrupt for hard blockers (PDD unreadable, Agent/Coded App missing critical info, unresolved `[SME REVIEW]` items before finalizing).
 > 2. **Interactive** — I will pause at each phase checkpoint (summary, architecture, final SDD) for your review before proceeding.
 
-Record the choice — it goes into the SDD's `## Planner Handoff` header (Phase 3 Step 2) and propagates to `uipath-planner` for task review behavior.
+Record the choice — it goes into the SDD's `## Planner Handoff` header (Phase 3 Step 2) and propagates to Lane A (task derivation) for task review behavior.
 
 In **Autonomous** mode:
 - Skip Phase 1 summary presentation (generate internally, do not wait for confirmation)
 - Skip Phase 2 architecture review (generate, do not wait)
 - Still ask the SME Review resolution question before writing (Step 1.5) — this is a hard blocker
 - Still ask the Agent/Coded App gap-filling question if triggered — this is a hard blocker
-- **Insert a "Decisions Made" block** at the top of the SDD (immediately after the Planner Handoff header and before any other section) listing the four highest-leverage architectural picks with one-sentence reasons. See Step 2 below for the exact block format. Do **NOT** use `AskUserQuestion` — the picks are decided autonomously; the block makes them scannable in the SDD's first screenful so a reviewer can spot a wrong call without reading the whole document.
+- **Insert a "Decisions Made" block** at the top of the SDD (immediately after the Planner Handoff header and before any other section) listing the four highest-leverage architectural picks with one-sentence reasons. See Phase 3 Step 2 item 3 for the exact block format. Do **NOT** use `AskUserQuestion` — the picks are decided autonomously; the block makes them scannable in the SDD's first screenful so a reviewer can spot a wrong call without reading the whole document.
 
 In **Interactive** mode:
 - Present and wait at every checkpoint as described in the steps below
@@ -44,7 +44,7 @@ Mark each task `in_progress` when starting and `completed` when done.
 
 > If Step 0.5 `TaskCreate` failed, silently skip every subsequent `Mark "X" as in_progress / as completed` instruction in this guide — the tasks do not exist to update, and a second warning to the user is noise.
 
-These tasks track SDD generation. Implementation tasks are owned by `uipath-planner` and are created when the user loads the planner with this SDD — do NOT create implementation tasks here.
+These tasks track SDD generation. Implementation tasks are owned by Lane A (task derivation), which runs after Phase D writes the SDD — do NOT create implementation tasks here.
 
 ### Step 1: Read the PDD
 
@@ -146,21 +146,9 @@ Emit the summary block described in "Presenting the Recommendation" in the [Prod
 **System Errors:** <ERROR_COUNT> defined in PDD
 **Gaps Detected:** <DEFAULT_COUNT> [DEFAULT], <SME_REVIEW_COUNT> [SME REVIEW]
 
-## Recommended Scope
-**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, <PRODUCT_2>, ...)>
-**Reasoning:**
-- <PDD_SIGNAL_1> → <PRODUCT_MAPPING>
-- <PDD_SIGNAL_2> → <PRODUCT_MAPPING>
-
-**Alternatives considered:**
-- <REJECTED_OPTION> — rejected because <REASON>
-
-## Project List
-<UNIFIED_PROJECT_LIST_FROM_LEVEL_2.5_PART_B>
-
-## Queue Architecture (RPA Master Project rows only)
-<QUEUE_TABLE_OR_N/A>
-**Decomposition signals matched:** <LIST_MATCHED_SIGNALS_PER_RPA_PROCESS_PROJECT_OR_N/A>
+<RECOMMENDED_SCOPE_SUMMARY_BLOCK — emit the "Summary block" from
+product-selection-guide.md → Presenting the Recommendation:
+Recommended Scope + Project List + Queue Architecture>
 
 ### Clarifying Questions
 <NUMBERED_QUESTIONS_IF_ANY>
@@ -193,7 +181,7 @@ The architectural core sections differ per template. For each product, generate
 - §5 Data Definitions (C# records or dictionary tables per §13 Implementation Mode)
 - §9 Application Inventory (flag Integration Service connectors, specify email protocol)
 - §10 Master Project Architecture (apply Level 2.5 Part A from [rpa-product-guide.md](rpa-product-guide.md#level-25-part-a--rpa-decomposition-signals) — Single vs Master Project, sub-projects, queue schema)
-- §11 Project Structure (per sub-project if Master Project: project type, framework, folder layout, workflow inventory)
+- §11 Project Structure (per sub-project if Master Project: project type, framework, folder layout, workflow inventory) — the most load-bearing SDD section: Lane A derives tasks from it
 - §12 Queue Architecture (Master Project only — queue definitions, item schemas, processing rules)
 - §13 Implementation Mode (XAML / Coded / Hybrid — apply Level 2 from [rpa-product-guide.md](rpa-product-guide.md#level-2--authoring-mode))
 - §14 Packages (infer NuGet packages from §9 Application Inventory and process steps)
@@ -299,9 +287,9 @@ Fill in all sections of the chosen template not covered in Phase 1 or Phase 2. S
 - Roles & RACI Matrix (Case)
 - Evaluation Criteria (Agents)
 - **Testing Strategy — always thorough.** Cover happy path, edge cases, error scenarios, and (for Master Projects) end-to-end pipeline tests. Do NOT ask the user about test depth — depth is non-negotiable here. Implementation specialists may scope tests down at execution time if the user wants a quick MVP.
-- **Next Steps — points at `uipath-planner`.** Replaces the legacy "Implementation Plan" section. The planner owns the implementation task list; this skill does not generate one.
+- **Next Steps — points at Lane A (task derivation).** Replaces the legacy "Implementation Plan" section. Lane A owns the implementation task list; Phase D does not generate one.
 
-> **What Phase 3 does NOT produce:** an Implementation Plan section, a task list, or `TaskCreate` calls for implementation work. Those are owned by `uipath-planner`. The SDD's `## Next Steps` section points the user at the planner, and that is the entire handoff surface.
+> **What Phase 3 does NOT produce:** an Implementation Plan section, a task list, or `TaskCreate` calls for implementation work. Those are owned by Lane A (task derivation). The SDD's `## Next Steps` section marks the boundary into Lane A, and that is the entire Phase D output surface.
 
 ### Step 1.5: Resolve SME Review Items
 
@@ -332,7 +320,7 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
 > **Progress:** Mark "Resolve SME review items" as `completed`. Mark "Write SDD to disk" as `in_progress`.
 
 1. Assemble all sections in template order.
-2. **Fill the `## Planner Handoff` header** that appears in every template after `## Document History`. This is the load-bearing handoff to `uipath-planner`. The planner accepts **either** the heading OR the adjacent `<!-- planner-handoff:v1 -->` HTML marker as a detection signal — both ship in every template and both should survive into the generated file:
+2. **Fill the `## Planner Handoff` header** that appears in every template after `## Document History`. This is the load-bearing detection contract. The Entry Guard accepts **either** the heading OR the adjacent `<!-- planner-handoff:v1 -->` HTML marker as a detection signal — both ship in every template and both should survive into the generated file (so a later session, or a hand-written SDD, still routes to Lane A):
 
    ```markdown
    <!-- DO NOT RENAME: uipath-planner detects SDDs via this exact heading or the marker below. -->
@@ -343,15 +331,15 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
    |---|---|
    | **Execution autonomy** | <autonomous | interactive>          ← from Phase 1 Step 0
    | **SDD scope** | <single-product | solution>                  ← from Phase 1 Step 4 (Level 1 / Level 1.75)
-   | **Project list section** | §10 / §3 / Project Inventory      ← template-specific (RPA: §10; Flow: §3 + §7; etc.)
+   | **Project list section** | §11 / §10 + §11 / Project Inventory ← template-specific (RPA single: §11; RPA Master: §10 + §11; Flow: §3 + §7; etc.)
    | **Tasks file** | `<PROCESS_NAME_KEBAB>-tasks.md`             ← planner writes here on first run
-   | **Generated by** | uipath-solution v<VERSION>
+   | **Generated by** | uipath-planner
    | **Generation date** | <YYYY-MM-DD>
    ```
 
    Do NOT rename the heading or strip the marker. They are redundant on purpose — keeping both means a hand-edit of one signal does not silently break Lane A detection.
 
-3a. **Autonomous-mode Decisions Made block.** If `Execution autonomy: autonomous`, insert a `## Decisions Made` block immediately after the Planner Handoff header and before any `Action Required — SME Review Items` block or the Table of Contents. The block makes the four highest-leverage architectural picks scannable in the SDD's first screenful so a reviewer can spot a wrong call without reading the whole document. In `Execution autonomy: interactive`, this block is optional — the user already reviewed each decision at the Phase 1/Phase 2 checkpoints. Skip the block for interactive runs.
+3. **Autonomous-mode Decisions Made block.** If `Execution autonomy: autonomous`, insert a `## Decisions Made` block immediately after the Planner Handoff header and before any `Action Required — SME Review Items` block or the Table of Contents. The block makes the four highest-leverage architectural picks scannable in the SDD's first screenful so a reviewer can spot a wrong call without reading the whole document. In `Execution autonomy: interactive`, this block is optional — the user already reviewed each decision at the Phase 1/Phase 2 checkpoints. Skip the block for interactive runs.
 
    Format:
 
@@ -375,7 +363,7 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
    - For non-RPA scopes (e.g., Single-product Agent), rows 2-4 collapse to N/A with one row covering the product-specific Level-1.5-equivalent (framework choice, app type, etc.).
    - The block does NOT replace the per-section detail later in the SDD — §10 / §11 / §13 still carry the full justification. The block is the **scannable index** of those decisions.
 
-3. If any `[SME REVIEW]` items remain, add a consolidated warning section after the Planner Handoff header (and after the `## Decisions Made` block if present) and before the Table of Contents:
+4. If any `[SME REVIEW]` items remain, add a consolidated warning section after the Planner Handoff header (and after the `## Decisions Made` block if present) and before the Table of Contents:
 
 ```markdown
 ## Action Required — SME Review Items
@@ -387,22 +375,22 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
 > These items are marked `[SME REVIEW]` in the document. The automation can be built with defaults, but these must be verified before production.
 ```
 
-4. **Target SDD length: 300-800 lines of markdown** for single-project SDDs. **Master Project SDDs may reach 600-1200 lines** due to per-sub-project structure sections — this is expected. For processes with more than 20 steps, group related steps and summarize at the parent level. For processes with more than 10 business rules, prioritize the 10 most impactful.
-5. **Re-run handling.** If `<PROCESS_NAME_KEBAB>-sdd.md` already exists, ask the user via `AskUserQuestion`:
+5. **Target SDD length: 300-800 lines of markdown** for single-project SDDs. **Master Project SDDs may reach 600-1200 lines** due to per-sub-project structure sections — this is expected. For processes with more than 20 steps, group related steps and summarize at the parent level. For processes with more than 10 business rules, prioritize the 10 most impactful.
+6. **Re-run handling.** If `<PROCESS_NAME_KEBAB>-sdd.md` already exists, ask the user via `AskUserQuestion`:
 
    > An SDD already exists at `<sdd-path>`. How should I proceed?
    >
-   > 1. **Keep the existing SDD and stop** *(recommended)* — load `uipath-planner` if you want to refresh the task list
+   > 1. **Keep the existing SDD and stop** *(recommended)* — proceed to Lane A if you want to refresh the task list
    > 2. **Regenerate from the PDD** — overwrites the existing SDD
    > 3. **Generate alongside as `<name>-v2-sdd.md`** — for diffing
 
    Default is "keep" — overwriting an SDD the user might have hand-edited is the more destructive action.
 
-6. Write the output file(s) to the current working directory:
+7. Write the output file(s) to the current working directory. If the user specified an output path for the SDD, use it instead of these defaults:
    - **Single-product scope:** one file at `<PROCESS_NAME_KEBAB>-sdd.md`.
    - **Solution scope:** the solution overview at `<SOLUTION_NAME_KEBAB>-solution-sdd.md` PLUS one per-project SDD at `<PROJECT_NAME_KEBAB>-sdd.md` for each project in the unified project list. Put the `[SME REVIEW]` warning block in the solution overview AND in any per-project file where a review item lives in that project. Each per-project SDD gets its own `## Planner Handoff` header.
 
-6a. **Template-superset check (mandatory final step before Step 7).** After writing each SDD file, re-read it and extract every H2 (`## `) and H3 (`### `) heading. Compare against the template's Table of Contents and required subsections. The generated SDD's heading set MUST be a superset — extra subsections are fine, missing template sections are an SDD defect.
+8. **Template-superset check (mandatory before the item 9 summary).** After writing each SDD file, re-read it and extract every H2 (`## `) and H3 (`### `) heading. Compare against the template's Table of Contents and required subsections. The generated SDD's heading set MUST be a superset — extra subsections are fine, missing template sections are an SDD defect.
 
    Minimum required H2 headings per template:
    - **RPA template:** §1 Process Overview, §2 Process Map, §3 Detailed Process Steps, §4 Business Rules, §5 Data Definitions, §6 Value Mappings, §7 Exception Handling, §8 Error Handling, §9 Application Inventory, §10 Master Project Architecture, §11 Project Structure, §12 Queue Architecture (Master Project only — may be omitted for Single Project), §13 Implementation Mode, §14 Packages, §15 Credentials & Assets, §16 Deployment Environment, §17 Testing Strategy, §18 Next Steps
@@ -415,7 +403,7 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
 
    Common slip-fail: skipping §4 Business Rules because the PDD has no dedicated "Business Rules" section. Rules are usually buried in "Remarks", step descriptions, or screenshots — the PDD analysis guide's "Embedded business rules" pointer applies. Treat zero rules in §4 as a regeneration trigger, not a finished section.
 
-7. Output a summary in the conversation:
+9. Output a summary in the conversation:
 
 ```markdown
 ## SDD Generated
@@ -426,18 +414,17 @@ This step runs in BOTH Autonomous and Interactive modes — it is a hard blocker
 
 <SME_REVIEW_COUNT> unresolved SME review items (if any — list them).
 
-**Next:** load `uipath-planner` and pass it the SDD path. The planner will derive the task list and emit live `TaskCreate` calls.
+**Next:** Phase D is complete. Proceed into Lane A (task derivation) with this SDD path — Lane A derives the task list and emits live `TaskCreate` calls.
 ```
 
-### Step 3: Hand Off to the Planner
+### Step 3: Proceed to Lane A (Task Derivation)
 
 > **Progress:** Mark "Write SDD to disk" as `completed`. All progress tasks are now done.
 
-The SDD is the deliverable for this skill. **Do not generate an Implementation Plan section. Do not create implementation `TaskCreate` calls. Do not start executing.**
+The SDD is the deliverable of Phase D. **Do not generate an Implementation Plan section inside the SDD. Do not create implementation `TaskCreate` calls during Phase D. Do not start executing.**
 
-Tell the user the next step explicitly:
+Then transition based on the user's intent:
 
-> The SDD is written. Load `uipath-planner` and pass it `<sdd-path>` to generate the implementation task list. The planner will write `<process-kebab>-tasks.md` alongside the SDD and emit live tasks routing to specialist skills.
+> The SDD is written. **Fall through into Lane A** with `<sdd-path>` to generate the implementation task list. Lane A reads the `## Planner Handoff` header you just wrote, derives tasks, writes `<process-kebab>-tasks.md` alongside the SDD, and emits live tasks routing to specialist skills.
 
-If the user's intent implies implementation ("create / build / implement / set up / make"), the main agent will load `uipath-planner` automatically when this skill returns. If the user only asked to "design / architect / generate an SDD", stop here — the SDD is enough.
-```
+If the user's intent implies implementation ("create / build / implement / set up / make"), continue directly into Lane A — see [pdd-driven-lane-guide.md](pdd-driven-lane-guide.md). If the user only asked to "design / architect / generate an SDD", stop here — the SDD is enough.

package/skills/{uipath-solution/references/design → uipath-planner/references}/tenant-library-search-guide.md

@@ -11,7 +11,7 @@ The tenant feed is authoritative for org-published libraries. Do NOT search the
 One command, one global filter:
 
 ```bash
-uip resource libraries list --limit 500 --output json
+uip or libraries list --limit 500 --output json
 ```
 
 Returns `Data: [{ Key, Title, Version, Authors }]`. `Key` is `PackageId:Version` and is always populated. `Title` can be `null`.
@@ -32,12 +32,12 @@ There is **no `--search` flag** and **no `--feed-id` flag** on `libraries list`.
 
 ```bash
 # Single keyword
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && contains(Title, 'Excel')]" \
   --output json
 
 # Multi-keyword OR
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Title != null && (contains(Title, 'Common') || contains(Title, 'Shared'))]" \
   --output json
 ```
@@ -49,7 +49,7 @@ For case-insensitive matching, lowercase the keyword in the filter and the field
 For orgs that publish libraries with cryptic Titles but a stable `Authors` value, filter on `Authors` instead of `Title`:
 
 ```bash
-uip resource libraries list --limit 500 \
+uip or libraries list --limit 500 \
   --output-filter "[?Authors != null && contains(Authors, '<OrgName>')]" \
   --output json
 ```
@@ -58,7 +58,7 @@ Combine `Title` and `Authors` filters with `||` when the org uses both conventio
 
 ## Procedure
 
-1. **Auth preflight.** Run a benign call once: `uip resource libraries list --limit 1 --output json`. If `Result == "Failure"` with an auth-related message, surface it and switch to the manual fallback (below). Do NOT retry silently.
+1. **Auth preflight.** Run a benign call once: `uip or libraries list --limit 1 --output json`. If `Result == "Failure"` with an auth-related message, surface it and switch to the manual fallback (below). Do NOT retry silently.
 2. **Extract keywords** from the source (PDD Application Inventory, user prompt, project intent). Cap at 6:
    - Org-prefix terms: `Common`, `Shared`, `Utils`, `Helpers`, `<Company>` if known
    - Capability terms: `Excel`, `SAP`, `ServiceNow`, `Salesforce`, `Email`, `PDF`, `SharePoint`, `Outlook`, `Citrix`, etc. — drawn from the in-scope applications
@@ -97,8 +97,8 @@ If `uip` is unauthenticated, ask the legacy question:
 ## Anti-patterns
 
 1. **Searching the local filesystem first.** Tenant is authoritative; local matches do not indicate org adoption.
-2. **Using `--search`.** That flag does not exist on `uip resource libraries list`. Filter via `--output-filter`.
-3. **Using `--feed-id`.** That flag does not exist on `uip resource libraries list` (it does on `uip or packages list` — different command). The libraries command always targets the default tenant feed.
+2. **Using `--search`.** That flag does not exist on `uip or libraries list`. Filter via `--output-filter`.
+3. **Using `--feed-id`.** That flag does not exist on `uip or libraries list` (it does on `uip or packages list` — different command). The libraries command always targets the default tenant feed.
 4. **Calling `contains(Title, ...)` without `Title != null` guard.** Tenants commonly hold packages with null Title — the call fails fast with `Invalid type: contains() expected ... received type null`.
 5. **Listing all libraries with no `--limit` bump, or paginating past the end.** Default 50 truncates large tenants and silently misses candidates. Use `--limit 500` for a one-shot scan; paginate via `--offset` only if `Data.length == 500`. If `Data.length < --limit` on a paginated call, you have seen the entire feed — stop searching, do not run more filtered queries hoping for hidden matches.
 6. **Auto-selecting a candidate.** Library selection drives §14 Packages and project compilability — always confirm via `AskUserQuestion`.