Point the installer and docs at btraceio/agent-plugins, where jafar-perf now lives

[jbachorik]

What & why

The jafar-perf plugin moved from btraceio/jafar-perf-box into the btraceio/agent-plugins marketplace (btraceio/agent-plugins#8). install.sh and the docs still named the old repository and the old marketplace, so the installer would set people up with a frozen copy that never gets --attach or any later change.

• install.sh adds btraceio/agent-plugins and installs jafar-perf@btraceio-agent-plugins for Claude Code, and installs git:github.com/btraceio/agent-plugins for pi.
• Re-running it migrates an existing install. Without that, anyone who ran the old installer would end up with the plugin twice (duplicate skills and agents). Once the new copy is in place it uninstalls jafar-perf@btraceio and removes the old marketplace (Claude Code), and removes the old package (pi). It does this only after the new install succeeds, so a failed install never leaves a machine without the plugin, and a failure to remove the old copy warns instead of failing.
• Docs: README.md, jfr-mcp/README.md, doc/agents/Mcp.md, doc/mcp/WhenToUseWhich.md and doc/cli/AskTutorial.md name the new repository and marketplace. doc/agents/Mcp.md also says where the tool-drift check now runs and what it does and does not catch (a renamed or removed tool, not a changed parameter). CHANGELOG.md and doc/plans keep their history.

Merge after btraceio/agent-plugins#10. For pi the new package only brings the jafar MCP server once that package registers it (pi.mcp); until then a pi user would get skills and no server. For pi the package is also the whole agent-plugins package, so it brings the other btraceio skills too (the installer says so).

How verified

Command	Result
scratch HOME set up the old way (marketplace btraceio, jafar-perf@btraceio, the jafar-perf-box pi package), then install.sh --harness claude,pi	Claude Code ends with only jafar-perf@btraceio-agent-plugins and the btraceio-agent-plugins marketplace; pi ends with only git:github.com/btraceio/agent-plugins plus pi-mcp-adapter; the log reports each removal
a second install.sh --harness claude,pi run	changes nothing, no warnings, exit 0
shellcheck -S warning install.sh, bash -n install.sh	clean
git grep jafar-perf-box outside CHANGELOG.md and doc/plans	only the intentional migration references

Coverage notes

There are no automated tests for install.sh; the migration was exercised for real against the Claude Code and pi CLIs with the actual old and new repositories, in a scratch HOME.

Not verified / known limitations

• --daemon, --dev, and a live pi session using the server.
• jfr-mcp/install.sh (which install.sh wraps) still prints jbang jfr-mcp@btraceio --stdio in its client hints rather than --stdio --attach. Both work; I left it out of this change.
• Side effect of my own testing, for the record: jbang resolves its directory from the user's real home rather than $HOME, so the scratch runs re-installed ~/.jbang/bin/jfr-mcp on my machine (same content). Nothing else outside the scratch directory was touched.

Why this is a draft: it should merge after btraceio/agent-plugins#10, and the items above are open. It flips to ready once that merges.

Breaking changes / migration

Anyone who installed through the old route is migrated by re-running the installer; by hand it is /plugin marketplace remove btraceio, /plugin marketplace add btraceio/agent-plugins, /plugin install jafar-perf@btraceio-agent-plugins (the README has the commands). No change for anyone who has not installed the plugin.

Links

Depends on btraceio/agent-plugins#10 (pi MCP registration). Follows #119 and btraceio/agent-plugins#8. Once both merge, btraceio/jafar-perf-box can be archived; its README pointer is prepared.

🤖 Generated with Claude Code

[github-actions]

Combined JUnit Test Report

• Total: 2294
• Passed: 2278
• Failures: 0
• Errors: 0
• Skipped: 16

HTML Test Reports

Run artifacts: https://github.com/btraceio/jafar/actions/runs/37149124323

• JDK 8: HTML report artifact
• JDK 21: HTML report artifact