Remove sunset Haunt plugin

[Darko893]

Summary

• remove the Haunt entry from the community plugin list
• remove the mirrored Haunt plugin bundle

Why

I own Haunt and am sunsetting the service. Its API and MCP endpoint will be withdrawn, so this catalog should not offer an installable plugin that depends on the discontinued service.

The original listing was accepted in #233 and later materialized by the repository's marketplace sync. Root generated catalog metadata is left to the existing sync workflow after merge.

Validation

• python3 scripts/validate-plugin-pr.py --base-ref upstream/main
• node build.js (built 213 plugins from the removal branch)
• git diff --check

The repository's alphabetical check currently also fails on unmodified upstream/main because X (Twitter) Skills is out of order in Tools & Integrations; this PR does not change that unrelated entry.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[kantorcodes]

Summary

• remove the Haunt entry from the community plugin list
• remove the mirrored Haunt plugin bundle

Why

I own Haunt and am sunsetting the service. Its API and MCP endpoint will be withdrawn, so this catalog should not offer an installable plugin that depends on the discontinued service.

The original listing was accepted in #233 and later materialized by the repository's marketplace sync. Root generated catalog metadata is left to the existing sync workflow after merge.

Validation

• python3 scripts/validate-plugin-pr.py --base-ref upstream/main
• node build.js (built 213 plugins from the removal branch)
• git diff --check

The repository's alphabetical check currently also fails on unmodified upstream/main because X (Twitter) Skills is out of order in Tools & Integrations; this PR does not change that unrelated entry.

Sorry to hear that you've had to sunset the service. Thank you for contributing. You're more than welcome to stay in the HOL ecosystem!

[github-actions]

🎉 Hey @Darko893, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.