Merge remote-tracking branch 'origin/master' into sstoychev/trigger-new-api-loc

Author: ChronosSF

.github/AGENTS-README.md

@@ -401,15 +401,32 @@ CHANGELOG.md                                      root changelog
 src/app/<component>/                              demo pages
 ```
 
-The system also relies on repository-specific guidance in:
+The system also relies on repository-specific guidance and internal operational skills in:
 
 ```text
 .github/copilot-instructions.md
 skills/igniteui-angular-components/SKILL.md
 skills/igniteui-angular-grids/SKILL.md
 skills/igniteui-angular-theming/SKILL.md
+.github/skills/igniteui-angular-build/SKILL.md
+.github/skills/igniteui-angular-testing/SKILL.md
+.github/skills/igniteui-angular-linting/SKILL.md
 ```
 
+Repository-specific skills for implementation guidance:
+
+- `igniteui-angular-components` — shared guidance for general component patterns, structure, and repository conventions.
+- `igniteui-angular-grids` — shared guidance for grid architecture, patterns, and grid-specific implementation work.
+- `igniteui-angular-theming` — shared guidance for SCSS structure, theme wiring, and style-system conventions.
+
+The internal operational skills are shared references for repository commands and validation flow:
+
+- `igniteui-angular-build` — build command reference for full and partial builds such as library, schematics, migrations, elements, i18n, and related repo build targets.
+- `igniteui-angular-testing` — test suite selection guide, Karma config mapping, and command reference for choosing the smallest relevant test run.
+- `igniteui-angular-linting` — lint command reference, ESLint and Stylelint config locations, and lint expectations before work is considered complete.
+
+Orchestrators should use these skills for command selection instead of repeating command lists inline.
+
 ---
 
 ## Maintenance Notes

.github/CONTRIBUTING.md

@@ -88,38 +88,15 @@ Accessibility is an integral part of any UI component. We as a team are committe
 2. `status: localized` this status is for issues that were with a pending translation status and have already been localized. Place this status label once these translation changes have been included in the current pull request, or the changes are already pulled with a different pull request.
 
 ## Localization (i18n) - applicable to components' string resources
-There are several ways to localize components' string resources:
+There are several ways to localize components' string resources. For more information on how it works, refer to our [Documentation - Localization (i18n)](https://www.infragistics.com/products/ignite-ui-angular/angular/components/general/localization#localization-i18n-1).
 
-1. Using custom resource strings:
-    1.1. Localize a given instance of component - each component which supports localization has input property `resourceStrings`. Setting a newly instantiated object to this property will localize only that given component's instance.
-    1.2. Localize all resources for a component type - each component which supports localization has input property `resourceStrings`. To localize all instances of a given component in the application the following steps should be performed - get the value of the input property `resourceStrings` of the component to be localized; do not create a new instance but replace the existing strings within the object. By default all components of a given type in an application share one instance of the resource strings. Replacing a value in that instance affects all components of that type in the application.
-    1.3. Localize all resources for all components - use global method `getCurrentResourceStrings` to get an object containing current resource strings for all components. To provide localized resources just pass an object of type `IResourceStrings` to the global method `changei18n`.
-    1.4 As of 21.1.x the localization has new implementation and you can use the new API `registerI18n` to register resource string for a component or all components for the whole app, as well as which locale it corresponds to. To localize a single component you will need to get is corresponding resource string keys using one of the available resources and provide only those keys.
+**NOTE** As of 21.1.x, the localization resource strings have been moved to the [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n) repository under `projects/igniteui-i18n-resources`. The package `igniteui-angular-i18n` under `./projects/igniteui-angular-i18n` remains as a source of the localization resources for Ignite UI for Angular, that derives the resources from [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n).
 
-2. Using npm package:
-We've created new repository which will hold the resource strings for languages different than English:
-https://github.com/IgniteUI/igniteui-angular-i18n 
-
-**NOTE** The localization repo has been moved to live inside the `igniteui-angular` repository under `./projects/igniteui-angular-i18n`
-**NOTE** As of 21.1.x the localization resource strings have been moved to the [`igniteui-i18n`](https://github.com/IgniteUI/igniteui-i18n) repository under `projects/igniteui-i18n-resources`.
+**NOTE (21.0.x and lower)** The localization resource strings live inside the `igniteui-angular` repository under `./projects/igniteui-angular-i18n`.
 
 A npm package should be published each time we release new version of Ignite UI for Angular. Its version should correspond to the version of the igniteui-angular npm package.
 One could localize an application by importing the corresponding localized resource strings from the localization package (`igniteui-angular-i18n`) and use the methods described in the previous bullet to localize the whole application or part of it.
 
-**Example:**
-
-Inside app.module you can perform:
-```ts
-import { IgxResouceStringsJA } from ‘igniteui-angular-i18n’;
-changei18n(IgxResouceStringsJA);
-```
-
-**Example new API:**
-```ts
-import { ResouceStringsJA } from ‘igniteui-i18n-resources’;
-registerI18n(IgxResouceStringsJA, 'ja');
-```
-
 ### Resource strings keys naming convention
 Each key in the `IResourceStrings` (and `IGridResourceStrings`, `ITimePickerResourceStrings`, etc.) is prefixed with components' selector and followed by the resource string key. Having components' selectors as prefixes allows us to have same resource strings keys for more than one component.
 Example: _igx_grid_groupByArea_message_.

.github/agents/bug-fixing-orchestrator-agent.md

@@ -109,16 +109,9 @@ Do not add sections such as:
 
 ---
 
-## Component-Specific Patterns
-
-Check the relevant skill file for component APIs and patterns:
-- Non-grid components → `skills/igniteui-angular-components/SKILL.md`
-- Grid components → `skills/igniteui-angular-grids/SKILL.md`
-- Theming & styling → `skills/igniteui-angular-theming/SKILL.md`
-
-Each skill file is a routing hub pointing to detailed reference files under its `references/` folder. **Read the relevant reference files** when investigating the root cause.
-
-If the bug touches component SCSS or theme wiring, read `skills/igniteui-angular-theming/references/contributing.md` during investigation and plan a dedicated `theming-styles-agent` handoff.
+> Skills:
+> - APIs: `skills/igniteui-angular-{components,grids,theming}/SKILL.md`
+> - Build / test / lint: `.github/skills/`
 
 ---
 
@@ -172,10 +165,15 @@ Present a brief scope summary to the user:
 
 Keep it short and high-level. Confirm scope, not solution details.
 
-Wait for user confirmation.
+Before routing any work, ask:
+
+**`Do you want me to proceed with this implementation flow?`**
+
+If the fix is user-visible, also ask:
+
+**`Do you want a demo/sample update for this feature?`**
 
-If a demo/sample is relevant, ask explicitly:
-`Do you want a demo/sample update for this change? Yes / No`
+Wait for the user's answer before routing work.
 
 ### Step 4 — Route Work
 
@@ -218,6 +216,7 @@ After all agents finish, check:
 - If a demo/sample was requested, was the existing demo structure updated appropriately?
 - If a demo/sample was not requested, was it correctly skipped?
 - Is multi-branch cherry-picking needed?
+- Run `npm run lint:lib` and verify it passes.
 
 Report what was done and any remaining items.
 

.github/agents/feature-orchestrator-agent.md

@@ -103,6 +103,12 @@ Do not add sections such as:
 
 ---
 
+> Skills:
+> - APIs: `skills/igniteui-angular-{components,grids,theming}/SKILL.md`
+> - Build / test / lint: `.github/skills/`
+
+---
+
 ## Key Repository Paths
 
 ```
