chore: update mds

onlyexeption · onlyexeption · commit a5fa208f07bd · 2026-05-11T09:56:08.000+03:00
diff --git a/packages/igniteui-mcp/Specification.md b/packages/igniteui-mcp/Specification.md
@@ -142,26 +142,25 @@ Doc "<name>" not found for framework "<framework>". Use list_components to see a
 **Return**: Markdown setup guidance only. The response contains installation, scaffolding, and next-step instructions for the selected framework.
 
 ### **search_api**
-**Purpose**: Search Ignite UI API entries by keyword, feature, or partial component name across Angular, React, and Web Components. Returns up to 10 results ranked by match count.
+**Purpose**: Search Ignite UI API entries by keyword, feature, or partial component name across all four platforms. Returns up to 10 results ranked by match count.
 
 **Logic**:
 - Searches against component names, keywords, API type, and document content
-- Omitting `platform` searches all three supported platforms simultaneously
+- Omitting `platform` searches all four supported platforms simultaneously
 - Results are ranked by match count; each result includes the exact component name, platform tag, API type (class/interface/directive/enum), match count, keyword list, and a content excerpt
 
 **Schema**:
 - `query`: String — keyword, partial name, or feature description; max 256 characters — required
-- `platform`: Enum (angular|react|webcomponents) — optional; omit to search all platforms
+- `platform`: Enum (angular|react|webcomponents|blazor) — optional; omit to search all platforms
 
 **Constraints**:
-- Blazor is not supported
 - Output is text, not structured JSON
 - Returns an empty-query message immediately if the input is blank
 
 **Return**: Up to 10 ranked text results. Use the exact `component` name and `platform` from a result to call `get_api_reference`.
 
 ### **get_api_reference**
-**Purpose**: Retrieve the full API reference for one Ignite UI component or class. Supports Angular, React, and Web Components. Component name matching is case-insensitive.
+**Purpose**: Retrieve the full API reference for one Ignite UI component or class. Supports Angular, React, Web Components, and Blazor. Component name matching is case-insensitive.
 
 **Logic**:
 - Requires the exact component name (obtained from user code or an `search_api` result)
@@ -171,12 +170,9 @@ Doc "<name>" not found for framework "<framework>". Use list_components to see a
 
 **Schema**:
 - `component`: String — exact component or class name; max 128 characters — required
-- `platform`: Enum (angular|react|webcomponents) — required
+- `platform`: Enum (angular|react|webcomponents|blazor) — required
 - `section`: Enum (all|properties|methods|events) — optional; defaults to `all`
 
-**Constraints**:
-- Blazor is not supported
-
 **Return**: Formatted Markdown for the requested API entry. The full entry (`section="all"`) includes the class/interface summary, properties with types and descriptions, methods with signatures, and events.
 
 #### Error Response Contract
diff --git a/packages/igniteui-mcp/igniteui-doc-mcp/CLAUDE.md b/packages/igniteui-mcp/igniteui-doc-mcp/CLAUDE.md
@@ -28,7 +28,11 @@ This is the **Ignite UI Documentation MCP Server** — a Model Context Protocol
 │   ├── export-blazor-docs.ts          # Export Blazor docs from xplat gulp build (toc.json-driven, flatten hierarchy)
 │   ├── inject-blazor-docs.ts          # Inject Blazor sample code (github-src based, .razor/.razor.cs/.css files)
 │   ├── compress-blazor-docs.ts        # LLM-based compression with Blazor-specific prompt (Igb prefix, no suffix, supports --batch mode)
-│   └── validate-docs.ts               # LLM-as-Judge validation of compressed docs (platform-independent)
+│   ├── validate-docs.ts               # LLM-as-Judge validation of compressed docs (platform-independent)
+│   ├── export-angular-api.ts          # Build Angular API docs from blazor/api-docs submodule → docs/angular-api/
+│   ├── export-react-api.ts            # Build React API docs from blazor/api-docs submodule → docs/react-api/
+│   ├── export-wc-api.ts               # Build Web Components API docs from blazor/api-docs submodule → docs/webcomponents-api/
+│   └── export-blazor-api.ts           # Build Blazor API docs from blazor/api-docs submodule → docs/blazor-api/
 ├── docs/
 │   ├── knowledgebase.md                # Lessons learned and issues for cross-platform reference (32 entries)
 │   ├── db.md                           # SQLite + FTS4 database integration (IMPLEMENTED)
@@ -42,6 +46,10 @@ This is the **Ignite UI Documentation MCP Server** — a Model Context Protocol
 │   ├── react-pipeline.md              # React pipeline implementation plan
 │   ├── wc-pipeline-plan.md            # WebComponents pipeline implementation plan
 │   └── blazor-pipeline-plan.md        # Blazor pipeline implementation plan
