From a74d0502b909a37c80cc23cda45d2de56395dccf Mon Sep 17 00:00:00 2001 From: GamerDubz Date: Tue, 13 Oct 2026 15:16:31 +0200 Subject: [PATCH] docs(skill): use the plugin's pinned version for package-runner checks The plugin recovery section left the package-runner version to the skill's generic @latest fallback, so a doctor run could describe a newer release than the server an installed plugin starts. Tell the agent to use the version pinned in the plugin manifest. Co-Authored-By: Claude Opus 5.5 --- .../references/connection-and-recovery.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md index ccc13fbc7..35d0042c7 100644 --- a/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md +++ b/.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md @@ -53,7 +53,10 @@ missing tools. Instead: - Check analysis engines through the connected server's `binary_session.result.tool_availability`. `rea doctor --provider --json` from a shell reports that shell's environment, which can differ from the - environment the client gave the plugin server. + environment the client gave the plugin server. If you still run it through + the package runner, use the version pinned in the plugin manifest's server + entry (`rea-agents@`), not `@latest`, so it matches the server the + plugin starts. Use the setup repair below only when the user wants a setup-owned registration instead of the plugin, and remove or disable the plugin first.