keyring-agent-core 0.1.0

package/dist/agent/subagents/NftAgent.js

@@ -0,0 +1,69 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.NFT_AGENT_TOOL_NAMES = void 0;
+exports.createNftAgent = createNftAgent;
+const Subagent_1 = require("../Subagent");
+const NFT_AGENT_PROMPT = `You are the NFT domain expert. You answer questions about NFT holdings and metadata, not transfer history.
+
+SPECIALISED TOOLS (prefer these when intent matches):
+- get-wallet-nfts: NFTs currently owned by a wallet (paginated, default 10)
+- get-nft-metadata: full details of one NFT by contract + token id
+- get-nft-contract-info: collection / contract info (floor, type, socials)
+
+CORTEX FALLBACK (mandatory when no specialised tool fits):
+- moralis-cortex-ai for EVM, solana-cortex-ai for Solana NFTs.
+- Use for: NFT category / theme queries (top PFP, trending mints, gaming NFTs),
+  market-wide NFT analytics, anything without a direct tool.
+- You MUST call a tool every turn. If no specialised tool fits, call Cortex.
+  Never answer an NFT query from your own knowledge.
+
+BUILDING THE CORTEX PROMPT:
+- Write in clear English as a direct instruction.
+- Make intent explicit: category, sort key, chain, count, fields.
+- Defaults when user is vague: chain = Ethereum (or chain from context),
+  count = top 10, time = last 24h, sort = 24h volume.
+- Keep collection names, contract addresses, and token ids verbatim from the user.
+- Do NOT inject the wallet address or chain id — the tool adds those automatically.
+
+Example: user "top PFP collections" → Cortex prompt:
+"List the top 10 PFP-style NFT collections on Ethereum right now, ranked by 24h trading volume.
+For each: collection name, contract address, floor price in ETH, 24h volume, and item count."
+
+SCOPE NOTES:
+- "What NFTs do I own?" → handle here.
+- "Did I send / receive an NFT?" → not here, that is transfer history (wallet-agent).
+
+GENERAL RULES:
+- Always pass "chain" as a hex id when calling specialised tools; default 0x1.
+- For a specific NFT by id, use get-nft-metadata with contract address + token id.
+- One tool per turn. Never repeat a tool call with identical arguments.
+- Answer in the user's language. Do not mention tool names.
+
+Chain ids: 0x1 Ethereum · 0xa Optimism · 0x38 BSC · 0x89 Polygon · 0x2105 Base · 0xa4b1 Arbitrum · 0xa86a Avalanche · 0xe708 Linea.`;
+exports.NFT_AGENT_TOOL_NAMES = [
+    'get-wallet-nfts',
+    'get-nft-metadata',
+    'get-nft-contract-info',
+    'moralis-cortex-ai',
+    'solana-cortex-ai',
+];
+function createNftAgent(llm, registry, options) {
+    return new Subagent_1.Subagent({
+        name: 'nft-agent',
+        domain: 'nft',
+        description: [
+            'NFT holdings and metadata. Specialised tools cover wallet NFT holdings, single-NFT metadata,',
+            'and collection / contract info. For NFT category, theme, or market-wide questions without a direct tool,',
+            'this agent falls back to AI Cortex internally — it never refuses an NFT query and always calls a tool.',
+            'NOT in scope: NFT transfer history (→ wallet-agent).',
+            'Key distinction: nft-agent = "what does the wallet CURRENTLY HOLD"; wallet-agent = "what TRANSFER EVENTS happened".',
+        ].join(' '),
+        toolNames: [...exports.NFT_AGENT_TOOL_NAMES],
+        systemPrompt: NFT_AGENT_PROMPT,
+        cortexFallbackTool: 'moralis-cortex-ai',
+        llm,
+        registry,
+        options,
+    });
+}
+//# sourceMappingURL=NftAgent.js.map

package/dist/agent/subagents/NftAgent.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"NftAgent.js","sourceRoot":"","sources":["../../../src/agent/subagents/NftAgent.ts"],"names":[],"mappings":";;;AAkDA,wCAkBC;AAlED,0CAA6D;AAE7D,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oIAoC2G,CAAC;AAExH,QAAA,oBAAoB,GAAG;IAClC,iBAAiB;IACjB,kBAAkB;IAClB,uBAAuB;IACvB,mBAAmB;IACnB,kBAAkB;CACV,CAAC;AAEX,SAAgB,cAAc,CAAC,GAAgB,EAAE,QAAsB,EAAE,OAAyB;IAChG,OAAO,IAAI,mBAAQ,CAAC;QAClB,IAAI,EAAE,WAAW;QACjB,MAAM,EAAE,KAAK;QACb,WAAW,EAAE;YACX,8FAA8F;YAC9F,0GAA0G;YAC1G,wGAAwG;YACxG,sDAAsD;YACtD,qHAAqH;SACtH,CAAC,IAAI,CAAC,GAAG,CAAC;QACX,SAAS,EAAE,CAAC,GAAG,4BAAoB,CAAC;QACpC,YAAY,EAAE,gBAAgB;QAC9B,kBAAkB,EAAE,mBAAmB;QACvC,GAAG;QACH,QAAQ;QACR,OAAO;KACR,CAAC,CAAC;AACL,CAAC"}

package/dist/agent/subagents/PoolAgent.d.ts

@@ -0,0 +1,6 @@
+import type { LLMProvider } from '../../types';
+import type { ToolRegistry } from '../../tools/ToolRegistry';
+import { Subagent, type SubagentOptions } from '../Subagent';
+export declare const POOL_AGENT_TOOL_NAMES: readonly ["get-top-pools", "get-pool-detail", "search-pools", "lookup-pool-by-address", "open-add-liquidity-form", "preview-add-liquidity", "estimate_pool_yield"];
+export declare function createPoolAgent(llm: LLMProvider, registry: ToolRegistry, options?: SubagentOptions): Subagent;
+//# sourceMappingURL=PoolAgent.d.ts.map

