@n8n/instance-ai 1.26.2 → 1.27.0

package/skills/agent-builder/SKILL.md

@@ -9,6 +9,7 @@ description: >-
   artifact is no longer clear.
 recommended_tools:
   - build-agent
+  - agent-context
   - build-workflow
   - data-tables
 ---
@@ -22,11 +23,17 @@ when the conversation already targets an Agent and the user is continuing that
 build. Do not rerun intent recognition for routine Agent edits or extensions.
 Use `build-agent` only for Agent artifacts.
 
+For read-only research, use `agent-context` directly. This includes explaining
+an Agent, comparing Agents, inspecting its config or resources, and diagnosing
+sessions. Do not call `build-agent` for these requests. Call `build-agent` only
+when the request creates, changes, tests, or publishes an Agent. Set its
+`operation` to the matching activity for an existing Agent.
+
 For a new Agent request, make the first `build-agent` call with a faithful copy
 of the request as soon as any required orchestrator-owned prerequisites are
 ready. Before that call, use `ask-user` only to choose a supported channel or to
 define a workflow or data-table prerequisite that the orchestrator must create.
-Only ask about the channel after `list-agent-capabilities` shows that the
+Only ask about the channel after `agent-context` with `type: "capabilities"` shows that the
 requested channel is unsupported. Do not collect model, service, tool, topic,
 schedule, credential, or other Agent implementation choices first. The embedded
 Agent Builder asks those questions through the `build-agent` call.
@@ -39,7 +46,7 @@ on the Agent.
 
 ## Supported channels & unsupported requests
 
-`list-agent-capabilities` returns every chat channel n8n Agents support, each
+`agent-context` with `type: "capabilities"` returns every chat channel n8n Agents support, each
 with `capabilities`, `useIntegrationWhen`, and `useNodeToolWhen`. It is the
 authoritative source the orchestrator can read before building; a channel
 absent from its result is unsupported for agents.
@@ -85,6 +92,19 @@ into a request for a Slack node tool. Preserve unspecified and ambiguous
 implementation details so the builder can resolve them with its own guidance
 and interactive tools.
 
+Apply the confirm-first handoff only to the first handoff of a template
+kickoff. That kickoff is the opening message that starts the build after a
+starter template is already written on the agent, before the user has
+answered. Read that config. Forward the message as a request to confirm
+those selections. Do not rewrite them into requirements the user stated.
+Do not tell the builder to finish the build before the user answers.
+
+Forward every other message as the user wrote it. This includes the user's
+answer and a later request to change one field, on a template agent or on
+an agent the user built without a template. Do not turn a change request
+into another confirmation. Do not add tools, tasks, or instructions the
+user did not ask for. A change to one field updates only that field.
+
 ## Prerequisites
 
 Before the first `build-agent` call, create prerequisites the builder cannot
@@ -163,3 +183,13 @@ those tools do not appear in your toolset.
 When the builder needs a user choice, credential, chat channel, or approval, it
 surfaces an interactive card in this chat. Do not relay the question yourself;
 the `build-agent` call resumes with the user's answer.
+
+## Agent UI labels
+
+When you send the user to the agent editor, use the labels they see:
+
+- Sessions tab: past agent conversations, tests, and activity. Each item is a session.
+- Preview: the live test-chat dock, not the history list.
+- Workflow execution history stays "Executions". Do not reuse that name for agents.
+
+Never say Runs tab, Executions tab, Activity History, or Runs Activity History for an agent.

package/skills/debugging-executions/SKILL.md

@@ -86,6 +86,10 @@ first move whenever the user is debugging a **read** node that already failed a
 real execution: the node ran for real once already, and a mock-only check is
 what sends the user back for a second session.
 
+The action refuses a replay that would re-run a node above the target: an
+unpinned one the execution never reached, one that failed there, or a loop
+that did not finish. Pick another execution, or tell the user which node would run again.
+
 ### Decide whether the node is safe to run first
 
 A step run is a real run. The node uses the user's real credentials and reaches
@@ -142,6 +146,55 @@ Mocked input does **not** make a write node safe. The node still runs for real
 against the user's systems; only its input is invented, which makes the effect
 less predictable, not more.
 
