@elitedcs/ghl-mcp 3.76.0 → 3.77.1

package/CHANGELOG.md

@@ -1,5 +1,63 @@
 # Changelog
 
+## 3.77.1 — the Blueprint can build a client account, and had been saying it could not
+
+If you ran the Blueprint, it planned the account, showed you the two checklists, and then
+printed this at the bottom:
+
+> _v1 stops here. When you approve, the automatic list is ready for one-shot staging (phase 2)._
+
+**That was wrong, and it had been wrong for months.** The Blueprint builds. You approve the
+plan, it dry-runs the automatic list without writing anything, shows you exactly what it
+would create, and on your go it builds: pipelines and stages, custom fields, tags, custom
+values, calendars, forms, funnel structure, templates, and workflows chained and verified,
+each object read back before anything that depends on it is created.
+
+The plan-only sentence was true of the first version. The builder was finished afterwards
+and nobody removed the old wording. It was in four files, and those files ship inside the
+package, so it has been on your machine reading the wrong thing to you the whole time.
+
+**Two of them were worse than a stale sentence.** One instructed the assistant to tell you
+execution was not available yet, so it was not merely present, it was being read out. And
+the description of `apply_build_plan` itself said `execute = live writes (not yet enabled)`
+three hundred lines above the code that performs those writes, which means an assistant
+reading that description could decline to run a build you had just asked for. Meanwhile the
+same skill file gave the correct build instruction further down, so it contradicted itself
+and the half you saw was the false one.
+
+**What has not changed is the gate.** Nothing is built until you say so, the dry run still
+writes nothing, and workflows are still created as drafts unless you ask for them
+published. The old wording carried that promise correctly, which is a large part of why the
+false half went unnoticed. The gate stays; only the claim that building does not exist is
+gone.
+
+A test now fails the build on any of the six ways this was phrased, anywhere in the skill or
+in that tool, so it cannot come back quietly.
+
+Counts unchanged: 248 tools, 51 modules, free tier 112.
+
+## 3.77.0 — the account you aimed at, even when two things run at once
+
+`switch_location` used to change your API key first and your location a moment later.
+A failed switch was already put back exactly as it was, so that part was never the
+problem. The gap in between was: anything running alongside the switch could read the
+**new account's key against the old account's id**. Claude issues tool calls in
+parallel, so that window was real, not theoretical.
+
+The switch now verifies the new account with a throwaway probe and touches nothing until
+that succeeds. Key and location are then committed together with no pause between them,
+so another call in flight sees either the old account or the new one, never half of each.
+
+**`health_check` stopped quoting you a tool count you do not have.** On a licence that
+does not include every module it reported the full registered number, which is not what
+you can run. It now states the tools your licence includes, and says separately how many
+are not included and answer with a notice.
+
+Everything else added in this release sits outside the GHL Command licence and answers
+with a notice, the same as the tools already in that position.
+
+Counts unchanged: 248 tools, 51 modules, free tier 112.
+
 ## 3.76.0 — the workflows you cannot edit, and the audit that said they were fine
 
 GoHighLevel tightened what its workflow builder will save. Workflows built from older

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.76.0
+**Version:** 3.77.1
 
 ---