fix(plugins): correct llm-box source type to unblock plugin validation

[anistark]

Summary

plugins/llm-box.json declares "source": "git", which is not one of the source types the validator accepts. .github/workflows/validate-plugin.yml allows github, url, git-subdir and npm, so the schema step fails with:

plugins/llm-box.json: Invalid or missing source type `git`. Must be one of: github, url, git-subdir, npm

The catch is that the schema step loops over every file in plugins/, not just the ones a PR touches:

for f in plugins/*.json; do

So this single entry fails validation on every PR that touches plugins/, no matter what that PR changes. It is currently blocking #37, and it is the only one of 305 entries with an invalid source type (the rest are 226 git-subdir, 74 github, 3 url, 2 npm).

It landed in #34, where this same check was already in place and already failing. There is no required status check on the repo, so it merged anyway.

The fix

Switch the entry to a github source, matching the 74 other GitHub-hosted entries and the shape documented in CONTRIBUTING.md.

The repo has also been renamed from alib8b8/llm-box to alib8b8/aflare since the entry was added. GitHub's redirect still resolves the old name, but pointing at the canonical one avoids a break if the old name is ever reclaimed.

Verified locally

• Replayed the full schema validation over all 305 entries: 0 errors.
• ./scripts/build-marketplace.sh succeeds (305 plugins, 96 authors).
• marketplace.json deliberately not committed, since the build-marketplace workflow regenerates it on push to main.

Follow-ups, not in this PR

• The entry pins "version": "0.3.0", but upstream is on v0.11.0 (released 2026-08-26). Per CONTRIBUTING.md, /plugin update compares the installed version against the registry, so anyone who installed llm-box is stuck and gets "already at the latest version". The llm-box name and description are also stale branding after the rename to aflare.
• The validation loop is worth scoping to changed files, or the check made required, so one broken entry cannot merge and then block every PR behind it.

Type of change

• Add a plugin
• Update a plugin
• Remove a plugin
• Marketplace / registry change (schema, validation, plugins/ tooling)
• Site / docs change (landing page, README, content)
• CI / workflow / repo tooling
• Bug fix
• Other

Checklist

• I have read and understood the contributing guidelines
• Changes are scoped and focused on a single concern
• Tested locally where applicable
• Updated relevant docs (README, site content, etc.) if behavior changed
• Did not hand-edit marketplace.json (it is generated)

🤖 Generated with Claude Code

[github-actions]

Plugin Validation ✅

Check	Status
Duplicate check	✅ success
Schema validation	✅ success
Marketplace build	✅ success

Great plugin! Add this badge to your plugin's README for better discovery:

Markdown:

[![AgentHub](https://agenthub.nullorder.org/badge.svg)](https://agenthub.nullorder.org)

HTML:

<a href="https://agenthub.nullorder.org">
  <img src="https://agenthub.nullorder.org/badge.svg" alt="AgentHub" />
</a>