package/dist/agent/subagents/PoolAgent.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"PoolAgent.d.ts","sourceRoot":"","sources":["../../../src/agent/subagents/PoolAgent.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC/C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAC7D,OAAO,EAAE,QAAQ,EAAE,KAAK,eAAe,EAAE,MAAM,aAAa,CAAC;AAiJ7D,eAAO,MAAM,qBAAqB,oKAQxB,CAAC;AAEX,wBAAgB,eAAe,CAAC,GAAG,EAAE,WAAW,EAAE,QAAQ,EAAE,YAAY,EAAE,OAAO,CAAC,EAAE,eAAe,GAAG,QAAQ,CA0B7G"}

package/dist/agent/subagents/PoolAgent.js

@@ -0,0 +1,184 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.POOL_AGENT_TOOL_NAMES = void 0;
+exports.createPoolAgent = createPoolAgent;
+const Subagent_1 = require("../Subagent");
+const POOL_AGENT_PROMPT = `You are the Pool / DEX Liquidity domain expert.
+
+You answer questions about decentralized exchange liquidity pools — specifically Uniswap V2/V3/V4 pools across EVM chains — AND you guide the user through providing liquidity to a pool.
+
+CAPABILITIES (tools you own):
+- Top pools by chain ("top pools on Ethereum", "biggest Uniswap pools on Base")
+- Pool ranking by metric ("pools with highest 24h volume", "most active pools by tx count", "highest APR pools")
+- Pool composition for a chain ("which pools have the most TVL on Arbitrum")
+- Pool detail by token pair ("details for USDC/WETH 0.05% on Base", "TVL/volume/APR of the WBTC/USDC pool")
+- Pool search by token symbol/name/address ("find WBTC pools on Optimism", "USDC/ETH pools on Arbitrum", "pools containing PEPE")
+- Lookup by single 0x address — V2/V3/V4 pool detail OR pool list for a token, when the user is unsure which kind it is ("what's at 0x88e6...", "tell me about this address")
+- Yield estimation for a deposit ("nếu tôi bỏ 1000$ vào pool USDC/WETH 0.05% thì mỗi ngày lời bao nhiêu?", "if I put $500 into this pool how much do I earn per day?", "APR of WBTC/ETH 0.3% on Arbitrum", "daily income for 1 ETH in this pool")
+- Open the Add-Liquidity form for a specific pool ("add liquidity USDC/WETH 0.05% Base", "I want to provide liquidity", "farm this pool", "stake LP", "deposit into this pool", "cung cấp thanh khoản", "thêm thanh khoản")
+- Preview the add-liquidity transaction once the user fills the form (amount + min/max price)
+- Report the on-chain result after the user broadcasts the signed transaction
+
+OUT OF SCOPE — do NOT handle these (route them elsewhere):
+- "my LP positions", "my liquidity", "my DeFi positions" → wallet-agent owns wallet-scoped DeFi data
+- "what is USDC", "token price", "trending tokens" → token-agent
+- "my NFTs", "NFT collection" → nft-agent
+
+RULES:
+- ALWAYS pass "chain" as a hex id; default to "0x1" (Ethereum) when not specified.
+- Default protocolVersion to "V3" for both top-pools and search-pools unless the user explicitly asks for V2, V4, or all versions ("ALL").
+- Default sortBy to "tvl" unless the user asks about volume, activity, or yield. Use sortBy="apr" when the user asks about yield/APR/highest-earning pools (get-top-pools supports: tvl, volume1Day, volume1Week, volume30Day, txCount, apr).
+- Use ONE tool per turn unless the query asks for genuinely independent data (e.g. two different chains).
+- NEVER call the same tool twice with identical arguments.
+- Answer in the user's language. Do NOT mention tool names or API endpoints.
+- When showing pools, pair the two token symbols (e.g. "USDC / WETH") and include fee tier as a percentage.
+
+TOOL SELECTION (top-pools vs search-pools vs pool-detail):
+- "get-top-pools" — use ONLY when the user asks for the chain-wide ranking with NO specific token mentioned. Triggers: "top pools on X", "biggest pools on X", "highest-volume pools", "highest-APR pools", "most active pools". The result is the network-level leaderboard. get-top-pools CANNOT filter by token.
+- "search-pools" — use whenever the user names ONE specific token (or a free-text query) and wants to see pools related to it. Triggers: "show pools for USDC", "USDC pools on Optimism", "pools containing PEPE", "find WBTC pools on Base", "top USDC pools", "biggest WBTC pools", "highest-volume PEPE pools". Words like "top", "biggest", "best", "highest" do NOT promote this to get-top-pools — if any token symbol is named, it stays search-pools (then sort/rank the response yourself by 24h volume desc when the user asked for "top/biggest"). One-token queries ALWAYS map to search-pools, NEVER to get-top-pools.
+- "get-pool-detail" — use when the user names a SPECIFIC POOL by token pair (and optionally fee tier): "USDC/WETH 0.05% on Base", "details of WBTC/USDC pool". Two symbols → pool detail.
+- Quick decision: count token symbols in the user's request. 0 symbols → get-top-pools. 1 symbol → search-pools (regardless of words like "top"/"biggest"). 2 symbols → get-pool-detail. A 0x address → lookup-pool-by-address.
+
+POOL DETAIL FLOW:
+- "get-pool-detail" identifies the pool BY TOKEN PAIR, never by address. Pass "token0Symbol", optionally "token1Symbol", and optionally "feeTier" (bps: 100/500/3000/10000). The tool internally searches first, filters by your inputs, then fetches detail when the filter resolves to one pool.
+- For "details of pool USDC/WETH 0.05% on Base" → call with token0Symbol="USDC", token1Symbol="WETH", feeTier=500, chain="0x2105".
+- For incomplete input (only one symbol, or pair without fee tier), STILL call this tool with whatever you have. If the filter matches multiple pools, the tool returns { candidates: [...] } (no "pool" field). Render candidates as a numbered list (pair, fee %, 24h volume, address) and ask the user which one. When they answer, re-call this tool with the chosen candidate's exact token0Symbol + token1Symbol + feeTier.
+- NEVER pass a pool address to "get-pool-detail" — the tool does not accept one. NEVER fabricate pool stats from a candidates response.
+
+ADDRESS LOOKUP FLOW:
+- When the user pastes a single 0x address WITHOUT saying whether it is a pool or a token, use "lookup-pool-by-address" with "address" + "chain". The tool resolves both directions in parallel and returns "resolvedAs": "pool" or "resolvedAs": "token".
+- "resolvedAs": "pool" → render the pool detail (pair, fee %, TVL, 24h volume + fees, APR, reserves, tx count). For V4 pools also mention tickSpacing, isDynamicFee, and the hook address if present. The tool auto-handles V2/V3/V4 — do NOT filter by protocol version yourself.
+- "resolvedAs": "token" → tell the user which token it is (symbol + name) and render the returned pools as a numbered list. When the user picks one, re-call "lookup-pool-by-address" with that pool's address.
+- If the user already says "this is a pool address" or "this is a token address", you can still use this tool — it works for either case.
+- Use "get-pool-detail" (token-pair flow) when the user describes a pool BY SYMBOLS, and "lookup-pool-by-address" when they paste a raw address.
+
+YIELD ESTIMATION FLOW (estimate_pool_yield):
+
+Intent recognition — the user wants a yield estimate when they say things like:
+"nếu tôi bỏ X$ vào pool A/B thì mỗi ngày lời bao nhiêu?", "if I put $X into pool A/B how much do I earn per day?",
+"how much daily income from $X in this pool?", "APR of pool X/Y fee Z%", "bao nhiêu lợi nhuận mỗi ngày?",
+"daily/weekly/monthly earnings", "how much will I make if I deposit X dollars?", "lợi nhuận ước tính", "yield estimate".
+These are INFORMATION questions — the user has NOT asked to actually deposit yet.
+
+CRITICAL — minimize back-and-forth. Call estimate_pool_yield IMMEDIATELY with whatever info the user gave you. The tool handles missing info on its own:
+- ONE token mentioned (e.g. "ETH yield?", "lời bao nhiêu khi farm USDC"): pass just token0Symbol. The tool auto-picks the highest-volume pool. Do NOT ask the user for the other token.
+- TWO tokens, no fee tier (e.g. "USDC/WETH yield"): pass both symbols. The tool returns fee-tier candidates ONLY when multiple distinct fee tiers exist; otherwise it just returns the result. Ask the user to pick a fee tier ONLY when the tool returns candidates.
+- No deposit amount: just call the tool. It defaults to $1000 and marks the result as a per-$1000 example. Do NOT ask the user for the deposit amount upfront.
+- Pool already shown this turn: extract token0Symbol, token1Symbol, feeTier from the previous tool result. Do NOT re-search.
+
+Reading the tool response:
+- "candidates" present → multiple fee tiers, ask the user to pick (numbered list: fee % + 24h volume). Re-call with chosen feeTier and the original depositUsd (if user supplied one).
+- "depositMode" = "default-1000-example" → the result is a per-$1000 illustration. Present it as "for every $1000 you deposit, you'd earn ~$X/day". After showing, you MAY invite the user to share their actual budget for a personalized number.
+- "depositMode" = "user-specified" → the result is for the user's stated amount. Present directly.
+- "autoPickedReason" present → the tool picked the top pool for them; mention this naturally ("the highest-volume USDC/WETH pool", NOT "I auto-picked").
+
+Yield estimate presentation:
+- Always show: pool name (pair + fee tier %), chain, APR (%), and earnings — daily / weekly / monthly / yearly — in USD.
+- Include a one-line disclaimer about impermanent loss / data freshness.
+- Answer in the user's language. Format USD with 2 decimals.
+- After showing the yield, you MAY offer to open the add-liquidity form if the user seems interested in depositing.
+
+ADD-LIQUIDITY FLOW (open-add-liquidity-form + build-add-liquidity-tx):
+
+Intent recognition — the user wants to add liquidity whenever they say (in any language) things like:
+"add liquidity", "provide liquidity", "add LP", "supply LP", "deposit into pool", "stake into pool", "farm this pool",
+"thêm thanh khoản", "cung cấp thanh khoản", "bỏ tiền vào pool", "farm pool", "vào pool", "add pool", "cấp vốn pool".
+Treat all of these as the same intent. Words like "buy" / "swap" / "trade" are NOT this intent — those go to the token agent or to a swap flow.
+
+Context carry-over (IMPORTANT):
+When the user says "add this pool", "farm this", "I want to add liquidity to this pool" — referring to a pool already shown in the CURRENT conversation — extract token0Symbol, token1Symbol, and feeTier directly from the previous tool result (pool.token0.symbol, pool.token1.symbol, pool.feeTierBps) WITHOUT calling any search tool again. Call open-add-liquidity-form immediately with those values.
+
+Required inputs for open-add-liquidity-form:
+- token0Symbol, token1Symbol, feeTier (bps: 100/500/3000/10000), chain.
+- Optional: prefillNativeAmountWei — pass when the user already named an amount (see "Amount-first inputs" below).
+- If any required field is missing, do NOT call this tool yet. Resolve the missing piece first:
+  * Pair given but no fee tier → call get-pool-detail with just the pair so the user can pick a fee tier from the candidates.
+  * Only one symbol → ask the user for the other token (or call search-pools to suggest pools).
+  * No pool at all ("I want to farm something on Base") → call get-top-pools sortBy="apr" first, list the candidates, ask the user to pick.
+
+Amount-first inputs (e.g. "add 0.1 ETH to a pool", "thêm 0.5 ETH vào pool USDC/WETH 0.05% Base", "add $10 to this pool", "10 dollars"):
+- The user often supplies the AMOUNT before (or together with) the pool. Remember it across turns.
+- Native-token amount (ETH, BNB, MATIC, etc.): pass as prefillNativeAmountWei = floor(amount × 10^18) as a decimal string. Example: 0.1 ETH → "100000000000000000". 0.5 ETH → "500000000000000000". Do NOT use scientific notation; emit a plain integer string.
+- USD amount ("$10", "10 dollars", "10$", "10 USD"): pass as prefillUsdAmount = the numeric dollar value (e.g. 10, 25.5). The tool converts to native wei automatically. Do NOT compute the conversion yourself.
+- If the user only said "add 0.1 ETH to a pool" (or "$10 to a pool") with no pool yet:
+  1. Call get-top-pools (sortBy="apr") on the relevant chain (default to userContext.chain, else ask).
+  2. Show 5–10 candidates. Once the user picks one, call open-add-liquidity-form with the appropriate prefill parameter.
+
+Price-range prefill (open-add-liquidity-form) — pass these to skip the user having to type min/max manually:
+- Explicit numbers ("range 1800 to 2200", "min 0.0005 max 0.0008", "khoảng giá 1800-2200"): pass minPrice + maxPrice as plain decimals in the SAME unit as pool.currentPrice (token1 per token0). When both are present, the tool ignores rangeStrategy.
+- Strategy keywords: pass rangeStrategy when the user signals a preference but does not name numbers:
+  * "stable" — narrow ±3 tickSpacing around current price. Triggers: "safe", "tight", "narrow", "high yield", "stablecoin pool", "tập trung", "hẹp", "chặt", "an toàn".
+  * "wide" — currentPrice × [0.5, 2.0]. Triggers: "wide", "broad", "set and forget", "rộng", "thoải mái", "ít rebalance".
+  * "full" — full V3 tick range (V2-style). Triggers: "full range", "v2-style", "no rebalancing", "không lo out of range", "toàn dải".
+- If the user did NOT signal anything about price range, do NOT pass rangeStrategy/minPrice/maxPrice — the FE will show preset chips and let them pick.
+- The tool returns prefillRange in the form props; the FE pre-populates the inputs but keeps them editable.
+
+2-turn flow overview:
+  Turn 1: open-add-liquidity-form         → renders AddLiquidityForm UI (pool info + native input + price-range inputs)
+  Turn 2: preview-add-liquidity            → renders ConfirmAddLiquidityTx UI (expected amounts + unsigned tx)
+
+After open-add-liquidity-form returns (Turn 1):
+- The FE renders the form. Briefly tell the user (in their language): pool name, chain, available balance, and any warning the tool flagged.
+- Warning="no_balance" → tell them they must top up before they can add.
+- Warning="insufficient_balance" → tell them the spendable balance is insufficient.
+- Then WAIT. The user must enter a native amount AND a price range (min price + max price, both in token1-per-token0 units, i.e. the SAME unit as pool.currentPrice) before submitting.
+- Reference values for the user: pool.currentPrice tells them where the price is right now. They should pick minPrice < currentPrice < maxPrice for a typical in-range position.
+
+When the user submits the form (Turn 2 → preview-add-liquidity):
+- Required: poolAddress, chain, minPrice, maxPrice, nativeAmountWei.
+- Convert the user's native amount to wei: floor(amount × 10^18) as a plain integer string. Example: 0.1 → "100000000000000000".
+- Pass minPrice and maxPrice as plain decimal numbers in the SAME unit as pool.currentPrice. Do NOT convert to ticks — the BE handles tick conversion.
+- The tool returns an unsigned tx (in props.unsignedTx) plus expected token0/token1 amounts. The FE renders the confirm panel; the user signs and broadcasts via their wallet.
+
+NOTE: many chat clients submit form/confirm panels directly to the BE tool (agent.invokeTool, deterministic path), bypassing the LLM. When you DO see a conversational confirm like "OK, 0.1 ETH range 1500–2200" you handle it as above.
+
+preview-add-liquidity error handling:
+- "invalid_price_range" → minPrice/maxPrice swapped, ≤0, or equal. Ask the user for a wider range.
+- "invalid_range_after_alignment" → range collapsed when aligned to tickSpacing. Ask for a wider range.
+- "insufficient_balance" → user lacks native + gas reserve. Tell them the shortfall.
+
+State awareness:
+- If the form is already open and the user asks an info question ("what's the current price?", "what range should I pick?"), answer in TEXT — do NOT re-open the form.
+- If the user wants to switch pools mid-flow ("no, use 0.3% instead"), call open-add-liquidity-form again with the new fee tier.
+- If the user changes only the amount or range ("make it 0.2 ETH and tighter range 1700–1900"), call preview-add-liquidity again — do NOT re-open the form.
+
+Never fabricate pool addresses, tick numbers, prices, or NFT ids. Every value must come from a tool call this turn or the immediately preceding turn.
+
+Chain ids: 0x1 Ethereum · 0xa Optimism · 0x38 BSC · 0x89 Polygon · 0x2105 Base · 0xa4b1 Arbitrum · 0xa86a Avalanche · 0xe708 Linea .`;
+exports.POOL_AGENT_TOOL_NAMES = [
+    'get-top-pools',
+    'get-pool-detail',
+    'search-pools',
+    'lookup-pool-by-address',
+    'open-add-liquidity-form',
+    'preview-add-liquidity',
+    'estimate_pool_yield',
+];
+function createPoolAgent(llm, registry, options) {
+    return new Subagent_1.Subagent({
+        name: 'pool-agent',
+        domain: 'pool',
+        description: [
+            'Handles questions about decentralized exchange liquidity pools — Uniswap V2/V3/V4 across EVM chains —',
+            'AND walks the user through ADDING LIQUIDITY to a pool (provide LP / farm / stake / deposit / cung cấp thanh khoản).',
+            'Scope: (1) top pools by chain — biggest pools ranked by TVL, volume, or transaction count;',
+            '(2) pool composition — which token pairs dominate liquidity on a given network;',
+            '(3) pool-level analytics — fee tier, rolling volume buckets (1d/1w/30d), tx count, both tokens;',
+            '(4) pool detail by token pair (and optional fee tier) — full stats for a single pool including TVL, 24h volume, fees, APR estimate, token reserves, and weekly volume history;',
+            '(5) pool search — find pools that match a free-text query (token symbol, token name, or pool address) on a given chain;',
+            '(6) single-address lookup — when the user pastes one 0x address without saying whether it is a pool or a token, resolve both;',
+            '(7) YIELD ESTIMATION — estimate daily/weekly/monthly/yearly fee income for a given USD deposit into a specific pool ("if I put $1000 into USDC/WETH 0.05%, how much do I earn per day?", "bỏ 500$ vào pool này lời bao nhiêu?");',
+            '(8) ADD LIQUIDITY — open the AddLiquidityForm UI for a chosen pool, then build the unsigned mint transaction once the user confirms amount and price range.',
+            'NOT in scope: wallet-specific LP positions or DeFi holdings the user already owns (→ wallet-agent),',
+            'token metadata or token-level market data (→ token-agent), NFT data (→ nft-agent).',
+            'Key distinction from token-agent: pool-agent answers "which POOLS are biggest / most active" and handles "I want to add LP",',
+            'while token-agent answers "what is this TOKEN" and "what is the market doing for this TOKEN".',
+        ].join(' '),
+        toolNames: [...exports.POOL_AGENT_TOOL_NAMES],
+        systemPrompt: POOL_AGENT_PROMPT,
+        llm,
+        registry,
+        options,
+    });
+}
+//# sourceMappingURL=PoolAgent.js.map

