registry(1.76.0): re-pin agent-skills-toolkit to v1.18.0 (e7e3dfc)

[github-actions]

agent-skills-toolkit published v1.18.0 while this registry is pinned to v1.17.1.

The re-pin is prepared and pushed on branch repin/agent-skills-toolkit, with registry metadata.version bumped to 1.76.0. strict: true preserved; no other member entry moves.

Open the pull request: https://github.com/product-on-purpose/agent-plugins/compare/main...repin/agent-skills-toolkit?expand=1

validate-registry.mjs passed against that exact tree inside the job. This workflow opens an issue rather than a pull request on purpose: creating one from Actions needs a repository setting that also lets any workflow APPROVE pull requests, and that would become a self-approval hole the day main gains a review requirement. Pushing a branch and asking for one click leaves review intact.

This automation does the noticing, not the deciding. A member can ship a release this registry deliberately skips.

Re-pin checklist (CONTRIBUTING.md Section 7)

• The pinned sha sits on release tag v1.18.0, and CI at that sha is green
• Versions agree: registry entry == release tag == library.json == plugin.json
• The plugin repository CHANGELOG.md has the v1.18.0 entry
• Registry metadata.version bumped; entry added to this repository CHANGELOG.md
• strict: true preserved; registry validate check green