docs(agents): agents with small improvements for clarity and accuracy

Author: georgianastasov

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

@@ -59,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/feature-orchestrator-agent.md

@@ -182,7 +182,7 @@ 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.
@@ -198,8 +198,8 @@ After all agents finish, check:
 - 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?
+- 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

@@ -120,6 +120,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