@elitedcs/ghl-mcp 3.89.0-beta.9 → 3.89.0

package/guide/guide.html

@@ -4,7 +4,7 @@
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>GHL Command — User Guide</title>
-<!-- guides-hash: f5a3b2744fb86bef -->
+<!-- guides-hash: 6fb2473cea0a7413 -->
 <style>
 /* Deliberately light in every environment, including a dark-mode OS. This is a
    reference document people read at length, print, and save to PDF, and a page
@@ -584,7 +584,7 @@ Before you build: confirm the [Consult] calendar exists and scope the trigger to
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
-<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The reminder arrived three weeks early.&quot;</td><td>Fixed delays were used instead of appointment-relative waits. Rebuild the waits to count back from the appointment.</td></tr><tr><td>&quot;It reminded people about the wrong appointment type.&quot;</td><td>The trigger was not scoped to a calendar.</td></tr><tr><td>&quot;They got a reminder after they cancelled.&quot;</td><td>Add an exit so cancellations drop out of the sequence.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The reminder arrived three weeks early.&quot;</td><td>Fixed delays were used instead of appointment-relative waits. Rebuild the waits to count back from the appointment.</td></tr><tr><td>&quot;It reminded people about the wrong appointment type.&quot;</td><td>The trigger was not scoped to a calendar.</td></tr><tr><td>&quot;They got a reminder after they canceled.&quot;</td><td>Add an exit so cancellations drop out of the sequence.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -803,14 +803,14 @@ Before you build: confirm both tags exist in my account, and show me the two pat
 <ul>
 <li>You are <b>switched to the client's sub-account</b> (<code>switch_location</code>).</li>
 <li>The <b>workflow builder is set up</b> for it. The template library needs that same one-time Firebase sign-in; an API key alone is refused. If you have ever built a workflow in this account you already have it.</li>
-<li>Optionally, a <b>look to brand it with</b>. Six are built in, and you can adjust one to a client's colours and faces before you use it. Without one you can still install a template. It just arrives in the designer's own colours.</li>
+<li>Optionally, a <b>look to brand it with</b>. Six are built in, and you can adjust one to a client's colors and faces before you use it. Without one you can still install a template. It just arrives in the designer's own colors.</li>
 </ul>
 </div>
 <div class="gsec"><h2>Do this</h2>
 <p class="gpara"><b>1. Find one.</b></p>
 <div class="prompt"><q>Find me a GoHighLevel template for a chiropractic clinic, in warm gold and cream.</q><button class="copy" type="button">Copy</button></div>
 <p class="gpara">You get a shortlist with install counts, a thumbnail you can open, and the reason each one is on the list. Install count is other agencies voting with their accounts. It is the only quality signal GoHighLevel publishes, and it is not the same as good.</p>
-<p class="gpara">To see what the library is organised by first: *Show me the GoHighLevel template categories.*</p>
+<p class="gpara">To see what the library is organized by first: *Show me the GoHighLevel template categories.*</p>
 <p class="gpara"><b>2. Install it, in the client's brand.</b></p>
 <div class="prompt"><q>Install template 68158120b6bd0de1fe287f59 into this account, branded with the calm-clinic look.</q><button class="copy" type="button">Copy</button></div>
 <p class="gpara">You confirm before it writes. It installs one funnel, reads the account back, and reports the funnel that actually appeared with the exact call that removes it.</p>
@@ -824,7 +824,7 @@ Before you build: confirm both tags exist in my account, and show me the two pat
 </div>
 <div class="gsec"><h2>Honest limits</h2>
 <ul>
-<li><b>&quot;In your client's colours&quot;, not &quot;a bespoke design&quot;.</b> The re-paint claims six roles: the accent, the ground, the body colour, a second hue, the tint big section bands use, and the two faces. Some large background areas keep the template's own colour, because painting every remaining shade would wreck the photography.</li>
+<li><b>&quot;In your client's colors&quot;, not &quot;a bespoke design&quot;.</b> The re-paint claims six roles: the accent, the ground, the body color, a second hue, the tint big section bands use, and the two faces. Some large background areas keep the template's own color, because painting every remaining shade would wreck the photography.</li>
 <li><b>It cannot invent proof.</b> The template arrives with the designer's placeholder testimonials and stock numbers. Those are yours to replace with things that are true.</li>
 <li><b>A branded page is not a persuasive page.</b> The design check measures craft, not whether anyone would buy. If you want that judged too, ask for the copy to be graded.</li>
 </ul>
@@ -1071,7 +1071,7 @@ Do not change any contact, and do not delete any list that is already there.</p>
   <a class="back" href="#top">&#8592; All guides</a>
   <div class="gsec"><h2>What you'll get</h2>
 <ul>
-<li>A page rebuilt for your client from a page you point at, with their name, colours, contact details, and copy.</li>
+<li>A page rebuilt for your client from a page you point at, with their name, colors, contact details, and copy.</li>
 <li>A rights question at the start that decides how the rebuild is done, and an honest answer either way.</li>
 <li>A review report at the end listing everything that still belongs to whoever owned the original.</li>
 </ul>
@@ -1094,13 +1094,13 @@ When you are done, give me the review list of everything still belonging to the
 <ol class="steps">
 <li>Claude asks what rights you have to the page, and records your answer.</li>
 <li>With rights, it makes a faithful rebuild. Without them, it takes the design system, meaning the layout logic, spacing, and type scale, and builds a fresh page on it instead of copying the original.</li>
-<li>It swaps in your client's brand: name, contact details, colours. It does NOT rewrite the page's words.</li>
+<li>It swaps in your client's brand: name, contact details, colors. It does NOT rewrite the page's words.</li>
 <li>It hands you a review list: everything it found that still belongs to the original owner and everything it could not be sure about.</li>
 </ol>
 </div>
 <div class="gsec"><h2>Good to know</h2>
 <ul>
-<li><b>Changing the colours is riskier than it sounds.</b> A palette is a set of relationships, not a list of hex codes. Swap a dark background for a light one and text that was white for the dark background is now white on light, and invisible. Nothing checks this for you. After any colour change, look at the page before you show anyone.</li>
+<li><b>Changing the colors is riskier than it sounds.</b> A palette is a set of relationships, not a list of hex codes. Swap a dark background for a light one and text that was white for the dark background is now white on light, and invisible. Nothing checks this for you. After any color change, look at the page before you show anyone.</li>
 <li><b>A clone copies. It does not rewrite.</b> When it finishes, the layout and brand are your client's and every word is still the original's, so the page still reads as the other business. Rewriting is a second ask, on purpose: a clone that paraphrases as it copies is the one that comes back &quot;not even close&quot;.</li>
 <li>Read the review list. It exists because some things cannot be caught by find and replace: a brand name split across styled text, a logo inside an image, branding baked into a booking widget, another business's testimonials.</li>
 <li>Lead and payment destinations are the dangerous ones. A cloned page that still posts leads to the original owner is worse than no page.</li>
@@ -1109,7 +1109,7 @@ When you are done, give me the review list of everything still belonging to the
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
-<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The clone still has the other company's name in one spot.&quot;</td><td>That is what the review list catches, usually a name split across styled text. Fix the items it names before you show the client.</td></tr><tr><td>&quot;A booking button still goes to the original business.&quot;</td><td>Say which account and which calendar the buttons should point at, in the ask. Then check every button on the live page.</td></tr><tr><td>&quot;The new colours made half the page unreadable.&quot;</td><td>Text colours were not swapped alongside the backgrounds they sit on. Caught live: a navy-to-cream background left white headings invisible. Change colours only if you will check the result by eye, or leave them alone and clone exactly.</td></tr><tr><td>&quot;The header still showed the old brand after a clean replace.&quot;</td><td>A two-tone brand mark is split across markup, so no find-and-replace can reach it. It is caught and listed for a hand edit. The proving run had exactly two.</td></tr><tr><td>&quot;The logo still says the other company.&quot;</td><td>The brand is inside the image file. Pixels cannot be substituted; the review list names the files so you can swap the artwork.</td></tr><tr><td>&quot;It refused to make an exact copy.&quot;</td><td>You said you have no rights to the page. That answer routes you to a rebuild on the design system instead, which is the version you can actually ship.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;The clone still has the other company's name in one spot.&quot;</td><td>That is what the review list catches, usually a name split across styled text. Fix the items it names before you show the client.</td></tr><tr><td>&quot;A booking button still goes to the original business.&quot;</td><td>Say which account and which calendar the buttons should point at, in the ask. Then check every button on the live page.</td></tr><tr><td>&quot;The new colors made half the page unreadable.&quot;</td><td>Text colors were not swapped alongside the backgrounds they sit on. Caught live: a navy-to-cream background left white headings invisible. Change colors only if you will check the result by eye, or leave them alone and clone exactly.</td></tr><tr><td>&quot;The header still showed the old brand after a clean replace.&quot;</td><td>A two-tone brand mark is split across markup, so no find-and-replace can reach it. It is caught and listed for a hand edit. The proving run had exactly two.</td></tr><tr><td>&quot;The logo still says the other company.&quot;</td><td>The brand is inside the image file. Pixels cannot be substituted; the review list names the files so you can swap the artwork.</td></tr><tr><td>&quot;It refused to make an exact copy.&quot;</td><td>You said you have no rights to the page. That answer routes you to a rebuild on the design system instead, which is the version you can actually ship.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1223,7 +1223,7 @@ Before you build: look up the real calendar, the real workflows you are removing
 <ol class="steps">
 <li>Sign in to your Stripe Dashboard and choose the account you want to read.</li>
 <li>Open Developers, then API keys. If your dashboard shows Workbench, open its API keys page.</li>
-<li>Under Restricted keys, choose Create restricted key and give it a name you recognise.</li>
+<li>Under Restricted keys, choose Create restricted key and give it a name you recognize.</li>
 <li>Set Customers, Invoices, Subscriptions, Charges and Products to Read. Leave other permissions at None, then create the key.</li>
 <li>Copy the key into the password field on the Stripe card on the Connections screen, add an account label if useful, and choose Connect. Use a live-mode key for real income.</li>
 </ol>
@@ -1363,7 +1363,7 @@ Before you build: look up the real calendar, the real workflows you are removing
 <ol class="steps">
 <li>Open marketplace.zoom.us and sign in with your Zoom account.</li>
 <li>Choose Develop at the top right, then Build App.</li>
-<li>Pick Server-to-Server OAuth App and choose Create. Give it a name you will recognise, such as Morning brief reader.</li>
+<li>Pick Server-to-Server OAuth App and choose Create. Give it a name you will recognize, such as Morning brief reader.</li>
 <li>On App Credentials, copy the Account ID, the Client ID and the Client Secret. Keep them somewhere private until you paste them here.</li>
 <li>Fill in the Information page with your name and email; Zoom asks for them before it lets the app run.</li>
 <li>Open Scopes and choose Add Scopes. Add the user read scope, which Zoom may list as View a user (user:read:user:admin), and the cloud recording read scope, which Zoom may list as View all user recordings (cloud&#95;recording:read:list&#95;user&#95;recordings:admin). Add nothing else.</li>
@@ -1612,7 +1612,7 @@ Then tell me which ones I should chase, in order.</p></div>
 </ul>
 </div>
 <div class="gsec"><h2>Where people go wrong</h2>
-<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It sent to the wrong Dana.&quot;</td><td>Two contacts, same first name. Give the email address and Claude confirms the match before sending.</td></tr><tr><td>&quot;The template list is missing one.&quot;</td><td>It exists in a different sub-account. Confirm which account you are in first.</td></tr><tr><td>&quot;The client says the document is blank.&quot;</td><td>The template has no signature or content blocks filled in. That is fixed in the GHL template editor, then resent.</td></tr><tr><td>&quot;I only wanted to see what it would look like, and the client got it.&quot;</td><td>That was the old behaviour and it changed on 31 August. Creating from a template now leaves the contract as a draft, and sending is a separate instruction.</td></tr></table></div>
+<div style="overflow-x:auto"><table class="wrongtbl"><tr><th>What happened</th><th>The fix</th></tr><tr><td>&quot;It sent to the wrong Dana.&quot;</td><td>Two contacts, same first name. Give the email address and Claude confirms the match before sending.</td></tr><tr><td>&quot;The template list is missing one.&quot;</td><td>It exists in a different sub-account. Confirm which account you are in first.</td></tr><tr><td>&quot;The client says the document is blank.&quot;</td><td>The template has no signature or content blocks filled in. That is fixed in the GHL template editor, then resent.</td></tr><tr><td>&quot;I only wanted to see what it would look like, and the client got it.&quot;</td><td>That was the old behavior and it changed on 31 August. Creating from a template now leaves the contract as a draft, and sending is a separate instruction.</td></tr></table></div>
 </div>
 <div class="gsec"><h2>Related guides</h2>
 <ul>
@@ -1690,7 +1690,7 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
   <a class="back" href="#top">&#8592; All guides</a>
   <div class="gsec"><h2>Before you start: what you need</h2>
 <ul>
-<li><b>A GoHighLevel plan that includes API access.</b> That is GoHighLevel Unlimited ($297 a month) or Agency Pro ($497). The $97 Starter plan has no API, so nothing can connect to it, GHL Command included. Check under Settings, then Billing, in GoHighLevel before you install. On Unlimited ($297), GoHighLevel does not let GHL Command create sub-accounts or add staff users. Both are Agency Pro only, so on $297 you do those two jobs in GoHighLevel yourself.</li>
+<li><b>A GoHighLevel plan that includes API access.</b> That is GoHighLevel Unlimited ($297 a month) or Agency Pro ($497). The $97 Starter plan has no API, so nothing can connect to it, GHL Command included. Check under Settings, then Billing, in GoHighLevel before you install. On Unlimited ($297), GoHighLevel does not let GHL Command create sub-accounts or add staff users. Both are Agency Pro only, so on $297 you do both jobs in GoHighLevel yourself.</li>
 <li><b>Claude on this computer.</b> GHL Command runs inside the Claude Desktop app or inside Claude Code in a terminal. It cannot run in a claude.ai tab in your browser. Not sure which you have? The Members Hub page Which Claude do I use? settles it in two minutes, and with it every later question about restarts.</li>
 <li><b>A Private Integration token</b> from the sub-account you want to work in, and that sub-account's location ID. Claude asks for both during setup, not the installer. Inside the sub-account, create the token under Settings, then Private Integrations (under Other settings), then Create New Integration. The location ID is under Settings, then Business Profile, at the top of the General Information card, with a copy button. It is also the part of the sub-account's web address after /location/.</li>
 </ul>
@@ -1742,7 +1742,7 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
   <div class="gsec"><h2>What you'll get</h2>
 <ul>
 <li>An invoice raised against a real contact, itemised and priced, without touching the billing screen.</li>
-<li>A promo code you can hand out, and a product catalogue Claude can price from.</li>
+<li>A promo code you can hand out, and a product catalog Claude can price from.</li>
 <li>A straight answer to &quot;what came in this month&quot;, read from the account rather than a dashboard.</li>
 </ul>
 </div>
@@ -1770,7 +1770,7 @@ Do not send it. I will send it myself once I have read it.</p></div>
 <li>Invoices are created as drafts and stay that way until sent. A draft costs nothing and can be deleted; a sent invoice has landed in someone's inbox and cannot be unsent.</li>
 <li>Say &quot;do not send&quot; in the ask when you are experimenting. Claude honours it, and it removes the only irreversible step in the whole flow.</li>
 <li>New invoices are real and payable by default. If you want one that cannot be paid, for a demo or a screenshot, ask for a test-mode invoice explicitly.</li>
-<li>Products are the catalogue, invoices are the bill. Creating a product does not create a price on its own, so ask for the price in the same breath if you want one attached.</li>
+<li>Products are the catalog, invoices are the bill. Creating a product does not create a price on its own, so ask for the price in the same breath if you want one attached.</li>
 <li>Coupons need a code, a type (percentage or fixed) and an amount. Without all three GHL rejects it.</li>
 <li>&quot;What was I paid&quot; is a different question from &quot;what did I invoice&quot;. Ask for transactions or orders for money that actually moved, and for invoices for money you asked for.</li>
 <li>Invoicing needs the full license. The Free plan can read invoices and payments but not raise them.</li>
@@ -2931,7 +2931,7 @@ Tell me plainly what happens on my side when somebody clicks it, and what I woul
   <div class="gsec"><h2>What you'll get</h2>
 <ul>
 <li>New leads for the week, total contacts, open and won and lost deals, and how many conversations are live in the account.</li>
-<li>Every figure labelled with the window it covers, so a week number is never mistaken for an all-time number.</li>
+<li>Every figure labeled with the window it covers, so a week number is never mistaken for an all-time number.</li>
 <li>Anything that cannot be read is reported as unavailable, not as a zero. A zero you cannot trust is worse than no number.</li>
 </ul>
 </div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.89.0-beta.9",
+  "version": "3.89.0",
   "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",
@@ -17,6 +17,7 @@
     "src/command-os/design/rules/anti-default-contract.mjs",
     "dist/index.js",
     "dist/capture-helper.js",
+    "dist/shopper-child.js",
     "templates/action-schemas.json",
     "templates/clinic-medspa.json",
     "templates/trigger-schemas.json",
@@ -31,7 +32,7 @@
     "!skills/blueprint/presets/clinic-launch-a2p.md"
   ],
   "scripts": {
-    "build": "node src/command-os/assessment/build-app.mjs && node scripts/gen-report-css.mjs && esbuild src/index.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/index.js --packages=external && esbuild src/capture-helper.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/capture-helper.js --packages=external",
+    "build": "node src/command-os/assessment/build-app.mjs && node scripts/gen-report-css.mjs && esbuild src/index.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/index.js --packages=external && esbuild src/capture-helper.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/capture-helper.js --packages=external && esbuild src/shopper-child.ts --bundle --platform=node --target=node20 --format=cjs --outfile=dist/shopper-child.js --packages=external",
     "typecheck": "tsc --noEmit",
     "setup": "node setup-wizard.mjs",
     "catalogue": "node scripts/export-command-os-catalogue.mjs",

package/skills/blueprint/references/external-funnel.md

@@ -260,11 +260,13 @@ verify_funnel({
   expectCustom: [ { fieldId: "<id>", value: "<sent value>", label: "<label>" }, ... ], // from formFields
   consentFieldId: "<consent field id, if the workflow messages>",
   // testPhone: "<a test-safe number YOU control>",  // only if asserting SMS-path; real SMS may bill
-  cleanup: true                                       // removes the blueprint-qa sentinel after
+  // verify_funnel never deletes anything: the result lists every contact that now carries the test address (id, name,
+  // phone, email, created). Check each before deleting any with delete_contact: a phone-matching form can put the
+  // test address on an existing customer.
 })
 ```
 
-This proves, from the backend (not the UI): (1) the contact is **actually created** (with submit→appear
+This proves, from the backend (not the UI): (1) a contact carrying the test address **actually appears** (with submit→appear
 latency); (2) each `expectCustom` value **persisted** (field-value fidelity — catches a wrong field id);
 (3) the **trigger tag landed**; (4) SMS/A2P pre-check; (5) **workflow is not DRAFT** (a draft never fires
 on real leads); (6) the **outreach actually fired** (an outbound message was logged — proves enroll +