@@ -132,7 +138,7 @@ projects/igniteui-angular/core/src/core/styles/   ← component SCSS themes
    - Whether a migration schematic is needed
    - Whether i18n strings are affected
    - Whether styles or component themes are affected
-   - Which test suite to use (grid vs non-grid)
+   - Which test suite to use (grid vs non-grid vs schematics/styles/i18n)
 
 ### Step 2 — Request Missing Context
 
@@ -153,10 +159,15 @@ Present a brief scope summary to the user:
 
 Keep it short and high-level. Confirm scope, not solution details.
 
-Wait for user confirmation.
+Before routing any work, ask:
+
+**`Do you want me to proceed with this implementation flow?`**
+
+If the feature is user-visible, also ask:
+
+**`Do you want a demo/sample update for this feature?`**
 
-If a demo/sample is relevant, ask explicitly:
-`Do you want a demo/sample update for this feature? Yes / No`
+Wait for the user's answer before routing work.
 
 ### Step 4 — Route Work
 
@@ -202,5 +213,6 @@ After all agents finish, check:
 - Do migrations exist for any breaking changes?
 - If a demo/sample was requested, was the existing demo structure updated appropriately?
 - If a demo/sample was not requested, was it correctly skipped?
+- Run `npm run lint:lib` and verify it passes.
 
 Report what was done and any remaining items.

