fix(plugin): pin the plugin server launch to the release version

Both manifests started `rea-agents@latest`, so a server start could run a
different package version from the installed plugin and bundled skill, and
would execute whatever npm's latest tag pointed at. Pin the launch to the
manifest version and have Release Please rewrite it with each release.

Release Please reserializes JSON extra-files with JSON.stringify, which the
formatter would reject in every release PR. Store both manifests in that
form, exempt them from the formatter, and assert the form in conformance.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
GamerDubz
2026-10-12 09:50:02 +02:00
co-authored by Claude Opus 5.5
parent 2f134aaa7e
commit 102661ca6f
6 changed files with 110 additions and 58 deletions
+13 -3
View File
@@ -15,11 +15,17 @@
"decompiler",
"mcp-server"
],
"skills": ["./.agents/skills/reverse-engineer-anything"],
"skills": [
"./.agents/skills/reverse-engineer-anything"
],
"mcpServers": {
"rea": {
"command": "npx",
"args": ["-y", "rea-agents@latest", "mcp"],
"args": [
"-y",
"rea-agents@6.4.0",
"mcp"
],
"startup_timeout_sec": 30
}
},
@@ -29,7 +35,11 @@
"longDescription": "Use REA to explain shipped behavior from native binaries, managed assemblies, Electron and JavaScript bundles, packages, firmware, and browser targets, with evidence that separates observations from inferences.",
"developerName": "morluto",
"category": "Developer Tools",
"capabilities": ["Interactive", "Read", "Write"],
"capabilities": [
"Interactive",
"Read",
"Write"
],
"websiteURL": "https://rea.tools/",
"defaultPrompt": [
"Use REA to explain how this binary implements a feature.",