@bridge_gpt/mcp-server 0.1.16 → 0.1.17

package/README.md

@@ -47,7 +47,8 @@ npx -y @bridge_gpt/mcp-server start-tickets [flags] KEY [KEY ...]
 | `--terminal terminal\|iterm` | auto-detect via `$TERM_PROGRAM` | Override the macOS terminal app (honored on macOS only) |
 | `--dry-run` | off | Print intended actions; create no worktrees, open no tabs (any OS) |
 | `--branch KEY=BRANCH` | `feature/<KEY>` | Use a custom branch for that ticket (repeatable) |
-| `--no-refresh-main` | off | Skip `git fetch origin main` + fast-forward of local `main` |
+| `--base-branch <BRANCH>` | `main` | Cut new worktrees from `<BRANCH>` and refresh `origin/<BRANCH>` instead of `main` |
+| `--no-refresh-main` | off (the configured base branch is refreshed) | Skip refresh of the configured base branch (default `main`). Historical flag name preserved for backward compatibility — despite the name, it now skips refresh of whatever `--base-branch` resolves to. |
 | `--max-parallel N` | `3` | Max worktrees created concurrently |
 | `-h`, `--help` | — | Show usage |
 
@@ -244,6 +245,40 @@ Commands are slash commands you invoke from your AI assistant's chat. Most orche
 
 > Commands are designed for Claude Code. Other editors may support slash commands differently — check your editor's documentation for how to invoke prompt files.
 
+## Smoke testing
+
+The package ships a canonical, **opt-in** in-host smoke-test runbook at
+`smoke-test/SMOKE-TEST.md`. An AI agent running inside your host (Claude Code,
+Cursor, Codex, Windsurf, or VS Code/Copilot) executes it to verify that the MCP
+server actually works end-to-end *inside that host* — it calls the real tools and
+records a PASS/FAIL verdict for each one in a markdown report.
+
+- `smoke-test/SMOKE-TEST.md` **ships with the npm package** and is the
+  **canonical** source of truth for the smoke test.
+- The smoke test **adds no MCP tool** and **does not change the registered
+  tool surface** (the server still registers its existing 51 tools).
+- It is **opt-in**: default `--init` **does not scaffold `/smoke-test-mcp`**, so
+  consumer command palettes are not polluted.
+
+### Running it
+
+You have two options:
+
+1. **Copy the opt-in command manually.** Copy the packaged command stub into your
+   host's command directory, then invoke `/smoke-test-mcp`:
+
+   ```bash
+   # Claude Code
+   cp node_modules/@bridge_gpt/mcp-server/smoke-test/smoke-test-mcp.md .claude/commands/smoke-test-mcp.md
+   # Cursor
+   cp node_modules/@bridge_gpt/mcp-server/smoke-test/smoke-test-mcp.md .cursor/commands/smoke-test-mcp.md
+   ```
+
+2. **Open the runbook directly.** Alternatively, open
+   `smoke-test/SMOKE-TEST.md` and ask the host agent to execute it.
+
+Reports are written to `<BAPI_DOCS_DIR>/smoke-test/REPORT-<host>-<timestamp>.md`.
+
 ## Available Tools
 
 MCP tools are the low-level primitives Bridge exposes to your AI assistant. You don't call them directly — ask your AI assistant to perform the task you need, or compose them into a custom pipeline.

package/build/agent-launchers/claude.js