.github/copilot-instructions.md

@@ -121,3 +121,6 @@ Domain-specific skills for AI-assisted development are located in the [`skills/`
 - [`skills/igniteui-angular-components`](../skills/igniteui-angular-components/SKILL.md) — UI Components (form controls, layout, data display, feedback/overlays, directives — Input Group, Combo, Select, Date/Time Pickers, Calendar, Tabs, Stepper, Accordion, List, Card, Dialog, Snackbar, Button, Ripple, Tooltip, Drag and Drop, Layout Manager, Dock Manager) and Charts (Area Chart, Bar Chart, Column Chart, Stock/Financial Chart, Pie Chart)
 - [`skills/igniteui-angular-grids`](../skills/igniteui-angular-grids/SKILL.md) — Data Grids (grid type selection, column config, sorting, filtering, selection, editing, grouping, paging, remote data, state persistence, Tree Grid, Hierarchical Grid, Grid Lite, Pivot Grid)
 - [`skills/igniteui-angular-theming`](../skills/igniteui-angular-theming/SKILL.md) — Theming & Styling (includes MCP server setup)
+- [`.github/skills/igniteui-angular-build`](skills/igniteui-angular-build/SKILL.md) — Building the library (full build, `build:lib`, partial builds for styles, migrations, schematics, i18n, elements)
+- [`.github/skills/igniteui-angular-testing`](skills/igniteui-angular-testing/SKILL.md) — Testing (choosing the right test suite, grid vs non-grid, watch mode, schematics/styles/i18n tests)
+- [`.github/skills/igniteui-angular-linting`](skills/igniteui-angular-linting/SKILL.md) — Linting (ESLint + Stylelint, `lint:lib`, configuration files)

.github/skills/igniteui-angular-build/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: igniteui-angular-build
+description: "Quick-reference for building the core Ignite UI for Angular library and related packages. Covers the full production build (`build:lib`), individual partial builds (styles, extras, migrations, schematics, i18n, elements), and the combined build-all command. Use when an agent needs to compile the library, produce a dist output, or verify that code changes compile cleanly. Do NOT use for running tests — use igniteui-angular-testing instead. Do NOT use for linting — use igniteui-angular-linting instead."
+user-invocable: true
+---
+
+# Ignite UI for Angular — Build
+
+Quick-reference card for the core library and related build commands in this repository.
+
+## Prerequisites
+
+- Run `npm install` at the repo root before any build command.
+
+## Full Build
+
+```bash
+npm run build
+```
+
+Runs all sub-builds in sequence (library, elements, schematics, migrations, i18n, extras). Use this when you need a complete publishable output or before running the full CI pipeline locally. Check `package.json` for the exact sequence.
+
+## Library Build (most common)
+
+```bash
+npm run build:lib
+```
+
+This is the primary build command. It does two things:
+
+1. `ng build igniteui-angular --configuration production` — compiles the library with ng-packagr using Angular Package Format. Uses `ng-package.prod.json` (production config).
+2. `npm run build:styles` — runs `node scripts/build-styles.mjs` to compile and bundle Sass themes into distributable CSS.
+
+**Output**: `dist/igniteui-angular/`
+
+### When to use `build:lib`
+
+- After implementing a feature or fix, to verify the code compiles.
+- Before checking that new public symbols are correctly exported.
+- When another project needs to consume a local build of the library.
+
+## Partial Builds
+
+| Command | What it does |
+|---|---|
+| `npm run build:styles` | Compiles Sass themes only (`scripts/build-styles.mjs`). Already included in `build:lib`. |
+| `npm run build:extras` | Builds the extras package and then runs extras migrations. |
+| `npm run build:schematics` | Copies and compiles `ng add` schematics (`projects/igniteui-angular/schematics/`). |
+| `npm run build:migrations` | Copies and compiles `ng update` migration schematics (`projects/igniteui-angular/migrations/`). |
+| `npm run build:i18n` | Compiles the i18n package (`projects/igniteui-angular-i18n/`). |
+| `npm run build:elements` | Builds the Angular Elements package + bundling + style copy. |
+| `npm run build:docs` | Generates TypeDoc + SassDoc documentation. |
+
+### When to use partial builds
+
+- **`build:schematics`** — after editing files under `projects/igniteui-angular/schematics/`.
+- **`build:migrations`** — after editing files under `projects/igniteui-angular/migrations/`. Required before running `test:schematics`.
+- **`build:extras`** — after editing the extras package or when validating the full root `build` flow.
+- **`build:i18n`** — after changing i18n resource strings.
+- **`build:elements`** — when working on the Angular Elements wrapper.
+
+## Key Paths
+
+| Path | Purpose |
+|---|---|
+| `projects/igniteui-angular/` | Library source root |
+| `projects/igniteui-angular/ng-package.prod.json` | Production ng-packagr config |
+| `projects/igniteui-angular/ng-package.json` | Dev ng-packagr config (preserves dest) |
+| `dist/igniteui-angular/` | Build output |
+| `scripts/build-styles.mjs` | Sass theme compilation script |
+
+## Related Skills
+
+- [`igniteui-angular-testing`](../igniteui-angular-testing/SKILL.md) — Running tests
+- [`igniteui-angular-linting`](../igniteui-angular-linting/SKILL.md) — Linting code and styles

.github/skills/igniteui-angular-linting/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: igniteui-angular-linting
+description: "Quick-reference for linting the core Ignite UI for Angular library. Covers the combined lint command (`lint:lib`), ESLint for TypeScript and templates, and Stylelint for Sass/SCSS styles. Use when an agent needs to run the main linters, fix lint errors, or understand the primary lint configuration. Do NOT use for building — use igniteui-angular-build instead. Do NOT use for running tests — use igniteui-angular-testing instead."
+user-invocable: true
+---
+
+# Ignite UI for Angular — Linting
+
+Quick-reference card for the core lint commands for the main library in this repository.
+
+## Prerequisites
+
+- Run `npm install` at the repo root.
+
+## Commands
+
+| Command | What it runs |
+|---|---|
+| `npm run lint:lib` | ESLint **+** Stylelint (both — use this as the default) |
+| `npm run lint:styles` | Stylelint only (Sass/SCSS files) |
+| `npm run lint` | `ng lint` — ESLint only (TypeScript + templates) |
+| `ng lint --fix` | Quick fix for tool identifiable fixes |
+
+### `lint:lib` (recommended)
+
+```bash
+npm run lint:lib
+```
+
+This is the combined command and the one agents should run before considering work complete. It executes:
+
+1. `ng lint` — ESLint on TypeScript source and Angular templates, using the config at `projects/igniteui-angular/eslint.config.mjs`.
+2. `npm run lint:styles` — Stylelint on Sass files under `projects/igniteui-angular/core/src/core/styles`.
+
+### Lint Styles Only
+
+```bash
+npm run lint:styles
+```
+
+Runs `stylelint "projects/igniteui-angular/core/src/core/styles"`. Use when you only changed SCSS/Sass and want a faster check.
+
+## Configuration Files
+
+| File | Purpose |
+|---|---|
+| `eslint.config.mjs` (repo root) | Root ESLint config |
+| `projects/igniteui-angular/eslint.config.mjs` | Library-specific ESLint config (referenced in `angular.json`) |
+| `.stylelintrc.json` (repo root) | Root Stylelint config used by `npm run lint:styles` |
+
+## Agent Rules
+
+- **Always run `npm run lint:lib` before marking work complete** — this is a requirement from [AGENTS.md](../../../AGENTS.md).
+- Fix all lint errors before committing. Do not disable rules without justification.
+- If a lint rule conflicts with the intended change, investigate whether the rule is correct before suppressing it.
+
+## Related Skills
+
+- [`igniteui-angular-build`](../igniteui-angular-build/SKILL.md) — Building the library
+- [`igniteui-angular-testing`](../igniteui-angular-testing/SKILL.md) — Running tests