Skip to content

Releases: ruvnet/metaharness

v0.1.3 β€” Every scaffold ships .claude-plugin/plugin.json

14 Jun 16:48

Choose a tag to compare

What's new

metaharness@0.1.3 + @ruvnet/agent-harness-generator@0.1.1 β€” every scaffolded harness now ships a Claude Code plugin manifest, so claude -p --plugin-dir <harness> works on any template, not just minimal.

Highlights

  • 20/20 templates ship .claude-plugin/plugin.json β€” minimal plus 19 verticals (devops, legal, research, support, trading, education, sales, gaming, crm, coding, ai, business, advertising, agentics, exotic, health, marketplace, repo-maintainer, ruview, marketing).
  • Per-vertical categories + tags β€” vertical:devops lands categories: [agent-harness, metaharness-scaffold, vertical, devops/incident-response] so the Claude Code marketplace can filter by vertical.
  • 42 new regression tests lock the propagation in β€” static (every manifest references the entry) + e2e (scaffold proof, substitution works, no leftover {{}}).
  • CI guard β€” the iter-131 smoke-all-hosts job in published-smoke.yml now validates this across all 8 hosts (claude-code, codex, pi-dev, hermes, openclaw, rvm, copilot, opencode) from the live registry on every push + daily cron.

Try it

```bash
npx metaharness@latest my-bot --template vertical:devops --host claude-code
claude -p --plugin-dir my-bot "What can you do?"
```

Verified live

```json
$ cat my-bot/.claude-plugin/plugin.json
{
"name": "my-bot",
"categories": ["agent-harness", "metaharness-scaffold", "vertical", "devops/incident-response"],
"tags": ["metaharness", "agent-harness", "vertical:devops", "devops/incident-response"]
}
```

Full details: see commits `ee6d89a` (iter 131 β€” template) and `1af5014` (iter 132 β€” propagation).