chore(skills): regenerate omni-settings after the pool egress-observation route

The generated skill catalog went stale when #13581 added GET
/api/settings/proxies/pool/egress-observation: check:agent-skills-sync
(the Merge integrity job) fails on the pure release tip and on every PR
cut from it. Regenerated with scripts/skills/generate-agent-skills.mjs
--apply; the only change is the new route's generated section.

Refs #12732

changelog.d/maintenance/12732-agent-skills-sync-omni-settings.md

@@ -0,0 +1 @@
+- **chore(skills):** regenerate the `omni-settings` agent skill after the pool egress-observation route landed (#13581), clearing the `check:agent-skills-sync` base-red (#12732)

skills/omni-settings/SKILL.md

@@ -1150,6 +1150,17 @@ curl -X DELETE https://localhost:20128/api/settings/proxies/pool \
   -H "Authorization: Bearer $OMNIROUTE_TOKEN"
 ```
 
+### GET /api/settings/proxies/pool/egress-observation
+
+GET settings › proxies › pool › egress observation
+
+Read-only observation of how many distinct egress IPs actually served the members of a proxy pool over the last 24 h, read from the proxy log (numbers only, never used for routing). Opt-in through the PROXY_POOL_EGRESS_OBSERVATION feature flag: while it is off, or when the read fails, the body is JSON null. Results are cached for 30 seconds per normalized scope (key is read as account, global as the stored global pool).
+
+```bash
+curl https://localhost:20128/api/settings/proxies/pool/egress-observation \
+  -H "Authorization: Bearer $OMNIROUTE_TOKEN"
+```
+
 ### POST /api/settings/proxy/cloudflare-deploy
 
 POST settings › proxy › cloudflare deploy