@elitedcs/ghl-mcp 3.84.9 → 3.84.10

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 3.84.10 — confirming a call's numbers no longer files the call twice
+
+When you answered "confirm all" after bringing in a client call, the call was filed a second time: a duplicate call file marked "(2)" and the same call added to "Client understanding" twice. Now the confirmation adds one dated "Confirmed by you" section to the call you already filed, and to Client understanding, listing the numbers that saved. If the first call was never filed, the whole call is filed then, so nothing is lost. The reply says the numbers saved only when they actually did.
+
 ## 3.84.9 — build steps you can read
 
 Each client's build now shows a progress bar, the next step across the full width with one clear button, and one readable row per step, instead of seven narrow columns. Nothing about how building works changed: the same steps, checks and typed confirmations. Step descriptions now say what each step really does. Verify checks the links between workflows, pipelines and fields and tests the form, and reports anything it cannot check.

package/README.md

@@ -897,7 +897,7 @@ Built by **[Elite DCs, LLC](https://elitedcs.com)** — a digital marketing and
 
 **Tech stack:** TypeScript, Node.js, esbuild, MCP SDK, Zod, GHL API v2, Firebase Auth
 
-**Version:** 3.84.9
+**Version:** 3.84.10
 
 ---
 

package/dist/index.js

@@ -29058,7 +29058,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@elitedcs/ghl-mcp",
-      version: "3.84.9",
+      version: "3.84.10",
       mcpName: "io.github.drjerryrelth/ghl-command",
       description: "GoHighLevel MCP Server for Claude. 250 tools \u2014 full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
       main: "dist/index.js",
@@ -39495,7 +39495,8 @@ __export(client_calls_exports, {
   gateAnalysis: () => gateAnalysis,
   processClientCall: () => processClientCall,
   safeName: () => safeName,
-  writeClientFileLocally: () => writeClientFileLocally
+  writeClientFileLocally: () => writeClientFileLocally,
+  writeConfirmationLocally: () => writeConfirmationLocally
 });
 function gateAnalysis(transcript, analysis) {
   const rejected = [];
@@ -39722,6 +39723,37 @@ function writeClientFileLocally(baseDir, file2) {
     return { written: false, error: `could not write the client file: ${e?.message ?? String(e)}` };
   }
 }
+function writeConfirmationLocally(baseDir, file2) {
+  const c = file2.confirmation;
+  if (!c) return writeClientFileLocally(baseDir, file2);
+  try {
+    if (!path32.isAbsolute(baseDir)) return { written: false, error: `the client files folder must be a full path, not "${baseDir}".` };
+    const base = path32.resolve(baseDir);
+    const callPath = path32.resolve(base, ...file2.call.folderParts, c.callName);
+    const understandingPath = path32.resolve(base, ...file2.understanding.folderParts, file2.understanding.name);
+    if (!inside(base, callPath) || !inside(base, understandingPath)) return { written: false, error: "the client folder name would land outside the client files folder." };
+    let st;
+    try {
+      st = fs34.lstatSync(callPath);
+    } catch {
+    }
+    if (!st) return writeClientFileLocally(baseDir, { ...file2, confirmation: void 0 });
+    if (st.isSymbolicLink() || !st.isFile() || st.nlink > 1) return { written: false, error: `${callPath} is a link, not a plain file, so nothing was added to it.` };
+    if (!inside(fs34.realpathSync(base), fs34.realpathSync(callPath))) return { written: false, error: "the call file resolves outside the client files folder, so nothing was added." };
+    fs34.appendFileSync(callPath, c.appendToCall, { encoding: "utf8", mode: 384 });
+    let u;
+    try {
+      u = fs34.lstatSync(understandingPath);
+    } catch {
+    }
+    if (u && (u.isSymbolicLink() || !u.isFile() || u.nlink > 1)) return { written: false, error: `${understandingPath} is a link, not a plain file, so it was not appended to. The call file was updated: ${callPath}` };
+    if (u) fs34.appendFileSync(understandingPath, c.appendToUnderstanding, { encoding: "utf8", mode: 384 });
+    else fs34.writeFileSync(understandingPath, file2.understanding.headerIfNew + c.appendToUnderstanding, { encoding: "utf8", flag: "wx", mode: 384 });
+    return { written: true, callFile: callPath, transcriptFile: "", understandingFile: understandingPath };
+  } catch (e) {
+    return { written: false, error: `could not add the confirmation to the client file: ${e?.message ?? String(e)}` };
+  }
+}
 function contactNames(raw) {
   const c = raw?.contact ?? {};
   const s = (k) => typeof c[k] === "string" && c[k].trim() ? c[k].trim() : "";
@@ -39916,8 +39948,32 @@ To confirm:
 ${confirmList(gated.held).map((l) => `- ${l}`).join("\n")}
 ${CONFIRM_INSTRUCTION}`;
   const clientName = save?.businessName ?? save?.contactName ?? clean(input.businessName);
+  const confirmPass = (input.confirmed?.length ?? 0) > 0;
   const clientFile = clientName ? buildClientFile({ clientName, date, source: input.source, gated, analysis, transcript: input.transcript, saveLine, confirmedByOwner: save?.confirmedByOwner }) : null;
-  const localCopy = clientFile && deps.clientFilesDir ? writeClientFileLocally(deps.clientFilesDir, clientFile) : null;
+  if (clientFile && confirmPass) {
+    const today2 = now.toISOString().slice(0, 10);
+    const confirmedIds = new Set(save?.confirmedByOwner ?? []);
+    const lines = save?.status === "SAVED" ? gated.accepted.filter((a) => confirmedIds.has(a.questionId)).map((a) => `${ASK.get(a.questionId) ?? a.questionId} **${a.value}**. They said: ${q2(a.quote)}`) : [];
+    const body = lines.length ? `Saved on the GoHighLevel contact ${save?.contactId}:
+${bullet(lines)}` : `Not saved on the contact: ${save?.reason ?? save?.status ?? "no contact was named"}.`;
+    clientFile.confirmation = {
+      callName: clientFile.call.name,
+      appendToCall: `
+
+## Confirmed by you, ${today2}
+
+${body}
+`,
+      appendToUnderstanding: `
+
+### ${today2}: numbers from the ${date} call confirmed by you
+
+${body}
+`
+    };
+    clientFile.howToWrite = `This call confirms answers from a call you have probably already filed. First SEARCH the client's Calls folder for "${clientFile.call.name}". If it is there, append clientFile.confirmation.appendToCall to it and clientFile.confirmation.appendToUnderstanding to Client understanding, and write nothing else. If it is NOT there, the call was never filed: write the whole call as follows. ${clientFile.howToWrite}`;
+  }
+  const localCopy = clientFile && deps.clientFilesDir ? clientFile.confirmation ? writeConfirmationLocally(deps.clientFilesDir, clientFile) : writeClientFileLocally(deps.clientFilesDir, clientFile) : null;
   const { applied, ...legacyRest } = legacyOf(gated);
   return {
     // Never hand back unchecked values beside a failed save (review D-3).
@@ -39929,7 +39985,7 @@ ${CONFIRM_INSTRUCTION}`;
     source: noteSource ? { ...noteSource, dateFromRecording: fromRecording } : null,
     analysis: analysis ? { ...analysis.kept, leftOutForQuote: analysis.rejected, forTheOwnerOnly: true } : null,
     clientFile,
-    clientFileNote: clientFile ? null : "No client name was known (no contact, no businessName), so no client file entry was made.",
+    clientFileNote: !clientFile ? "No client name was known (no contact, no businessName), so no client file entry was made." : clientFile.confirmation ? `This call confirms answers from an earlier call. Add only the "Confirmed by you" sections to that call's file and to Client understanding; do not file the call again.${save?.status === "SAVED" ? " The confirmed answers are on the contact." : " The confirmed answers did NOT save on the contact; see the reply."}` : null,
     localCopy
   };
 }