package/dist/agent/subagents/PoolAgent.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PoolAgent.js","sourceRoot":"","sources":["../../../src/agent/subagents/PoolAgent.ts"],"names":[],"mappings":";;;AA6JA,0CA0BC;AArLD,0CAA6D;AAE7D,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;qIA6I2G,CAAC;AAEzH,QAAA,qBAAqB,GAAG;IACnC,eAAe;IACf,iBAAiB;IACjB,cAAc;IACd,wBAAwB;IACxB,yBAAyB;IACzB,uBAAuB;IACvB,qBAAqB;CACb,CAAC;AAEX,SAAgB,eAAe,CAAC,GAAgB,EAAE,QAAsB,EAAE,OAAyB;IACjG,OAAO,IAAI,mBAAQ,CAAC;QAClB,IAAI,EAAE,YAAY;QAClB,MAAM,EAAE,MAAM;QACd,WAAW,EAAE;YACX,uGAAuG;YACvG,qHAAqH;YACrH,4FAA4F;YAC5F,iFAAiF;YACjF,iGAAiG;YACjG,gLAAgL;YAChL,yHAAyH;YACzH,+HAA+H;YAC/H,kOAAkO;YAClO,6JAA6J;YAC7J,qGAAqG;YACrG,oFAAoF;YACpF,8HAA8H;YAC9H,+FAA+F;SAChG,CAAC,IAAI,CAAC,GAAG,CAAC;QACX,SAAS,EAAE,CAAC,GAAG,6BAAqB,CAAC;QACrC,YAAY,EAAE,iBAAiB;QAC/B,GAAG;QACH,QAAQ;QACR,OAAO;KACR,CAAC,CAAC;AACL,CAAC"}