@@ -0,0 +1,85 @@
+/**
+ * The v1 `claude` agent launcher (BAPI-327).
+ *
+ * Resolves the `claude` binary against the *baked schedule-time PATH* (not the
+ * ambient process default), builds the locked
+ * `/full-automation --scheduled-at <T> --idea-file <abs> [--auto-approve]`
+ * prompt, and emits `{ exe, args: ["-p", prompt] }`. Claude Code has no
+ * working-directory flag, so the cwd is always set by the scheduler unit — this
+ * adapter must never add a cwd argument to the invocation.
+ */
+import { pathApiForPlatform } from "../scheduler-backends/types.js";
+import { posixShellQuote, windowsCmdQuote } from "../scheduler-backends/escaping.js";
+/**
+ * Resolve a bare command to an absolute path using the platform PATH-probe,
+ * forcing the baked PATH so the schedule resolves the same binary the user had
+ * at creation time. On Windows both `PATH` and `Path` are overridden (Node and
+ * `where.exe` disagree on casing). Returns the first non-empty *absolute* path
+ * from stdout, or `null` when the probe fails or yields only relative paths.
+ */
+export async function resolveCommandOnPath(command, envPath, deps) {
+    const pathApi = pathApiForPlatform(deps.platform);
+    const probe = deps.platform === "win32" ? "where.exe" : "which";
+    const env = { ...deps.env, PATH: envPath };
+    if (deps.platform === "win32") {
+        // Windows env var lookup is case-insensitive but Node preserves the literal
+        // key; override both casings so neither the probe nor child sees a stale one.
+        env.Path = envPath;
+    }
+    const result = await deps.runCommand(probe, [command], { env });
+    if (result.exitCode !== 0)
+        return null;
+    const candidate = result.stdout
+        .split(/\r?\n/)
+        .map((line) => line.trim())
+        .find((line) => line.length > 0);
+    if (!candidate)
+        return null;
+    if (!pathApi.isAbsolute(candidate))
+        return null;
+    return pathApi.normalize(candidate);
+}
+/**
+ * Quote the idea-file path so it survives as a single `/full-automation`
+ * argument even when it contains spaces or markup-significant characters
+ * (`&`, `<`, `>`, …) that would otherwise be split or mangled when the slash
+ * command is parsed. Only an embedded double quote needs escaping; the same
+ * absolute path is additionally baked into `BRIDGE_GPT_IDEA_FILE` by every
+ * backend as a robust environment fallback.
+ */
+export function quoteIdeaFileForPrompt(ideaFile) {
+    return `"${ideaFile.replace(/"/g, '\\"')}"`;
+}
+/**
+ * Build the exact full-automation prompt. `--auto-approve` is appended by
+ * default; it is omitted only when the caller selected `--no-auto-approve`.
+ */
+export function buildClaudePrompt(input) {
+    const base = `/full-automation --scheduled-at ${input.runAtIso} ` +
+        `--idea-file ${quoteIdeaFileForPrompt(input.ideaFile)}`;
+    return input.autoApprove ? `${base} --auto-approve` : base;
+}
+const CLAUDE_CAPABILITY = {
+    name: "claude",
+    command: "claude",
+    supportsCwdFlag: false,
+    promptFlag: "-p",
+};
+/** Create the v1 Claude agent launcher. */
+export function createClaudeLauncher() {
+    return {
+        capability: CLAUDE_CAPABILITY,
+        resolveBinary(envPath, deps) {
+            return resolveCommandOnPath("claude", envPath, deps);
+        },
+        buildInvocation(exe, input) {
+            const prompt = buildClaudePrompt(input);
+            // No working-directory flag: cwd is owned by the scheduler unit.
+            return { exe, args: [CLAUDE_CAPABILITY.promptFlag, prompt], prompt };
+        },
+        formatInvocationLine(invocation, platform) {
+            const quote = platform === "win32" ? windowsCmdQuote : posixShellQuote;
+            return [invocation.exe, ...invocation.args].map((part) => quote(part)).join(" ");
+        },
+    };
+}

package/build/agent-launchers/index.js

@@ -0,0 +1,17 @@
+/**
+ * Agent-launcher registry (BAPI-327). v1 ships only `claude`; the lookup returns
+ * `null` for every other name so the CLI can reject unsupported agents with a
+ * clear message rather than silently falling back.
+ */
+import { createClaudeLauncher } from "./claude.js";
+export { createClaudeLauncher } from "./claude.js";
+const CLAUDE_LAUNCHER = createClaudeLauncher();
+/** Return the launcher for a name, or `null` when unsupported in v1. */
+export function getAgentLauncher(name) {
+    return name === "claude" ? CLAUDE_LAUNCHER : null;
+}
+/** Comma-separated list of valid agent-launcher names (just `claude` in v1). */
+export function formatValidAgentLauncherNames() {
+    const names = ["claude"];
+    return names.join(", ");
+}

package/build/agent-launchers/types.js

@@ -0,0 +1 @@
+export {};