+### Running a tool
+
+A tool never runs on its own. n8n runs it through the node that owns it —
+usually the Agent. A step run on a tool therefore behaves like a step run on
+that Agent:
+
+- `mockInput` feeds the **Agent's** input, not the tool's arguments.
+- `reuseExecutionId` replays the nodes above the **Agent**.
+- A chain run (neither option) runs every node above the Agent for real. Give
+  one of the two options when a node up there writes.
+- `ranThroughNodeNames` lists **every** node that can run the tool, not the one
+  that ran it. A tool on several agents lists them all: the engine picks one,
+  and it does not report which. Do not name a single Agent to the user when
+  this field holds more than one.
+- A tool on two Agents where one runs above the other is refused. Run the
+  upper Agent, then read the tool with `executions(action="get-node-output")`.
+
+The tool's own arguments come from `toolArguments` — the values the agent would
+normally decide:
+
+```
+executions(action="run-step", workflowId, nodeName="Search Tickets Tool",
+           reuseExecutionId=<the failed execution>,
+           toolArguments={"query": "login fails", "status": "open"})
+```
+
+The example targets a **read** tool on purpose. The write rule above holds here
+too, and a tool hides the write behind a friendly name: a step run on a "Create
+Ticket" tool creates the ticket again, and `toolArguments` does not change that.
+Only run one when the user has accepted a second write.
+
+Use the argument names from the node's `$fromAI` calls, which
+`workflows(action="get-as-code")` shows. Pass a plain string instead for a tool
+that takes one free-text input (Wikipedia, Code Tool, a vector store used as a
+tool).
+
+A tool that declares `$fromAI` arguments is refused without them: it would
+otherwise fail for a reason that has nothing to do with the user's problem, and
+you would report that as the defect. A node that holds several tools is refused
+outright, because nothing here can name one of its tools the way the agent
+does: the "MCP Client Tool" node, and every node the MCP registry added, whose
+type is `@n8n/mcp-registry.<server slug>`. Run the Agent for those, and read
+the node's output from that execution.
+
+A sub-node that is not a tool — a model, memory, embeddings — cannot be run this
+way at all. Run the Agent, and read the sub-node with
+`executions(action="get-node-output")` on **that** execution: n8n records every
+call a sub-node made while the Agent ran.
+
 ## Successful execution with wrong or empty value
 
 When `debug` doesn't apply because nothing errored, call

package/skills/intent-recognition/SKILL.md

@@ -281,7 +281,7 @@ continuity for that primitive.
 
 **Unsupported capabilities**: when the user names a specific channel or
 capability for an agent (e.g. "WhatsApp", "Teams"), call
-`list-agent-capabilities` before classifying. If the named channel is
+`agent-context` with `type: "capabilities"` before classifying. If the named channel is
 absent, it is unsupported for agents — do not classify the request as a
 workflow substitute, do not improvise workflow nodes to fake the channel,
 and do not claim it can be configured. Explain that it is unavailable for
@@ -396,7 +396,7 @@ valid, apply the growth tiebreaker instead of asking a theoretical preference.
   actions or whether an investigator must choose and adapt them.
 - "Build me an agent my team can @mention on WhatsApp to triage customer
   messages." -> **agent-anchored** (explicit agent artifact + chat
-  interaction), but call `list-agent-capabilities` first: WhatsApp is absent,
+  interaction), but call `agent-context` with `type: "capabilities"` first: WhatsApp is absent,
   so do not build. Explain WhatsApp is unsupported for agents, offer the
   supported chat channels the tool returned, with their
   `capabilities`, and ask which to use — or whether the user wants a
@@ -438,7 +438,7 @@ valid, apply the growth tiebreaker instead of asking a theoretical preference.
   workflow-anchored pipeline. A Chat Trigger workflow is correct only when
   chat is merely the manual trigger for a fixed graph.
 - Never improvise a workflow substitute for an unsupported agent channel or
-  capability. When the user names a channel not in `list-agent-capabilities`,
+  capability. When the user names a channel not returned by `agent-context`,
   explain the limitation and offer supported alternatives — do not add
   workflow nodes that fake the channel or silently translate the request
   into a workflow change.

package/skills/suggest-automations/SKILL.md