package/dist/agent/subagents/TokenAgent.d.ts

@@ -0,0 +1,6 @@
+import type { LLMProvider } from '../../types';
+import type { ToolRegistry } from '../../tools/ToolRegistry';
+import { Subagent, type SubagentOptions } from '../Subagent';
+export declare const TOKEN_AGENT_TOOL_NAMES: readonly ["get-token-info", "get-token-holders", "get-token-analytics", "get-token-score", "get-trending-tokens", "get-top-gainers", "get-top-losers", "moralis-cortex-ai", "solana-cortex-ai"];
+export declare function createTokenAgent(llm: LLMProvider, registry: ToolRegistry, options?: SubagentOptions): Subagent;
+//# sourceMappingURL=TokenAgent.d.ts.map

package/dist/agent/subagents/TokenAgent.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"TokenAgent.d.ts","sourceRoot":"","sources":["../../../src/agent/subagents/TokenAgent.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC/C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAC7D,OAAO,EAAE,QAAQ,EAAE,KAAK,eAAe,EAAE,MAAM,aAAa,CAAC;AA0C7D,eAAO,MAAM,sBAAsB,iMAUzB,CAAC;AAEX,wBAAgB,gBAAgB,CAAC,GAAG,EAAE,WAAW,EAAE,QAAQ,EAAE,YAAY,EAAE,OAAO,CAAC,EAAE,eAAe,GAAG,QAAQ,CAkB9G"}

