@elitedcs/ghl-mcp 3.75.0 → 3.77.0

package/CHANGELOG.md

@@ -1,5 +1,76 @@
 # Changelog
 
+## 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
+snapshots carry three things it now refuses: step ids that are not proper UUIDs, wait
+units written in the singular ("1 day" instead of "days"), and an older shape of the
+internal notification step. **They run exactly as before. What broke is editing them.**
+Change one step, save, and GoHighLevel rejects the whole workflow, naming steps you never
+touched, so the error looks unrelated to the edit that caused it.
+
+Measured across 23 accounts on 2026-09-01: 486 workflows, 78 affected. On one account,
+20 of 43, while `audit_workflows` reported `status: "ok"`. That was the part that was
+ours: the audit reassured you about the exact thing biting you.
+
+**The audit now tells you.** Four new warning categories, never errors, because the
+workflows genuinely run. Two say *it runs, you cannot edit it* (`legacy_step_id`,
+`legacy_wait_unit`). Two say the reverse, *it saves, it runs, and it silently does
+nothing* (`missing_required_attribute`, `missing_integration`). The advice for each is
+opposite, so they are named separately.
+
+**We no longer write the ids GoHighLevel refuses.** A build session could hand the
+builder a step id like `oc-wait2` and we would save a workflow this same product could
+never update again. A new step now gets a proper id, and every reference to it follows:
+next, previous, siblings, if/else branches and their condition rows, goal references,
+goto targets, and the branch table a multi-path step (Find Opportunity, Facebook
+messenger) keeps inside itself.
+Singular wait units and the old notification shape are corrected silently on every
+write, because neither changes an id.
+
+**A step that is already saved is never re-minted, and this is the important part.** A
+contact part-way through a workflow is bound to the step they are waiting on. Change or
+remove that step and they are dropped mid-sequence, silently, and there is no way to put
+them back where they were. So every workflow write now checks who is parked first and
+refuses to remove or alter a step somebody is standing on, or a step that step depends
+on. There is no force flag. Deleting a whole workflow is the one exception: it refuses,
+tells you how many people are inside, and you re-run naming that number. A workflow
+already carrying bad ids is repaired by choice, step by step, with the parked count in
+hand; the guide in your library, "Workflows that will not save", walks through it and
+leads with the part that costs leads.
+
+**Install slots stopped burning on a machine that cannot write its device file.** A
+relative or unwritable config directory, or a read-only volume, meant the last-resort
+identity was random, and every restart claimed a fresh slot until the licence capped.
+The headline version of this was fixed in 3.69.0; this closes the fallback behind it.
+That identity is now deterministic (user, platform, architecture, deliberately not the
+hostname, which changes on a new network). Stated cost: two machines that share all
+three and also cannot write their device file share one slot, which errs in your favour.
+
+Counts unchanged: 248 tools, 51 modules, free tier 112.
+
 ## 3.75.0 — what you install is only what you bought
 
 Your install shipped a 49KB page for a product that is not on sale, and named that
@@ -26,7 +97,9 @@ with a browser window — pass `open=true` when you actually want it opened.
 
 Counts unchanged: 248 tools, 51 modules, free tier 112.
 
-## Unreleased — your income is not all one shape
+## Also in 3.75.0 — your income is not all one shape
+
+_This entry was headed "Unreleased" in the 3.75.0 package by mistake; the tools it describes shipped in 3.75.0._
 
 Not part of the GHL Command licence; these tools answer with a notice. The commercial
 record could hold exactly one kind of thing: a

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.75.0
+**Version:** 3.77.0
 
 ---