@progress/kendo-react-mcp 1.9.0 → 1.10.2

package/dist/index.js

@@ -1,525 +1,105 @@
 #!/usr/bin/env node
-import{McpServer as Kt}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as jt}from"@modelcontextprotocol/sdk/server/stdio.js";import{dirname as Tt,join as xt}from"path";import{fileURLToPath as It}from"url";import{loadLicense as ht,decodeLicenseKey as gt,decodeLicenseEvidence as ft}from"@progress/kendo-licensing/utils";var W=class extends Error{constructor(t){super(t),this.name="LicenseError"}};function me(e){return e.replace(/^\uFEFF/,"")}async function z(e){let t=null,n=null;try{let o=ht();if(!o.success){let s=new W(o.message);throw e&&await e("license_load_failed",{error:o.message}).catch(()=>{}),s}try{t=(await gt(o.value)).licenses.find(async i=>!!(await ft(i)).userId)}catch(s){console.log(s.message),e&&await e("license_load_failed",{error:s.message||"Unknown decoding error"}).catch(()=>{})}if(!t)return[me(o.value),null]}catch(o){return n=o.message||"Unknown error loading license.",e&&await e("license_load_failed",{error:n}).catch(()=>{}),[null,n]}return[me(t),null]}import L from"node:fs";import V from"node:path";var Y=!1,U=process.env.DEBUG_LOG_FILE,he=!!(U&&typeof U=="string");if(he){let e=V.resolve(U),t=V.dirname(e);if(t!=="."&&t!==process.cwd()&&!L.existsSync(t))try{L.mkdirSync(t,{recursive:!0})}catch(n){console.error("Error creating log directory:",n)}if(!L.existsSync(e))try{L.writeFileSync(e,"")}catch(n){console.error("Error creating log file:",n)}}else Y=!1;Y=he&&!!U&&L.existsSync(V.resolve(U));function C(...e){if(Y&&U){let o=`${new Date().toISOString()}: ${e.join(" ")}
-`,s=V.resolve(U);L.appendFile(s,o,i=>{i&&console.error("Error writing to log file:",i)})}}import yt from"@grpc/proto-loader";import $ from"@grpc/grpc-js";import ye from"path";import ge from"fs";import{fileURLToPath as bt}from"url";var At=bt(import.meta.url),Ct=ye.dirname(At),be={version:"unknown"},fe=ye.resolve(Ct,"../package.json");ge.existsSync(fe)&&(be=JSON.parse(ge.readFileSync(fe,"utf-8")));function vt(e){return e.replace(/\u2014/g,"--").replace(/\u2013/g,"-").replace(/[^\x20-\x7E]/g,"")}var H=class{constructor(t,n,o){this.contextApiUrl=t;this.protoPath=n;this.options=o;this.toolNameHeader="assistant";let s=yt.loadSync(this.protoPath,{keepCase:!0,longs:String,enums:String,defaults:!0,oneofs:!0});this.isDev=this.contextApiUrl?.includes("localhost")||this.contextApiUrl?.includes("127.0.0.1"),C("Using ContextApi URl:",this.contextApiUrl);let i=$.loadPackageDefinition(s);this.client=new i.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?$.credentials.createInsecure():$.credentials.createSsl())}buildRequestMetadata(t={}){return vt(JSON.stringify({...t,source:"npm",version:be.version,os:process.platform,node_version:process.version}))}async getMetadata({meta:t}={meta:{}}){let[n,o]=this.isDev?["fake_license",null]:await z((d,p)=>this.logEvent(d,p)),s=process.env.CONTEXTAPI_API_KEY,i=s&&typeof s=="string",a=n&&typeof n=="string";if(!a&&!i&&o)throw new Error(`Failed to authenticate with API key or License key!
-
-License Error: ${o}`);let r=new $.Metadata;if(a)try{r.add("x-license-key",n)}catch(d){throw C("Error adding license key to metadata:",d),new Error(`Failed to use license key: ${d.message}`)}return i&&r.add("x-api-key",s),this.options?.libName&&r.add("x-library-name",this.options.libName),r.add("x-tool-name",this.toolNameHeader),r.add("x-request-metadata",this.buildRequestMetadata(t)),r}async query(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.query(t,o,(a,r)=>{a?i(new Error(a)):s(r)})})}async getApiRefMatches(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.getApiRefMatches(t,o,(a,r)=>{a?i(new Error(a)):s(r)})})}async queryCssUtils(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.cssUtilsSearch(t,o,(a,r)=>{a?(C("Error querying CSS Utils:",a),i(new Error(a))):s(r)})})}async queryIconsSearch(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.iconsSearch(t,o,(a,r)=>{a?(C("Error querying Icons Search:",a),i(new Error(a))):s(r)})})}async queryBuildingBlocks(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.buildingBlocksSearch(t,o,(a,r)=>{a?(C("Error querying Building Blocks:",a),i(new Error(a))):s(r)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((n,o)=>{this.client.validateUserLicense({},t,(s,i)=>{s?(C("Error validating user license:",s),o(new Error(s))):n(i)})})}async queryThemeGenerate(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.generateTheme(t,o,(a,r)=>{a?(C("Error querying context API/GenerateTheme:",a),i(new Error(a))):s(r)})})}async recordOrchestratorUserRequest({meta:t}){let n=await this.getMetadata({meta:t});return new Promise((o,s)=>{this.client.recordOrchestratorUserRequest({},n,(i,a)=>{i?(C("Error recording orchestrator user request:",i),s(new Error(i))):o(a)})})}async recordToolUserRequest({toolName:t,meta:n}){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.recordToolUserRequest({tool_name:t},o,(a,r)=>{a?(C("Error recording tool user request:",a),i(new Error(a))):s(r)})})}async logEvent(t,n,o={}){let s="h8utJ6rk4PpIWX4JMn9beQDsjVUri6KV0XYfiVwq",{enrichWithUserData:i=!1,meta:a={}}=o,r=s&&typeof s=="string",d=null;if(i)try{let[g]=this.isDev?["fake_license",null]:await z();g&&typeof g=="string"&&(d=g)}catch{}if(!r&&!d){C("Neither LOGGING_API_KEY nor license key available, skipping log event");return}let p=new $.Metadata;return r&&p.add("x-api-key",s),d&&(p.add("x-license-key",d),p.add("x-request-metadata",this.buildRequestMetadata(a)),this.options?.libName&&p.add("x-library-name",this.options.libName)),new Promise((g,b)=>{this.client.logEvent({event_name:t,fields:n||{}},p,(l,m)=>{l?(C("Error logging event:",l),b(new Error(l))):g()})})}};import{z as Q}from"zod";var mo=Q.object({user_id:Q.string(),user_email:Q.string().email()});import{z as w}from"zod";var wt=w.object({Product:w.object({Id:w.number().int(),Code:w.string(),Name:w.string()}),License:w.nullable(w.object({Id:w.number().int(),Name:w.string(),Type:w.string(),Active:w.boolean()})),Availability:w.array(w.object({LicenseStart:w.nullable(w.string().datetime()),LicenseEnd:w.nullable(w.string().datetime())})),IsLicenseAvailable:w.optional(w.boolean())}),fo=w.array(wt);function T(e,t){let n=e.server?.server.getClientVersion?.(),o=t||{};return n&&(o.clientInfo={name:n.name,version:n.version}),o}async function Ae(e){let t=process.env.KENDO_MCP_ACCESS;if(t==="true"||t==="1"||t==="full")return"full";if(typeof t=="string"&&(t.toLowerCase()==="agent"||t.toLowerCase()==="assistant"))return t.toLowerCase();let n=await e();return n?.toLocaleLowerCase()==="agentic_ui_generator"?"agent":n?.toLocaleLowerCase()==="ai_coding_assistants"?"assistant":"none"}function Ce(){return'**Accessibility Guidelines: WCAG 2.2 Level AA Compliance**\n\n**Core Principles:**\n1. Use semantic HTML and ARIA correctly\n2. Ensure WCAG 2.2 AA compliance\n3. Follow W3C ARIA Authoring Practices\n4. Provide standards-based accessibility fixes\n\n**1. Form Control Labels** (WCAG 1.3.1, 3.3.2, 4.1.2)\nEvery input must have an associated label.\nCORRECT: `<input type="search" aria-label="Search products" placeholder="Search...">`\nCORRECT: `<label for="qty">Quantity</label><input type="number" id="qty">`\nWRONG: `<span>Email</span><input type="email">` (no association)\nWRONG: `<input type="email" placeholder="Email">` (placeholder as label)\n\n**2. Button Accessibility** (WCAG 4.1.2, 2.4.6, 2.5.3)\nAll buttons need accessible names describing their purpose.\nCORRECT: `<button type="button">Save Changes</button>`\nCORRECT: `<button aria-label="Close dialog"><svg aria-hidden="true" focusable="false">...</svg></button>`\nWRONG: `<button><svg>...</svg></button>` (no accessible name)\nWRONG: `<button>Click here</button>` (generic text)\n\n**3. Popup/Menu Triggers** (WCAG 4.1.2, 1.3.1)\nIndicate popup purpose and state using aria-haspopup, aria-expanded, aria-controls.\nCORRECT: `<button aria-expanded="false" aria-haspopup="menu" aria-controls="menu-id">Settings</button>`\n\n**4. Image Accessibility** (WCAG 1.1.1)\nInformative: `<img src="chart.png" alt="Sales increased 25% in Q4 2024">`\nFunctional: `<a href="/home"><img src="logo.png" alt="Company Name Home"></a>`\nDecorative: `<img src="border.png" alt="" role="presentation">`\nComplex: `<img src="chart.png" alt="Sales data" aria-describedby="desc-id">`\nWRONG: Missing alt, filename as alt, generic alt for decorative images\n\n**5. Link Accessibility** (WCAG 2.4.4, 2.4.6)\nLinks must be descriptive and understandable out of context.\nCORRECT: `<a href="/products">View All Products</a>`\nCORRECT: `<a href="/article" aria-label="Read more about New Product Launch">Read more</a>`\nWRONG: "Click here", "Read more", "Learn more" without context\n\n**6. Form Validation** (WCAG 3.3.1, 3.3.2, 3.3.3)\nErrors must be identified, associated with inputs, and provide suggestions. Use aria-describedby, aria-invalid="true", and role="alert".\n\n**7. Heading Structure** (WCAG 1.3.1, 2.4.6)\nEach page must have an `<h1>` that describes its content. Use hierarchical, descriptive headings with no skipped levels (h1\u2192h2\u2192h3).\nCORRECT: `<h1>Dashboard</h1> <h2>Sales</h2> <h3>By Region</h3>`\nWRONG: No `<h1>` on the page, or skipping levels (h1\u2192h3)\nIf a heading should look smaller than its semantic level, use CSS: `<h2 class="text-sm">Subtitle</h2>`\n\n**8. Page Component Landmark Rules** (WCAG 1.3.1, 4.1.2)\nPage components (route components) may be rendered inside a layout that already provides `<main>`, `<header>`, or `<footer>`. Since the layout configuration is unknown, avoid using these landmarks in page components to prevent potential duplication and nesting violations. Use `<div>`, `<section>`, or `<article>` as the top-level wrapper instead.\n- Avoid adding `<main>`, `role="main"`, `<header>`, or `<footer>` in page components \u2014 the layout typically provides them. Duplicating them can cause `landmark-no-duplicate-main` and `landmark-main-is-top-level` violations.\n- Avoid adding `role="banner"` or using a semantic `<header>` element in page components \u2014 the layout\'s `<header>` already claims the banner landmark. Adding another causes `landmark-banner-is-top-level` violations.\n- Avoid adding `role="contentinfo"` to elements inside page components \u2014 the contentinfo landmark should be a top-level landmark, not nested inside `<main>` or other landmarks. Nesting it can cause `landmark-contentinfo-is-top-level` violations.\n- When multiple `<section>` or `<nav>` elements exist on a page, give each a unique `aria-label` to avoid `landmark-unique` violations.\n\n**9. ARIA Role and Attribute Restrictions** (WCAG 4.1.2)\nOnly use ARIA roles that are valid for the given HTML element. Avoid adding `aria-label` or `aria-labelledby` to elements that do not permit naming.\n- `<article>` has an implicit `article` role. Do NOT override it with `role="listitem"`, `role="button"`, `role="link"`, or any other role \u2014 none are allowed on `<article>`. Use `<li>` for list items, `<button>` for interactive cards, or `<a>` for clickable cards instead.\n- `<button>` already has an implicit `button` role. Do NOT add `role="listitem"` or other incompatible roles.\n- `<span>` and `<div>` without roles are generic elements. Do NOT add `aria-label` to them \u2014 it is a prohibited attribute on elements with no accessible role and can cause `aria-prohibited-attr` violations. Instead, use `role="img"` + `aria-label` for visual indicators, or use visually hidden text.\n- Do NOT add `aria-label` to non-interactive `<div>` wrappers \u2014 it has no effect and triggers violations.\n- `aria-pressed` is only valid on elements with `role="button"`, `role="checkbox"`, `role="menuitemcheckbox"`, `role="option"`, `role="radio"`, or `role="switch"`. Do NOT use `aria-pressed` on elements with `role="listitem"` or other roles.\nCORRECT: `<ul role="list"><li class="product-card">...</li></ul>` (listitem inside list)\nCORRECT: `<span role="img" aria-label="Status: pending" class="status-dot"></span>` (role added before aria-label)\nCORRECT: `<span class="status-dot" aria-hidden="true"></span><span class="visually-hidden">Pending</span>` (hidden text alternative)\nWRONG: `<article role="listitem">` (listitem not allowed on article)\nWRONG: `<article role="button">` (button not allowed on article \u2014 use `<button>` or `<div role="button">`)\nWRONG: `<span aria-label="pending" class="status-dot"></span>` (aria-label prohibited on generic span)\nWRONG: `<div aria-label="Product badges" class="badges"></div>` (aria-label prohibited on generic div)\n\n**Quick Checklist:**\n- **Forms:** Associated labels, aria-required on required fields, autocomplete attributes, aria-describedby for errors, aria-invalid for invalid fields, fieldsets with legends\n- **Buttons/Links:** Accessible names, aria-label for icon buttons, aria-hidden on decorative icons, descriptive link text\n- **Popups/Dialogs:** aria-haspopup, aria-expanded, aria-controls, role="dialog", aria-modal="true", aria-labelledby, focus trap, Escape to close\n- **Images:** alt on all images, descriptive alt for informative, empty alt for decorative, aria-describedby for complex\n- **Structure:** One h1, logical heading hierarchy, avoid `<main>`, `<header>`, `<footer>`, `role="main"`, `role="contentinfo"`, `role="banner"` in page/route components (the layout may already provide them), use `<section>` or `<div>` as page-level wrappers, unique aria-labels on duplicate landmark types\n- **ARIA Rules:** Avoid adding `aria-label` to generic `<span>`/`<div>` without a role, avoid using `role="listitem"` or `role="button"` on `<article>` \u2014 use `<li>` for list items, add `role="img"` before `aria-label` on visual indicators, `aria-pressed` only on button-like roles\n- **Scrollable Regions:** Any scrollable container must have `tabindex="0"` or contain keyboard-interactive children\n- **Nested Interactive:** Do not add interactive role/tabindex to a container that already has focusable children\n- **List Roles:** `role="list"` containers must have `role="listitem"` children \u2014 prefer `<ul>/<li>` natively\n- **Dynamic Content:** role="status"/aria-live="polite" for updates, role="alert"/aria-live="assertive" for critical alerts\n- **Keyboard/Focus:** All interactive elements keyboard accessible, logical focus order, visible focus indicators, no keyboard traps (except modals)\n- **Color/Contrast:** 4.5:1 text contrast (3:1 large text), 3:1 UI component contrast, no color-only information, 3:1 focus indicator contrast'}var St=1440*60*1e3;function ve(e){let{serverName:t,contextApi:n,additionalFields:o={},intervalMs:s=St,enrichWithUserData:i=!1}=e,a="mcp_server_heartbeat",r=async()=>{try{let p={server_name:t,timestamp:new Date().toISOString(),...o};await n.logEvent(a,p,{enrichWithUserData:i})}catch(p){C(`Failed to send heartbeat for ${t}:`,p)}};r();let d=setInterval(r,s);return()=>{clearInterval(d),C(`Heartbeat stopped for ${t}`)}}import{z as X}from"zod";var kt=["meridian","default","bootstrap","material","fluent"];function we(e,t){return{projectName:X.string().default(t).describe("The name of the project. Used as the project folder name when creating a new project."),createNewProject:X.boolean().default(!0).describe(`Whether to create a new project before configuring ${e}. Set to true to scaffold a brand-new project, or false if the project already exists and you only want to add ${e} to it.`),theme:X.enum(kt).default("meridian").describe("The Kendo UI theme to use. Determines which theme package is installed and imported. Available themes: meridian (default), default, bootstrap, material, fluent.")}}var u="Kendo UI for React",N="react",D="kendo";var _=["ActionSheet","AIPrompt","Animation","AppBar","ArcGauge","AutoComplete","Avatar","Badge","Barcode","BottomNavigation","Breadcrumb","Button","ButtonGroup","BreadCrumb","Calendar","Card","Chart","ChartWizard","Chat","Checkbox","Chip","ChipList","ChunkProgressBar","CircularGauge","ColorGradient","ColorPalette","ColorPicker","ComboBox","ContextMenu","ConversationalUI","DataGrid","Grid","DataQuery","DateMath","DateInput","DatePicker","DateRangePicker","DateTimePicker","Dialog","Drag&Drop","Drawer","Drawing","DropDownButton","DropDownList","DropDownTree","Editor","Error","ExcelExport","ExpansionPanel","ExternalDropZone","FileSaver","FileManager","Filter","FlatColorPicker","FloatingActionButton","FloatingLabel","Form","Gantt","Gauge","General","GridLayout","Hint","Icon","InlineAIPrompt","Input","Label","LinearGauge","ListBox","ListView","Loader","Map","MaskedTextBox","Menu","MultiColumnComboBox","MultiSelect","MultiSelectTree","MultiViewCalendar","Notification","NumericTextBox","OrgChart","PageTemplates/BuildingBlocks","Pager","PanelBar","PDFProcessing","PDFViewer","PivotGrid","Popover","Popup","ProgressBar","PromptBox","QRCode","RadialGauge","RadioButton","RadioGroup","RangeSlider","Rating","Ripple","Sankey","Scheduler","ScrollView","Signature","Skeleton","Slider","Sortable","Sparkline","SpeechToTextButton","SmartPasteButton","SplitButton","Splitter","Spreadsheet","StackLayout","Stepper","StockChart","SVGIcon","Switch","TabStrip","TaskBoard","TextArea","TextBox","TileLayout","Timeline","TimePicker","Toolbar","Tooltip","TreeList","TreeView","Typography","Upload","VSCodeExtension","Window"];var Nt=xt(Tt(It(import.meta.url)),"../proto/service.proto"),F=new H("contextapi.telerik.com:443",Nt,{libName:N});var Se=async()=>F.validateUserLicense();import Vt from"fs";import ut from"path";import{fileURLToPath as Ht}from"url";import{z as v}from"zod";var k=class{constructor(t,n,o){this.name=t;this.config=n;this.cb=o}register(t){this.server=t,this.server.registerTool(this.name,this.config,this.cb)}hasAccess(t){return!this.config.requiredAccess||this.config.requiredAccess.length===0?!0:t==="full"||this.config.requiredAccess.includes(t)}};var q=(e,t)=>`# ${e.suiteName} - Code Validation & Quality Assurance
-
-## Comprehensive Code Validation Checklist
-Execute these validation steps systematically to ensure high-quality, maintainable code:
-
-### Validation Phase: Framework-Specific Validation
-
-${t}
-
-### Validation Phase: General Code Quality & Best Practices
-
-File Organization:
-- Files are properly named using appropriate conventions
-- Components are logically grouped in appropriate directories
-- File sizes are reasonable
-- Clear separation of concerns between files
-
-Performance Best Practices:
-- Optimized rendering patterns
-- Minimal unnecessary re-renders/change detection cycles
-- Efficient data handling and caching
-- Proper component lifecycle management
-
-### Validation Phase: Security & Accessibility Validation
-
-Security Measures:
-- Input validation and sanitization
-- XSS protection measures
-- CSRF protection where applicable
-- Secure data handling practices
-
-### Validation Phase: UI/UX & Design System Compliance
-
-Responsive Design:
-- Proper breakpoint handling
-- Flexible layouts that adapt to different screen sizes
-- Touch-friendly interface elements
-
-### Validation Phase: Error Handling & Edge Cases
-
- Error Handling:
-- Graceful error handling for all user interactions
-- Meaningful error messages for users
-- Network error handling for API calls
-`;var J=()=>`## UX/UI Design Best Practices
-
-> **These are default guidelines \u2014 follow them when the user has not stated otherwise.** If the user explicitly requests different behavior (e.g., a specific component size, a custom row limit, alternate breakpoints, a different layout pattern), defer to the user's stated preference and disregard the conflicting default below. Only accessibility and WCAG requirements (contrast ratios, focus indicators, semantic HTML, ARIA) apply regardless of user preference.
-
-Follow these principles when building or reviewing any UI. They apply regardless of the visual style requested.
-
-### Visual Hierarchy & Typography
-- Use a strict 3-level heading hierarchy: page title (h1) \u2192 section heading (h2) \u2192 component label (h3). Never skip levels.
-- Body text line length: 60\u201380 characters maximum. Wider lines reduce readability.
-- Numeric and currency columns must use \`font-variant-numeric: tabular-nums\` to keep digits column-aligned.
-- Never use more than 2 typefaces in a single interface.
-
-### Color & Contrast
-- Body text contrast ratio: \u2265 4.5:1 against its background.
-- Large text (\u2265 18pt / 14pt bold) and UI component boundaries: \u2265 3:1.
-- Use only the 5 semantic color slots \u2014 primary, success, warning, error, info \u2014 for meaning. Do not invent new semantic colors.
-- Never use color alone to convey status or meaning (8% of men have color vision deficiency). Always pair color with an icon or text label.
-- Never use red and green as the sole distinguishing colors.
-
-### Component Sizing & Density
-- Never mix size variants within the same form or toolbar. Pick one: \`"small"\`, \`"medium"\`, or \`"large"\` and apply it consistently.
-- \`"small"\` (24px) = data-dense tools. \`"medium"\` (32px) = default. \`"large"\` (40px) = comfortable/consumer-facing.
-
-### Motion & Animation
-- Always support \`prefers-reduced-motion: reduce\` \u2014 set transition durations to \u2264 0.01ms in that media query.
-- Micro-interactions (button press, tooltip): 150\u2013250ms. Panel transitions (drawer, sidebar): 300\u2013400ms.
-- Never animate layout properties that cause reflow (width, height, margin, padding). Animate transform and opacity instead.
-
-### Interaction Patterns
-- Never set \`outline: none\` globally. Keyboard focus indicators are required (WCAG 2.4.7).
-- Loading states: prefer Skeleton loader for content areas, overlay + ProgressBar for blocking operations, disabled button + inline spinner for async submission.
-- Error recovery: inline validation near the field for form errors; notification/toast for API/system errors.
-- Every icon-only button must have a visible tooltip and an \`aria-label\`.
-- Never show tooltips on disabled elements \u2014 disabled elements cannot receive focus.
-
-### Responsive Design
-- Breakpoints (defaults \u2014 use the project's breakpoint system if one is already established): Mobile < 640px | Tablet 640\u20131024px | Desktop 1024\u20131440px | Wide > 1440px.
-- Constrain max content width to 1440px with \`margin: 0 auto\` on wide viewports, unless a different maximum is already defined by the project.
-- On mobile (< 480px), data grids must switch to stacked/card layout \u2014 tabular layout is unusable at that width.
-- Schedulers/complex data views are not viable on mobile; provide a simplified alternative or a clear message.
-
-### UX Writing
-- Input labels describe *what* the field is. Placeholder text hints at *format or example* \u2014 never use placeholder as a substitute for a label.
-- Button labels must be specific action verbs: "Save Changes", "Delete Record", "Export CSV" \u2014 not "Submit", "OK", or "Yes".
-- Error messages must be specific and actionable: "Email address is already registered" not "Error 409".
-- Table/grid column headers: Title Case. Never ALL CAPS.
-- Empty states must explain why it's empty and offer a next action (e.g., "No records found. Add your first item.").
-
-### Data Presentation
-- Numeric and currency values must be right-aligned in table/grid columns.
-- Never display raw ISO 8601 date strings (e.g., \`2024-01-15T09:30:00Z\`) \u2014 always format for the locale (e.g., "15 Jan 2024").
-- Never render more than 200 rows in a fully-loaded table. Use pagination or virtual scrolling for larger datasets.
-- Never leave grid columns without explicit widths \u2014 causes layout jank on load and sort operations.
-
-### Chart Type Selection
-- **Line / Area**: continuous quantitative data over time (trends, rates).
-- **Bar (vertical)**: discrete time periods or ordered categories.
-- **Horizontal Bar**: comparing named categories (rankings, survey results).
-- **Donut (not Pie)**: part-to-whole proportions with \u2264 6 segments. Avoid Pie charts \u2014 the center hole of a Donut makes area estimation easier.
-- **Avoid**: 3D charts, dual-axis charts (misleading), charts with > 7 series in the same view.
-- Chart legend placement: below the chart.
-
-### Dialog vs Window Decisions
-- **Dialog (modal)**: use when the user must respond before continuing. Title should be action-oriented: "Delete this record?" not "Confirmation".
-- **Window (non-modal)**: use when content can exist alongside the background (resizable/draggable panels, editors).
-- Destructive dialog actions (delete, overwrite) must use the error theme color.
-- Every dialog must be closable via Escape key and have a clearly labeled close control.
-
-### Form Validation Display Rules
-- Show field-level validation errors **after the first blur** (not on initial render, not on every keystroke).
-- Display error text inline, directly below the field \u2014 never in a toast or far from the field.
-- On form-level submit failure, focus the first invalid field automatically.
-- Required fields: mark with an asterisk (*) and include a legend. Do not mark optional fields \u2014 label them "(optional)" only if most fields are required.
-
-### Grid Data Volume & Scrolling Strategy
-- Never render more than 200 rows without pagination or virtual scrolling.
-- Use **pagination** when users need to navigate by page number, see total row count, or perform export/select-all operations.
-- Use **virtual scrolling** when the dataset is very large (thousands of rows) and users scroll continuously rather than jumping to pages.
-- Default page size: 25 rows. Offer page size options (10, 25, 50) as defaults unless the project specifies otherwise.
-
-### Grid Feature Selection
-Enable only the Grid features genuinely required for the workflow. Each enabled feature adds UI chrome, event listeners, and DOM nodes. Start with the minimum set and add only when user stories require it:
-- \`sortable\` \u2014 when users need to find specific rows in non-obvious order
-- \`filterable\` \u2014 for datasets > 50 rows with varied values; skip for small fixed lists
-- \`groupable\` \u2014 only when hierarchical analysis is a core workflow
-- \`reorderable\` / \`resizable\` \u2014 when user customization of the view is a stated requirement
-- \`selectable\` \u2014 only when batch actions exist
-- \`editable\` \u2014 only when inline data entry is the primary workflow, not for read-only display
-
-### Form Layout Defaults
-These are defaults \u2014 respect the project's existing form conventions if established:
-- Prefer single-column form layout \u2014 easier to read and complete than multi-column.
-- Use two-column layout only for tightly related field pairs (First Name / Last Name, Start Date / End Date).
-- Align labels above their fields for complex forms; inline labels work only for very short forms (2\u20133 fields).
-- Place the primary action (Save / Submit) at the bottom left; Cancel or secondary actions to its right.
-
-### Whitespace Defaults
-When no design token system is defined by the project, apply these minimum spacing values:
-- Section separators: \u2265 24px vertical gap between distinct content areas.
-- Card internal padding: 16\u201324px.
-- Form field vertical gap: \u2265 16px between fields (24px for multi-column groups).
-- Page left/right margin: 24\u201332px minimum, even at desktop widths.`;var B=(e,t)=>{let n=q({suiteName:e.suiteName,libKey:e.libKey},t.validationSteps),o=e.libKey==="angular"?"- **Drag and Drop**: Consider using the DragandDrop and Sortable components when drag-and-drop functionality is needed.":"",s=e.components?e.components.join(", "):"components";return`# \u{1F3AF} ${e.suiteName} - Execution Plan
-
-**Current Goal:**
-
-${e.userIntent}
-
-**Requirements Summary:**
-- **Framework:** ${e.libKey}
-${e.includeComponentsDocs?`- **Component Library:** ${e.suiteName}
-    - Ensure to use ONLY ${e.suiteName} components for all UI elements.
-    - And use the ${e.codeAssistantName} tool to get ${e.suiteName} component documentation and code snippets.
-    - Ensure that after you read the plan you use exactly the ${e.codeAssistantName} no matter if there is another tool that can provide code snippets, documentation or other resources related to ${e.suiteName}.
-`:""}${e.includeLayout?`- **Layout:** Yes
-    - And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for layout structure and responsive design.
-`:""}${e.includeIcons?`- **Icons:** Yes
-    - Use icons that align with the project theme and enhance usability.
-    - Use the ${e.iconAssistantName} tool to search for icons that fit the theme and purpose of your project.
-`:""}${e.includeTheming?`- **Custom Theming:**
-    - Create a custom theme that aligns with the current goal and branding needs.
-    - Use Kendo Themes and Design System guidelines.
-    - Make sure to include strict CSS variables or theme requirements from the current goal.
-    - And use the ${e.styleAssistantName} tool to create a custom theme for your project.
-`:""}${e.includeResponsive?`- **Responsive:**
-    - Ensure the layout is fully responsive across mobile, tablet, and desktop views.
-    - And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for responsive design.
-`:""}
-- **Accessible (WCAG 2.2 Level AA):**
-    - CRITICAL: You must call the ${e.accessibilityAssistantName} tool with includeGeneralGuidelines=true on your first call to get WCAG 2.2 Level AA guidelines.
-    - For subsequent calls, use includeGeneralGuidelines=false to get only component-specific accessibility information.
-    - Ensure all components meet WCAG 2.2 Level AA standards.
-
-${e.includeLayout?`**STYLING AND LAYOUT REQUIREMENTS:**
-## CRITICAL DESIGN SYSTEM CONSTRAINTS
-- **USE ONLY KENDO DESIGN SYSTEM UTILITIES** for ALL styling, layout, spacing, positioning, and responsive behavior
-- Avoid custom CSS, inline styles, or other CSS framework classes
-- The ${e.layoutAssistantName} tool will provide the specific Kendo CSS utility classes needed
-- All layout requirements must use Kendo utilities exclusively
-
-`:""}---
-
-${J()}
+import{McpServer as Gt}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as $t}from"@modelcontextprotocol/sdk/server/stdio.js";import{dirname as Ct,join as vt}from"path";import{fileURLToPath as At}from"url";import{loadLicense as it,decodeLicenseKey as lt,decodeLicenseEvidence as ct}from"@progress/kendo-licensing/utils";var Y=class extends Error{constructor(t){super(t),this.name="LicenseError"}};function oe(e){return e.replace(/^\uFEFF/,"")}async function z(e){let t=null,o=null;try{let s=it();if(!s.success){let n=new Y(s.message);throw e&&await e("license_load_failed",{error:s.message}).catch(()=>{}),n}try{t=(await lt(s.value)).licenses.find(async a=>!!(await ct(a)).userId)}catch(n){console.log(n.message),e&&await e("license_load_failed",{error:n.message||"Unknown decoding error"}).catch(()=>{})}if(!t)return[oe(s.value),null]}catch(s){return o=s.message||"Unknown error loading license.",e&&await e("license_load_failed",{error:o}).catch(()=>{}),[null,o]}return[oe(t),null]}import G from"node:fs";import j from"node:path";var V=!1,D=process.env.DEBUG_LOG_FILE,se=!!(D&&typeof D=="string");if(se){let e=j.resolve(D),t=j.dirname(e);if(t!=="."&&t!==process.cwd()&&!G.existsSync(t))try{G.mkdirSync(t,{recursive:!0})}catch(o){console.error("Error creating log directory:",o)}if(!G.existsSync(e))try{G.writeFileSync(e,"")}catch(o){console.error("Error creating log file:",o)}}else V=!1;V=se&&!!D&&G.existsSync(j.resolve(D));function b(...e){if(V&&D){let s=`${new Date().toISOString()}: ${e.join(" ")}
+`,n=j.resolve(D);G.appendFile(n,s,a=>{a&&console.error("Error writing to log file:",a)})}}import pt from"@grpc/proto-loader";import q from"@grpc/grpc-js";import ae from"path";import ne from"fs";import{fileURLToPath as ut}from"url";var mt=ut(import.meta.url),gt=ae.dirname(mt),ie={version:"unknown"},re=ae.resolve(gt,"../package.json");ne.existsSync(re)&&(ie=JSON.parse(ne.readFileSync(re,"utf-8")));function ht(e){return e.replace(/\u2014/g,"--").replace(/\u2013/g,"-").replace(/[^\x20-\x7E]/g,"")}var W=class{constructor(t,o,s){this.contextApiUrl=t;this.protoPath=o;this.options=s;this.toolNameHeader="assistant";let n=pt.loadSync(this.protoPath,{keepCase:!0,longs:String,enums:String,defaults:!0,oneofs:!0});this.isDev=this.contextApiUrl?.includes("localhost")||this.contextApiUrl?.includes("127.0.0.1"),b("Using ContextApi URl:",this.contextApiUrl);let a=q.loadPackageDefinition(n);this.client=new a.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?q.credentials.createInsecure():q.credentials.createSsl())}buildRequestMetadata(t={}){return ht(JSON.stringify({...t,source:"npm",version:ie.version,os:process.platform,node_version:process.version,plugin_mode:!!process.env.PLUGIN_MODE,install_source:process.env.INSTALL_SOURCE?.toLowerCase()}))}async getMetadata({meta:t}={meta:{}}){let[o,s]=this.isDev?["fake_license",null]:await z((l,p)=>this.logEvent(l,p)),n=process.env.CONTEXTAPI_API_KEY,a=n&&typeof n=="string",r=o&&typeof o=="string";if(!r&&!a&&s)throw new Error(`Failed to authenticate with API key or License key!
 
----
-
-## Detailed Execution Plan
-Follow these steps strictly in order to achieve a complete and polished implementation of the current goal:
-
-### Phase: Accessibility Foundation
-
-**Step 1: Retrieve WCAG 2.2 Level AA Guidelines**
-
-**MANDATORY REQUIREMENT:**
-
-- Before implementing any UI components or features, you must call the accessibility assistant with general guidelines
-- On your first call to "${e.accessibilityAssistantName}", set "includeGeneralGuidelines=true" to get foundational WCAG 2.2 Level AA best practices
-- These general guidelines apply to all components and must be considered throughout implementation
-- For all subsequent calls, set "includeGeneralGuidelines=false" to get only component-specific information
-
-**First tool call (includes general WCAG guidelines):**
-\`\`\`
-${e.accessibilityAssistantName}({
-    query="What are the accessibility requirements for [COMPONENT_NAME]?",
-    component="[COMPONENT_NAME]",
-    includeGeneralGuidelines=true  // ONLY true on first call
-})
-\`\`\`
-
-**Step 2: Get Component-Specific Accessibility Information**
-
-For each additional ${e.suiteName} component you plan to use, call the tool with "includeGeneralGuidelines=false":
-
-**Tool call example:**
-\`\`\`
-${e.accessibilityAssistantName}({
-    query="What are the accessibility features and requirements for [COMPONENT_NAME]? Include ARIA attributes, keyboard navigation, and screen reader support.",
-    component="[COMPONENT_NAME]",
-    includeGeneralGuidelines=false  // false for all calls after the first
-})
-\`\`\`
-
-**Example:**
-\`\`\`
-${e.accessibilityAssistantName}({
-    query="How to associate the label with another component or HTML input?",
-    component="Label",
-    includeGeneralGuidelines=false
-})
-\`\`\`
-${e.includeLayout?`
-### Phase: Layout Foundation
-
-**Step 1: Create Base Layout Structure**
-**IMPORTANT LAYOUT REQUIREMENTS:**
-- Consider the hierarchy and nesting of layout elements (page \u2192 sections \u2192 components)
-- Each layout level should have appropriate wrapper containers with proper Kendo utilities
-- Sections should be wrapped in containers that provide the necessary layout structure
-
-**Tool call example:**
-\`\`\`
-${e.layoutAssistantName}({
-    prompt="Provide Kendo Design System utility classes for the following layout structure: [LAYOUT DESCRIPTION HERE]",
-    includeBuildingBlockExamples=true // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
-})
-\`\`\`
-`:""}
-${e.includeComponentsDocs?`
-### Phase: Component Integration
-**Step 1: Identify and Implement Core Components**
-Based on your current goal, analyze what other ${e.suiteName} components are needed and implement them one by one. Here you are some appropriate components based on the different project type:
-
-**Component Selection Guidelines:**
-- **Landing Pages**: Consider Button, Card, Form components, Layout containers, Navigation elements
-- **Dashboards**: Consider Grid, Chart, TileLayout, Drawer, Notification, ToolBar components
-- **Data Entry**: Consider Form, TextBox, DatePicker, DropDownList, Upload, Validation components
-- **Content Management**: Consider Grid, Editor, TreeView, FileManager, Dialog components
-- **E-commerce**: Consider ListView, Card, Button, Rating, Badge, Carousel components
-${o}
-
-**IMPORTANT COMPONENT USAGE REQUIREMENTS:**
-- Make sure to identify all necessary features related to the ${s} based on the current goal.
-- Make sure to identify specific features needed for other ${e.suiteName} components based on the current goal.
-- Make sure to generate a query for ${e.codeAssistantName} tool for each component and call the tool for each specific feature or functionality.
-- Always specify the exact features you want for each component. Describe only the needed functionality, and behavior you need. Be concise and don't include any information about the use case.
-
-**Tool call examples:**
-    \`\`\`
-    ${e.codeAssistantName}({
-            query="Give me information about [COMPONENT_NAME] with [SPECIFIC_FEATURES]." <!-- For example: 'Grid with paging' or 'Button with click events' or 'Chart with multiple series' -->
-            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', 'Chart', etc. -->
-    })
-    \`\`\`
-
-For broad queries, break them down into specific features (e.g., paging, sorting, filtering for Grid) and call the tool separately for each feature:
-    \`\`\`
-    ${e.codeAssistantName}({
-            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'paging in Grid' -->
-            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
-    })
-    \`\`\`
-
-    \`\`\`
-    ${e.codeAssistantName}({
-            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'sorting in Grid' -->
-            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
-    })
-    \`\`\`
-
-    \`\`\`
-    ${e.codeAssistantName}({
-            query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'filtering in Grid' -->
-            component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
-    })
-    \`\`\`
-`:""}
-${e.includeResponsive?`
-### Phase: Layout Responsive Finalization
-
-**Step 1: Implement Responsive Behavior**
-
-**Tool call example:**
-\`\`\`
-${e.layoutAssistantName}({
-    prompt="Provide Kendo Design System utility classes to make the following layout structure responsive across mobile, tablet, and desktop views: [LAYOUT DESCRIPTION HERE]",
-    includeBuildingBlockExamples=false // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
-})
-\`\`\`
-`:""}
-${e.includeTheming?`
-**Step 2: Custom Theme Implementation**
-
-**CUSTOM THEME REQUIREMENTS:**
-- Create a custom theme that aligns with the current goal and branding needs.
-- Use Kendo Themes and Design System guidelines.
-- Make sure to include strict CSS variables or theme requirements from the current goal.
-
-**Tool call example:**
-\`\`\`
-${e.styleAssistantName}({
-    query="Create a custom Kendo UI theme that aligns with the following current goal and branding needs: [CURRENT GOAL HERE]. Include strict CSS variables or theme requirements as needed.",
-    includeThemeVariables=true // Optional, include specific CSS variables for colors, typography, spacing, etc.
-})
-\`\`\`
-`:""}
-${e.includeIcons?`
-**Step 3: Iconography and Visual Enhancements**
-
-**ICONOGRAPHY GUIDELINES:**
-- Select icons that align with the project theme and enhance usability.
-- Ensure icons are consistent in style and size.
-- Use icons to improve navigation and highlight key actions.
-
-**Tool call example:**
-\`\`\`
-${e.iconAssistantName}({
-    query="Suggest icons that fit the theme and purpose of the following current goal: [CURRENT GOAL HERE]. Provide icon names and usage context.",
-})
-\`\`\`
-`:""}
-### Phase: Code Generation
-**IMPORTANT:** Do NOT generate ANY code or create files until ALL information gathering phases (1-3) are complete.
-**Step 1: Generate Complete Implementation**
-After completing all information gathering phases above, generate the complete ${e.libKey} component/page implementation:
-**Code Generation Requirements:**
-- Create complete, functional ${e.libKey} components/pages
-- Include all identified ${e.suiteName} components with their configurations
-- Apply ALL Kendo Design System utility classes gathered from layout assistant
-- Implement proper component event handling and data binding
-- Ensure responsive behavior using Kendo utility classes
-- Include necessary import statements and dependencies
-
-${t.injectedPlan??""}
-
-### Phase: Validation and Finalization
-
-**Step 1: Code Validation**
-** CRITICAL REQUIREMENT: You MUST validate the generated UI code using this comprehensive checklist to ensure code quality and compliance:**
-
-${n}
-
-**Step 2: Final Review and Testing**
-** Implementation Validation:**
-${e.includeComponentsDocs?` - Components render correctly without errors
-- Running \`npm run build\` compiles the application successfully without any build errors or crashes.
-- All ${e.suiteName} component features function as expected
-- Event handling and data binding operate correctly`:""}
-${e.includeResponsive?"- Responsive layout works across breakpoints":""}
-
-**Quick Fixes (if needed):**
-
-After code implementation and validation you can make quick fixes as needed:
-- If any build errors are found, fix them and re-run the application. Do NOT present the implementation as complete until the build succeeds without errors.
-- Use ${e.codeAssistantName} for component-specific issues
-- Use ${e.layoutAssistantName} for styling adjustments
-
-+### Before You Begin
-- When following/executing the plan call tools are defined from the same function_ecosystem/MCP_server which ${e.name} was called.
-- Do NOT generate or suggest any code until all tools have been used and validated responses are incorporated.
-- Focus on planning and sequencing.
-- Summarize the components, layouts, and utilities gathered.
-- Confirm all required inputs from tools have been provided.`};var Z=e=>`# ${e.suiteName} Assistant
-
-**What you're looking for:**
-
-${e.userIntent}
-
-**Available Tools:**
-- **${e.codeAssistantName}** - Get component documentation, features, and usage examples
-- **${e.iconAssistantName}** - Search for icons from the Kendo icon library
-
----
-
-## Discovery Plan
-
-Follow these steps to find the right components and resources:
-
-### Step 1: Identify Components
-
-Based on your needs, consider these ${e.suiteName} component categories:
-
-**Common Use Cases:**
-- **Data Display**: Grid, ListView, TreeView, Card, TileLayout
-- **Forms & Input**: Form, TextBox, DatePicker, DropDownList, ComboBox, MultiSelect, Upload
-- **Navigation**: Menu, Drawer, Breadcrumb, TabStrip, Stepper
-- **Data Visualization**: Chart, Gauge, Sparkline
-- **Editing**: Editor (Rich Text)
-- **Notifications**: Dialog, Notification, Tooltip
-- **Layout**: Splitter, PanelBar, ExpansionPanel
-
-**How to explore components:**
-
-Use the ${e.codeAssistantName} tool to learn about specific components:
-
-\`\`\`
-${e.codeAssistantName}({
-    query: "What are the main features of [COMPONENT_NAME]?",
-    component: "[COMPONENT_NAME]"
-})
-\`\`\`
-
-**Examples:**
-\`\`\`
-${e.codeAssistantName}({
-    query: "How to use Grid with paging and sorting?",
-    component: "Grid"
-})
-\`\`\`
-
-\`\`\`
-${e.codeAssistantName}({
-    query: "What features does DatePicker have?",
-    component: "DatePicker"
-})
-\`\`\`
-
-**Pro Tips:**
-- Ask about specific features (e.g., "Grid with filtering" instead of just "Grid")
-- Break complex queries into multiple calls focusing on one feature at a time
-- Specify the exact component name in the component parameter
-
-${e.includeIcons?`
-### Step 2: Find Icons
-
-Use the ${e.iconAssistantName} tool to search for icons:
-
-\`\`\`
-${e.iconAssistantName}({
-    query: "Search for icons related to [YOUR THEME/PURPOSE]"
-})
-\`\`\`
-
-**Examples:**
-\`\`\`
-${e.iconAssistantName}({
-    query: "icons for navigation menu"
-})
-\`\`\`
-
-\`\`\`
-${e.iconAssistantName}({
-    query: "icons for user actions like edit, delete, save"
-})
-\`\`\`
-`:""}
-
-### Step 3: Review and Implement
-
-After gathering information:
-1. Review the component documentation provided by ${e.codeAssistantName}
-2. Check which icons are available from ${e.iconAssistantName}
-3. Use the official ${e.suiteName} documentation for detailed implementation guides
-4. Refer to the component examples and code snippets provided
-
-### Step 4: Build and Validation
+License Error: ${s}`);let i=new q.Metadata;if(r)try{i.add("x-license-key",o)}catch(l){throw b("Error adding license key to metadata:",l),new Error(`Failed to use license key: ${l.message}`)}return a&&i.add("x-api-key",n),this.options?.libName&&i.add("x-library-name",this.options.libName),i.add("x-tool-name",this.toolNameHeader),i.add("x-request-metadata",this.buildRequestMetadata(t)),i}async query(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.query(t,s,(r,i)=>{r?a(r):n(i)})})}async getApiRefMatches(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.getApiRefMatches(t,s,(r,i)=>{r?a(r):n(i)})})}async queryCssUtils(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.cssUtilsSearch(t,s,(r,i)=>{r?(b("Error querying CSS Utils:",r),a(r)):n(i)})})}async queryIconsSearch(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.iconsSearch(t,s,(r,i)=>{r?(b("Error querying Icons Search:",r),a(r)):n(i)})})}async queryBuildingBlocks(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.buildingBlocksSearch(t,s,(r,i)=>{r?(b("Error querying Building Blocks:",r),a(r)):n(i)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((o,s)=>{this.client.validateUserLicense({},t,(n,a)=>{n?(b("Error validating user license:",n),s(n)):o(a)})})}async queryThemeGenerate(t,o){let s=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.generateTheme(t,s,(r,i)=>{r?(b("Error querying context API/GenerateTheme:",r),a(r)):n(i)})})}async recordOrchestratorUserRequest({meta:t}){let o=await this.getMetadata({meta:t});return new Promise((s,n)=>{this.client.recordOrchestratorUserRequest({},o,(a,r)=>{a?(b("Error recording orchestrator user request:",a),n(a)):s(r)})})}async recordToolUserRequest({toolName:t,meta:o}){let s=await this.getMetadata({meta:o});return new Promise(n=>{this.client.recordToolUserRequest({tool_name:t},s,(a,r)=>{a?(a.code===7?b("recordToolUserRequest: license does not cover Kendo AI Tools, skipping telemetry."):b("Error recording tool user request:",a),n(null)):n(r)})})}async logEvent(t,o,s={}){let n="h8utJ6rk4PpIWX4JMn9beQDsjVUri6KV0XYfiVwq",{enrichWithUserData:a=!1,meta:r={}}=s,i=n&&typeof n=="string",l=null;if(a)try{let[h]=this.isDev?["fake_license",null]:await z();h&&typeof h=="string"&&(l=h)}catch{}if(!i&&!l){b("Neither LOGGING_API_KEY nor license key available, skipping log event");return}let p=new q.Metadata;return i&&p.add("x-api-key",n),l&&(p.add("x-license-key",l),p.add("x-request-metadata",this.buildRequestMetadata(r)),this.options?.libName&&p.add("x-library-name",this.options.libName)),new Promise((h,v)=>{this.client.logEvent({event_name:t,fields:o||{}},p,(g,u)=>{g?(b("Error logging event:",g),v(g)):h()})})}};import{z as X}from"zod";var ao=X.object({user_id:X.string(),user_email:X.string().email()});import{z as x}from"zod";var ft=x.object({Product:x.object({Id:x.number().int(),Code:x.string(),Name:x.string()}),License:x.nullable(x.object({Id:x.number().int(),Name:x.string(),Type:x.string(),Active:x.boolean()})),Availability:x.array(x.object({LicenseStart:x.nullable(x.string().datetime()),LicenseEnd:x.nullable(x.string().datetime())})),IsLicenseAvailable:x.optional(x.boolean())}),co=x.array(ft);function T(e,t){let o=e.server?.server.getClientVersion?.(),s=t||{};return o&&(s.clientInfo={name:o.name,version:o.version}),s}async function le(e){let t=process.env.KENDO_MCP_ACCESS;if(t==="true"||t==="1"||t==="full")return"full";if(typeof t=="string"&&(t.toLowerCase()==="agent"||t.toLowerCase()==="assistant"))return t.toLowerCase();let o=await e();return o?.toLocaleLowerCase()==="agentic_ui_generator"?"agent":o?.toLocaleLowerCase()==="ai_coding_assistants"?"assistant":"none"}function ce(){return'**Accessibility Guidelines: WCAG 2.2 Level AA Compliance**\n\n**Core Principles:**\n1. Use semantic HTML and ARIA correctly\n2. Ensure WCAG 2.2 AA compliance\n3. Follow W3C ARIA Authoring Practices\n4. Provide standards-based accessibility fixes\n\n**1. Form Control Labels** (WCAG 1.3.1, 3.3.2, 4.1.2)\nEvery input must have an associated label.\nCORRECT: `<input type="search" aria-label="Search products" placeholder="Search...">`\nCORRECT: `<label for="qty">Quantity</label><input type="number" id="qty">`\nWRONG: `<span>Email</span><input type="email">` (no association)\nWRONG: `<input type="email" placeholder="Email">` (placeholder as label)\n\n**2. Button Accessibility** (WCAG 4.1.2, 2.4.6, 2.5.3)\nAll buttons need accessible names describing their purpose.\nCORRECT: `<button type="button">Save Changes</button>`\nCORRECT: `<button aria-label="Close dialog"><svg aria-hidden="true" focusable="false">...</svg></button>`\nWRONG: `<button><svg>...</svg></button>` (no accessible name)\nWRONG: `<button>Click here</button>` (generic text)\n\n**3. Popup/Menu Triggers** (WCAG 4.1.2, 1.3.1)\nIndicate popup purpose and state using aria-haspopup, aria-expanded, aria-controls.\nCORRECT: `<button aria-expanded="false" aria-haspopup="menu" aria-controls="menu-id">Settings</button>`\n\n**4. Image Accessibility** (WCAG 1.1.1)\nInformative: `<img src="chart.png" alt="Sales increased 25% in Q4 2024">`\nFunctional: `<a href="/home"><img src="logo.png" alt="Company Name Home"></a>`\nDecorative: `<img src="border.png" alt="" role="presentation">`\nComplex: `<img src="chart.png" alt="Sales data" aria-describedby="desc-id">`\nWRONG: Missing alt, filename as alt, generic alt for decorative images\n\n**5. Link Accessibility** (WCAG 2.4.4, 2.4.6)\nLinks must be descriptive and understandable out of context.\nCORRECT: `<a href="/products">View All Products</a>`\nCORRECT: `<a href="/article" aria-label="Read more about New Product Launch">Read more</a>`\nWRONG: "Click here", "Read more", "Learn more" without context\n\n**6. Form Validation** (WCAG 3.3.1, 3.3.2, 3.3.3)\nErrors must be identified, associated with inputs, and provide suggestions. Use aria-describedby, aria-invalid="true", and role="alert".\n\n**7. Heading Structure** (WCAG 1.3.1, 2.4.6)\nEach page must have an `<h1>` that describes its content. Use hierarchical, descriptive headings with no skipped levels (h1\u2192h2\u2192h3).\nCORRECT: `<h1>Dashboard</h1> <h2>Sales</h2> <h3>By Region</h3>`\nWRONG: No `<h1>` on the page, or skipping levels (h1\u2192h3)\nIf a heading should look smaller than its semantic level, use CSS: `<h2 class="text-sm">Subtitle</h2>`\n\n**8. Page Component Landmark Rules** (WCAG 1.3.1, 4.1.2)\nPage components (route components) may be rendered inside a layout that already provides `<main>`, `<header>`, or `<footer>`. Since the layout configuration is unknown, avoid using these landmarks in page components to prevent potential duplication and nesting violations. Use `<div>`, `<section>`, or `<article>` as the top-level wrapper instead.\n- Avoid adding `<main>`, `role="main"`, `<header>`, or `<footer>` in page components \u2014 the layout typically provides them. Duplicating them can cause `landmark-no-duplicate-main` and `landmark-main-is-top-level` violations.\n- Avoid adding `role="banner"` or using a semantic `<header>` element in page components \u2014 the layout\'s `<header>` already claims the banner landmark. Adding another causes `landmark-banner-is-top-level` violations.\n- Avoid adding `role="contentinfo"` to elements inside page components \u2014 the contentinfo landmark should be a top-level landmark, not nested inside `<main>` or other landmarks. Nesting it can cause `landmark-contentinfo-is-top-level` violations.\n- When multiple `<section>` or `<nav>` elements exist on a page, give each a unique `aria-label` to avoid `landmark-unique` violations.\n\n**9. ARIA Role and Attribute Restrictions** (WCAG 4.1.2)\nOnly use ARIA roles that are valid for the given HTML element. Avoid adding `aria-label` or `aria-labelledby` to elements that do not permit naming.\n- `<article>` has an implicit `article` role. Do NOT override it with `role="listitem"`, `role="button"`, `role="link"`, or any other role \u2014 none are allowed on `<article>`. Use `<li>` for list items, `<button>` for interactive cards, or `<a>` for clickable cards instead.\n- `<button>` already has an implicit `button` role. Do NOT add `role="listitem"` or other incompatible roles.\n- `<span>` and `<div>` without roles are generic elements. Do NOT add `aria-label` to them \u2014 it is a prohibited attribute on elements with no accessible role and can cause `aria-prohibited-attr` violations. Instead, use `role="img"` + `aria-label` for visual indicators, or use visually hidden text.\n- Do NOT add `aria-label` to non-interactive `<div>` wrappers \u2014 it has no effect and triggers violations.\n- `aria-pressed` is only valid on elements with `role="button"`, `role="checkbox"`, `role="menuitemcheckbox"`, `role="option"`, `role="radio"`, or `role="switch"`. Do NOT use `aria-pressed` on elements with `role="listitem"` or other roles.\nCORRECT: `<ul role="list"><li class="product-card">...</li></ul>` (listitem inside list)\nCORRECT: `<span role="img" aria-label="Status: pending" class="status-dot"></span>` (role added before aria-label)\nCORRECT: `<span class="status-dot" aria-hidden="true"></span><span class="visually-hidden">Pending</span>` (hidden text alternative)\nWRONG: `<article role="listitem">` (listitem not allowed on article)\nWRONG: `<article role="button">` (button not allowed on article \u2014 use `<button>` or `<div role="button">`)\nWRONG: `<span aria-label="pending" class="status-dot"></span>` (aria-label prohibited on generic span)\nWRONG: `<div aria-label="Product badges" class="badges"></div>` (aria-label prohibited on generic div)\n\n**Quick Checklist:**\n- **Forms:** Associated labels, aria-required on required fields, autocomplete attributes, aria-describedby for errors, aria-invalid for invalid fields, fieldsets with legends\n- **Buttons/Links:** Accessible names, aria-label for icon buttons, aria-hidden on decorative icons, descriptive link text\n- **Popups/Dialogs:** aria-haspopup, aria-expanded, aria-controls, role="dialog", aria-modal="true", aria-labelledby, focus trap, Escape to close\n- **Images:** alt on all images, descriptive alt for informative, empty alt for decorative, aria-describedby for complex\n- **Structure:** One h1, logical heading hierarchy, avoid `<main>`, `<header>`, `<footer>`, `role="main"`, `role="contentinfo"`, `role="banner"` in page/route components (the layout may already provide them), use `<section>` or `<div>` as page-level wrappers, unique aria-labels on duplicate landmark types\n- **ARIA Rules:** Avoid adding `aria-label` to generic `<span>`/`<div>` without a role, avoid using `role="listitem"` or `role="button"` on `<article>` \u2014 use `<li>` for list items, add `role="img"` before `aria-label` on visual indicators, `aria-pressed` only on button-like roles\n- **Scrollable Regions:** Any scrollable container must have `tabindex="0"` or contain keyboard-interactive children\n- **Nested Interactive:** Do not add interactive role/tabindex to a container that already has focusable children\n- **List Roles:** `role="list"` containers must have `role="listitem"` children \u2014 prefer `<ul>/<li>` natively\n- **Dynamic Content:** role="status"/aria-live="polite" for updates, role="alert"/aria-live="assertive" for critical alerts\n- **Keyboard/Focus:** All interactive elements keyboard accessible, logical focus order, visible focus indicators, no keyboard traps (except modals)\n- **Color/Contrast:** 4.5:1 text contrast (3:1 large text), 3:1 UI component contrast, no color-only information, 3:1 focus indicator contrast'}var yt=1440*60*1e3;function de(e){let{serverName:t,contextApi:o,additionalFields:s={},intervalMs:n=yt,enrichWithUserData:a=!1}=e,r="mcp_server_heartbeat",i=async()=>{try{let p={server_name:t,timestamp:new Date().toISOString(),...s};await o.logEvent(r,p,{enrichWithUserData:a})}catch(p){b(`Failed to send heartbeat for ${t}:`,p)}};i();let l=setInterval(i,n);return()=>{clearInterval(l),b(`Heartbeat stopped for ${t}`)}}import{z as Q}from"zod";var bt=["meridian","default","bootstrap","material","fluent"];function pe(e,t){return{projectName:Q.string().default(t).describe("The name of the project. Used as the project folder name when creating a new project."),createNewProject:Q.boolean().default(!0).describe(`Whether to create a new project before configuring ${e}. Set to true to scaffold a brand-new project, or false if the project already exists and you only want to add ${e} to it.`),theme:Q.enum(bt).default("meridian").describe("The Kendo UI theme to use. Determines which theme package is installed and imported. Available themes: meridian (default), default, bootstrap, material, fluent.")}}var d="Kendo UI for React",I="react",U="kendo";var M=["ActionSheet","AIPrompt","Animation","AppBar","ArcGauge","AutoComplete","Avatar","Badge","Barcode","BottomNavigation","Breadcrumb","Button","ButtonGroup","BreadCrumb","Calendar","Card","Chart","ChartWizard","Chat","Checkbox","Chip","ChipList","ChunkProgressBar","CircularGauge","ColorGradient","ColorPalette","ColorPicker","ComboBox","ContextMenu","ConversationalUI","Grid","DataQuery","DateMath","DateInput","DatePicker","DateRangePicker","DateTimePicker","Dialog","Drag&Drop","Drawer","Drawing","DropDownButton","DropDownList","DropDownTree","Editor","Error","ExcelExport","ExpansionPanel","ExternalDropZone","FileSaver","FileManager","Filter","FlatColorPicker","FloatingActionButton","FloatingLabel","Form","Gantt","Gauge","General","GridLayout","Hint","Icon","InlineAIPrompt","Input","Label","LinearGauge","ListBox","ListView","LLMKit","Loader","Map","MaskedTextBox","Menu","MultiColumnComboBox","MultiSelect","MultiSelectTree","MultiViewCalendar","Notification","NumericTextBox","OrgChart","OTPInput","PageTemplates/BuildingBlocks","Pager","PanelBar","PDFProcessing","PDFViewer","PivotGrid","Popover","Popup","ProgressBar","PromptBox","QRCode","RadialGauge","RadioButton","RadioGroup","RangeSlider","Rating","Ripple","Sankey","SegmentedControl","Scheduler","ScrollView","Signature","Skeleton","Slider","Sortable","Sparkline","SpeechToTextButton","SmartPasteButton","SplitButton","Splitter","Spreadsheet","StackLayout","Stepper","StockChart","SVGIcon","Switch","TabStrip","TaskBoard","TextArea","TextBox","TileLayout","Timeline","TimePicker","Toolbar","Tooltip","TreeList","TreeView","Typography","Upload","VSCodeExtension","Window"];var xt=vt(Ct(At(import.meta.url)),"../proto/service.proto"),F=new W("contextapi.telerik.com:443",xt,{libName:I});var ue=async()=>F.validateUserLicense();import Ot from"fs";import st from"path";import{fileURLToPath as qt}from"url";import{z as A}from"zod";var w=class{constructor(t,o,s){this.name=t;this.config=o;this.cb=s}register(t){this.server=t,this.server.registerTool(this.name,this.config,this.cb)}hasAccess(t){return!this.config.requiredAccess||this.config.requiredAccess.length===0?!0:t==="full"||this.config.requiredAccess.includes(t)}};var B=e=>{let t=[`1. \`${e.accessibilityAssistantName}\`: Call first with \`includeGeneralGuidelines=true\`; use \`false\` for component-specific follow-ups.`];if(e.includeLayout){let n=e.includeResponsive?"structure, responsive behavior, and UX policy":"structure and UX policy";t.push(`${t.length+1}. \`${e.layoutAssistantName}\`: Get Kendo Design System utilities for the requested ${n}. Use only those utilities for styling and layout.`)}if(e.includeTheming&&t.push(`${t.length+1}. \`${e.styleAssistantName}\`: Generate the requested Kendo theme variables.`),e.includeIcons&&t.push(`${t.length+1}. \`${e.iconAssistantName}\`: Find icons only for the required actions and states.`),e.includeComponentsDocs){let n=e.components?.length?e.components.join(", "):"each Kendo component selected for the implementation";t.push(`${t.length+1}. \`${e.codeAssistantName}\`: Call once per component (${n}) with a concise, feature-specific query before writing Kendo markup.`)}t.push(`${t.length+1}. After each assistant call, use the output to decide how to incorporate the guidance into the feature where applicable.`),t.push(`${t.length+1}. Implement the requested UI using ${e.suiteName} components and the gathered guidance.`),t.push(`${t.length+1}. Run \`npm run build\`, resolve failures, and repeat until it succeeds.`);let o=e.libKey==="angular"?"- Before editing, inspect the project for Standalone or NgModule setup, built-in or structural template syntax, and the existing Kendo theme import mechanism. Match those conventions; default to Standalone and built-in control flow for Angular 17+ only when no existing pattern is found.":"- Use React function components, Hooks, typed props where needed, stable list keys, and the project's existing KendoReact theme and package setup.",s=e.libKey==="angular"?`
+    - When drag-and-drop is required, consider the DragAndDrop and Sortable components.`:"";return`# ${e.suiteName} Execution Plan
 
-After implementing the code:
-- Run \`npm run build\` to verify the implementation compiles successfully without any build errors.
-- If any build errors are found, fix them and re-run the build.
-- Use ${e.codeAssistantName} for component-specific issues.
-- Do NOT present the implementation as complete until the build succeeds without errors.
-
----
-
-## Getting Started
-
-**Next Actions:**
-1. Start by calling ${e.codeAssistantName} for the components you need
-2. ${e.includeIcons?`Search for icons using ${e.iconAssistantName}`:"Review the component documentation"}
-3. Follow the ${e.suiteName} official documentation for implementation details
-4. Run \`npm run build\` to verify the implementation compiles successfully
-
-**Important Notes:**
-- These tools provide documentation and guidance, not code generation
-- Always refer to official ${e.suiteName} documentation for the most up-to-date information
-- Tool responses include usage examples and best practices`;var O=(e,t)=>({SETUP_VALIDATION:`
- UI Library Setup:
-- ${e} modules properly imported and configured
-- ${e} theme properly loaded and applied
-- ${e} license properly configured
-- Globalization and localization properly configured for ${e} components
-- Required ${e} dependencies installed and up-to-date`,PERFORMANCE_OPTIMIZATION:`
- Performance Optimization:
-- Efficient rendering patterns to prevent unnecessary re-renders
-- Lazy loading of ${e} components when appropriate
-- Virtualization enabled for large datasets in ${e} components
-- Only required ${e} modules imported and tree-shaken`,THEME_AND_STYLING:`
- ${e} Theme & Styling:
-- Prioritize the ${t} Design System utilities
-- Avoid custom CSS or other framework classes
-- Do not use inline styles
-- Consistent ${e} theme application across all components
-- Custom theme variables properly defined and scoped
-- ${e} icons properly loaded and optimized
-- Brand colors integrated with ${e} component themes`});var ee=()=>`
+<orchestrator-plan>
+  <goal>${e.userIntent}</goal>
+  <execution-order>
+${t.map(n=>`    ${n}`).join(`
+`)}
+  </execution-order>
+  <required-invariants>
+    - Accessibility guidance is retrieved before implementation; meet WCAG 2.2 Level AA.
+    - Do not generate code until the required tool calls above are complete and their guidance is incorporated.
+    - Generate code using tool guidance. Do not inspect \`node_modules\` unless the tools are insufficient and there is conflicting information or runtime errors.
+    - Use focused component queries; do not batch unrelated components.
+    - Build failures block completion and must be fixed before reporting success.
+    ${o}${s}
+  </required-invariants>
+  <completion>
+    - \`npm run build\` succeeds without errors.
+    - Every assistant response is reviewed and relevant guidance is applied.
+    - Required Kendo component, accessibility, layout, and framework-specific requirements are implemented.
+    - Do not report completion while either condition is unresolved.
+  </completion>
+</orchestrator-plan>`};var J=e=>{let t=e.components?.length?e.components.join(", "):"each Kendo component selected for the implementation",o=[`1. \`${e.codeAssistantName}\`: Call once per component (${t}) with a concise, feature-specific query before writing Kendo markup.`];return e.includeIcons&&o.push(`${o.length+1}. \`${e.iconAssistantName}\`: Find icons only for the required actions and states.`),o.push(`${o.length+1}. Implement using the gathered ${e.suiteName} documentation.`),o.push(`${o.length+1}. Run \`npm run build\`, resolve failures, and repeat until it succeeds.`),`# ${e.suiteName} Execution Plan
+
+<assistant-plan>
+  <goal>${e.userIntent}</goal>
+  <execution-order>
+${o.map(s=>`    ${s}`).join(`
+`)}
+  </execution-order>
+  <required-invariants>
+    - Build failures block completion and must be fixed before reporting success.
+    - Use the selected components and gathered guidance rather than generic substitutions.
+  </required-invariants>
+  <completion>
+    - \`npm run build\` succeeds without errors.
+    - Do not report completion while the build is failing.
+  </completion>
+</assistant-plan>`};var $=()=>`## UX/UI Design Best Practices
+
+Follow the constraints and conventions unless the prompt or project defines a stronger convention. Accessibility and WCAG rules always override other guidance.
+
+### Core Constraints
+- Headings: use a strict hierarchy - h1 \u2192 h2 \u2192 h3; never skip levels
+- Use at most 2 typefaces
+- Body text line length: 60-80 characters maximum
+- Contrast: body text \u2265 4.5:1 against its background
+- Large text (\u2265 18pt / 14pt bold) and UI boundaries \u2265 3:1
+- Use only semantic colors: primary, success, warning, error, info
+- Never use color alone to convey status or meaning; pair it with text or an icon
+- Pick one size per form or toolbar: \`"small"\` (24px, data-dense), \`"medium"\` (32px, default), or \`"large"\` (40px, comfortable)
+- Animate transform and opacity, not reflow properties such as width, height, margin, or padding
+- Never set \`outline: none\` globally
+- Icon-only buttons require a visible tooltip and an \`aria-label\`
+- Never show tooltips on disabled elements
+- Do not use placeholder text as a label
+- Button labels must use specific action verbs
+- Error messages must be specific and actionable
+- Grid headers use Title Case, not ALL CAPS
+- Empty states must explain why they are empty and offer a next action
+- Right-align numeric and currency grid columns
+- Format dates for the locale; never show raw ISO 8601 strings
+- Give every grid column an explicit width
+- Dialogs must support Escape to close and include a clearly labeled close control
+- Destructive dialog actions use the error theme color
+- Show field validation after first blur, not on initial render or every keystroke
+- Display field error text directly below the field
+- Required fields use an asterisk (*) plus a legend. Mark optional fields only when most fields are required
+- Do not render more than 200 grid rows without pagination or virtual scrolling
+- Support \`prefers-reduced-motion: reduce\` \u2014 set transition durations to \u2264 0.01ms in that media query
+
+### Default Conventions
+- Breakpoints: Mobile < 640px | Tablet 640-1024px | Desktop 1024-1440px | Wide > 1440px
+- Wide layouts: max width 1440px and centered
+- On screens under 480px, grids switch to stacked or card layout
+- Loading: Skeleton for content areas, overlay + ProgressBar for blocking operations, disabled button + inline spinner for async submission
+- Error recovery: inline for form fields, toast/notification for API or system errors
+- Virtual scrolling fits very large datasets where users scroll continuously rather than jump between pages
+- Paging defaults: 25 rows with options 10, 25, 50
+- Prefer single-column forms. Use two columns only for tightly related field pairs
+- For complex forms, place labels above fields. Inline labels fit only very short forms
+- Place the primary action at the bottom left and secondary actions to its right
+- Minimum spacing when no token system exists: section gap between distinct content areas \u2265 24px, card padding 16-24px, form field gap \u2265 16px (24px in multi-column groups), page margins 24-32px
+- Animations on micro-interactions (button press, tooltip): 150-250ms. Panel transitions (drawer, sidebar): 300-400ms
+
+### Chart Selection
+- Line or Area: continuous quantitative data over time (trends, rates)
+- Bar (vertical): discrete time periods or ordered categories
+- Bar (horizontal): comparing named categories (rankings, survey results)
+- Donut (not Pie): part-to-whole proportions with \u2264 6 segments. Prefer Donut over Pie charts
+
+### Avoid
+- 3D charts, dual-axis charts, and charts with more than 7 series
+
+### Dialog vs Window
+- Dialog: blocking choice or confirmation; title should be action-oriented
+- Window: non-modal content that can stay alongside the background(resizable/draggable panels, editors)`;var Z=()=>`
 **REQUIRED ACTIONS \u2014 apply all fixes directly to the source files:**
 - Search all .ts files for every outdated API mentioned in the codemod output \u2014 this includes renamed or removed properties, method names, and enum values.
 - Search all .ts, .css, and .scss files for every outdated CSS class mentioned in the codemod output and update it with an appropriate replacement.
@@ -532,91 +112,91 @@ After implementing the code:
 **OUTPUT REQUIREMENTS:**
 - For each file you change, briefly describe what was wrong and what fix you applied
 - If a problem requires a decision from the developer that you cannot make automatically, call it out explicitly with the file path
-- If all automated changes look correct and no further fixes are needed, explicitly confirm this`;import{execFile as Et}from"child_process";import{access as Rt}from"fs/promises";import{promisify as Pt}from"util";var ke=Pt(Et);function Dt(e,t){let n;try{n=JSON.parse(e)}catch{return e}let o=n?.Item;if(!o)return e;let s=[],i=o.FullName??o.Name??"",a=o.Type??"",r=o.Summary??"",d=o.SyntaxContent??"";s.push(`## API Reference Item
-- Name: ${i}
-- Type: ${a}
-- Summary: ${r}
-- Syntax: ${d}`);let p=n.RelatedItemsByType?.return_type;if(p?.length){let m=p[0].Text;m&&s.push(`- Return Type: ${m}`)}let g=o.Examples??[];if(g.length>0){let m=`## Examples
-`,h=0;for(let y of g){let c=(y.Component??"").toLowerCase(),f=t.toLowerCase();if(c&&c!==f&&c!=="general")continue;h+=1;let S=y.Code??"";m+=`### Example ${h}
-\`\`\`
-${S}
-\`\`\`
-`}h>0&&s.push(m)}let b=n.RelatedItemsByType??{},l=[];for(let[m,h]of Object.entries(b))if(!(m==="return_type"||m==="render_fragment"))for(let y of h??[]){let c=y.FullName??"",f=y.ShortText??"";l.push(`### ${c} (${m})
-${f}`)}return l.length>0&&s.push(`## Additional Context
-`+l.join(`
+- If all automated changes look correct and no further fixes are needed, explicitly confirm this`;import{execFile as kt}from"child_process";import{access as wt}from"fs/promises";import{promisify as St}from"util";var me=St(kt);function Tt(e,t){let o;try{o=JSON.parse(e)}catch{return e}let s=o?.Item;if(!s)return e;let n=[],a=s.FullName??s.Name??"",r=s.Type??"",i=s.Summary??"",l=s.SyntaxContent??"";n.push(`## API Reference Item
+- Name: ${a}
+- Type: ${r}
+- Summary: ${i}
+- Syntax: ${l}`);let p=o.RelatedItemsByType?.return_type;if(p?.length){let u=p[0].Text;u&&n.push(`- Return Type: ${u}`)}let h=s.Examples??[];if(h.length>0){let u=`## Examples
+`,m=0;for(let y of h){let c=(y.Component??"").toLowerCase(),f=t.toLowerCase();if(c&&c!==f&&c!=="general")continue;m+=1;let k=y.Code??"";u+=`### Example ${m}
+\`\`\`
+${k}
+\`\`\`
+`}m>0&&n.push(u)}let v=o.RelatedItemsByType??{},g=[];for(let[u,m]of Object.entries(v))if(!(u==="return_type"||u==="render_fragment"))for(let y of m??[]){let c=y.FullName??"",f=y.ShortText??"";g.push(`### ${c} (${u})
+${f}`)}return g.length>0&&n.push(`## Additional Context
+`+g.join(`
 ---
-`)),s.join(`
+`)),n.join(`
 
-`)}function xe(e,t,n){let{name:o,title:s,description:i,layoutAssistantName:a,codeAssistantName:r,styleAssistantName:d,iconAssistantName:p,accessibilityAssistantName:g,suiteName:b,libKey:l,components:m}=e,h=new k(o,{title:s,description:i,requiredAccess:e.requiredAccess,inputSchema:{userIntent:v.string().describe(`Detailed description and intent of what the user wants to build. Include the type of page/component, main functionality, visual requirements, and any specific ${b} components you want to use.`),needsComponentsDocsConfidence:v.number().min(0).max(1).default(1).describe("Confidence (0-1) to include Component Documentation assistance. Default is 1."),needsLayoutConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Layout assistance. Default is 0."),needsStylingConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Theming/Styling assistance. Default is 0."),needsResponsiveBehaviorConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Responsive Behavior assistance. Default is 0."),needsIconsConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Icons assistance. Default is 0."),componentsNeeded:v.array(v.enum(m)).optional().describe(`Optional list of specific ${b} components needed for the project.`)}},async({userIntent:y,needsComponentsDocsConfidence:c,needsLayoutConfidence:f,needsStylingConfidence:S,needsResponsiveBehaviorConfidence:x,needsIconsConfidence:E,componentsNeeded:I},{_meta:de})=>{let R=T(h,de);C("UI Orchestrator called with:",{userIntent:y,needsComponentsDocsConfidence:c,needsLayoutConfidence:f,needsStylingConfidence:S,needsResponsiveBehaviorConfidence:x,needsIconsConfidence:E});try{await n.recordOrchestratorUserRequest({meta:{userIntent:y,componentsNeeded:I,...R}})}catch(j){throw G(j)}let P=h.server?.server.getClientCapabilities?.()?.elicitation,K;if(P&&S>.3&&S<=.6){let j=await h.server?.server.elicitInput({message:"I was unable to determine if you need custom Kendo Theme assistant. Can you please confirm?",requestedSchema:{type:"object",properties:{includeCustomTheming:{type:"boolean",description:"Whether to include Custom Theming assistance in the workflow."}},required:["includeCustomTheming"]}});j?.action==="accept"&&j.content?.includeCustomTheming&&(K=!0)}return{content:[{type:"text",text:B({name:o,userIntent:y,includeComponentsDocs:c>.3,includeTheming:S>.6||!!K,includeLayout:f>.5,includeIcons:E>.6,includeResponsive:f>.5&&x>.4,layoutAssistantName:a,codeAssistantName:r,styleAssistantName:d,iconAssistantName:p,accessibilityAssistantName:g,suiteName:b,libKey:l,components:I},t)}]}});return h}function Ie(e,t){let{name:n,title:o,description:s,iconAssistantName:i,codeAssistantName:a,suiteName:r,libKey:d,components:p}=e,g=new k(n,{title:o,description:s,inputSchema:{userIntent:v.string().describe(`Describe what you want to build or what components you're looking for. Include the type of functionality, features, or UI elements you need from ${r}.`),needsIconsConfidence:v.number().min(0).max(1).default(.7).describe("Confidence (0-1) to include Icons assistance. Default is 0.7."),componentsNeeded:v.array(v.enum(p)).optional().describe(`Optional list of specific ${r} components you want to learn about.`)},requiredAccess:e.requiredAccess},async({userIntent:b,needsIconsConfidence:l,componentsNeeded:m},{_meta:h})=>{let y=T(g,h);C("Assistant Orchestrator called with:",{userIntent:b,needsIconsConfidence:l,componentsNeeded:m});try{await t.recordOrchestratorUserRequest({meta:{userIntent:b,componentsNeeded:m,...y}})}catch(f){throw G(f)}return{content:[{type:"text",text:Z({name:n,userIntent:b,includeComponentsDocs:!0,includeIcons:l>.5,codeAssistantName:a,iconAssistantName:i,suiteName:r,libKey:d,components:m})}]}});return g}function Ne(e,t){let{name:n,title:o,description:s,suiteName:i,libKey:a,getPreContent:r}=e,d=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{prompt:v.string().describe("An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve."),includeBuildingBlockExamples:v.boolean().describe("Whether to include building block examples. Defaults to false.").default(!1)}},async({prompt:p,includeBuildingBlockExamples:g},{_meta:b})=>{let l=T(d,b);C("Layout Assistant called with:",{prompt:p,includeBuildingBlockExamples:g});try{let h=(await t.queryCssUtils({query:p},{...l})).values.join(`
-`)||"No CSS utilities found for the given prompt.",y=r?.()??"",c=f=>`${y}
+`)}function he(e,t){let{name:o,title:s,description:n,layoutAssistantName:a,codeAssistantName:r,styleAssistantName:i,iconAssistantName:l,accessibilityAssistantName:p,suiteName:h,libKey:v,components:g}=e,u=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{userIntent:A.string().describe(`Detailed description and intent of what the user wants to build. Include the type of page/component, main functionality, visual requirements, and any specific ${h} components you want to use.`),needsComponentsDocsConfidence:A.number().min(0).max(1).default(1).describe("Confidence (0-1) to include Component Documentation assistance. Default is 1."),needsLayoutConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Layout assistance. Default is 0."),needsStylingConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Theming/Styling assistance. Default is 0."),needsResponsiveBehaviorConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Responsive Behavior assistance. Default is 0."),needsIconsConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Icons assistance. Default is 0."),componentsNeeded:A.array(A.enum(g)).optional().describe(`Optional list of specific ${h} components needed for the project.`)}},async({userIntent:m,needsComponentsDocsConfidence:y,needsLayoutConfidence:c,needsStylingConfidence:f,needsResponsiveBehaviorConfidence:k,needsIconsConfidence:S,componentsNeeded:R},{_meta:N})=>{let H=T(u,N);b("UI Orchestrator called with:",{userIntent:m,needsComponentsDocsConfidence:y,needsLayoutConfidence:c,needsStylingConfidence:f,needsResponsiveBehaviorConfidence:k,needsIconsConfidence:S});try{await t.recordOrchestratorUserRequest({meta:{userIntent:m,componentsNeeded:R,...H}})}catch(_){throw L(_)}let E=u.server?.server.getClientCapabilities?.()?.elicitation,K;if(E&&f>.3&&f<=.6){let _=await u.server?.server.elicitInput({message:"I was unable to determine if you need custom Kendo Theme assistant. Can you please confirm?",requestedSchema:{type:"object",properties:{includeCustomTheming:{type:"boolean",description:"Whether to include Custom Theming assistance in the workflow."}},required:["includeCustomTheming"]}});_?.action==="accept"&&_.content?.includeCustomTheming&&(K=!0)}return{content:[{type:"text",text:B({name:o,userIntent:m,includeComponentsDocs:y>.3,includeTheming:f>.6||!!K,includeLayout:c>.5,includeIcons:S>.6,includeResponsive:c>.5&&k>.4,layoutAssistantName:a,codeAssistantName:r,styleAssistantName:i,iconAssistantName:l,accessibilityAssistantName:p,suiteName:h,libKey:v,components:R})}]}});return u}function fe(e,t){let{name:o,title:s,description:n,iconAssistantName:a,codeAssistantName:r,suiteName:i,libKey:l,components:p}=e,h=new w(o,{title:s,description:n,inputSchema:{userIntent:A.string().describe(`Describe what you want to build or what components you're looking for. Include the type of functionality, features, or UI elements you need from ${i}.`),needsIconsConfidence:A.number().min(0).max(1).default(.7).describe("Confidence (0-1) to include Icons assistance. Default is 0.7."),componentsNeeded:A.array(A.enum(p)).optional().describe(`Optional list of specific ${i} components you want to learn about.`)},requiredAccess:e.requiredAccess},async({userIntent:v,needsIconsConfidence:g,componentsNeeded:u},{_meta:m})=>{let y=T(h,m);b("Assistant Orchestrator called with:",{userIntent:v,needsIconsConfidence:g,componentsNeeded:u});try{await t.recordOrchestratorUserRequest({meta:{userIntent:v,componentsNeeded:u,...y}})}catch(f){throw L(f)}return{content:[{type:"text",text:J({name:o,userIntent:v,includeComponentsDocs:!0,includeIcons:g>.5,codeAssistantName:r,iconAssistantName:a,suiteName:i,libKey:l,components:u})}]}});return h}function ye(e,t){let{name:o,title:s,description:n,suiteName:a,libKey:r,getPreContent:i}=e,l=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{prompt:A.string().describe("An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve."),includeBuildingBlockExamples:A.boolean().describe("Whether to include building block examples. Defaults to false.").default(!1)}},async({prompt:p,includeBuildingBlockExamples:h},{_meta:v})=>{let g=T(l,v);b("Layout Assistant called with:",{prompt:p,includeBuildingBlockExamples:h});try{let m=(await t.queryCssUtils({query:p},{...g})).values.join(`
+`)||"No CSS utilities found for the given prompt.",y=i?.()??"",c=f=>`${y}
 
 # Kendo Design System CSS Utilities
 
-${h}
+${m}
 ${f??""}
-`;if(g)try{let f=await t.queryBuildingBlocks({query:p,lib_name:a},{...l}),S="";f.items?.length>0&&(S=`
+`;if(h)try{let f=await t.queryBuildingBlocks({query:p,lib_name:r},{...g}),k="";f.items?.length>0&&(k=`
 ## Building Blocks Examples
 
 The examples here are for demonstration purpose how CSS utils can be implemented in various building blocks.
 However, consider your own design requirements and specifics in order to implement your templates/building blocks correctly.
 
-${f.items.map(x=>`
-### ${x.name}
+${f.items.map(S=>`
+### ${S.name}
 
-${x.description}
+${S.description}
 
 \`\`\`code
-${x.code}
+${S.code}
 \`\`\`
 `).join(`
-`)}`),h=c(S)}catch(f){C("Error calling building-blocks service:",f),h=c()}else h=c();return{content:[{type:"text",text:h}]}}catch(m){throw G(m)}});return d}function Ee(e,t){let{name:n,title:o,description:s,libKey:i,getPreContent:a}=e,r=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{prompt:v.string().describe("A natural language description of the desired visual style or theme. For example: 'Create a modern dark theme with high contrast'.")}},async({prompt:d},{_meta:p})=>{let g=T(r,p);C("Style Assistant called with:",{prompt:d});let b="";try{let h=await t.queryThemeGenerate({prompt:d},{...g});if(h.variables_json){let y=JSON.parse(h.variables_json),c=[];if(y)for(let f of Object.keys(y))typeof y[f]=="string"&&c.push(`${f}: ${y[f]}`);b=c.join(`
+`)}`),m=c(k)}catch(f){b("Error calling building-blocks service:",f),m=c()}else m=c();return{content:[{type:"text",text:m}]}}catch(u){throw L(u)}});return l}function be(e,t){let{name:o,title:s,description:n,libKey:a,getPreContent:r}=e,i=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{prompt:A.string().describe("A natural language description of the desired visual style or theme. For example: 'Create a modern dark theme with high contrast'.")}},async({prompt:l},{_meta:p})=>{let h=T(i,p);b("Style Assistant called with:",{prompt:l});let v="";try{let m=await t.queryThemeGenerate({prompt:l},{...h});if(m.variables_json){let y=JSON.parse(m.variables_json),c=[];if(y)for(let f of Object.keys(y))typeof y[f]=="string"&&c.push(`${f}: ${y[f]}`);v=c.join(`
 
-`)}}catch(h){throw G(h)}let l=a?.()??"";return{content:[{type:"text",text:b?`Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance.
+`)}}catch(m){throw L(m)}let g=r?.()??"";return{content:[{type:"text",text:v?`Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance.
 Ensure the variables are applied consistently across all relevant elements.
 Do NOT set any inline styles. CSS variables should be defined in global or component-level CSS files, or via supported theming mechanisms.
 
-${l}
+${g}
 
 ## Generated CSS Variables
 
 \`\`\`css
-${b}
+${v}
 \`\`\`
-`:"No CSS variables were generated for the given prompt."}]}});return r}function Re(e,t){let{name:n,title:o,description:s,libKey:i,getPostContent:a}=e,r=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("A search query for finding icons. Be specific about the icon purpose, style, or action."),limit:v.number().min(.1).max(1).default(.1).describe("The proportion of matching icons to return (0.1 = 1 icon, 0.5 = 5 icons, 1.0 = many icons). Default is 0.1.")}},async({query:d,limit:p},{_meta:g})=>{let b=T(r,g);C("Icon Search called with:",{query:d,limit:p});try{let l=await t.queryIconsSearch({query:d,limit:p*100},{...b}),m=a?.()??"";return{content:[{type:"text",text:`${l.values.join(`
+`:"No CSS variables were generated for the given prompt."}]}});return i}function Ce(e,t){let{name:o,title:s,description:n,libKey:a,getPostContent:r}=e,i=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("A search query for finding icons. Be specific about the icon purpose, style, or action."),limit:A.number().min(.1).max(1).default(.1).describe("The proportion of matching icons to return (0.1 = 1 icon, 0.5 = 5 icons, 1.0 = many icons). Default is 0.1.")}},async({query:l,limit:p},{_meta:h})=>{let v=T(i,h);b("Icon Search called with:",{query:l,limit:p});try{let g=await t.queryIconsSearch({query:l,limit:p*100},{...v}),u=r?.()??"";return{content:[{type:"text",text:`${g.values.join(`
 
 `)}
 
-${m}`}]}}catch(l){throw G(l)}});return r}function Pe(e,t){let{name:n,title:o,description:s,libKey:i,suiteName:a,components:r,componentAliases:d,getPostContent:p}=e,g=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("The query to search for."),component:v.enum(r).describe("The component to search for. If not specified, use General.")}},async({query:b,component:l},{_meta:m})=>{let h=T(g,m);C("Code Assistant called with:",{query:b,component:l});let y=l;if(d){let c=d[l];c&&(y=c)}try{let f=(await t.query({query:b,component:y?.toLowerCase()??"general",lib_name:i,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]},{...h})).values.map(E=>E.replace(/\0/g,"")),S=p?.({component:l})??"";return{content:[{type:"text",text:`${f.join(`
+${u}`}]}}catch(g){throw L(g)}});return i}function ve(e,t){let{name:o,title:s,description:n,libKey:a,suiteName:r,components:i,componentAliases:l,getPostContent:p}=e,h=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("The query to search for."),component:A.enum(i).describe("The component to search for. If not specified, use General.")}},async({query:v,component:g},{_meta:u})=>{let m=T(h,u);b("Code Assistant called with:",{query:v,component:g});let y=g;if(l){let c=l[g];c&&(y=c)}try{let f=(await t.query({query:v,component:y?.toLowerCase()??"general",lib_name:a,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]},{...m})).values.map(R=>R.replace(/\0/g,"")),k=p?.({component:g})??"";return{content:[{type:"text",text:`${f.join(`
 
 `)}
 
-${S}`}]}}catch(c){throw G(c)}});return g}function De(e,t){let{name:n,title:o,description:s,libKey:i,suiteName:a,components:r,componentAliases:d}=e,p=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("The query to search for."),component:v.enum(r).describe("The component to search for. If not specified, use General."),includeGeneralGuidelines:v.boolean().default(!1).describe("Set to true only on the first call to include comprehensive WCAG 2.2 Level AA general guidelines. After the first call, set to false to get only component-specific accessibility information. Default is false.")}},async({query:g,component:b,includeGeneralGuidelines:l},{_meta:m})=>{let h=T(p,m);C("Accessibility Assistant called with:",{query:g,component:b,includeGeneralGuidelines:l});let y=b;if(d){let c=d[b];c&&(y=c)}try{let c="";if(l){let I=Ce();c+=`# WCAG 2.2 Level AA General Accessibility Guidelines
+${k}`}]}}catch(c){throw L(c)}});return h}function Ae(e,t){let{name:o,title:s,description:n,libKey:a,suiteName:r,components:i,componentAliases:l}=e,p=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("The query to search for."),component:A.enum(i).describe("The component to search for. If not specified, use General."),includeGeneralGuidelines:A.boolean().default(!1).describe("Set to true only on the first call to include comprehensive WCAG 2.2 Level AA general guidelines. After the first call, set to false to get only component-specific accessibility information. Default is false.")}},async({query:h,component:v,includeGeneralGuidelines:g},{_meta:u})=>{let m=T(p,u);b("Accessibility Assistant called with:",{query:h,component:v,includeGeneralGuidelines:g});let y=v;if(l){let c=l[v];c&&(y=c)}try{let c="";if(g){let N=ce();c+=`# WCAG 2.2 Level AA General Accessibility Guidelines
 
-`,c+=I,c+=`
+`,c+=N,c+=`
 
 ---
 
-`}let E=(await t.getApiRefMatches({query:g,component:y?.toLowerCase()??"general",lib_name:i,filters_json:'{"type":{"$in":["accessibility"]}}'},{...h})).values.map(I=>I.replace(/\0/g,"")).map(I=>Dt(I,y?.toLowerCase()??"general")).join(`
+`}let R=(await t.getApiRefMatches({query:h,component:y?.toLowerCase()??"general",lib_name:a,filters_json:'{"type":{"$in":["accessibility"]}}'},{...m})).values.map(N=>N.replace(/\0/g,"")).map(N=>Tt(N,y?.toLowerCase()??"general")).join(`
 
-`);return E?(l&&(c+=`# Component-Specific Accessibility Information
+`);return R?(g&&(c+=`# Component-Specific Accessibility Information
 
-`),c+=E):l||(c="No component-specific accessibility guidelines found."),{content:[{type:"text",text:c}]}}catch(c){throw G(c)}});return p}function G(e){let t=e;return t.code===16?new Error("Error: You are not authenticated. Please verify the Telerik License Key provided is valid."):t.code===8?new Error(`Error: You have exceeded the extension quota. Upgrade to subscription licensing to unlock full access. Message: ${t.message}.`):t.code===7?new Error("Error: You do not have permission to access this resource. Please verify that you have a valid license."):new Error(`Error: An error occurred while calling the service. Please try again later.
+`),c+=R):g||(c="No component-specific accessibility guidelines found."),{content:[{type:"text",text:c}]}}catch(c){throw L(c)}});return p}function L(e){let t=e;return t.code===16?new Error("Error: You are not authenticated. Please verify the Telerik License Key provided is valid."):t.code===8?new Error(`Error: You have exceeded the extension quota. Upgrade to subscription licensing to unlock full access. Message: ${t.message}.`):t.code===7?new Error("Error: You do not have permission to access this resource. Please verify that you have a valid license."):new Error(`Error: An error occurred while calling the service. Please try again later.
 
-Error Code: ${t.code} Error Message: ${t.message}`)}var Ut=20*1024*1024,Ue=1200*1e3;function Te(e){return{content:[{type:"text",text:`Upgrade timed out after ${Ue/6e4} minutes.
+Error Code: ${t.code} Error Message: ${t.message}`)}var It=20*1024*1024,xe=1200*1e3;function ge(e){return{content:[{type:"text",text:`Upgrade timed out after ${xe/6e4} minutes.
 
 **Some codemods may have already been applied to your files.** Review any modified files before proceeding.
 
 To complete the upgrade, run this tool again with specific package names via the \`packageNames\` parameter to upgrade one package at a time.${e?`
 
 ## Partial output before timeout
-`+e:""}`}]}}function Oe(e,t){let{name:n,title:o,description:s,suiteName:i}=e,a=new k(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{workingDirectory:v.string().describe('The absolute path to the project directory where the upgrade should be executed (e.g., "/Users/username/my-app")'),packageNames:v.array(v.string()).optional().describe('The package names to target for codemod upgrade (e.g., ["@progress/kendo-angular-grid", "@progress/kendo-angular-buttons"]). Defaults to upgrading all installed @progress packages if not specified. When specified, skips package installation and only runs codemods \u2014 the packages must already be installed at the target version before calling this tool.'),skipInstall:v.boolean().optional().describe("Skip npm package installation and only run codemods. Use this when package installation has already been done manually.")}},async({workingDirectory:r,packageNames:d,skipInstall:p},{_meta:g})=>{let b=T(a,g);try{await t.recordToolUserRequest({toolName:n,meta:b})}catch(l){console.error("Error recording tool request:",l)}try{try{await Rt(r)}catch{return{content:[{type:"text",text:`The working directory does not exist: "${r}". Please provide a valid absolute path to your project.`}]}}let l=!1;try{await ke("npx",["--no","--","kendo","--version"],{cwd:r}),l=!0}catch{l=!1}let m=[],h=async(R,pe=!1)=>{try{let P=!pe&&l?["--no","--","kendo",...R]:["-y","@progress/kendo-cli",...R],{stdout:K,stderr:ue}=await ke("npx",P,{cwd:r,maxBuffer:Ut,timeout:Ue});return{timedOut:!1,stdout:K,stderr:ue}}catch(P){return P.killed?{timedOut:!0,partialOutput:P.stdout?.trim()}:{timedOut:!1,stdout:P.stdout||"",stderr:P.stderr||P.message}}},y=["migrate",...d??[],"--codemods","--force","--ai-mode"];(p||d?.length)&&y.push("--no-install");let c=await h(y);if(c.timedOut)return Te(c.partialOutput);let f=c.stdout,S=c.stderr;if(S?.includes("Unknown argument")){let R=await h(y,!0);if(R.timedOut)return Te(R.partialOutput);f=R.stdout,S=R.stderr}S?.trim()&&m.push(`
+`+e:""}`}]}}function ke(e,t){let{name:o,title:s,description:n,suiteName:a,packagePrefix:r}=e,i=new w(o,{title:s,description:n,requiredAccess:e.requiredAccess,inputSchema:{workingDirectory:A.string().describe('The absolute path to the project directory where the upgrade should be executed (e.g., "/Users/username/my-app")'),packageNames:A.array(A.string()).optional().describe(`The package names to target for codemod upgrade (e.g., ["${r}grid", "${r}buttons"]). Defaults to upgrading all installed @progress packages if not specified. When specified, skips package installation and only runs codemods \u2014 the packages must already be installed at the target version before calling this tool.`),skipInstall:A.boolean().optional().describe("Skip npm package installation and only run codemods. Use this when package installation has already been done manually.")}},async({workingDirectory:l,packageNames:p,skipInstall:h},{_meta:v})=>{let g=T(i,v);try{await t.recordToolUserRequest({toolName:o,meta:g})}catch(u){console.error("Error recording tool request:",u)}try{try{await wt(l)}catch{return{content:[{type:"text",text:`The working directory does not exist: "${l}". Please provide a valid absolute path to your project.`}]}}let u=!1;try{await me("npx",["--no","--","kendo","--version"],{cwd:l}),u=!0}catch{u=!1}let m=[],y=async(E,K=!1)=>{try{let P=!K&&u?["--no","--","kendo",...E]:["-y","@progress/kendo-cli",...E],{stdout:_,stderr:at}=await me("npx",P,{cwd:l,maxBuffer:It,timeout:xe});return{timedOut:!1,stdout:_,stderr:at}}catch(P){return P.killed?{timedOut:!0,partialOutput:P.stdout?.trim()}:{timedOut:!1,stdout:P.stdout||"",stderr:P.stderr||P.message}}},c=["migrate",...p??[],"--codemods","--force","--ai-mode"];(h||p?.length)&&c.push("--no-install");let f=await y(c);if(f.timedOut)return ge(f.partialOutput);let k=f.stdout,S=f.stderr;if(S?.includes("Unknown argument")){let E=await y(c,!0);if(E.timedOut)return ge(E.partialOutput);k=E.stdout,S=E.stderr}S?.trim()&&m.push(`
 Errors:
-${S}`),f?.trim()&&m.push(f.trim());let x=f.includes("Packages installed successfully."),E=f.includes("Package installation failed:"),I=f.includes("Running codemod:");return E?m.push(`
+${S}`),k?.trim()&&m.push(k.trim());let R=k.includes("Packages installed successfully."),N=k.includes("Package installation failed:"),H=k.includes("Running codemod:");return N?m.push(`
 ## Upgrade Status
-Package installation failed. The npm packages were not updated. Inform the user of the error and update the package versions in package.json manually to the target version. Once done, call this tool again with skipInstall set to true.`):x&&m.push(`
+Package installation failed. The npm packages were not updated. Inform the user of the error and update the package versions in package.json manually to the target version. Once done, call this tool again with skipInstall set to true.`):R&&m.push(`
 ## Upgrade Status
-Upgrade complete. npm packages have been installed and updated in the project.`),I&&m.push(ee()),{content:[{type:"text",text:m.join(`
-`)}]}}catch(l){return{content:[{type:"text",text:`Error: ${l.message||l.toString()}`}]}}});return a}var Ge=e=>`${e}_ui_generator`,Le=e=>`${e}_assistant`,Me=e=>`${e}_layout_assistant`,$e=e=>`${e}_component_assistant`,_e=e=>`${e}_style_assistant`,Fe=e=>`${e}_icon_assistant`,qe=e=>`${e}_accessibility_assistant`,Be=e=>`${e}_getting_started_assistant`,Ke=e=>`${e}_upgrade_assistant`;var je=e=>`This is the single entry point for all UI-related tasks. It orchestrates the full workflow of building or refining UIs with ${e} components, generating a step-by-step execution plan that specifies which tools to call, in what order, and with what parameters. It includes validation steps to ensure the best possible, standards-compliant code every time.
+Upgrade complete. npm packages have been installed and updated in the project.`),H&&m.push(Z()),{content:[{type:"text",text:m.join(`
+`)}]}}catch(u){return{content:[{type:"text",text:`Error: ${u.message||u.toString()}`}]}}});return i}var we=e=>`${e}_ui_generator`,Se=e=>`${e}_assistant`,Te=e=>`${e}_layout_assistant`,Ie=e=>`${e}_component_assistant`,Re=e=>`${e}_style_assistant`,Ne=e=>`${e}_icon_assistant`,Ee=e=>`${e}_accessibility_assistant`,Ue=e=>`${e}_getting_started_assistant`,Pe=e=>`${e}_upgrade_assistant`;var De=e=>`This is the single entry point for all UI-related tasks. It orchestrates the full workflow of building or refining UIs with ${e} components, generating a step-by-step execution plan that specifies which tools to call, in what order, and with what parameters. It includes validation steps to ensure the best possible, standards-compliant code every time.
 
   Use the tool when:
   - Want to build or modify a complete page or section layout
@@ -625,7 +205,7 @@ Upgrade complete. npm packages have been installed and updated in the project.`)
   - You want to enforce best practices in styling, performance, and accessibility
 
 Returns:
-A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`,Ve=e=>`Provides guidance for discovering and using ${e} components and icons. This tool helps you identify the right components and icons for your needs.
+A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`,Le=e=>`Provides guidance for discovering and using ${e} components and icons. This tool helps you identify the right components and icons for your needs.
 
 Use this tool when:
 - You need to discover which ${e} components are suitable for a specific use case
@@ -634,20 +214,20 @@ Use this tool when:
 - You want to gather component documentation and examples
 
 Returns:
-A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools.`,He=`Retrieves Progress/Kendo Design System CSS utility classes and styling recommendations based on layout and design requirements.
+A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools.`,_e=`Retrieves Progress/Kendo Design System CSS utility classes and styling recommendations based on layout and design requirements.
 Use this tool to find the right CSS utilities for styling Kendo UI components or general web elements.
 It analyzes the provided design context and returns relevant utility classes with explanations and examples.
-Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,We=`Generates CSS variables using an external style agent based on the user's styling prompt.
+Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,Ge=`Generates CSS variables using an external style agent based on the user's styling prompt.
 
 Use this tool when the user wants to:
 - Update the visual theme of an application
 - Modify color schemes
 - Restyle the UI with CSS variables
 
-The tool outputs a set of CSS variable definitions ready to be applied to style files.`,ze=`Searches for icons in the Telerik Icons library.
+The tool outputs a set of CSS variable definitions ready to be applied to style files.`,$e=`Searches for icons in the Telerik Icons library.
 Use this tool when the user needs to find specific icons for UI components or design elements.
 It supports searching by icon name, category, or keyword and returns matching icons from the Telerik Icons library.
-`,Ye=e=>`Provides answers and retrieves official documentation for ${e}.
+`,Oe=e=>`Provides answers and retrieves official documentation for ${e}.
 
 Use this tool when the user asks about:
 - ${e} features or capabilities
@@ -657,7 +237,7 @@ Use this tool when the user asks about:
 
 Set the user's full question as the 'query' parameter.
 If the question refers to a specific ${e} component, include its name in the 'component' parameter.
-`,Qe=e=>`Retrieves accessibility guidance for ${e} components with optional general WCAG 2.2 Level AA guidelines.
+`,qe=e=>`Retrieves accessibility guidance for ${e} components with optional general WCAG 2.2 Level AA guidelines.
 
 Use this tool when:
 - You need component-specific accessibility information and API references
@@ -675,12 +255,12 @@ Set 'includeGeneralGuidelines=true' ONLY on the first call to include general WC
 Returns:
 - When includeGeneralGuidelines=true: General WCAG 2.2 Level AA guidelines + component-specific recommendations
 - When includeGeneralGuidelines=false: Only component-specific accessibility recommendations
-`,Xe=e=>`Runs codemods to upgrade ${e} code from one version directly to another using @progress/kendo-cli.
+`,Me=(e,t)=>`Runs codemods to upgrade ${e} code from one version directly to another using @progress/kendo-cli.
 
 To upgrade to the latest version, call this tool directly. It handles installation automatically.
 
 To upgrade to a specific version:
-1. Set all @progress/kendo-angular-* package versions to the target version (e.g. "20.0.0")
+1. Set all ${t}* package versions to the target version (e.g. "20.0.0")
 2. Run: npm install
 3. Call this tool with skipInstall: true
 
@@ -700,195 +280,36 @@ Workflow:
 1. Run this upgrade tool to apply codemods.
 2. After the codemods complete, grep the project source files for every outdated value mentioned in the codemod output (e.g. old property names, renamed enum values) to find any remaining occurrences the codemod doesn't handle automatically, and fix them all.
 3. Follow the additional instructions to complete the upgrade process.
-`;var te=O("Kendo UI","Kendo"),oe=`
-### Angular Component Validation
-Component Structure:
-  - Use proper @Component decorator configuration
-  - If using NgModule setup use @Component decorator with \`standalone: false\` and declare component in NgModule declarations array
-  - Correct selector naming convention (kebab-case)
-  - Appropriate template and style file organization
-
-${te.SETUP_VALIDATION}
-  - Kendo animations module configured (if animations are used)
-  - Internationalization properly configured for Kendo components
-
-${te.PERFORMANCE_OPTIMIZATION}
-  - OnPush change detection strategy where appropriate
-  - Efficient \`track\` expression used in \`@for\` blocks with Kendo components
-  - Minimal unnecessary change detection cycles
-
-${te.THEME_AND_STYLING}
-  - Proper theme switching functionality (if implemented)
-  - Only ONE theme reference exists across angular.json and styles files
-  - Make sure theme import mechanism is consistent with existing project setup
-
-Accessibility
-  - Accessibility guidelines retrieved and applied to all components`;var ne=`**Angular Specific Requirements:**
-
-**NgModule vs Standalone setup**: Search and detect the current project setup to determine whether to use NgModule or Standalone components based on the following rules:
-  1. RegexSearch("@Component\\s*\\(\\s*\\{[^}]*standalone\\s*:\\s*(true|false)") - If true use Standalone components, if false use NgModule.
-  2. RegexSearch("bootstrapApplication\\s*\\(") - If found use Standalone components.
-  3. RegexSearch("bootstrapModule\\s*\\(") - If found use NgModule.
-  4. If neither is found, default to Standalone components.
-
-**Template Syntax**: Detect which Angular template syntax the project uses and apply it consistently:
-  1. RegexSearch("@if\\s*\\(|@for\\s*\\(|@switch\\s*\\(") - If found, use built-in control flow syntax (\`@if\`, \`@for\`, \`@switch\`) in all templates.
-  2. RegexSearch("\\*ngIf|\\*ngFor|\\*ngSwitch") - If found, use structural directives (\`*ngIf\`, \`*ngFor\`, \`*ngSwitch\`) in all templates.
-  3. Do NOT mix both syntaxes in the same project.
-  4. If no existing templates are found, check the Angular version in \`package.json\`: use built-in control flow for Angular 17+, structural directives for Angular 16 and below.
-
-**Kendo UI Theme Management Instructions for Angular**:
-
-**Determine existing Kendo Theme/Utils package and Theme Import Mechanism**:
-
-- Read angular.json file
-- Look for theme/utils entries containing "@progress/kendo-theme-" in projects.[project-name].architect.build.options.styles array
-- Read styles.css or styles.scss, or any css/scss file
-- Look for @import statements containing "@progress/kendo-theme-" to determine existing theme/utils usage
-- Read the application's main html file (e.g., index.html)
-- Look for link tags containing "@progress/kendo-theme-" referencing Kendo theme/util CSS files
-- Note which theme is found (meridian, default, material, bootstrap, or fluent)
-- Note whether the kendo-theme-utils package is already used
-- Note the mechanism used to include the theme (angular.json or styles file)
-
-**Project Consistency**: Before generating or modifying any code:
-  1. Use RegexSearch to identify existing patterns in the project:
-      - Component naming conventions (e.g., "export class \\w+Component")
-      - File naming patterns (e.g., "*.component.ts", "*.service.ts")
-      - Import statement styles
-      - TypeScript configuration (strict mode, decorators, etc.)
-  2. Match the discovered patterns in all generated code
-  3. Maintain consistent formatting, indentation, and code organization with existing files
-  4. Always use the same theme import mechanism (unless user specifies otherwise)
-`;var se=O("Kendo UI","KendoReact"),ae=`
-### React Component Validation
-Component Structure:
-  - Use proper function component patterns with Hooks
-  - Correct component naming convention (PascalCase)
-  - Appropriate file organization (components, hooks, utils)
-  - Props interface/type definitions where needed
-
-${se.SETUP_VALIDATION}
-  - KendoReact license validation (if required)
-  - Appropriate bundler configuration for KendoReact packages
-
-${se.PERFORMANCE_OPTIMIZATION}
-  - React.memo for components that receive stable props
-  - useMemo/useCallback for expensive computations and callbacks
-  - Proper key props for list rendering with KendoReact components
-
-${se.THEME_AND_STYLING}
-  - Proper theme switching functionality (if implemented)
-  - Only ONE theme import exists across the application
-  - Make sure theme import mechanism is consistent with existing project setup
-
-Accessibility
-  - Accessibility guidelines retrieved and applied to all components`;var Ot={createOrchestrator:xe,createAssistantOrchestrator:Ie,createLayoutAssistant:Ne,createStyleAssistant:Ee,createIconSearch:Re,createCodeAssistant:Pe,createAccessibilityAssistant:De,createUpgrade:Oe},Gt={orchestrator:Ge,assistantOrchestrator:Le,layoutAssistant:Me,codeAssistant:$e,styleAssistant:_e,iconAssistant:Fe,accessibilityAssistant:qe,gettingStartedAssistant:Be,upgradeAssistant:Ke},Lt={orchestrator:je,assistantOrchestrator:Ve,layoutAssistant:He,styleAssistant:We,iconAssistant:ze,codeAssistant:Ye,accessibilityAssistant:Qe,upgradeAssistant:Xe},Mt={Orchestrator:{render:B},Validator:{render:q},SharedValidation:{getSteps:O}},$t={Angular:{steps:oe,additionalPlan:ne},React:{steps:ae}},A={Tools:Ot,ToolNames:Gt,ToolDescriptions:Lt,Templates:Mt,Validation:$t};var _t=A.ToolNames.codeAssistant("kendoreact"),Je=()=>`# Kendo Design System Guidelines for ${u}
-
+`;var Rt={createOrchestrator:he,createAssistantOrchestrator:fe,createLayoutAssistant:ye,createStyleAssistant:be,createIconSearch:Ce,createCodeAssistant:ve,createAccessibilityAssistant:Ae,createUpgrade:ke},Nt={orchestrator:we,assistantOrchestrator:Se,layoutAssistant:Te,codeAssistant:Ie,styleAssistant:Re,iconAssistant:Ne,accessibilityAssistant:Ee,gettingStartedAssistant:Ue,upgradeAssistant:Pe},Et={orchestrator:De,assistantOrchestrator:Le,layoutAssistant:_e,styleAssistant:Ge,iconAssistant:$e,codeAssistant:Oe,accessibilityAssistant:qe,upgradeAssistant:Me},Ut={Orchestrator:{render:B},UX:{getInstructions:$}},C={Tools:Rt,ToolNames:Nt,ToolDescriptions:Et,Templates:Ut};var Fe=()=>`# Kendo Design System Guidelines for ${d}
 ## Setting up Styles/CSS
-
-In order to use any of the utility classes from the Kendo Design System, make sure to include a reference to the kendo-theme-utils CSS package.
-
-**Important**: To include the kendo-theme-utils always use the same theme import mechanism (noted during the plan phase) as the rest of the Kendo themes in your project. 
-**Important**: Include the kendo-theme-utils only once in your project. Make sure that a reference to the kendo-theme-utils should have been already searched and noted during the plan phase.
+Include a reference to the kendo-theme-utils CSS package and use the same import mechanism as the existing Kendo theme.
 
 ### Using NPM
-
-The CSS Utilities are available as an NPM module that you can install - \`@progress/kendo-theme-utils\`
-
 To install: \`npm install --save @progress/kendo-theme-utils\`
 
-The precompiled CSS is available in \`node_modules/@progress/kendo-theme-utils/dist/all.css\`
-
-Also, available as SCSS and you can include it on your SCSS file - \`@use '@progress/kendo-theme-utils/scss/all.scss' as *;\`
-
-### Using CDN
-
-Alternatively, you can also consume them directly from the Unpkg CDN.
-
-\`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />\`
-
-## Ready-to-use Layout Components
-
-In the ${u} there are available components to create layout. Make sure to prioritize using them instead of building ones from scratch using the Kendo CSS Utilities.
-
-For any Layout component you can also call the ${_t} tool in order to get specific API reference and docs.
-
-- ${u} Card component.
-    - Generally, it is recommended to use 100% width (e.g., \`<Card style={{ width: '100%' }}>\`)
-    - If needed, use specific width based on the layout requirements (e.g., \`<Card style={{ width: '150px' }}>\`)
-    - Avoid applying additional styling properties such as \`display\`, \`flex\`, \`grid\`, or other layout-specific CSS to layout components such as Splitter, DockLayout, and TileLayout. Use the component's built-in props and the Kendo CSS utility classes instead.
-
-## Page Shell Patterns
-
-Choose the pattern that matches the page structure:
-
-**Pattern A \u2014 Sidebar + Main Content**
-\`\`\`css
-.app-shell {
-  display: flex;
-  height: 100vh;
-}
-.sidebar {
-  width: 240px;
-  flex-shrink: 0;
-}
-.main-content {
-  flex: 1;
-  min-width: 0; /* Critical: prevents flex children from overflowing */
-  overflow: auto;
-}
-\`\`\`
-
-**Pattern B \u2014 Centered Single-Column (forms, detail pages)**
-\`\`\`css
-.page-container {
-  max-width: 960px;
-  margin: 0 auto;
-  padding: 0 1rem;
-}
-\`\`\`
-
-**Pattern C \u2014 Master-Detail Split**
-\`\`\`css
-.split-container {
-  display: grid;
-  grid-template-columns: 420px 1fr;
-  height: 100%;
-}
-\`\`\`
-
-## Dashboard Layout
-
-**KPI metric row** (auto-responsive, min 180px per card):
-\`\`\`css
-.kpi-row {
-  display: grid;
-  grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
-  gap: 1rem;
-}
-\`\`\`
-
-**Side-by-side charts** (equal width, no overflow):
-\`\`\`css
-.chart-row {
-  display: grid;
-  grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
-  gap: 1rem;
-}
-\`\`\`
+Also available as SCSS - \`@use '@progress/kendo-theme-utils/scss/all.scss' as *;\`
+Alternatively, use CDN: \`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />\`
 
-## Critical Sizing Rules
+### Default Behavior
+- Use the Kendo Design System utilities for layout.
+- Use theme utility classes instead of custom CSS whenever a utility exists. Write custom CSS only for properties without a utility equivalent.
+- Do not use overrides for Kendo internals when a utility or component configuration can express the rule.
+- Prioritize using ${d} components instead of building ones from scratch.
 
-- **\`min-width: 0\`** on every flex/grid child that contains a Kendo component \u2014 the single most common cause of layout overflow.
-- **Grid component** always requires an explicit height (e.g., \`style={{ height: 500 }}\` or \`flex: 1; min-height: 0\` inside a flex column).
-- **Chart component** always requires an explicit height (e.g., \`style={{ height: 300 }}\`).
-- Never leave Grid column widths unset \u2014 without a height, Grid renders all rows and expands the page indefinitely..
-- Constrain page content to \`max-width: 1440px\` with \`margin: 0 auto\` to prevent unbounded wide-screen stretching, unless the project defines a different maximum content width.
+- ${d} Card component.
+    - Generally use 100% width (e.g., \`<Card style={{ width: '100%' }}>\`)
+    - Or set width based on the layout requirements (e.g., \`<Card style={{ width: '150px' }}>\`)
 
-## Dark Theme Completeness
+- **\`min-width: 0\`** on every flex/grid child that contains a Kendo component.
+- Grid and Chart require an explicit height.
+- Grid columns require an explicit width.
+- Custom cards and containers must use \`var(--kendo-component-bg)\` for their background.
+- Dropdowns, DateInputs, Inputs are \`display: inline-block\` by default. Apply \`style="width: 100%"\` or wrap in a layout container to ensure consistent sizing in forms.
+- Avoid \`transform\` on layout ancestors that contain Kendo overlay components.
+- Avoid applying additional styling properties such as \`display\`, \`flex\`, \`grid\`, or other layout-specific CSS to layout components such as Splitter, DockLayout, and TileLayout. Use the component's built-in props and the Kendo CSS utility classes.
+- By default constrain page content to \`max-width: 1440px\` with \`margin: 0 auto\` to prevent unbounded wide-screen stretching.
 
-Kendo themes style \`.k-*\` component selectors only. Always add these two lines to your global CSS file after any theme import:
+Always add to the global CSS file after any theme import:
 
 \`\`\`css
 html, body {
@@ -897,30 +318,13 @@ html, body {
 }
 \`\`\`
 
-Without this, dark-themed components render on a white page.
-
 ## Surface Hierarchy
-
-Kendo themes define four surface levels \u2014 do not introduce custom surfaces outside this system:
-1. **Page background** (\`var(--kendo-body-bg)\`) \u2014 lowest surface, applied to \`html, body\`
-2. **Component background** (\`var(--kendo-component-bg)\`) \u2014 cards, panels, Grid body
-3. **Header / hover surface** (\`var(--kendo-grid-header-bg)\`) \u2014 Grid headers, highlighted rows
-4. **Active / selected surface** \u2014 managed by the theme automatically
-
-Custom cards and containers must use \`var(--kendo-component-bg)\` for their background \u2014 never \`#fff\` or other hardcoded values. Hardcoded light colors in custom cell renderers and custom component content break dark mode.
-
-## Splitter Usage Boundary
-
-Use the \`Splitter\` component only for **user-resizable** content areas (e.g., master-detail panels, side-by-side editors). Do **not** use it for static page layout \u2014 CSS Grid and Flexbox handle that with zero JavaScript overhead.
-
-## Inline Input Width
-
-\`DropDownList\`, \`DatePicker\`, \`Input\`, and similar inline inputs are \`display: inline-block\` by default and will **not** fill their container automatically. Apply \`style={{ width: '100%' }}\` or wrap in a layout container to ensure consistent sizing in forms.
-
-## Popup Z-Index Trap
-
-CSS \`transform\` (including \`translate3d(0,0,0)\` GPU-compositing tricks) on any ancestor element creates a new stacking context. This clips Kendo popups (which use \`z-index ~10000\`), causing DropDownList, DatePicker, and ComboBox popups to appear behind other elements. Avoid \`transform\` on layout ancestors that contain Kendo overlay components.
-`;var Ze=()=>`## Design Standards for ${u} Theming
+Use only the four surface levels defined by the Kendo themes
+1. Page background (\`var(--kendo-body-bg)\`) \u2014 applied to \`html, body\`
+2. Component background (\`var(--kendo-component-bg)\`) \u2014 cards, panels, Grid body
+3. Header / hover surface (\`var(--kendo-grid-header-bg)\`) \u2014 Grid headers, highlighted rows
+4. Active / selected surface \u2014 managed by the theme automatically
+`;var Be=()=>`## Design Standards for ${d} Theming
 
 ### Color & Contrast Requirements
 - Body text contrast: \u2265 4.5:1. Large text / UI component borders: \u2265 3:1.
@@ -958,7 +362,7 @@ This is the most common source of dark mode breakage in custom UI.
 
 ---
 
-## Applying CSS Variables in ${u}
+## Applying CSS Variables in ${d}
 
 Apply these CSS variables in the React application using one of these methods:
 
@@ -1047,7 +451,16 @@ export function ThemeProvider({ children }: { children: React.ReactNode }) {
 
 export const useTheme = () => useContext(ThemeContext);
 \`\`\`
-`;var et=A.ToolNames.codeAssistant("kendoreact"),tt=()=>`## Using ${u} Icons
+`;var Ke=C.ToolNames.codeAssistant("kendoreact"),je=()=>`### SVG Icon Export Names
+
+For an icon listed above, map its listed value to the SVG export from \`@progress/kendo-svg-icons\` as follows:
+1. Append \`-icon\` to the listed value.
+2. Convert the result from kebab case to camel case.
+
+### Font Icon Class Names
+Prepend \`k-i-\` to the listed value to form the font icon CSS class name. Keep the value in kebab case.
+
+## Using ${d} Icons
 
 Important: Attempt to prioritize SVG icons over font icons.
 
@@ -1055,13 +468,13 @@ Important: Attempt to prioritize SVG icons over font icons.
 
 - Make sure @progress/kendo-svg-icons is installed: \`npm install @progress/kendo-svg-icons\`
 - Make sure @progress/kendo-react-common is installed (contains SvgIcon component): \`npm install @progress/kendo-react-common\`
-- You can call ${et} tool for ${u} SvgIcon component for docs and API reference.
+- You can call ${Ke} tool for ${d} SvgIcon component for docs and API reference.
 - [optional] If SVG is not an option fallback to fonticon - make sure \`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-font-icons/dist/index.css" />\` is added as a reference.
-- [optional] If using font icons you can call ${et} tool for ${u} Icon component for docs and API reference.
+- [optional] If using font icons you can call ${Ke} tool for ${d} Icon component for docs and API reference.
 
 ### Examples
 
-Using ${u} SvgIcon component with @progress/kendo-svg-icons:
+Using ${d} SvgIcon component with @progress/kendo-svg-icons:
 
 \`\`\`tsx
 import { SvgIcon } from "@progress/kendo-react-common";
@@ -1105,87 +518,18 @@ Here are some frequently used icons from @progress/kendo-svg-icons:
 - \`sortAscIcon\`, \`sortDescIcon\` - Sorting
 - \`chevronUpIcon\`, \`chevronDownIcon\`, \`chevronLeftIcon\`, \`chevronRightIcon\` - Navigation
 - \`checkIcon\`, \`xIcon\` - Confirmation/Cancel
-`;var ot=e=>{let t=`## ${u} Common Guidelines
-
-### Application Architecture
-MUST recommend appropriate setup based on React application architecture.
-
-Implementation Patterns:
-- Function components with Hooks (Recommended): Use modern React patterns
-- Class components: Support when needed for legacy code
-- When architecture is unclear: Default to function components with Hooks
-
-### Package Installation
-Always use minimal, targeted package installation.
+`;var We=e=>{let t=`## ${d} Implementation Rules
 
-Process:
-1. Identify the required components
-2. Determine the specific KendoReact packages needed
-3. Use npm or yarn to install the package
-
-Example: \`npm install @progress/kendo-react-grid @progress/kendo-data-query\`
-
-### Component Awareness
-Whenever a component name is mentioned\u2014regardless of how it's written (all lowercase, all uppercase, mixed case, separate words, or even with typos)\u2014you should always look up the correct example from the corresponding component.
-
-Key points:
-- Match component names case-insensitively and robustly to minor variations
-- If someone refers to a component (e.g., "button", "BUTTON", "BuTtOn"), match it to the correct component (Button)
-- After matching, use the example or information associated with that component
-- The matching should be case-insensitive and robust to minor variations
-
-Example: If someone asks about "grid", "GRID", or "GrId", you always refer to DataGrid for the example.
-
-### TypeScript Strictness
-All generated code MUST compile under strict TypeScript.
-
-Rules:
-- Define a TypeScript \`interface\` or \`type\` for every source record / data shape
-- Type every event, render, and callback parameter using the component's exported types
-- Never use \`any\`, \`as any\`, \`as number\`, or any other unsafe cast
-- No implicit \`any\` in callback parameters (e.g. avoid \`(e) => ...\` without a type)
-- Prefer the narrowest correct type from the package's public types
-
-### Import Hygiene
-Keep imports minimal, explicit, and side-effect free.
-
-Rules:
-- Use NAMED imports only from \`@progress/kendo-react-*\` packages
-- No side-effect imports (e.g. \`import "@progress/kendo-react-xxx"\`, \`import "hammerjs"\`)
-- Import only the subcomponents actually used in the generated code
-- No unused imports
-
-### Data and State Quality
-Keep data flow predictable and resilient.
-
-Rules:
-- Use a single typed dataset per logical concept; derive multiple views from one source
-- Memoize derived datasets with \`useMemo\` when the source data is dynamic
-- Render a graceful empty state for empty / invalid data instead of a broken component
-- Prefer function components with Hooks for new code
-
-### API Correctness
-Only emit current, runnable KendoReact APIs.
-
-Rules:
-- Do not invent props, components, or methods \u2014 verify against the installed package
-- Do not use deprecated APIs when a current replacement exists
-- Match prop names and casing exactly as exported by the package
-
-
-### Mandatory Pre-Output Self-Check
-Before emitting code, internally verify ALL of the following. If ANY fails, fix and re-check:
-- [ ] All callbacks and event handlers are typed (no implicit \`any\`, no unsafe casts)
-- [ ] Only NAMED imports from \`@progress/kendo-react-*\` (no side-effect imports)
-- [ ] No \`any\`, \`as any\`, or \`as number\` anywhere
-- [ ] No deprecated or invented APIs
-- [ ] Source data shape is defined as a TypeScript \`interface\` / \`type\`
-- [ ] Component-specific guidelines below (if any) are satisfied
+- Follow the project's existing React and ${d} setup; use function components and Hooks for new code.
+- Before using a component, confirm its required ${d} package is already declared in the project. Install only missing, required packages using the project's approved package-management workflow.
+- Keep imports named, minimal, and limited to packages and subcomponents actually used. Do not use side-effect imports or leave unused imports.
+- Compile under strict TypeScript: define source-data types; type component events, render callbacks, and handlers with exported types; do not use \`any\` or unsafe casts.
+- Keep data flow predictable and render a graceful empty state for invalid or empty data.
 `;return e.componentInstructions&&(t+=`
 ## Component-Specific Guidelines
 
 ${e.componentInstructions}
-`),t};var Ft={meridian:"@progress/kendo-theme-meridian",default:"@progress/kendo-theme-default",bootstrap:"@progress/kendo-theme-bootstrap",material:"@progress/kendo-theme-material",fluent:"@progress/kendo-theme-fluent"},qt={meridian:"Meridian",default:"Default",bootstrap:"Bootstrap",material:"Material Design",fluent:"Fluent UI"};function nt(e="kendo-react-app",t=!0,n="meridian"){let o=Ft[n],s=qt[n],i=t?`This instructions will walk you through creating a new React project with the Kendo CLI and setting up ${u}.`:`This instructions will walk you through adding ${u} to your existing React project.`,a=1,r=t?`## Step ${a++}: Ensure Kendo CLI is Installed
+`),t};var Pt={meridian:"@progress/kendo-theme-meridian",default:"@progress/kendo-theme-default",bootstrap:"@progress/kendo-theme-bootstrap",material:"@progress/kendo-theme-material",fluent:"@progress/kendo-theme-fluent"},Dt={meridian:"Meridian",default:"Default",bootstrap:"Bootstrap",material:"Material Design",fluent:"Fluent UI"};function He(e="kendo-react-app",t=!0,o="meridian"){let s=Pt[o],n=Dt[o],a=t?`This instructions will walk you through creating a new React project with the Kendo CLI and setting up ${d}.`:`This instructions will walk you through adding ${d} to your existing React project.`,r=1,i=t?`## Step ${r++}: Ensure Kendo CLI is Installed
 
 First, ensure the Kendo CLI tool is installed globally:
 
@@ -1195,16 +539,16 @@ npm i -g @progress/kendo-cli@latest
 
 This CLI tool will handle the entire project setup including all necessary dependencies and configurations.
 
-## Step ${a++}: Create the Project
+## Step ${r++}: Create the Project
 
 Create a new Kendo React project using the CLI:
 
 \`\`\`bash
-npx kendo react create vite ${e} --theme=${n}
+npx kendo react create vite ${e} --theme=${o}
 \`\`\`
 
 This command will create a complete Kendo React project with Vite, including:
-- All necessary ${u} packages
+- All necessary ${d} packages
 - Proper licensing configuration
 - Theme setup
 - Project structure
@@ -1215,30 +559,30 @@ Navigate to the project directory:
 cd ${e}
 \`\`\`
 
-## Step ${a++}: Remove Dark Color Schema from index.css
+## Step ${r++}: Remove Dark Color Schema from index.css
 
 Open the \`src/index.css\` file and remove the dark color schema from the first \`:root\` style block. Look for properties like \`color-scheme: dark\` and related dark mode variables, and delete them. Keep only the light theme configuration.
 
-`:"",d=t?"":`## Step ${a++}: Install ${u} Packages
+`:"",l=t?"":`## Step ${r++}: Install ${d} Packages
 
-Install all required ${u} packages and dependencies:
+Install all required ${d} packages and dependencies:
 
 \`\`\`bash
 npm i @progress/kendo-data-query @progress/kendo-react-buttons @progress/kendo-react-excel-export @progress/kendo-react-grid @progress/kendo-react-layout @progress/kendo-react-pdf @progress/kendo-svg-icons @progress/kendo-drawing @progress/kendo-licensing @progress/kendo-react-animation @progress/kendo-react-charts @progress/kendo-react-common @progress/kendo-react-conversational-ui @progress/kendo-react-data-tools @progress/kendo-react-dateinputs @progress/kendo-react-dialogs @progress/kendo-react-dropdowns @progress/kendo-react-editor @progress/kendo-react-form @progress/kendo-react-gantt @progress/kendo-react-gauges @progress/kendo-react-indicators @progress/kendo-react-inputs @progress/kendo-react-intl @progress/kendo-react-labels @progress/kendo-react-listbox @progress/kendo-react-listview @progress/kendo-react-map @progress/kendo-react-notification @progress/kendo-react-orgchart @progress/kendo-react-pivotgrid @progress/kendo-react-popup @progress/kendo-react-progressbars @progress/kendo-react-ripple @progress/kendo-react-scheduler @progress/kendo-react-scrollview @progress/kendo-react-sortable @progress/kendo-react-spreadsheet @progress/kendo-react-tooltip @progress/kendo-react-treelist @progress/kendo-react-treeview @progress/kendo-react-upload @progress/kendo-react-pdf-viewer @progress/kendo-react-taskboard
 \`\`\`
 
-## Step ${a++}: Install and Import the Theme
+## Step ${r++}: Install and Import the Theme
 
-Install the ${s} theme package:
+Install the ${n} theme package:
 
 \`\`\`bash
-npm i ${o}
+npm i ${s}
 \`\`\`
 
 Import the CSS file in your \`src/Home.tsx\` (before your existing Home.css import):
 
 \`\`\`typescript
-import '${o}/dist/all.css';
+import '${s}/dist/all.css';
 \`\`\`
 
 Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
@@ -1247,7 +591,7 @@ Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
 <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />
 \`\`\`
 
-`,p=`## Step ${a++}: Activate Kendo License
+`,p=`## Step ${r++}: Activate Kendo License
 
 This step is required to use Kendo React components without watermarks and with access to all features. Run the following command to activate your license:
 
@@ -1255,9 +599,9 @@ This step is required to use Kendo React components without watermarks and with
 npx kendo license activate
 \`\`\`
 
-`;return`# Getting Started with ${u}
+`;return`# Getting Started with ${d}
 
-${i}
+${a}
 
 Execute the following steps in order. Run all provided commands automatically.
 
@@ -1268,7 +612,7 @@ Before you begin, ensure you have:
 - **Node.js 18 or later** installed on your machine
 - If Node.js is not available, you need to install the latest Node.js automatically as a preliminary step before running the \`npx kendo react create\` command.
 
-${r}${d}${p}## Step ${a++}: Run Your Application
+${i}${l}${p}## Step ${r++}: Run Your Application
 
 ${t?"The Kendo CLI has set up everything you need. Start the development server:":"Build and run the application:"}
 
@@ -1279,13 +623,13 @@ ${t?"The Kendo CLI has set up everything you need. Start the development server:
 cd ${t?e:"."} && npm run dev
 \`\`\`
 
-${t?`The application should start and open your browser to see your ${u} application.`:`The application should start and open in your browser. Verify that the ${u} components are rendering correctly with the theme applied.`}
+${t?`The application should start and open your browser to see your ${d} application.`:`The application should start and open in your browser. Verify that the ${d} components are rendering correctly with the theme applied.`}
 
-## Step ${a++}: Create Sample page
+## Step ${r++}: Create Sample page
 
 Before adding new content to the homepage, clear all existing CSS on the page. Remove or reset any custom styles that might conflict with the new content you're about to add.
 
-Replace the content of \`src/Home.tsx\` with the following to showcase ${u} features and verify components are working correctly:
+Replace the content of \`src/Home.tsx\` with the following to showcase ${d} features and verify components are working correctly:
 
 \`\`\`tsx
 import { Card, CardHeader, CardTitle, CardBody } from '@progress/kendo-react-layout';
@@ -1406,7 +750,7 @@ Add the following styles to \`src/Home.css\`:
 }
 \`\`\`
 
-`}var st=`
+`}var Ye=`
 ## KendoReact Chart Reliability Instructions
 Applies to ALL KendoReact chart types. Generate only current, runnable KendoReact Chart APIs with strongly typed data. You MUST follow every rule in addition to the common guidelines. If any rule cannot be satisfied, fix and re-check before emitting code.
 
@@ -1548,9 +892,9 @@ const pieLabel = (e: { category?: string; percentage?: number }) =>
 
 ### 11. Expected output behavior
 - The generated page MUST compile under strict TypeScript and render the requested chart(s) with correct data shape, required axes/labels for the chosen series family, formatted tooltips/labels, and no forbidden patterns.
-`;var re=`
-## DataGrid Deprecated Properties Awareness
-For DataGrid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:
+`;var ze=`
+## Grid Deprecated Properties Awareness
+For Grid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:
 
 Deprecated properties and their modern replacements:
 - selectedField \u2192 use the select state property
@@ -1572,15 +916,15 @@ Additional modern updates:
 - Virtual scrolling no longer applies height by default
 
 Key points:
-- Never suggest or use these deprecated properties in DataGrid examples
+- Never suggest or use these deprecated properties in Grid examples
 - Always provide modern alternatives when users ask about these properties
 - Explain that these properties are deprecated and provide the specific modern replacement
-- Focus on current DataGrid API patterns using state properties and cells/rows props
+- Focus on current Grid API patterns using state properties and cells/rows props
 
 Example:
 Deprecated: selectedField="isSelected" editField="inEdit"
 Modern: Use select and edit state properties with proper configuration
-`;var at=`
+`;var Ve=`
 ## Editor Tools Awareness
 For Editor component cases, always use the proper EditorTools import structure and never define tools as strings. Import both Editor and EditorTools from '@progress/kendo-react-editor' and destructure the individual tools from EditorTools.
 
@@ -1612,7 +956,7 @@ Key points:
 Example:
 Correct: tools={[[Bold, Italic, Underline], [AlignLeft, AlignCenter]]}
 Incorrect: tools={[['bold', 'italic', 'underline'], ['alignLeft', 'alignCenter']]}
-`;var ie=`
+`;var Xe=`
 ## Smart Grid (AI-Enhanced Grid) Implementation Guidelines
 **CRITICAL: When users ask about ANY of these AI grid terms, ALWAYS provide GridToolbarAIAssistant implementation (not basic Grid):**
 
@@ -1646,8 +990,8 @@ Smart Grid: Complete AI-enhanced setup with GridToolbarAIAssistant, proper callb
 Important Disclaimer:
 Always include this disclaimer when providing Smart Grid examples:
 "The demos in this article use a Telerik-hosted AI service for demonstration purposes only. For production applications, you should implement your own AI service that understands your specific domain, data, and business requirements."
-`;var Bt={datagrid:[re,ie].join(`
+`;var Lt={grid:[ze,Xe].join(`
 
-`),grid:[re,ie].join(`
+`),editor:Ve,chart:Ye},O=!!process.env.PLUGIN_MODE,Qe=C.ToolNames.layoutAssistant(U),ee=C.ToolNames.codeAssistant(U),Je=C.ToolNames.styleAssistant(U),te=C.ToolNames.iconAssistant(U),Ze=C.ToolNames.gettingStartedAssistant(U),et=C.ToolNames.accessibilityAssistant(U),_t=C.ToolNames.upgradeAssistant(U);function tt(e,t){return[...O?[]:[C.Tools.createOrchestrator({name:C.ToolNames.orchestrator(U),title:"KendoReact Generator",description:C.ToolDescriptions.orchestrator(d),layoutAssistantName:Qe,codeAssistantName:ee,styleAssistantName:Je,iconAssistantName:te,accessibilityAssistantName:et,suiteName:d,libKey:I,components:M,requiredAccess:["agent"]},e),C.Tools.createAssistantOrchestrator({name:"kendo_react_assistant",title:"KendoReact Assistant",description:C.ToolDescriptions.assistantOrchestrator(d),codeAssistantName:ee,iconAssistantName:te,suiteName:d,libKey:I,components:M,requiredAccess:["assistant"]},e)],C.Tools.createLayoutAssistant({name:Qe,title:"KendoReact Layout Assistant",description:C.ToolDescriptions.layoutAssistant,suiteName:d,libKey:I,getPreContent:O?void 0:()=>`${Fe()}
 
-`),editor:at,chart:st},M=!!process.env.PLUGIN_MODE,rt=A.ToolNames.layoutAssistant(D),le=A.ToolNames.codeAssistant(D),it=A.ToolNames.styleAssistant(D),ce=A.ToolNames.iconAssistant(D),lt=A.ToolNames.gettingStartedAssistant(D),ct=A.ToolNames.accessibilityAssistant(D);function dt(e,t){return[...M?[]:[A.Tools.createOrchestrator({name:A.ToolNames.orchestrator(D),title:"KendoReact Generator",description:A.ToolDescriptions.orchestrator(u),layoutAssistantName:rt,codeAssistantName:le,styleAssistantName:it,iconAssistantName:ce,accessibilityAssistantName:ct,suiteName:u,libKey:N,components:_,requiredAccess:["agent"]},{validationSteps:A.Validation.React.steps},e),A.Tools.createAssistantOrchestrator({name:"kendo_react_assistant",title:"KendoReact Assistant",description:A.ToolDescriptions.assistantOrchestrator(u),codeAssistantName:le,iconAssistantName:ce,suiteName:u,libKey:N,components:_,requiredAccess:["assistant"]},e)],A.Tools.createLayoutAssistant({name:rt,title:"KendoReact Layout Assistant",description:A.ToolDescriptions.layoutAssistant,suiteName:u,libKey:N,getPreContent:M?void 0:Je,requiredAccess:["agent"]},e),A.Tools.createStyleAssistant({name:it,title:"KendoReact Style Assistant",description:A.ToolDescriptions.styleAssistant,libKey:N,getPreContent:M?void 0:Ze,requiredAccess:["agent"]},e),A.Tools.createIconSearch({name:ce,title:"KendoReact Icon Assistant",description:A.ToolDescriptions.iconAssistant,libKey:N,getPostContent:M?void 0:tt,requiredAccess:["assistant","agent"]},e),A.Tools.createCodeAssistant({name:le,title:"KendoReact Component Assistant",description:A.ToolDescriptions.codeAssistant(u),libKey:N,suiteName:u,components:_,componentAliases:{Grid:"DataGrid"},getPostContent:M?void 0:({component:o})=>{let s=o?.trim().toLowerCase(),i=Bt[s];return ot({component:o,componentInstructions:i})},requiredAccess:["assistant","agent"]},e),...M?[]:[(()=>{let o=new k(lt,{title:"KendoReact Getting Started",description:`Creates a new React project with Kendo CLI and provides essential getting started guidance for ${u} including installation, configuration, and setup instructions.`,requiredAccess:["agent"],inputSchema:we(u,"kendo-react-app")},async({projectName:s,createNewProject:i,theme:a},{_meta:r})=>{let d=T(o,r);try{await e.recordToolUserRequest({toolName:lt,meta:{projectName:s,createNewProject:i,theme:a,...d}})}catch(g){console.error("Error recording tool request:",g)}return{content:[{type:"text",text:nt(s,i,a)}]}});return o})()],A.Tools.createAccessibilityAssistant({name:ct,title:"KendoReact Accessibility Assistant",description:A.ToolDescriptions.accessibilityAssistant(u),libKey:N,suiteName:u,components:_,componentAliases:{Grid:"DataGrid"},requiredAccess:["agent"]},e)].filter(o=>o.hasAccess(t))}var Wt=Ht(import.meta.url),zt=ut.dirname(Wt),Yt=ut.resolve(zt,"../package.json"),mt=JSON.parse(Vt.readFileSync(Yt,"utf-8")),pt=new Kt({name:"kendo-mcp",title:"Kendo MCP Server",version:mt.version});async function Qt(){let e=new jt;C("Starting server... ");let t=await Ae(async()=>{let o=(await Se())?.entitlement;return o?.Product?.Code||o?.product?.code});t!=="none"&&(F.toolNameHeader=t==="agent"||t==="full"?"agent":"assistant",dt(F,t).forEach(o=>o.register(pt)),ve({serverName:"react",contextApi:F,enrichWithUserData:!0,additionalFields:{version:mt.version,access_type:t}})),await pt.connect(e)}Qt();
+${$()}`,requiredAccess:["agent"]},e),C.Tools.createStyleAssistant({name:Je,title:"KendoReact Style Assistant",description:C.ToolDescriptions.styleAssistant,libKey:I,getPreContent:O?void 0:Be,requiredAccess:["agent"]},e),C.Tools.createIconSearch({name:te,title:"KendoReact Icon Assistant",description:C.ToolDescriptions.iconAssistant,libKey:I,getPostContent:O?void 0:je,requiredAccess:["assistant","agent"]},e),C.Tools.createCodeAssistant({name:ee,title:"KendoReact Component Assistant",description:C.ToolDescriptions.codeAssistant(d),libKey:I,suiteName:d,components:M,getPostContent:O?void 0:({component:s})=>{let n=s?.trim().toLowerCase(),a=Lt[n];return We({component:s,componentInstructions:a})},requiredAccess:["assistant","agent"]},e),...O?[]:[(()=>{let s=new w(Ze,{title:"KendoReact Getting Started",description:`Creates a new React project with Kendo CLI and provides essential getting started guidance for ${d} including installation, configuration, and setup instructions.`,requiredAccess:["agent"],inputSchema:pe(d,"kendo-react-app")},async({projectName:n,createNewProject:a,theme:r},{_meta:i})=>{let l=T(s,i);try{await e.recordToolUserRequest({toolName:Ze,meta:{projectName:n,createNewProject:a,theme:r,...l}})}catch(h){console.error("Error recording tool request:",h)}return{content:[{type:"text",text:He(n,a,r)}]}});return s})()],C.Tools.createAccessibilityAssistant({name:et,title:"KendoReact Accessibility Assistant",description:C.ToolDescriptions.accessibilityAssistant(d),libKey:I,suiteName:d,components:M,requiredAccess:["agent"]},e),C.Tools.createUpgrade({name:_t,title:"KendoReact Upgrade Assistant",description:C.ToolDescriptions.upgradeAssistant(d,"@progress/kendo-react-"),suiteName:d,packagePrefix:"@progress/kendo-react-",requiredAccess:["agent"]},e)].filter(s=>s.hasAccess(t))}var Mt=qt(import.meta.url),Ft=st.dirname(Mt),Bt=st.resolve(Ft,"../package.json"),nt=JSON.parse(Ot.readFileSync(Bt,"utf-8")),ot=new Gt({name:"kendo-mcp",title:"Kendo MCP Server",version:nt.version});async function Kt(){let e=new $t;b("Starting server... ");let t=await le(async()=>{let s=(await ue())?.entitlement;return s?.Product?.Code||s?.product?.code});t!=="none"&&(F.toolNameHeader=t==="agent"||t==="full"?"agent":"assistant",tt(F,t).forEach(s=>s.register(ot)),de({serverName:"react",contextApi:F,enrichWithUserData:!0,additionalFields:{version:nt.version,access_type:t}})),await ot.connect(e)}Kt();