Auth-runtime is infrastructure — cascading updates to all clients x
all skills is a business-system concern, not a CI job. Dependent
skills will pick up latest auth-runtime next time they are deployed
via their install.sh (which always does fresh npm install).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
When auth-runtime is pushed to main, CI notifies the skill-update
webhook to reinstall all dependent skills (1688-product-master,
client-finder, email-content-compose), ensuring they pick up the
latest auth-runtime via their install.sh.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>