@@ -0,0 +1,127 @@
+---
+name: suggest-automations
+description: >-
+  Offer the three most common automations for a user as a single-choice card,
+  from your own knowledge of their team and their apps, then build the one
+  they choose or offer more. The system preloads it on onboarding threads,
+  where the opening card already asked the user about themselves.
+  Use it on other threads when the user asks what they could automate or
+  wants ideas for a first workflow.
+recommended_tools:
+  - ask-user
+  - build-workflow
+---
+
+# Suggest automations
+
+## Input
+
+You need to know who the user is, at least their team and the apps they use.
+The user knows little about n8n: no n8n vocabulary, and no questions about
+tasks or pain points.
+
+On an onboarding thread the conversation already holds an `<onboarding-answer>`
+block with the user's team and apps, one line per question. Use every line of
+the block. The answers are final: use them as they come and do not ask these
+questions again. Two openings:
+
+- The block is followed by your message "Got it. Finally, tell me a little
+  about how you use <their apps>." and the user's reply. The reply describes how they
+  work, names a task in their own words, or names none. Start at step 1.
+- The block is the latest message and one answer is free text the user typed
+  into the card. Read that text first. A tool name is one of their apps: ask
+  "Got it. Finally, tell me a little about how you use <their apps>." and end
+  the turn. A task: start at step 1 with it. Anything else, for example a wish to
+  stop, a request about something else, a refusal or an insult: call
+  `leave-onboarding`, then write a one-sentence reply that invites the user to
+  explore the app and to come back with a task.
+
+On any other thread, ask in ONE `ask-user` call: a `single` question "What
+team are you on?" with the options Executive/Owner, Support, Product & Design,
+Sales, IT, Engineering and Marketing, and a `multi` question "Which apps do you
+use?" with the ten apps people use most at work, as product names such as
+Slack or Google Sheets. Never run a command or read a file to find them.
+
+## Flow
+
+1. Pick three automations that each solve a different problem, ordered from
+   the most to the least relevant. Each one runs on the user's apps and is
+   realistic for n8n. When the user named a task, even a specific and
+   complete one, suggestion one is that task in their words and the other two
+   are what people on their team set up next to it. Otherwise pick the three
+   that people on the team most often set up with the user's apps. The card
+   always comes before a build: a specific task gets confirmed with one click,
+   never built unasked. Decide in one step: do not run a command, read a file
+   or write the reasoning out.
+2. Write short text and no list: the card carries the options. First
+   reflect what the user shared, in their words, with no assumptions added:
+   - A goal or a problem: "Thanks, that helps. You want to ..."
+   - A clear workflow: "Thanks, that helps. You use <app> and <app> to ..."
+   - A general situation or activities: "Thanks, that helps. Your work
+     involves ..."
+   Say "You want" only when the user named an outcome they want. Then the
+   social proof that matches:
+   - A goal or a problem: "I've looked at how other users have solved
+     similar problems."
+   - A clear workflow: "I've looked at how other users approach similar
+     workflows."
+   - A general situation: "I've looked at how other users make their work
+     easier."
+   Then, after a blank line, "Here are three ways n8n could help:". With
+   nothing to reflect, drop the first part and use the general social proof.
+   Then ONE `ask-user` call with `questions` only: a `single`
+   question "Which one feels most useful?", `required: true`, with
+   four options: the three suggestions, most relevant first, and last
+   `Show me other ideas`. `Show me other ideas` is an action that asks for
+   three more suggestions, not a catch-all: always keep it as the fourth
+   option. Leave `introMessage` out. Set `freeTextLabel` to `Share more
+   context`: the card shows it as its built-in free-text row with a pencil
+   icon. Never add "Something else", "Share more context" or "None of these"
+   as an option.
+
+   A suggestion is one option string of two lines: the title, a newline,
+   then the description. The card shows the second line under the first.
+   - Title: a short action phrase of at most 6 words that names the result,
+     not the setup, for example "Capture new leads" or "Speed up customer
+     follow-ups". Not a sentence, and no punctuation at the end.
+   - Description: one plain sentence of at most 18 words about what the user
+     gets. State no trigger, schedule, recipient or other process detail the
+     user did not give. No Markdown, no n8n node names.
+   - Apps: name only apps the user selected or named, at most two in one
+     suggestion, and only where the name makes the suggestion clearer. With
+     no app or one app from the user, describe the result without app names.
+   Example option: "Capture new leads\nMove new enquiries into your sales
+   process so nothing gets missed."
+3. Read the answer.
+   - A suggestion: its first line, the title, names the automation to build.
+   - `Show me other ideas`: repeat step 2 with three automations not shown in
+     this thread yet, after one sentence such as "Here are three more."
+   - Free text that describes a task: that is the user's request; build it.
+   - Free text that asks for a change, for example another app or a topic:
+     repeat step 2 with three automations that fit it.
+   - Free text that names no task and no change, for example "skip", "no" or
+     "later", or `answered: false`: do not build. On an onboarding thread call
+     `leave-onboarding`, then write a one-sentence reply, for example "No
+     problem. Explore the app and tell me when you want to automate something."
+4. Write exactly one line before the first tool call, `Building <title> now.`,
+   and no other text until the `build-workflow` result. Load `workflow-builder`
+   and build the automation with the user's apps the normal way, then follow
+   `postBuildFlow.instructions` from the result. Ask about an app only for a
+   step the user's list does not cover, one question per turn.
+
+## Rules
+
+- One `ask-user` call per turn. Keep every message to four sentences or fewer.
+- A build needs a picked suggestion or a task in the user's words. Never
+  start one after a skip, a dismissal, or free text that names nothing.
+- No apps given: suggest what people on the team most often automate, and
+  name no app.
+- Talk about the automation, never about the mechanics. Do not say
+  "validate", "workspace" or a file name in a message. Say what is being
+  built and what the user gets, for example "Building the reminder now."
+- If the user wants to stop the onboarding or asks for something unrelated,
+  drop this flow. On an onboarding thread, whenever you stop asking the card
+  questions, call `leave-onboarding` first and then reply. A reply that skips
+  the questions without that call leaves the user stuck in the flow.
+- Never ask for credentials, keys, or passwords in chat.
+- Reply in the language the user writes in.

