@bridge_gpt/mcp-server 0.2.41 → 0.2.42

package/build/schedule-run.js

@@ -23,6 +23,7 @@ import { getAgentLauncher, formatValidAgentLauncherNames } from "./agent-launche
 import { resolveCommandOnPath } from "./agent-launchers/claude.js";
 import { discoverCommandCatalog, resolveSchedulableCommand, validateCommandArgv, } from "./command-catalog.js";
 import { buildTargetCommandLine } from "./scheduled-prompt.js";
+import { MCP_PACKAGE_NAME } from "./mcp-identity.js";
 /**
  * Default deps backed by real subprocesses / process state. Subprocess execution
  * uses `execFile` (list-based, never `shell: true`) and supports
@@ -96,7 +97,7 @@ const SCHEDULE_ID_PATTERN = /^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$/;
 export function getScheduleRunUsage() {
     return [
         "Usage:",
-        "  npx -y @bridge_gpt/mcp-server schedule-run <create|list|cancel|doctor> [flags]",
+        `  npx -y ${MCP_PACKAGE_NAME} schedule-run <create|list|cancel|doctor> [flags]`,
         "",
         "Schedules a local, one-shot run of ANY Bridge slash-command automation (from",
         "the repo's .claude/commands/*.md catalog) at a chosen time using an OS-native",
@@ -659,7 +660,7 @@ export async function resolveScheduleCreateInput(options, runAtIso, deps) {
     if (isTransientNpxEntryPath(cliEntryPath)) {
         warnings.push(`The scheduled run re-enters this CLI at '${cliEntryPath}', which is inside an npx cache ` +
             "directory. npx caches can be pruned before a future schedule fires, which would make the " +
-            "run fail with ENOENT. Install the CLI persistently (e.g. `npm i -g @bridge_gpt/mcp-server`) " +
+            `run fail with ENOENT. Install the CLI persistently (e.g. \`npm i -g ${MCP_PACKAGE_NAME}\`) ` +
             "and schedule with the installed binary so the trigger path stays stable.");
     }
     const paths = getSchedulePaths(id, deps.homeDir, deps.platform);