@elitedcs/ghl-mcp 3.97.1 → 3.97.2

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: f3d3ceee4e791b6f -->
+<!-- guides-hash: f56d1be300fe9f07 -->
 <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
@@ -1714,7 +1714,8 @@ Show me the first ten rows in the chat so I can sanity check them before you wri
 <ul>
 <li><b>Done means:</b> you asked &quot;Which account am I in?&quot; and Claude answered with the right account name. That is the whole test.</li>
 <li>Step 2 is part of the install, not an extra. Until it is done, Claude will keep reminding you the install is one step from finished. Nothing will pretend to be complete when it is not.</li>
-<li>If anything says &quot;not working&quot; afterward, say &quot;run a health check&quot;: it tests every connection and tells you in plain English what, if anything, needs attention.</li>
+<li>If anything says &quot;not working&quot; afterward, say &quot;run a health check&quot;: it tests every connection and tells you in plain English what, if anything, needs attention. Its first check, Host, names the assistant GHL Command is running in, and its License plan line says which plan this session runs on.</li>
+<li>You can have GHL Command open in more than one assistant window on the same computer. Each window saves your registered accounts, connections and cockpit board under a shared lock and adds its change to what the other saved. Saves keep unrelated changes made by another window. Editing the same details in both windows at once can still replace the earlier change. If the other window still holds the save after 5 seconds, the waiting save does not happen; if your plan includes the cockpit, some of a cockpit run's own saves try up to three times over a few seconds instead. When a tool, a run or the cockpit says something was not saved, follow what it tells you to do, such as running it again or checking the account and refreshing. A few background notes are skipped without a message. A sub-account that was created is still reported as created, even if its key or its card could not be saved yet. Do not create it again; register it with its key. If neither its key nor its card was saved and your plan includes the cockpit, its New Client page may show it as &quot;Created:&quot; followed by its name when no client is selected, and while it shows, the cockpit and chat refuse to create that name again. To clear it, register it with its key or, if you already removed it in GoHighLevel, press &quot;Dismiss: I removed this sub-account&quot;. Dismiss does not delete the sub-account or check that you removed it. If nothing shows, check GoHighLevel before you create it again.</li>
 <li>Stuck at any point? Email support@ghlcommand.com and a human answers.</li>
 </ul>
 </div>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elitedcs/ghl-mcp",
-  "version": "3.97.1",
+  "version": "3.97.2",
   "mcpName": "io.github.drjerryrelth/ghl-command",
   "description": "GoHighLevel MCP Server for Claude. 250 tools for CRM, automation and marketing, an account-wide workflow audit, live funnel-capture verification and a workflow builder, across client accounts.",
   "main": "dist/index.js",