package/skills/workflow-builder/SKILL.md

@@ -978,7 +978,7 @@ For AI Agent workflows:
 
 After building a workflow that uses a trigger with an HTTP endpoint, share the
 full production URL with the user. Use the Webhook base URL and Form base URL
-from Instance Info in the system prompt. Each trigger type has a distinct
+from the `<instance-urls>` block in the user's turn. Each trigger type has a distinct
 pattern:
 
 - **Webhook Trigger**: `{webhookBaseUrl}/{path}` (where `{path}` is the node's

package/dist/tools/agents.tool.d.ts

@@ -1,2 +0,0 @@
-import type { OrchestrationContext } from '../types';
-export declare function createAgentsTool(context: OrchestrationContext): import("@n8n/agents").BuiltTool;

package/dist/tools/agents.tool.js

@@ -1,40 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.createAgentsTool = createAgentsTool;
-const agents_1 = require("@n8n/agents");
-const zod_1 = require("zod");
-const tool_ids_1 = require("./tool-ids");
-const agentsInputSchema = zod_1.z.object({
-    action: zod_1.z
-        .literal('list')
-        .describe('List the n8n Agents in this project (id, name, published state, last update), most recently updated first.'),
-});
-const agentsOutputSchema = zod_1.z.object({
-    count: zod_1.z.number(),
-    agents: zod_1.z.array(zod_1.z.object({
-        agentId: zod_1.z.string(),
-        name: zod_1.z.string(),
-        published: zod_1.z.boolean(),
-        updatedAt: zod_1.z.string(),
-    })),
-});
-function createAgentsTool(context) {
-    return new agents_1.Tool(tool_ids_1.DOMAIN_TOOL_IDS.AGENTS)
-        .description('List the n8n Agent artifacts in this project — id, name, published state, and last ' +
-        'update, most recently updated first. Use it to answer questions about existing ' +
-        'agents and to find the `agentId` to pass to `build-agent` when the user wants to ' +
-        'edit an agent that was not built in this conversation. Read-only; agents are ' +
-        'created and edited via `build-agent`.')
-        .input(agentsInputSchema)
-        .output(agentsOutputSchema)
-        .handler(async () => {
-        const delegate = context.domainContext?.builderDelegate;
-        if (!delegate) {
-            throw new Error('Agent listing is not available on this instance.');
-        }
-        const agents = await delegate.listAgents();
-        return { count: agents.length, agents };
-    })
-        .build();
-}
-//# sourceMappingURL=agents.tool.js.map

package/dist/tools/agents.tool.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"agents.tool.js","sourceRoot":"","sources":["../../src/tools/agents.tool.ts"],"names":[],"mappings":";;;AAMA,wCAAmC;AACnC,6BAAwB;AAGxB,yCAA6C;AAE7C,MAAM,iBAAiB,GAAG,OAAC,CAAC,MAAM,CAAC;IAClC,MAAM,EAAE,OAAC;SACP,OAAO,CAAC,MAAM,CAAC;SACf,QAAQ,CACR,4GAA4G,CAC5G;CACF,CAAC,CAAC;AAEH,MAAM,kBAAkB,GAAG,OAAC,CAAC,MAAM,CAAC;IACnC,KAAK,EAAE,OAAC,CAAC,MAAM,EAAE;IACjB,MAAM,EAAE,OAAC,CAAC,KAAK,CACd,OAAC,CAAC,MAAM,CAAC;QACR,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE;QACnB,IAAI,EAAE,OAAC,CAAC,MAAM,EAAE;QAChB,SAAS,EAAE,OAAC,CAAC,OAAO,EAAE;QACtB,SAAS,EAAE,OAAC,CAAC,MAAM,EAAE;KACrB,CAAC,CACF;CACD,CAAC,CAAC;AAEH,0BAAiC,OAA6B;IAC7D,OAAO,IAAI,aAAI,CAAC,0BAAe,CAAC,MAAM,CAAC;SACrC,WAAW,CACX,qFAAqF;QACpF,iFAAiF;QACjF,mFAAmF;QACnF,+EAA+E;QAC/E,uCAAuC,CACxC;SACA,KAAK,CAAC,iBAAiB,CAAC;SACxB,MAAM,CAAC,kBAAkB,CAAC;SAC1B,OAAO,CAAC,KAAK,IAAI,EAAE;QACnB,MAAM,QAAQ,GAAG,OAAO,CAAC,aAAa,EAAE,eAAe,CAAC;QACxD,IAAI,CAAC,QAAQ,EAAE,CAAC;YACf,MAAM,IAAI,KAAK,CAAC,kDAAkD,CAAC,CAAC;QACrE,CAAC;QACD,MAAM,MAAM,GAAG,MAAM,QAAQ,CAAC,UAAU,EAAE,CAAC;QAC3C,OAAO,EAAE,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,CAAC;IACzC,CAAC,CAAC;SACD,KAAK,EAAE,CAAC;AACX,CAAC"}