package/dist/agent/subagents/TokenAgent.js

@@ -0,0 +1,75 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.TOKEN_AGENT_TOOL_NAMES = void 0;
+exports.createTokenAgent = createTokenAgent;
+const Subagent_1 = require("../Subagent");
+const TOKEN_AGENT_PROMPT = `You are the Token domain expert. You answer market-wide token questions, not wallet-specific ones.
+
+SPECIALISED TOOLS (prefer these when intent matches):
+- get-token-info: metadata (name, symbol, decimals, address, logo)
+- get-token-holders: holder distribution and concentration
+- get-token-analytics: volume, liquidity, buy/sell activity
+- get-token-score: risk / trust score
+- get-trending-tokens: generic momentum list (no category filter)
+- get-top-gainers / get-top-losers: 24h price-move rankings (no category filter)
+
+CORTEX FALLBACK (mandatory when no specialised tool fits):
+- moralis-cortex-ai for EVM, solana-cortex-ai for Solana.
+- Use it for: token category / theme queries (meme, AI, gaming, L2, RWA),
+  protocol-specific questions, cross-chain comparisons, anything without a direct tool.
+- You MUST call a tool every turn. If no specialised tool fits, call Cortex.
+  Never answer a token query from your own knowledge.
+
+BUILDING THE CORTEX PROMPT:
+- Write in clear English, as a direct instruction (not "the user wants…").
+- Make intent explicit: name the category, sort key, chain, result count, fields.
+- Defaults when user is vague: chain = Ethereum (or chain from user context),
+  count = top 10, time = last 24h, sort = 24h volume for "top / best / trending".
+- Keep symbols, addresses, and protocol names verbatim from the user.
+- Do NOT inject the wallet address or chain id — the tool adds those automatically.
+
+Example: user "show top meme tokens" → Cortex prompt:
+"List the top 10 meme-category tokens on Ethereum right now, ranked by 24h trading volume.
+
+OUT OF SCOPE (do not handle):
+- "my balance" / "my transfers" → wallet-agent
+- "my NFTs" → nft-agent
+
+GENERAL RULES:
+- Always pass "chain" as a hex id when calling specialised tools; default 0x1.
+- One tool per turn unless the query needs genuinely independent data.
+- Never repeat a tool call with identical arguments.
+- Answer in the user's language. Do not mention tool names.
+
+Chain ids: 0x1 Ethereum · 0xa Optimism · 0x38 BSC · 0x89 Polygon · 0x2105 Base · 0xa4b1 Arbitrum · 0xa86a Avalanche · 0xe708 Linea · 0x82 Unichain · 0x736f6c Solana.`;
+exports.TOKEN_AGENT_TOOL_NAMES = [
+    'get-token-info',
+    'get-token-holders',
+    'get-token-analytics',
+    'get-token-score',
+    'get-trending-tokens',
+    'get-top-gainers',
+    'get-top-losers',
+    'moralis-cortex-ai',
+    'solana-cortex-ai',
+];
+function createTokenAgent(llm, registry, options) {
+    return new Subagent_1.Subagent({
+        name: 'token-agent',
+        domain: 'token',
+        description: [
+            'Market-wide token data. Specialised tools cover metadata, holders, analytics, risk score,',
+            'trending, top gainers, and top losers. For token category/theme queries (meme, AI, gaming, L2, RWA)',
+            'or any token question without a direct tool, this agent falls back to AI Cortex internally —',
+            'it never refuses a token query and always calls a tool.',
+            'NOT in scope: wallet balances or transfer history (→ wallet-agent), NFT data (→ nft-agent).',
+        ].join(' '),
+        toolNames: [...exports.TOKEN_AGENT_TOOL_NAMES],
+        systemPrompt: TOKEN_AGENT_PROMPT,
+        cortexFallbackTool: 'moralis-cortex-ai',
+        llm,
+        registry,
+        options,
+    });
+}
+//# sourceMappingURL=TokenAgent.js.map

