chore(agents): move dependency change policy to AGENTS.md and trim instructions

Author: georgianastasov

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

@@ -114,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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

@@ -17,7 +17,6 @@ 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.
-- Do not modify `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
 
 ---
 

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

@@ -35,7 +35,6 @@ You do not implement production code, write tests, write migrations, or update `
 - Do not rewrite the whole README if only one area changed.
 - Do not update `CHANGELOG.md`.
 - Do not document private/internal implementation details.
-- Do not modify `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
 
 ---
 

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

@@ -40,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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

@@ -119,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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

@@ -65,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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.
 
 ---
 
@@ -188,17 +188,15 @@ Use agents in this order:
 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?
+- 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?

.github/agents/migration-agent.md

@@ -31,7 +31,7 @@ You create **`ng update` migration schematics** for breaking changes in Ignite U
 
 ## What You Do NOT Do
 
-- Do not modify `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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/tdd-test-writer-agent.md

@@ -56,8 +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. **Never modify dependency files.**
-   - `package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, and similar manifest or lock files are off-limits. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+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

@@ -122,7 +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 `package.json`, `package-lock.json`, or any other dependency manifest or lock file. If a dependency change appears truly necessary, ask for approval first. Never commit `package-lock.json` unless you have been explicitly approved to introduce a new dependency — committing unintended lock file changes can break builds.
+- 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.
 
 ---