@elitedcs/ghl-mcp 3.83.1 → 3.83.3

package/CHANGELOG.md

@@ -2,6 +2,48 @@
 
 ## Unreleased
 
+## 3.83.3 — an account you marked protected is now actually protected
+
+**Marking a client account protected did not stop fourteen write paths from writing to it.**
+The guard was real and it was in the right place for the public API, but this product also
+writes to GoHighLevel through its own builder connection, and those calls never passed it.
+So a build could create a pipeline and a form on an account you had explicitly told it never
+to touch, and nothing would say so. Pipelines and forms are the first two things a build
+creates. Every one of those paths now goes through the same check, including the template
+installer, which writes a funnel and its pages — the case that matters most, because
+GoHighLevel keeps only the first content save on a page.
+
+**Verify no longer needs your own Anthropic key before it will let you start.** A new client
+with no key met a disabled Run button, while the same screen said most people do not need to
+paste anything there. Both were true at once: runs use whatever you are signed in to Claude
+with and cost nothing extra, and the readiness check demanded a key anyway. The key is
+reported now, not required. If you have one saved, runs bill it; if you do not, they use your
+Claude sign-in.
+
+**The Verify tile stopped promising something it could not do.** It said it submits a test
+lead and deletes it. Since funnels left the build, no plan it creates has anywhere to send
+one, and the report a screen later said so. It now says what it actually does for every plan,
+and still discloses the test lead for the accounts that can take one.
+
+**An older install can no longer roll your skills backwards.** The installer refreshed any
+skill file it had written before, without checking whether the version doing the writing was
+older than the one that wrote it. Running an older copy alongside a newer one quietly reverted
+your skills. It refuses now and tells you it kept the newer ones.
+
+## 3.83.2 — the static design-rule harness and its fixtures leave the package
+
+A development harness and its four HTML fixtures were in the published package in
+3.83.0 and 3.83.1. The harness reads static HTML, so it can only look at the design
+rules that are visible without rendering a page, which is well under half of them.
+Run on a real page it would look at much less than it appears to, so it does not
+belong in an install.
+
+They stay in the repository and keep running in CI. Nothing imported them and nothing
+pointed at them in either earlier release. The design rules themselves
+(`anti-default.json`, `web.json`, `anti-default-contract.mjs`) still ship, unchanged;
+they are input to the design brief. The packaging guard now fails the build if the
+harness or a fixture reappears in the package.
+
 ## 3.83.1 — the Blueprint skill stops asking for the funnel 3.83.0 removed
 
 3.83.0 took funnels out of Blueprint installation, but the installed skill was not

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.83.1
+**Version:** 3.83.3
 
 ---