+├── angular-api/                        # Angular API docs (llms-full.txt files, built by build:docs:angular-api)
+├── react-api/                          # React API docs (llms-full.txt files, built by build:docs:react-api)
+├── webcomponents-api/                  # Web Components API docs (llms-full.txt files, built by build:docs:wc-api)
+├── blazor-api/                         # Blazor API docs (llms-full.txt files, built by build:docs:blazor-api)
 ├── angular/                            # Git submodules
 │   ├── igniteui-docfx/                 # DocFX-based Angular documentation (en/jp/kr)
 │   │   └── en/components/toc.yml       # Table of contents — source of truth for which files to process
@@ -74,6 +82,18 @@ npm run build      # compile TypeScript (tsc) → outputs to ./dist/
 npm start          # run MCP server in local mode (default, uses bundled SQLite DB)
 ```
 
+### API Docs Generation
+
+The `blazor/api-docs` submodule provides the Astro build pipeline used by all four platforms. Run these scripts once (or when upstream API data changes) to populate the `docs/*-api/` directories:
+
+```bash
+npm run build:docs:angular-api     # Angular: Astro build → docs/angular-api/
+npm run build:docs:wc-api          # Web Components: Astro build → docs/webcomponents-api/
+npm run build:docs:react-api       # React: Astro build → docs/react-api/
+npm run build:docs:blazor-api      # Blazor: docfx + Astro build → docs/blazor-api/
+npm run build:docs:all             # Build all four platforms
+```
+
 ### Server Modes
 
 | Mode | Activation | Data Source |
diff --git a/packages/igniteui-mcp/igniteui-doc-mcp/DEVELOPMENT.md b/packages/igniteui-mcp/igniteui-doc-mcp/DEVELOPMENT.md
@@ -6,7 +6,7 @@ MCP server that serves pre-compressed Ignite UI component documentation via full
 
 ```bash
 cd packages/igniteui-mcp/igniteui-doc-mcp
-git submodule update --init --recursive
+git submodule update --init blazor/api-docs
 npm install
 ```
 
@@ -24,19 +24,15 @@ npm run build:db
 ```
 
 ### Building the API markdown
-The repository already tracks the required documentation and source repositories as git submodules. A fresh clone still needs `git submodule update --init --recursive` to materialize them locally.
-
-Required submodules for local API markdown generation include:
-- `angular/igniteui-angular`
-- `webcomponents/igniteui-webcomponents`
+The `blazor/api-docs` submodule provides the Astro-based API build pipeline used by all four platforms. A fresh clone still needs `git submodule update --init blazor/api-docs` to materialize it locally.
 
 Before using the MCP server from a source checkout, generate the local API markdowns:
 
 ```bash
 npm run build:docs:all
 ```
 
-This step builds the Angular and Web Components API markdown used by the local MCP API tools. If you skip it, API lookups may be incomplete or unavailable even if the server itself builds successfully.
+This step generates API docs for all four platforms (Angular, React, Web Components, and Blazor). If you skip it, API lookups may be incomplete or unavailable even if the server itself builds successfully.
 
 If you want to refresh submodules to newer upstream commits, run:
 
@@ -421,70 +417,52 @@ Per-platform clear removes the platform subdirectory from `docs_processing/`, `d
 
 ## API Reference Documentation
 
-The MCP server provides API reference lookup via the `get_api_reference` and `search_api` tools. API docs are generated from framework submodules using TypeDoc and stored in `docs/<framework>/`.
+The MCP server provides API reference lookup via the `get_api_reference` and `search_api` tools. API docs are generated from the `blazor/api-docs` submodule using its Astro build pipeline and stored as `llms-full.txt` files in `docs/{platform}-api/`.
 
-Each framework uses one of two source strategies:
+All four platforms use the same source strategy:
 
-| Framework | Strategy | Source | Output |
-|-----------|----------|--------|--------|
-| Angular | `markdown-index` | `angular/igniteui-angular` (TypeDoc → markdown) | `docs/angular/api/*.md` + `index.json` |
-| React | `typedoc-json` | Pre-built TypeDoc JSON model | `docs/react/igniteui-react.json` |
-| Web Components | `markdown-index` | `webcomponents/igniteui-webcomponents` (TypeDoc → markdown) | `docs/webcomponents/api/*.md` + `index.json` |
-| Blazor | — | Not yet supported | — |
+| Platform | Build script | Output |
+|----------|-------------|--------|
+| Angular | `build:docs:angular-api` | `docs/angular-api/{package}/{version}/llms-full.txt` |
+| React | `build:docs:react-api` | `docs/react-api/{package}/{version}/llms-full.txt` |
+| Web Components | `build:docs:wc-api` | `docs/webcomponents-api/{package}/{version}/llms-full.txt` |
+| Blazor | `build:docs:blazor-api` | `docs/blazor-api/{package}/{version}/llms-full.txt` |
 
 ### Building API Docs
 
 ```bash
-npm run build:docs:angular         # Angular: TypeDoc → markdown + search index
-npm run build:docs:webcomponents   # Web Components: build lib → TypeDoc → markdown + search index
-npm run build:docs:all             # Build both Angular and Web Components
+npm run build:docs:angular-api     # Angular: Astro build → llms-full.txt files
+npm run build:docs:wc-api          # Web Components: Astro build → llms-full.txt files
+npm run build:docs:react-api       # React: Astro build → llms-full.txt files
+npm run build:docs:blazor-api      # Blazor: docfx + Astro build → llms-full.txt files
+npm run build:docs:all             # Build all four platforms
 ```
 
-Each `build:docs:<platform>` script:
-1. Initializes the required git submodule (`git submodule update --init`)
-2. Compiles the MCP server TypeScript (`npm run build`)
-3. Runs `scripts/build-docs.mjs <platform>` which:
-   - Checks the submodule is built (for Web Components, runs `npm install && npm run build:publish` if needed)
-   - Runs TypeDoc with the config from `typedoc/<platform>.typedoc.json`
-   - Generates markdown files in `docs/<platform>/api/`
-   - Builds a search index (`index.json`) with component names, types, keywords, and summaries
+Each `build:docs:{platform}-api` script:
+1. Initializes the `blazor/api-docs` git submodule
+2. Runs `npm install` in the submodule
+3. Runs the Astro static build for the platform (`npm run build:{platform}:en`)
+4. Copies the generated `llms-full.txt` files from `dist/en/api/{platform}/` to `docs/{platform}-api/`
 
-**React** uses a pre-built TypeDoc JSON model (`docs/react/igniteui-react.json`) that is checked into git. It does not need a `build:docs` step — the JSON is parsed at runtime by `ReactJsonParser`.
+The Blazor script additionally runs `dotnet tool restore` and `npm run fetch:tools:blazor` + the five docfx package build scripts before the Astro step. Angular's TypeDoc JSON data is pre-bundled in `blazor/api-docs/src/data/angular/` so no fetch step is needed.
 
 ### Rebuilding After Upstream Changes
 
-When the upstream Angular or Web Components library releases a new version:
+When a new version of `blazor/api-docs` is available:
 
-1. Update the submodule to the new version:
+1. Update the submodule:
    ```bash
-   cd angular/igniteui-angular    # or webcomponents/igniteui-webcomponents
-   git fetch && git checkout <new-tag>
+   cd blazor/api-docs
+   git fetch && git checkout <new-branch-or-tag>
    cd ../..
    ```
 
-2. Rebuild the API docs:
+2. Rebuild the affected platform's API docs:
    ```bash
-   npm run build:docs:angular     # or build:docs:webcomponents
+   npm run build:docs:angular-api   # or wc-api / react-api / blazor-api
    ```
 
-3. Commit the updated `docs/` output and submodule reference.
-
-### Web Components First-Time Build
-
-The Web Components submodule requires a one-time library build before TypeDoc can generate docs. The `build-docs.mjs` script handles this automatically:
-
-1. If `dist/index.d.ts` is missing, it runs `npm install && npm run build:publish`
-2. After TypeDoc completes, it cleans up `node_modules` if it installed them
-3. Subsequent runs skip the build step if `dist/index.d.ts` exists
-
-If the automatic build fails, build manually:
-
-```bash
-cd webcomponents/igniteui-webcomponents
-npm install && npm run build:publish
-cd ../..
-npm run build:docs:webcomponents
-```
+3. Commit the updated `docs/{platform}-api/` output and submodule reference.
 
 ## MCP Server
 
diff --git a/packages/igniteui-mcp/igniteui-doc-mcp/README.md b/packages/igniteui-mcp/igniteui-doc-mcp/README.md
@@ -20,21 +20,19 @@ npx @igniteui/mcp-server
 
 In order to run the MCP from this repository, git submodules must be initialized first. The repo already includes the submodule entries, but a fresh clone still needs to fetch them locally.
 
-Required submodules for local API markdown generation include:
-- `angular/igniteui-angular`
-- `webcomponents/igniteui-webcomponents`
+The `blazor/api-docs` submodule is required for local API markdown generation for all four platforms (Angular, React, Web Components, and Blazor).
 
 Recommended first-time setup:
 
 ```bash
 cd packages/igniteui-mcp/igniteui-doc-mcp
-git submodule update --init --recursive
+git submodule update --init blazor/api-docs
 npm install
 npm run build:docs:all
 npm run build
 ```
 
-`npm run build:docs:all` generates the local API markdown artifacts used by the MCP API tools for Angular and Web Components. Run it before starting the server.
+`npm run build:docs:all` generates the local API markdown artifacts used by the MCP API tools for all four platforms (Angular, React, Web Components, and Blazor). Run it before starting the server.
 
 If you need to refresh submodules to newer upstream commits later, use:
 