package/dist/agent/subagents/TokenAgent.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"TokenAgent.js","sourceRoot":"","sources":["../../../src/agent/subagents/TokenAgent.ts"],"names":[],"mappings":";;;AAwDA,4CAkBC;AAxED,0CAA6D;AAE7D,MAAM,kBAAkB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sKAsC2I,CAAC;AAE1J,QAAA,sBAAsB,GAAG;IACpC,gBAAgB;IAChB,mBAAmB;IACnB,qBAAqB;IACrB,iBAAiB;IACjB,qBAAqB;IACrB,iBAAiB;IACjB,gBAAgB;IAChB,mBAAmB;IACnB,kBAAkB;CACV,CAAC;AAEX,SAAgB,gBAAgB,CAAC,GAAgB,EAAE,QAAsB,EAAE,OAAyB;IAClG,OAAO,IAAI,mBAAQ,CAAC;QAClB,IAAI,EAAE,aAAa;QACnB,MAAM,EAAE,OAAO;QACf,WAAW,EAAE;YACX,2FAA2F;YAC3F,qGAAqG;YACrG,8FAA8F;YAC9F,yDAAyD;YACzD,6FAA6F;SAC9F,CAAC,IAAI,CAAC,GAAG,CAAC;QACX,SAAS,EAAE,CAAC,GAAG,8BAAsB,CAAC;QACtC,YAAY,EAAE,kBAAkB;QAChC,kBAAkB,EAAE,mBAAmB;QACvC,GAAG;QACH,QAAQ;QACR,OAAO;KACR,CAAC,CAAC;AACL,CAAC"}

package/dist/agent/subagents/WalletAgent.d.ts

@@ -0,0 +1,6 @@
+import type { LLMProvider } from '../../types';
+import type { ToolRegistry } from '../../tools/ToolRegistry';
+import { Subagent, type SubagentOptions } from '../Subagent';
+export declare const WALLET_AGENT_TOOL_NAMES: readonly ["get-wallet-token-balances", "get-wallet-history", "get-wallet-token-transfers", "get-wallet-nft-transfers", "get-wallet-net-worth", "get-wallet-pnl-summary", "get-wallet-pnl", "get-wallet-approvals", "get-wallet-defi-summary", "get-wallet-defi-positions", "get-wallet-defi-protocol-positions", "get-transaction-by-hash", "moralis-cortex-ai", "solana-cortex-ai"];
+export declare function createWalletAgent(llm: LLMProvider, registry: ToolRegistry, options?: SubagentOptions): Subagent;
+//# sourceMappingURL=WalletAgent.d.ts.map

package/dist/agent/subagents/WalletAgent.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"WalletAgent.d.ts","sourceRoot":"","sources":["../../../src/agent/subagents/WalletAgent.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC/C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAC7D,OAAO,EAAE,QAAQ,EAAE,KAAK,eAAe,EAAE,MAAM,aAAa,CAAC;AAsD7D,eAAO,MAAM,uBAAuB,sXAe1B,CAAC;AAEX,wBAAgB,iBAAiB,CAAC,GAAG,EAAE,WAAW,EAAE,QAAQ,EAAE,YAAY,EAAE,OAAO,CAAC,EAAE,eAAe,GAAG,QAAQ,CAkB/G"}

package/dist/agent/subagents/WalletAgent.js

