Merge branch 'master' into ganastasov/align-agents-md-with-repo-workflow

Author: georgianastasov

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

@@ -114,6 +114,7 @@ If the bug requires SCSS, theme wiring, or style-test changes, do not implement
 - Do not update `README.md` — the `component-readme-agent` handles that.
 - Do not create migration schematics — the `migration-agent` handles that.
 - Do not update `CHANGELOG.md` — the `changelog-agent` handles that.
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 

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

@@ -68,6 +68,7 @@ You do NOT write tests, production code, or detailed implementation instructions
 - Do not write tests or production code
 - Do not specify exact test cases, exact implementations, or exact file changes
 - Do not over-constrain the handoff prompts — give scope and root cause, not specs
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 

.github/agents/changelog-agent.md

@@ -5,6 +5,7 @@ tools:
   - search/codebase
   - edit/editFiles
   - read/problems
+  - web
 ---
 
 # Changelog Agent
@@ -13,6 +14,12 @@ You update `CHANGELOG.md` at the repository root for Ignite UI for Angular. Only
 
 ---
 
+## What You Do NOT Do
+
+- Do not modify production source code.
+
+---
+
 ## Steps
 
 ### 1. Find the Latest Version

.github/agents/component-readme-agent.md

@@ -5,6 +5,7 @@ tools:
   - search/codebase
   - edit/editFiles
   - read/problems
+  - web
 ---
 
 # Component README Agent
@@ -58,7 +59,8 @@ Component documentation is located at:
    - examples when needed
 5. If behavior changed, update the related explanatory text.
 6. If a new capability was added, add a short example only if the README style supports it.
-7. Match existing formatting exactly.
+7. If API was renamed or deprecated, update or remove stale examples and snippets that still reference the old usage.
+8. Match existing formatting exactly.
 
 ---
 

.github/agents/demo-sample-agent.md

@@ -7,6 +7,7 @@ tools:
   - read/problems
   - execute/runTests
   - read/terminalLastCommand
+  - web
 ---
 
 # Demo / Sample Agent
@@ -39,6 +40,7 @@ You do not implement the library change itself, create new samples or demo folde
 - Do not update component `README.md`.
 - Do not update `CHANGELOG.md`.
 - Do not create migrations.
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 

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

@@ -8,6 +8,7 @@ tools:
   - read/problems
   - execute/runTests
   - read/terminalLastCommand
+  - web
 ---
 
 # Implementer — GREEN + REFACTOR Phases
@@ -118,6 +119,7 @@ Update component agent skills if you need to guide other agents on how to use th
 - Do not update `README.md` — the `component-readme-agent` handles that.
 - Do not create migration schematics — the `migration-agent` handles that.
 - Do not update `CHANGELOG.md` — the `changelog-agent` handles that.
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 

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

@@ -6,6 +6,7 @@ tools:
   - search/codebase
   - search/changes
   - read/problems
+  - web
 agents:
   - tdd-test-writer-agent
   - feature-implementer-agent
@@ -64,6 +65,7 @@ You do NOT write tests, production code, or detailed acceptance criteria. Each s
 - Do not write detailed acceptance criteria that downstream agents must encode literally
 - Do not specify exact test cases, exact implementations, or exact file changes
 - Do not over-constrain the handoff prompts — give scope, not specs
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 
@@ -186,24 +188,22 @@ Use agents in this order:
 4. **`demo-sample-agent`** — only if the user explicitly wants a demo/sample update
 5. **`component-readme-agent`** — updates affected component `README.md` files
 6. **`migration-agent`** — only if breaking changes exist
-7. **`changelog-agent`** — updates `CHANGELOG.md`
+7. **`changelog-agent`** — only if the change warrants an entry under the existing `CHANGELOG.md` structure
 
 Only invoke `demo-sample-agent` if the user explicitly requested a demo/sample update.
 If the user declined, skip that handoff and continue with the remaining agents.
 
-If the feature is purely theming or styling, route directly from `tdd-test-writer-agent` to `theming-styles-agent` and skip the general
-implementer.
+If the feature is purely theming or styling, route directly from `tdd-test-writer-agent` to `theming-styles-agent` and skip the general implementer.
 
 ### Step 5 — Verify Completeness
 
 After all agents finish, check:
 
 - Were all affected areas covered?
 - Were public exports updated?
-- Were theming and style changes delegated when SCSS or theme wiring was
-  affected?
-- Was the component README updated?
-- Was `CHANGELOG.md` updated?
+- Were theming and style changes delegated when SCSS or theme wiring was affected?
+- Was the component README updated if needed?
+- Was `CHANGELOG.md` updated if needed?
 - 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?

.github/agents/migration-agent.md

@@ -8,6 +8,7 @@ tools:
   - execute/runTests
   - read/problems
   - read/terminalLastCommand
+  - web
 ---
 
 # Migration Schematic Agent
@@ -28,6 +29,12 @@ You create **`ng update` migration schematics** for breaking changes in Ignite U
 
 ---
 
+## What You Do NOT Do
+
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
+
+---
+
 ## Steps
 
 ### 1. Determine Version and Number
@@ -114,6 +121,7 @@ Before finishing:
 3. Run:
    - `npm run test:schematics`
    - `npm run build:migrations`
+   - `npm run lint:lib`
 4. Confirm the migration updates the old API and leaves unrelated code unchanged.
 
 ### 7. Commit

.github/agents/tdd-test-writer-agent.md

@@ -8,6 +8,7 @@ tools:
   - execute/runTests
   - read/problems
   - read/terminalLastCommand
+  - web
 ---
 
 # TDD Test Writer — RED Phase
@@ -55,6 +56,8 @@ Do not add extra scenarios unless they are explicitly requested, clearly require
    - No execution-order dependency.
 6. **Never write production code.**
    - Only test code in this phase to ensure the test does not give false negatives. The test MUST fail if the functionality is missing, or not behaving as intended.
+7. **Do not modify dependency files.**
+   - Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---
 

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

@@ -8,6 +8,7 @@ tools:
   - execute/runTests
   - read/problems
   - read/terminalLastCommand
+  - web
 ---
 
 # Theming and Styles Agent
@@ -121,6 +122,7 @@ If the task is purely documentation or planning, say clearly that style validati
 - Do not update component `README.md`.
 - Do not create migrations.
 - Do not update `CHANGELOG.md`.
+- Do not modify dependency manifests or lock files (`package.json`, `package-lock.json`, etc.). Ask for approval first if a dependency change is truly required.
 
 ---