package/dist/tools/orchestration/list-agent-capabilities.tool.d.ts

@@ -1,2 +0,0 @@
-import type { OrchestrationContext } from '../../types';
-export declare function createListAgentCapabilitiesTool(context: OrchestrationContext): import("@n8n/agents").BuiltTool;

package/dist/tools/orchestration/list-agent-capabilities.tool.js

@@ -1,45 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.createListAgentCapabilitiesTool = createListAgentCapabilitiesTool;
-const agents_1 = require("@n8n/agents");
-const zod_1 = require("zod");
-const tool_ids_1 = require("../tool-ids");
-const chatIntegrationDescriptorSchema = zod_1.z.object({
-    type: zod_1.z.string(),
-    label: zod_1.z.string(),
-    icon: zod_1.z.string(),
-    credentialTypes: zod_1.z.array(zod_1.z.string()),
-    capabilities: zod_1.z.array(zod_1.z.string()).optional(),
-    useIntegrationWhen: zod_1.z.array(zod_1.z.string()).optional(),
-    useNodeToolWhen: zod_1.z.array(zod_1.z.string()).optional(),
-});
-const listAgentCapabilitiesOutputSchema = zod_1.z.object({
-    channels: zod_1.z.array(chatIntegrationDescriptorSchema),
-    agentCapabilities: zod_1.z.array(zod_1.z.string()),
-    limitations: zod_1.z.array(zod_1.z.string()),
-});
-function createListAgentCapabilitiesTool(context) {
-    return new agents_1.Tool(tool_ids_1.ORCHESTRATION_TOOL_IDS.LIST_AGENT_CAPABILITIES)
-        .description('List what n8n Agents can do and the chat-channel integrations they support. ' +
-        "Returns each supported channel's `type`, `label`, supported credential types, " +
-        'and builder guidance (`capabilities`, `useIntegrationWhen`, `useNodeToolWhen`), ' +
-        'plus `agentCapabilities` (what an agent can do beyond chat) and `limitations` ' +
-        '(agent-level constraints to respect when planning a build). ' +
-        'Call this before building or modifying an agent whenever the user names a ' +
-        'specific channel or capability (e.g. WhatsApp, Teams): if the named channel ' +
-        'is absent from `channels`, it is unsupported for agents — explain the ' +
-        'limitation and offer the listed alternatives instead of improvising a ' +
-        'workflow substitute or claiming it is configured. Read-only; channels and ' +
-        'capabilities are configured via `build-agent`.')
-        .input(zod_1.z.object({}))
-        .output(listAgentCapabilitiesOutputSchema)
-        .handler(async () => {
-        const delegate = context.domainContext?.builderDelegate;
-        if (!delegate) {
-            throw new Error('Agent capabilities are not available on this instance.');
-        }
-        return await delegate.listAgentCapabilities();
-    })
-        .build();
-}
-//# sourceMappingURL=list-agent-capabilities.tool.js.map

