@arpproject/vibearp-mcp 1.3.0 → 1.3.2

package/README.md

@@ -41,6 +41,9 @@ rocrate-mcp-server -i codex
 Supported IDs are `codex`, `claude`, `opencode`, `kilo`, `roo`, `gemini`, and
 `qwen`. The generated configuration launches the standalone server through the
 shared per-user RockIT socket (`~/.rockit/rocrate-mcp-server.sock`).
+For OpenCode, the installer preserves the config format it finds: native V2
+configs use `mcp.servers`, while V1-shaped configs use the format that V2 still
+supports for compatibility.
 
 The standalone server and RocKIT share the same per-user profile and schema
 storage by default: `~/.rockit`. Set `ROCKIT_ROOT_PATH` to use another shared
@@ -111,6 +114,9 @@ Az elérhető azonosítók: `codex`, `claude`, `opencode`, `kilo`, `roo`, `gemin
 és `qwen`. A létrehozott konfiguráció a standalone szervert a közös,
 felhasználónkénti RockIT socketen (`~/.rockit/rocrate-mcp-server.sock`) keresztül
 indítja.
+OpenCode esetén a telepítő a meglévő konfiguráció formátumát követi: a natív V2
+konfigurációban az `mcp.servers` szerkezetet használja, a V1 alakú beállításokat
+pedig V2 kompatibilitási okból továbbra is elfogadja.
 
 A standalone szerver és a RocKIT alapértelmezés szerint ugyanazt a
 felhasználónkénti profil- és séma-tárolót használja: `~/.rockit`. Másik közös
@@ -150,6 +156,8 @@ engedélyezett hozzáféréssel rendelkezik.
 This package is maintained by SZTAKI, Department of Distributed Systems
 (<https://dsd.sztaki.hu>).
 
+Contact: [rockit@dsd.sztaki.hu](mailto:rockit@dsd.sztaki.hu).
+
 Individual contributors are listed in `package.json`.
 
 ## License

package/lib/server.js

@@ -29,9 +29,9 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
   mod
 ));
 
-// ../../node_modules/mime-types/node_modules/mime-db/db.json
+// ../rockit-common/node_modules/mime-db/db.json
 var require_db = __commonJS({
-  "../../node_modules/mime-types/node_modules/mime-db/db.json"(exports2, module2) {
+  "../rockit-common/node_modules/mime-db/db.json"(exports2, module2) {
     module2.exports = {
       "application/1d-interleaved-parityfec": {
         source: "iana"
@@ -8554,16 +8554,16 @@ var require_db = __commonJS({
   }
 });
 
-// ../../node_modules/mime-types/node_modules/mime-db/index.js
+// ../rockit-common/node_modules/mime-db/index.js
 var require_mime_db = __commonJS({
-  "../../node_modules/mime-types/node_modules/mime-db/index.js"(exports2, module2) {
+  "../rockit-common/node_modules/mime-db/index.js"(exports2, module2) {
     module2.exports = require_db();
   }
 });
 
-// ../../node_modules/mime-types/index.js
+// ../rockit-common/node_modules/mime-types/index.js
 var require_mime_types = __commonJS({
-  "../../node_modules/mime-types/index.js"(exports2) {
+  "../rockit-common/node_modules/mime-types/index.js"(exports2) {
     "use strict";
     var db = require_mime_db();
     var extname2 = require("path").extname;
@@ -8668,6 +8668,7 @@ var require_ro_crate_technical_files = __commonJS({
       exports2.RO_CRATE_METADATA_FILE,
       exports2.RO_CRATE_APPROVAL_FILE_NAME,
       exports2.RO_CRATE_APPROVAL_FILE,
+      "**/.DS_Store",
       "AGENTS.md",
       "CLAUDE.md",
       `${exports2.ROCKIT_IGNORE_DIR}/`
@@ -8675,7 +8676,8 @@ var require_ro_crate_technical_files = __commonJS({
     exports2.DEFAULT_IGNORED_ROOT_FILES = [
       exports2.RO_CRATE_METADATA_FILE,
       exports2.RO_CRATE_PREVIEW_FILE,
-      exports2.RO_CRATE_APPROVAL_FILE_NAME
+      exports2.RO_CRATE_APPROVAL_FILE_NAME,
+      ".DS_Store"
     ];
   }
 });
@@ -8797,6 +8799,9 @@ var require_default_ro_crate = __commonJS({
       if (!normalized) {
         return false;
       }
+      if (normalized.split("/").some((segment) => segment.toLowerCase() === ".ds_store")) {
+        return false;
+      }
       if (isRootEntry) {
         const rootName = normalized.split("/")[0];
         if (rootName.startsWith(".")) {
@@ -36475,6 +36480,9 @@ var require_schema_url_resolution = __commonJS({
     exports2.deriveResourceBaseUrl = deriveResourceBaseUrl;
     function buildSchemaFetchCandidates(input, provider) {
       const value = input.trim();
+      if (!value) {
+        return [];
+      }
       const resourceBaseUrl = deriveResourceBaseUrl(provider, value);
       const providerTemplateCandidates = buildProviderTemplateCandidates(value, provider, resourceBaseUrl);
       if (!/^https?:\/\//.test(value)) {
@@ -44429,7 +44437,7 @@ var AGENT_DEFINITIONS = [
     executables: ["opencode"],
     markerPaths: [".opencode"],
     config: {
-      relativePath: [".config", "opencode", "config.json"],
+      relativePath: [".config", "opencode", "opencode.json"],
       kind: "json"
     }
   },
@@ -44627,18 +44635,21 @@ function toSerializableLaunchConfig(launchConfig) {
 }
 function upsertJsonMcpConfig(content, agentId, launchConfig) {
   const parsed = content.trim() === "" ? {} : JSON.parse(content);
-  const existingMcp = parsed.mcp && typeof parsed.mcp === "object" && !Array.isArray(parsed.mcp) ? parsed.mcp : {};
-  const existingMcpServers = parsed.mcpServers && typeof parsed.mcpServers === "object" && !Array.isArray(parsed.mcpServers) ? parsed.mcpServers : {};
+  const existingMcp = isRecord(parsed.mcp) ? parsed.mcp : {};
+  const existingMcpServers = isRecord(parsed.mcpServers) ? parsed.mcpServers : {};
   if (agentId === "opencode") {
-    parsed.mcp = {
-      ...existingMcp,
-      rocrate: {
-        type: "local",
-        enabled: true,
-        command: [launchConfig.command, ...launchConfig.args],
-        environment: launchConfig.env
-      }
+    const nativeV2 = isOpenCodeV2ServerMap(existingMcp.servers);
+    const existingServers = isRecord(existingMcp.servers) ? existingMcp.servers : {};
+    const server = {
+      type: "local",
+      ...nativeV2 ? { disabled: false } : { enabled: true },
+      command: [launchConfig.command, ...launchConfig.args],
+      environment: launchConfig.env
     };
+    parsed.mcp = nativeV2 ? {
+      ...existingMcp,
+      servers: { ...existingServers, rocrate: server }
+    } : { ...existingMcp, rocrate: server };
   } else {
     parsed.mcpServers = {
       ...existingMcpServers,
@@ -44648,6 +44659,12 @@ function upsertJsonMcpConfig(content, agentId, launchConfig) {
   return `${JSON.stringify(parsed, null, 2)}
 `;
 }
+function isRecord(value) {
+  return typeof value === "object" && value !== null && !Array.isArray(value);
+}
+function isOpenCodeV2ServerMap(value) {
+  return isRecord(value) && typeof value.type !== "string" && typeof value.command !== "string" && !Array.isArray(value.command);
+}
 function buildMcpConfigSection(agent, launchConfig) {
   if (agent.configKind === "toml") {
     return `${buildTomlSnippet(launchConfig)}
