EXIM Hub Registry

Two files. data.js is the list of every EXIM tool and agent page; registry.js is the loader and the ⚡ nav strip. Each tool page and the Command Center include only the loader:

https://cdn.jsdelivr.net/npm/exim-hub-registry@1/registry.js

and it fetches data.js with an hourly cache-buster, so list changes appear within hours everywhere and instantly on Ctrl+F5. They were split on 18 Sep 2026 because jsDelivr caches the loader URL for 7 days — see HOW_TO_APPLY.md for the reasoning.

Add or change a tool

1. Open data.js on GitHub → pencil icon → add one line before /*EXIM_REG_END*/ using the next free n (never reuse a number), and bump EXIM_REGISTRY_VERSION on the line above the list.
2. Commit to main.
3. The "Publish registry to npm" Action runs (about 30 seconds). Check the Actions tab for a green tick.
4. Reload any tool page: the new entry appears. (jsDelivr's cache is purged by the Action; worst case a few minutes.)

Every page also carries an inline copy of the registry as a fallback, so if the CDN is unreachable the hub still works with the last patched list.

How publishing works (no tokens, nothing to renew)

The Action publishes to npm with Trusted Publishing: npm trusts this repository's publish.yml workflow directly (configured on npmjs.com → package exim-hub-registry → Settings → Trusted Publisher). There is no npm token and no GitHub secret to keep alive.

• Package name exim-hub-registry (change it in package.json and in the URL inside the tool pages if you ever rename it).
• Version 1.0.0 was published once by hand (npm login + npm publish on 16 Sep 2026); every later version is published by the Action, which bumps the patch number automatically.
• If the Action ever goes red on "Publish", check that the Trusted Publisher entry on npmjs.com still says user CaptRavinder, repository exim, workflow publish.yml, with "Allow npm publish" ticked.

Check page (loads the registry from the CDN with no fallback): https://claude.ai/artifact/3e1eudbVw7oeF8UMghQyey