@@ -40245,7 +40301,7 @@ function registerAssessmentTools(server2, client) {
   safeTool(
     server2,
     "read_assessment_transcript",
-    `Bring a recorded client call (Plaud or Zoom through your own connection, or a transcript file the owner exports from any other recorder and attaches) into the client's assessment, their needs analysis and their client file. The flow: 1) get the transcript yourself, with your own Plaud or Zoom connection or from the attached file; 2) propose assessment answers, each with the client's words copied VERBATIM from the transcript as the quote; for a text question the value is the client's own words taken from that quote, and for a number it is the number they said, written in digits (Plaud writes "a hundred percent"; send "100%"); 3) write the needs analysis, every need, unnamed problem and recommended solution tied to a verbatim quote of at least three words; 4) call this with the client's contactId and the source; 5) write the returned clientFile to the owner's Google Drive with your Drive connection, following clientFile.howToWrite; 6) show the owner the reply as given, including the "To confirm" list. EVERY NUMBER waits for the owner's OK and never saves on its own, because no word check can tell a figure that answers the question from one said in passing. Text answers in the client's own words save straight away. When the owner answers the list ("confirm all", or "confirm all except ..."), call again with the same transcript, proposed and contactId, and confirmed holding exactly the approved items (questionId and value from toConfirm); for an item marked replacesSaved, also set replace: true on that proposed answer. Never put an item in confirmed that the owner has not approved in this conversation. Drive allows two folders with the same name, so SEARCH for each folder in the path (and for the client's folder above all) before creating it, and never create a second tree. To append to "Client understanding": read it, add the new dated section at the end, write it back, then read it again and confirm every earlier section is still there. Answers and analysis points whose quote is not in the transcript are thrown out. With a contactId the saved answers are read back: the reply starts SAVED, NOT SAVED, NOT CONFIRMED or NOTHING TO SAVE, and only SAVED means they are on the contact. The needs analysis is advice for the owner and is never sent to the client. Without a contactId nothing is saved.`,
+    `Bring a recorded client call (Plaud or Zoom through your own connection, or a transcript file the owner exports from any other recorder and attaches) into the client's assessment, their needs analysis and their client file. The flow: 1) get the transcript yourself, with your own Plaud or Zoom connection or from the attached file; 2) propose assessment answers, each with the client's words copied VERBATIM from the transcript as the quote; for a text question the value is the client's own words taken from that quote, and for a number it is the number they said, written in digits (Plaud writes "a hundred percent"; send "100%"); 3) write the needs analysis, every need, unnamed problem and recommended solution tied to a verbatim quote of at least three words; 4) call this with the client's contactId and the source; 5) write the returned clientFile to the owner's Google Drive with your Drive connection, following clientFile.howToWrite (on the confirmation call below, follow clientFile.howToWrite exactly: it adds a "Confirmed by you" section to the call already filed instead of filing it again); 6) show the owner the reply as given, including the "To confirm" list. EVERY NUMBER waits for the owner's OK and never saves on its own, because no word check can tell a figure that answers the question from one said in passing. Text answers in the client's own words save straight away. When the owner answers the list ("confirm all", or "confirm all except ..."), call again with the same transcript, proposed and contactId, and confirmed holding exactly the approved items (questionId and value from toConfirm); for an item marked replacesSaved, also set replace: true on that proposed answer. Never put an item in confirmed that the owner has not approved in this conversation. Drive allows two folders with the same name, so SEARCH for each folder in the path (and for the client's folder above all) before creating it, and never create a second tree. To append to "Client understanding": read it, add the new dated section at the end, write it back, then read it again and confirm every earlier section is still there. Answers and analysis points whose quote is not in the transcript are thrown out. With a contactId the saved answers are read back: the reply starts SAVED, NOT SAVED, NOT CONFIRMED or NOTHING TO SAVE, and only SAVED means they are on the contact. The needs analysis is advice for the owner and is never sent to the client. Without a contactId nothing is saved.`,
     {
       transcript: import_zod61.z.string().min(20).describe("The recording, as text. Paste the whole thing."),
       proposed: import_zod61.z.array(import_zod61.z.object({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.84.9",
+  "version": "3.84.10",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 250 tools — full CRM, automation, marketing control, account-wide workflow audit, live funnel-capture verification, and the only programmatic GHL workflow builder, now multi-tenant across client accounts.",
   "main": "dist/index.js",