@@ -52328,7 +52345,7 @@ var tools = [
   },
   {
     name: "create_default_rocrate",
-    description: "Create an initial ro-crate-metadata.json for a directory that does not yet have one. Scans files, bootstraps .rockit/ignored.txt, and writes metadata atomically.",
+    description: "Create an initial ro-crate-metadata.json for a directory that does not yet have one. For a user-requested local crate creation or directory-file addition, call this as the first metadata operation before context/profile discovery. Scans directory contents while excluding .DS_Store at every depth, bootstraps .rockit/ignored.txt with the **/.DS_Store default ignore rule, and writes metadata atomically. Never use it to overwrite an existing crate unless overwrite=true was explicitly requested.",
     inputSchema: {
       type: "object",
       properties: {
@@ -52752,6 +52769,11 @@ You are editing an RO-Crate as a data steward.
 
 ## Mandatory Startup
 
+The configured RO-Crate MCP server's call names are "RO-Crate MCP" and
+"VibeARP". When a user says either name, use the configured server's tools even
+if the harness displays a different server label (commonly \`rocrate\` or
+\`rocrate-mcp-server\`).
+
 Before advising on or editing RO-Crate metadata, read this top-level workflow doc
 with \`read_agent_workflow_doc\`. Then read the step-specific workflow doc before
 each step.
@@ -52760,13 +52782,21 @@ Use MCP \`rocrate\` tools for metadata edits and validation. Do not edit
 \`ro-crate-metadata.json\` directly unless the user explicitly asks for raw JSON
 editing and accepts the risk.
 
-If the user starts work in a local directory and \`ro-crate-metadata.json\` is not
-present, offer to initialize the directory with \`create_default_rocrate\` before
-other metadata work. Explain that it scans the directory, writes
-\`ro-crate-metadata.json\`, and bootstraps \`.rockit/ignored.txt\`. Do not overwrite
-an existing metadata file unless the user explicitly asks and the tool call uses
+For a user-requested local RO-Crate creation or addition of files from a
+directory, check whether \`ro-crate-metadata.json\` exists. If it is absent, call
+\`create_default_rocrate\` as the first metadata operation after reading this
+workflow doc. Do not merely offer the tool or ask whether to initialize; the
+user's request authorizes this initialization. Then continue with
+\`get_rocrate_context\` and profile discovery before adding curated metadata. For
+read-only requests, do not initialize a missing crate. Do not overwrite an
+existing metadata file unless the user explicitly asks and the tool call uses
 \`overwrite=true\`.
 
+\`create_default_rocrate\` excludes \`.DS_Store\` files at every directory depth and
+adds the \`**/.DS_Store\` ignore rule to \`.rockit/ignored.txt\` by default. When
+adding files to an existing crate, omit \`.DS_Store\` entities by default and
+preserve or add its ignore rule in \`.rockit/ignored.txt\`.
+
 ## Managed Workflow
 
 Before each step, output a brief summary after reading the referenced workflow
@@ -52911,7 +52941,11 @@ These rules are mandatory for RO-Crate metadata quality.
 Always follow this sequence when curating RO-Crate metadata:
 
 0. Use MCP \`rocrate\` tools for metadata edits and validation. Do not edit JSON directly.
-1. Call \`get_rocrate_context\` before any edit.
+1. If the user requested local crate creation or adding files from a directory
+   and \`ro-crate-metadata.json\` is absent, call \`create_default_rocrate\` first.
+   This initializes the requested crate; do not stop to ask whether to do it.
+   Then call \`get_rocrate_context\`. For an existing crate, call
+   \`get_rocrate_context\` before any edit.
    In local mode this must be treated as a profile-resolution step as well as a context read.
    If the crate already contains \`conformsTo\` URLs, do not proceed until the corresponding
    profiles have been downloaded into the local profile store or the resolution failure
@@ -52934,7 +52968,9 @@ Always follow this sequence when curating RO-Crate metadata:
      locally,
    - do not collapse the list to only the profile you recommend,
    - if one profile seems best, mark it as recommended while still listing the other available profiles,
-   - offer a numbered menu in this order: all listed local profiles and remote templates first, then "provide another metadata profile URL", then "continue without a profile",
+   - show the choices in the visible chat message as a clearly formatted Markdown menu, not only in tool output or collapsed details. Use a numbered list with one selectable profile/template per item; do not combine choices into a comma-separated paragraph.
+   - group local profiles and remote CEDAR templates under separate short headings. Include each local profile's name, version, and \`conformsTo\` URL. For each remote leaf template, show its provider/folder path and template name; keep each choice on its own numbered line. Mark a recommendation inline without hiding other choices.
+   - offer a numbered menu in this order: all listed local profiles and remote templates first, then "provide another metadata profile URL", then "continue without a profile". End with a direct prompt such as "Reply with the number of your choice." Keep the numbering continuous across groups.
    - stop and wait for the user's choice before planning fields, searching the web, or writing metadata,
    - for an already-downloaded local profile, call \`update_profile_conforms_to\`
      with its \`conformsTo\` URL after the user chooses it,
@@ -69242,8 +69278,9 @@ async function startServerWithTransports(options) {
     const mcpServer = new McpServer(
       {
         name: "rocrate-mcp-server",
+        title: "RO-Crate MCP / VibeARP",
         version: getBuildInfo().version,
-        description: "RO-Crate metadata tools. The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file."
+        description: "RO-Crate metadata tools, also known as RO-Crate MCP or VibeARP. These names refer to this same server. The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file."
       },
       {
         capabilities: {
@@ -69983,15 +70020,17 @@ function getDashboardUrl() {
 }
 function getMcpServerInstructions() {
   return `RO-CRATE TOOL ROUTING
+This MCP server is known by the call names "RO-Crate MCP" and "VibeARP". When a user mentions either name, use this configured RO-Crate MCP server's tools, regardless of the server label shown by the harness (commonly "rocrate" or "rocrate-mcp-server"). Do not search for or select a different MCP server based on these names.
 The canonical way to open a local RO-Crate dataset in AROMA is open_aroma_for_local_file.
 For a direct request to open, view, show, inspect, or launch a dataset in AROMA\u2014including the exact request "open dataset in AROMA"\u2014call open_aroma_for_local_file immediately as the first tool. Treat "dataset" as the RO-Crate in the current working directory and pass "ro-crate-metadata.json"; otherwise pass the dataset's ro-crate-metadata.json path.
 Before RO-Crate editing/advice, call read_agent_workflow_doc with name "rocrate_workflow.md" and follow it.
 Read the referenced step doc before each workflow step.
 Primary artifact is ro-crate-metadata.json.
-If no ro-crate-metadata.json exists in a local directory, offer create_default_rocrate before other metadata work; never overwrite existing metadata unless explicitly requested with overwrite=true.
+For a user-requested local RO-Crate creation or addition of files from a directory, if the target has no ro-crate-metadata.json, call create_default_rocrate as the first metadata operation after reading the workflow doc. Do not merely offer the tool or ask whether to initialize; the user's request authorizes this initialization. Then continue with get_rocrate_context and profile discovery before adding curated metadata. For read-only requests, do not initialize a missing crate. Never overwrite existing metadata unless the user explicitly requests it and the tool call uses overwrite=true.
+When adding files from a directory, omit .DS_Store entities by default. The default initialization excludes .DS_Store at every depth and writes the recursive .DS_Store ignore rule to .rockit/ignored.txt; preserve or add that ignore rule when maintaining the ignore file.
 Prefer RO-Crate tools over ad-hoc edits.
 The RO-Crate MCP dashboard is available at ${getDashboardUrl()}; open it when the user asks to inspect MCP activity or dashboard telemetry.
-First edit step is get_rocrate_context to discover active profile constraints; do not start with web search.
+After initialization when needed, call get_rocrate_context to discover active profile constraints before curated metadata edits; do not start with web search.
 Use update_profile_conforms_to to change profile URLs on conformsTo; apply_changes must not edit conformsTo.
 apply_changes writes by default; set dryRun=true to preview without persisting.
 Treat profile scope as entity-local (only entities explicitly declaring that profile URL in conformsTo).