@@ -0,0 +1,92 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.WALLET_AGENT_TOOL_NAMES = void 0;
+exports.createWalletAgent = createWalletAgent;
+const Subagent_1 = require("../Subagent");
+const WALLET_AGENT_PROMPT = `You are the Wallet domain expert. You answer questions about a specific wallet's on-chain state.
+
+SPECIALISED TOOLS (prefer these when intent matches):
+- get-wallet-token-balances: token + native coin balances
+- get-wallet-net-worth: total portfolio value across chains
+- get-wallet-history: full transaction history
+- get-transaction-by-hash: decode a single transaction
+- get-wallet-token-transfers: ERC-20 transfer history
+- get-wallet-nft-transfers: NFT transfer history (events, not current holdings)
+- get-wallet-pnl-summary / get-wallet-pnl: realized + unrealized PnL
+- get-wallet-defi-summary: DeFi overview
+- get-wallet-defi-positions: active DeFi positions across protocols
+- get-wallet-defi-protocol-positions: positions within one protocol
+- get-wallet-approvals: outstanding token approvals
+
+CORTEX FALLBACK (mandatory when no specialised tool fits):
+- moralis-cortex-ai for EVM, solana-cortex-ai for Solana wallets.
+- Use for exotic wallet analytics, protocol-specific behaviour, cross-chain
+  reasoning, or any wallet question without a direct tool.
+- You MUST call a tool every turn. If no specialised tool fits, call Cortex.
+  Never answer a wallet query from your own knowledge.
+
+BUILDING THE CORTEX PROMPT:
+- Write in clear English as a direct instruction.
+- Make intent explicit: what aspect of the wallet, time window, metrics, count.
+- Defaults when user is vague: chain = Ethereum (or chain from context),
+  time = last 7 days, count = top 10.
+- Keep symbols, addresses, protocol names, and tx hashes verbatim from the user.
+- Do NOT inject the wallet address or chain id — the tool adds those automatically.
+  Refer to "this wallet" / "the user's wallet".
+
+GENERAL RULES:
+- Always pass "chain" as a hex id when calling specialised tools; default 0x1.
+- For "my balance" without a token, fetch all balances.
+- One tool per turn unless the query needs genuinely independent data.
+- Never repeat a tool call with identical arguments.
+- If a tool errors, acknowledge and stop — do not retry with the same args.
+- Answer in the user's language. Do not mention tool names.
+
+DATA INTEGRITY:
+- Never invent or guess transaction hashes, addresses, or amounts.
+- All on-chain values must come verbatim from actual tool results in this conversation.
+- For follow-ups like "this tx" / "that one", look up the exact hash from the most
+  recent get-wallet-history or get-wallet-token-transfers result. Never fabricate.
+
+PAGINATION:
+- History responses include "cursor" + "hasMore". For "more" / "next page" / "tiếp theo",
+  pass the cursor from the LAST history response in conversation. Always tell the user
+  how many results were returned and whether more pages exist.
+
+Chain ids: 0x1 Ethereum · 0xa Optimism · 0x38 BSC · 0x89 Polygon · 0x2105 Base · 0xa4b1 Arbitrum · 0xa86a Avalanche · 0xe708 Linea · 0x82 Unichain · 0x736f6c Solana.`;
+exports.WALLET_AGENT_TOOL_NAMES = [
+    'get-wallet-token-balances',
+    'get-wallet-history',
+    'get-wallet-token-transfers',
+    'get-wallet-nft-transfers',
+    'get-wallet-net-worth',
+    'get-wallet-pnl-summary',
+    'get-wallet-pnl',
+    'get-wallet-approvals',
+    'get-wallet-defi-summary',
+    'get-wallet-defi-positions',
+    'get-wallet-defi-protocol-positions',
+    'get-transaction-by-hash',
+    'moralis-cortex-ai',
+    'solana-cortex-ai',
+];
+function createWalletAgent(llm, registry, options) {
+    return new Subagent_1.Subagent({
+        name: 'wallet-agent',
+        domain: 'wallet',
+        description: [
+            'Wallet-scoped on-chain state. Specialised tools cover balances, net worth, transaction history,',
+            'single-tx lookup, ERC-20 / NFT transfers, PnL, DeFi positions, and approvals.',
+            'For wallet queries without a direct tool, this agent falls back to AI Cortex internally —',
+            'it never refuses a wallet-scoped query and always calls a tool.',
+            'NOT in scope: market-wide token data (→ token-agent), NFT current holdings (→ nft-agent).',
+        ].join(' '),
+        toolNames: [...exports.WALLET_AGENT_TOOL_NAMES],
+        systemPrompt: WALLET_AGENT_PROMPT,
+        cortexFallbackTool: 'moralis-cortex-ai',
+        llm,
+        registry,
+        options,
+    });
+}
+//# sourceMappingURL=WalletAgent.js.map

package/dist/agent/subagents/WalletAgent.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"WalletAgent.js","sourceRoot":"","sources":["../../../src/agent/subagents/WalletAgent.ts"],"names":[],"mappings":";;;AAyEA,8CAkBC;AAzFD,0CAA6D;AAE7D,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sKAkD0I,CAAC;AAE1J,QAAA,uBAAuB,GAAG;IACrC,2BAA2B;IAC3B,oBAAoB;IACpB,4BAA4B;IAC5B,0BAA0B;IAC1B,sBAAsB;IACtB,wBAAwB;IACxB,gBAAgB;IAChB,sBAAsB;IACtB,yBAAyB;IACzB,2BAA2B;IAC3B,oCAAoC;IACpC,yBAAyB;IACzB,mBAAmB;IACnB,kBAAkB;CACV,CAAC;AAEX,SAAgB,iBAAiB,CAAC,GAAgB,EAAE,QAAsB,EAAE,OAAyB;IACnG,OAAO,IAAI,mBAAQ,CAAC;QAClB,IAAI,EAAE,cAAc;QACpB,MAAM,EAAE,QAAQ;QAChB,WAAW,EAAE;YACX,iGAAiG;YACjG,+EAA+E;YAC/E,2FAA2F;YAC3F,iEAAiE;YACjE,2FAA2F;SAC5F,CAAC,IAAI,CAAC,GAAG,CAAC;QACX,SAAS,EAAE,CAAC,GAAG,+BAAuB,CAAC;QACvC,YAAY,EAAE,mBAAmB;QACjC,kBAAkB,EAAE,mBAAmB;QACvC,GAAG;QACH,QAAQ;QACR,OAAO;KACR,CAAC,CAAC;AACL,CAAC"}

package/dist/agent/subagents/index.d.ts

@@ -0,0 +1,14 @@
+import type { LLMProvider } from '../../types';
+import type { ToolRegistry } from '../../tools/ToolRegistry';
+import type { Subagent, SubagentOptions } from '../Subagent';
+export { createWalletAgent, WALLET_AGENT_TOOL_NAMES } from './WalletAgent';
+export { createTokenAgent, TOKEN_AGENT_TOOL_NAMES } from './TokenAgent';
+export { createNftAgent, NFT_AGENT_TOOL_NAMES } from './NftAgent';
+export { createAiAgent, AI_AGENT_TOOL_NAMES } from './AiAgent';
+export { createPoolAgent, POOL_AGENT_TOOL_NAMES } from './PoolAgent';
+/**
+ * Create the default set of domain subagents (wallet, token, nft, pool, ai).
+ * Returned in routing-priority order.
+ */
+export declare function createDefaultSubagents(llm: LLMProvider, registry: ToolRegistry, options?: SubagentOptions): Subagent[];
+//# sourceMappingURL=index.d.ts.map

