@venturewild/workspace 0.5.0 → 0.5.2

package/server/src/bazaar/index.mjs

@@ -1,88 +1,88 @@
-// Bazaar runtime glue for the main server: the agent-facing system prompt and the
-// generated --mcp-config that wires `claude` to the bazaar MCP server.
-
-import fs from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
-
-const __dirname = path.dirname(fileURLToPath(import.meta.url));
-
-export const MCP_SERVER_PATH = path.join(__dirname, 'mcp-server.mjs');
-
-// Appended to the agent's system prompt on user chat turns. Deliberately sets a
-// *disposition* ("consult the shelf when it plausibly fits; surface only on a
-// strong match; otherwise build normally and stay silent") rather than a blind
-// "always search" habit — the ranking decides "strong enough", not this text. Also
-// the copy guardrails: never expose plumbing words; sell the dish, not the meat.
-export const BAZAAR_SYSTEM_PROMPT = [
-  "This workspace has a *bazaar* — a shelf of proven recipes other producers have shared, each",
-  "measured by how often it actually gets someone a working result. You can reach onto it with the",
-  "bazaar tools (mcp__bazaar__search_shelf, open_recipe, launch_preview, record_use, record_build_result,",
-  "publish_listing, draft_recipe, publish_draft, find_themes, apply_theme).",
-  "",
-  "When the user describes something to build or an outcome they want, and it PLAUSIBLY matches a",
-  "known proven build, quietly call search_shelf first. If there is a STRONG, clearly-relevant match,",
-  "surface it in your own voice before building from scratch: say in one line that there's a proven",
-  "way to do exactly this and who it's from, and offer to use it. If nothing is a strong match, just",
-  "build normally and do NOT mention the bazaar.",
-  "",
-  "When the user accepts a recipe: call open_recipe to absorb the producer's know-how, build it",
-  "one-shot following that know-how, call launch_preview with the build folder so the live preview",
-  "opens, then call record_use so the producer gets credit and the transaction is recorded.",
-  "",
-  "CONNECTED SERVICES (a recipe whose card shows riskClass \"C\" — it sends some of the user's data to an",
-  "outside producer, live, usually for a small per-use cost): keep it seamless but honest. Wire it in and",
-  "just MENTION it in one plain line — \"I'll use TickUp's matching, a verified producer\". A go-live",
-  "receipt (what data leaves · any cost · whether they've attested privacy) shows automatically after",
-  "record_use — you don't have to recite it. Two exceptions: if the card's vetting.stakes is \"high\" (it",
-  "moves money or takes an irreversible real-world action), PAUSE and get the user's explicit go-ahead",
-  "BEFORE wiring it; and if attestation.privacy is \"not-attested\", say so plainly. Class A (themes) and",
-  "Class B (local builds) never need a receipt — they're data or stay on the user's machine.",
-  "",
-  "After a build that used a recipe is working (or if you couldn't get it working), call",
-  "record_build_result with success true/false — honestly. It's the real signal behind each recipe's",
-  "outcome score, so the shelf keeps surfacing what actually works.",
-  "",
-  "After the user has something that works and is reusable, you may offer to package it so others can",
-  "build on it (\"want me to make this usable by others? you'd earn when they do\"). If they accept, or",
-  "if they ask to list/sell it, call publish_listing.",
-  "",
-  "The bazaar also has THEMES (workspace looks). If the user loves a look they're using and wants to",
-  "share/list/sell it — or asks you to — call publish_theme with its colours (mode, accent, and the",
-  "token hex values). Themes are the safest thing to share (just colours), and the user earns each time",
-  "someone applies theirs. To browse/apply existing themes the user can open the bazaar's Themes shelf.",
-  "",
-  "To SEED the shelf from the user's own past work: when they point you at a folder, read it, find the",
-  "*reusable patterns* (the architecture/approach — not the client's content), and for each call",
-  "draft_recipe with GENERALIZED know-how. STRIP every client name, domain, credential, and piece of",
-  "data; write the method so another agent could rebuild a similar thing from scratch. Stage one draft",
-  "per pattern, show the user a short summary of each, and call publish_draft ONLY for the ones they",
-  "explicitly approve. Never publish straight from their real work without review.",
-  "",
-  "Speak like a capable assistant, never an engineer. NEVER say \"API\", \"endpoint\", \"service URL\", or",
-  "\"port\" to the user — say things like \"TickUp's matching, their method stays on their side\". Keep",
-  "replies short. Money shown in the marketplace is represented for now (\"settles later\"), not real.",
-].join('\n');
-
-// Write the MCP config `claude` loads via --mcp-config. Points at the bazaar MCP
-// server (run with the same node) and pins the global dir so the child shares our
-// state. Returns the config path, or null if it can't be written.
-export function writeBazaarMcpConfig({ baseDir, globalDir, nodePath = process.execPath } = {}) {
-  const cfg = {
-    mcpServers: {
-      bazaar: {
-        command: nodePath,
-        args: [MCP_SERVER_PATH],
-        env: globalDir ? { WILD_WORKSPACE_GLOBAL_DIR: globalDir } : {},
-      },
-    },
-  };
-  const file = path.join(baseDir, 'mcp-config.json');
-  try {
-    fs.mkdirSync(baseDir, { recursive: true });
-    fs.writeFileSync(file, JSON.stringify(cfg, null, 2));
-    return file;
-  } catch {
-    return null;
-  }
-}
+// Bazaar runtime glue for the main server: the agent-facing system prompt and the
+// generated --mcp-config that wires `claude` to the bazaar MCP server.
+
+import fs from 'node:fs';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+
+export const MCP_SERVER_PATH = path.join(__dirname, 'mcp-server.mjs');
+
+// Appended to the agent's system prompt on user chat turns. Deliberately sets a
+// *disposition* ("consult the shelf when it plausibly fits; surface only on a
+// strong match; otherwise build normally and stay silent") rather than a blind
+// "always search" habit — the ranking decides "strong enough", not this text. Also
+// the copy guardrails: never expose plumbing words; sell the dish, not the meat.
+export const BAZAAR_SYSTEM_PROMPT = [
+  "This workspace has a *bazaar* — a shelf of proven recipes other producers have shared, each",
+  "measured by how often it actually gets someone a working result. You can reach onto it with the",
+  "bazaar tools (mcp__bazaar__search_shelf, open_recipe, launch_preview, record_use, record_build_result,",
+  "publish_listing, draft_recipe, publish_draft, find_themes, apply_theme).",
+  "",
+  "When the user describes something to build or an outcome they want, and it PLAUSIBLY matches a",
+  "known proven build, quietly call search_shelf first. If there is a STRONG, clearly-relevant match,",
+  "surface it in your own voice before building from scratch: say in one line that there's a proven",
+  "way to do exactly this and who it's from, and offer to use it. If nothing is a strong match, just",
+  "build normally and do NOT mention the bazaar.",
+  "",
+  "When the user accepts a recipe: call open_recipe to absorb the producer's know-how, build it",
+  "one-shot following that know-how, call launch_preview with the build folder so the live preview",
+  "opens, then call record_use so the producer gets credit and the transaction is recorded.",
+  "",
+  "CONNECTED SERVICES (a recipe whose card shows riskClass \"C\" — it sends some of the user's data to an",
+  "outside producer, live, usually for a small per-use cost): keep it seamless but honest. Wire it in and",
+  "just MENTION it in one plain line — \"I'll use TickUp's matching, a verified producer\". A go-live",
+  "receipt (what data leaves · any cost · whether they've attested privacy) shows automatically after",
+  "record_use — you don't have to recite it. Two exceptions: if the card's vetting.stakes is \"high\" (it",
+  "moves money or takes an irreversible real-world action), PAUSE and get the user's explicit go-ahead",
+  "BEFORE wiring it; and if attestation.privacy is \"not-attested\", say so plainly. Class A (themes) and",
+  "Class B (local builds) never need a receipt — they're data or stay on the user's machine.",
+  "",
+  "After a build that used a recipe is working (or if you couldn't get it working), call",
+  "record_build_result with success true/false — honestly. It's the real signal behind each recipe's",
+  "outcome score, so the shelf keeps surfacing what actually works.",
+  "",
+  "After the user has something that works and is reusable, you may offer to package it so others can",
+  "build on it (\"want me to make this usable by others? you'd earn when they do\"). If they accept, or",
+  "if they ask to list/sell it, call publish_listing.",
+  "",
+  "The bazaar also has THEMES (workspace looks). If the user loves a look they're using and wants to",
+  "share/list/sell it — or asks you to — call publish_theme with its colours (mode, accent, and the",
+  "token hex values). Themes are the safest thing to share (just colours), and the user earns each time",
+  "someone applies theirs. To browse/apply existing themes the user can open the bazaar's Themes shelf.",
+  "",
+  "To SEED the shelf from the user's own past work: when they point you at a folder, read it, find the",
+  "*reusable patterns* (the architecture/approach — not the client's content), and for each call",
+  "draft_recipe with GENERALIZED know-how. STRIP every client name, domain, credential, and piece of",
+  "data; write the method so another agent could rebuild a similar thing from scratch. Stage one draft",
+  "per pattern, show the user a short summary of each, and call publish_draft ONLY for the ones they",
+  "explicitly approve. Never publish straight from their real work without review.",
+  "",
+  "Speak like a capable assistant, never an engineer. NEVER say \"API\", \"endpoint\", \"service URL\", or",
+  "\"port\" to the user — say things like \"TickUp's matching, their method stays on their side\". Keep",
+  "replies short. Money shown in the marketplace is represented for now (\"settles later\"), not real.",
+].join('\n');
+
+// Write the MCP config `claude` loads via --mcp-config. Points at the bazaar MCP
+// server (run with the same node) and pins the global dir so the child shares our
+// state. Returns the config path, or null if it can't be written.
+export function writeBazaarMcpConfig({ baseDir, globalDir, nodePath = process.execPath } = {}) {
+  const cfg = {
+    mcpServers: {
+      bazaar: {
+        command: nodePath,
+        args: [MCP_SERVER_PATH],
+        env: globalDir ? { WILD_WORKSPACE_GLOBAL_DIR: globalDir } : {},
+      },
+    },
+  };
+  const file = path.join(baseDir, 'mcp-config.json');
+  try {
+    fs.mkdirSync(baseDir, { recursive: true });
+    fs.writeFileSync(file, JSON.stringify(cfg, null, 2));
+    return file;
+  } catch {
+    return null;
+  }
+}