package/dist/tools/orchestration/list-agent-capabilities.tool.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"list-agent-capabilities.tool.js","sourceRoot":"","sources":["../../../src/tools/orchestration/list-agent-capabilities.tool.ts"],"names":[],"mappings":";;;AAWA,wCAAmC;AACnC,6BAAwB;AAGxB,0CAAqD;AAErD,MAAM,+BAA+B,GAAG,OAAC,CAAC,MAAM,CAAC;IAChD,IAAI,EAAE,OAAC,CAAC,MAAM,EAAE;IAChB,KAAK,EAAE,OAAC,CAAC,MAAM,EAAE;IACjB,IAAI,EAAE,OAAC,CAAC,MAAM,EAAE;IAChB,eAAe,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC;IACpC,YAAY,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE;IAC5C,kBAAkB,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE;IAClD,eAAe,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC,CAAC,QAAQ,EAAE;CAC/C,CAAC,CAAC;AAEH,MAAM,iCAAiC,GAAG,OAAC,CAAC,MAAM,CAAC;IAElD,QAAQ,EAAE,OAAC,CAAC,KAAK,CAAC,+BAA+B,CAAC;IAElD,iBAAiB,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC;IAEtC,WAAW,EAAE,OAAC,CAAC,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC;CAChC,CAAC,CAAC;AAEH,yCAAgD,OAA6B;IAC5E,OAAO,IAAI,aAAI,CAAC,iCAAsB,CAAC,uBAAuB,CAAC;SAC7D,WAAW,CACX,8EAA8E;QAC7E,gFAAgF;QAChF,kFAAkF;QAClF,gFAAgF;QAChF,8DAA8D;QAC9D,4EAA4E;QAC5E,8EAA8E;QAC9E,wEAAwE;QACxE,wEAAwE;QACxE,4EAA4E;QAC5E,gDAAgD,CACjD;SACA,KAAK,CAAC,OAAC,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;SACnB,MAAM,CAAC,iCAAiC,CAAC;SACzC,OAAO,CAAC,KAAK,IAAI,EAAE;QACnB,MAAM,QAAQ,GAAG,OAAO,CAAC,aAAa,EAAE,eAAe,CAAC;QACxD,IAAI,CAAC,QAAQ,EAAE,CAAC;YACf,MAAM,IAAI,KAAK,CAAC,wDAAwD,CAAC,CAAC;QAC3E,CAAC;QAID,OAAO,MAAM,QAAQ,CAAC,qBAAqB,EAAE,CAAC;IAC/C,CAAC,CAAC;SACD,KAAK,EAAE,CAAC;AACX,CAAC"}