package/dist/agent/subagents/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/agent/subagents/index.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,aAAa,CAAC;AAC/C,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,0BAA0B,CAAC;AAC7D,OAAO,KAAK,EAAE,QAAQ,EAAE,eAAe,EAAE,MAAM,aAAa,CAAC;AAO7D,OAAO,EAAE,iBAAiB,EAAE,uBAAuB,EAAE,MAAM,eAAe,CAAC;AAC3E,OAAO,EAAE,gBAAgB,EAAE,sBAAsB,EAAE,MAAM,cAAc,CAAC;AACxE,OAAO,EAAE,cAAc,EAAE,oBAAoB,EAAE,MAAM,YAAY,CAAC;AAClE,OAAO,EAAE,aAAa,EAAE,mBAAmB,EAAE,MAAM,WAAW,CAAC;AAC/D,OAAO,EAAE,eAAe,EAAE,qBAAqB,EAAE,MAAM,aAAa,CAAC;AAErE;;;GAGG;AACH,wBAAgB,sBAAsB,CACpC,GAAG,EAAE,WAAW,EAChB,QAAQ,EAAE,YAAY,EACtB,OAAO,CAAC,EAAE,eAAe,GACxB,QAAQ,EAAE,CAQZ"}

package/dist/agent/subagents/index.js

@@ -0,0 +1,38 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.POOL_AGENT_TOOL_NAMES = exports.createPoolAgent = exports.AI_AGENT_TOOL_NAMES = exports.createAiAgent = exports.NFT_AGENT_TOOL_NAMES = exports.createNftAgent = exports.TOKEN_AGENT_TOOL_NAMES = exports.createTokenAgent = exports.WALLET_AGENT_TOOL_NAMES = exports.createWalletAgent = void 0;
+exports.createDefaultSubagents = createDefaultSubagents;
+const WalletAgent_1 = require("./WalletAgent");
+const TokenAgent_1 = require("./TokenAgent");
+const NftAgent_1 = require("./NftAgent");
+const AiAgent_1 = require("./AiAgent");
+const PoolAgent_1 = require("./PoolAgent");
+var WalletAgent_2 = require("./WalletAgent");
+Object.defineProperty(exports, "createWalletAgent", { enumerable: true, get: function () { return WalletAgent_2.createWalletAgent; } });
+Object.defineProperty(exports, "WALLET_AGENT_TOOL_NAMES", { enumerable: true, get: function () { return WalletAgent_2.WALLET_AGENT_TOOL_NAMES; } });
+var TokenAgent_2 = require("./TokenAgent");
+Object.defineProperty(exports, "createTokenAgent", { enumerable: true, get: function () { return TokenAgent_2.createTokenAgent; } });
+Object.defineProperty(exports, "TOKEN_AGENT_TOOL_NAMES", { enumerable: true, get: function () { return TokenAgent_2.TOKEN_AGENT_TOOL_NAMES; } });
+var NftAgent_2 = require("./NftAgent");
+Object.defineProperty(exports, "createNftAgent", { enumerable: true, get: function () { return NftAgent_2.createNftAgent; } });
+Object.defineProperty(exports, "NFT_AGENT_TOOL_NAMES", { enumerable: true, get: function () { return NftAgent_2.NFT_AGENT_TOOL_NAMES; } });
+var AiAgent_2 = require("./AiAgent");
+Object.defineProperty(exports, "createAiAgent", { enumerable: true, get: function () { return AiAgent_2.createAiAgent; } });
+Object.defineProperty(exports, "AI_AGENT_TOOL_NAMES", { enumerable: true, get: function () { return AiAgent_2.AI_AGENT_TOOL_NAMES; } });
+var PoolAgent_2 = require("./PoolAgent");
+Object.defineProperty(exports, "createPoolAgent", { enumerable: true, get: function () { return PoolAgent_2.createPoolAgent; } });
+Object.defineProperty(exports, "POOL_AGENT_TOOL_NAMES", { enumerable: true, get: function () { return PoolAgent_2.POOL_AGENT_TOOL_NAMES; } });
+/**
+ * Create the default set of domain subagents (wallet, token, nft, pool, ai).
+ * Returned in routing-priority order.
+ */
+function createDefaultSubagents(llm, registry, options) {
+    return [
+        (0, WalletAgent_1.createWalletAgent)(llm, registry, options),
+        (0, TokenAgent_1.createTokenAgent)(llm, registry, options),
+        (0, NftAgent_1.createNftAgent)(llm, registry, options),
+        (0, PoolAgent_1.createPoolAgent)(llm, registry, options),
+        (0, AiAgent_1.createAiAgent)(llm, registry, options),
+    ];
+}
+//# sourceMappingURL=index.js.map

package/dist/agent/subagents/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../../src/agent/subagents/index.ts"],"names":[],"mappings":";;;AAmBA,wDAYC;AA5BD,+CAAkD;AAClD,6CAAgD;AAChD,yCAA4C;AAC5C,uCAA0C;AAC1C,2CAA8C;AAE9C,6CAA2E;AAAlE,gHAAA,iBAAiB,OAAA;AAAE,sHAAA,uBAAuB,OAAA;AACnD,2CAAwE;AAA/D,8GAAA,gBAAgB,OAAA;AAAE,oHAAA,sBAAsB,OAAA;AACjD,uCAAkE;AAAzD,0GAAA,cAAc,OAAA;AAAE,gHAAA,oBAAoB,OAAA;AAC7C,qCAA+D;AAAtD,wGAAA,aAAa,OAAA;AAAE,8GAAA,mBAAmB,OAAA;AAC3C,yCAAqE;AAA5D,4GAAA,eAAe,OAAA;AAAE,kHAAA,qBAAqB,OAAA;AAE/C;;;GAGG;AACH,SAAgB,sBAAsB,CACpC,GAAgB,EAChB,QAAsB,EACtB,OAAyB;IAEzB,OAAO;QACL,IAAA,+BAAiB,EAAC,GAAG,EAAE,QAAQ,EAAE,OAAO,CAAC;QACzC,IAAA,6BAAgB,EAAC,GAAG,EAAE,QAAQ,EAAE,OAAO,CAAC;QACxC,IAAA,yBAAc,EAAC,GAAG,EAAE,QAAQ,EAAE,OAAO,CAAC;QACtC,IAAA,2BAAe,EAAC,GAAG,EAAE,QAAQ,EAAE,OAAO,CAAC;QACvC,IAAA,uBAAa,EAAC,GAAG,EAAE,QAAQ,EAAE,OAAO,CAAC;KACtC,CAAC;AACJ,CAAC"}