Merge branch 'master' into vkombov/fix-17105

Author: ChronosSF

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,6 +6,9 @@ Closes #
  - [ ] Documentation
  - [ ] Demos
  - [ ] CI/CD
+ - [ ] Tests
+ - [ ] Changelog
+ - [ ] Skills/Agents
 
 ### Checklist:
  - [ ] All relevant tags have been applied to this PR

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

@@ -131,7 +131,7 @@ projects/igniteui-angular/core/src/core/styles/   ← component SCSS themes
 1. Read the feature request.
 2. Search the repo to identify affected components, directives, services, and files.
 3. If the feature touches theming or styles, read
-   `skills/igniteui-angular-theming/references/contributing.md` before planning the styling handoff.
+   `.github/themes-contributing.md` before planning the styling handoff.
 4. Determine:
    - Which components are affected and where they live
    - Whether this replaces, renames, or deprecates any existing API

.github/agents/theming-styles-agent.md

@@ -23,7 +23,7 @@ Your job is to implement visual fixes and style features in the in-repo SCSS sou
 
 1. Read the original request, bug report, or handoff summary.
 2. Read the relevant SCSS, component markup, and any existing tests before editing.
-3. Read `skills/igniteui-angular-theming/references/contributing.md` in full before modifying any `_*-theme.scss` or `_*-component.scss` file, wiring a component into the theme system, or changing style tests.
+3. Read `.github/themes-contributing.md` in full before modifying any `_*-theme.scss` or `_*-component.scss` file, wiring a component into the theme system, or changing style tests.
 4. Decide whether the change belongs in a component theme file, a structural component file, shared style infrastructure, or a minimal supporting markup hook.
 5. Implement the required theming and style changes without expanding into unrelated production logic.
 6. Run the relevant style validation before finishing.
@@ -32,7 +32,7 @@ Your job is to implement visual fixes and style features in the in-repo SCSS sou
 
 ## Required Reference
 
-Contributing to the in-repo SCSS source is covered in `skills/igniteui-angular-theming/references/contributing.md`.
+Contributing to the in-repo SCSS source is covered in `.github/themes-contributing.md`.
 
 Read that file when:
 - modifying or creating `_*-theme.scss` files

…gular-theming/references/contributing.md .github/themes-contributing.mdskills/igniteui-angular-theming/references/contributing.md renamed to .github/themes-contributing.md skills/igniteui-angular-theming/references/contributing.md renamed to .github/themes-contributing.md

@@ -62,11 +62,6 @@ module.exports.copyMigrations = (cb) => {
         '!**/tsconfig.json'
     ]).pipe(gulp.dest('./dist/igniteui-angular/migrations'));
 
-
-    gulp.src([
-        './projects/igniteui-angular/migrations/common/import-helper.js'
-    ]).pipe(gulp.dest('./dist/igniteui-angular/migrations/common'));
-
     cb();
 };