@elitedcs/ghl-mcp 3.84.1 → 3.84.3

package/CHANGELOG.md

@@ -2,6 +2,73 @@
 
 ## Unreleased
 
+## 3.84.3 — a branded template now looks branded
+
+**The colours a visitor sees are the brand's, on every page of an installed template.** GoHighLevel
+keeps a design's colours at the funnel level as named site colours, and the shared header, footer
+and FAQ sections are served last on every page and win. The repaint changed the page's own data,
+reported "repainted", and the page still rendered in the template's colours. It now repaints the
+funnel's shared sections through GoHighLevel's own save, reads them back, and judges every page
+from what GoHighLevel actually serves, not from what it stored: brand, still the template, mixed,
+nothing to judge, or unreadable. A page that is not the brand's is a problem and blocks any removal
+of the originals. The site-colour names come from the design's own colour registry, so both
+spellings GoHighLevel uses are judged. One side effect is stated in the result: shared sections are
+funnel-wide, so the template's original pages render in the brand's colours too.
+
+**Installing a template keeps the originals unless removal is asked for**, and removal reports only
+the pages it confirmed gone after a re-read. **Branded pages get real addresses** on fresh steps
+instead of blank slugs. **The template's existing form widget is bound to the member's form**, and
+the result says so per page. **Navigation on a branded page points at its replacement pages**, read
+back as a flag, and an unreadable original still stops the install. **A template whose accent
+already matches the brand is not a failed save.** **A checkup pointed at another account refuses**
+instead of reporting no breakage with the wrong key.
+
+## 3.84.2 — done means read back, not echoed
+
+Every tool that reports a thing as done, verified, ready or published was checked against a second,
+independent read of what GoHighLevel actually holds. Thirteen places were claiming an outcome from
+the write's own response, a counter, or the wrong field. Each now derives the claim from a read taken
+after the write, or says plainly what could not be confirmed.
+
+**A build report no longer says "Published N workflows live" for a workflow GoHighLevel kept as a
+draft.** The publish step already read the workflow back and said NOT LIVE when it was not; the
+build threw that answer away and counted it anyway. It is counted now, and a workflow that published
+with every trigger still inactive is named as such rather than called running. The publish tool's
+step and trigger counts come from the read after the write, with the number of active triggers
+beside them.
+
+**The workflow audit no longer says "ok" while dropping four kinds of warning.** Steps GoHighLevel
+will not accept on save, waits in the unit it no longer takes, an alert set to notify a specific
+person with nobody chosen, and steps needing a social account that is not connected were computed
+for every workflow and then left out of the roll-up. They are in it, and in the client-facing report,
+in plain words.
+
+**"Trained." means the pages are trained.** Training a knowledge base settled on a status shared
+with discovery, so it said Trained the moment discovery finished, for a failed run, and for pages
+queued behind an earlier batch. It now settles only when every requested page is in the trained
+bucket, and a crawl GoHighLevel stopped says so instead of "Discovery finished".
+
+**The morning brief no longer calls a morning quiet when your own calendar could not be read.**
+A connected Google Calendar that failed to open produced the same "Nothing needs you this morning"
+as an empty one. The headline now says the calendar could not be read.
+
+**Readiness, calendars, smart lists, keys and pages tell the truth.** A phone-agent readiness check
+no longer says READY on a number pool whose numbers it cannot read. Renaming a calendar carries the
+assigned staff back in the shape GoHighLevel validates and reports the stored team-member count from
+a read after the update. A contact smart list is refused on the opportunity service instead of being
+created where the Contacts screen never shows it. "Removed" for a sub-account key is said only when
+the key really left this computer's file. A page save whose baseline could not be read is reported
+as unverified rather than visible, and a page build is verified on the pointer GoHighLevel serves
+the page from. Switching accounts says the workflow-builder credentials were found, not tested.
+
+**Also in this release:** the eleven small findings deferred from the 3.84.1 reviews. Among them:
+a survey trigger is checked against the account instead of refused as a dead end; three more trigger
+slots are read back; a plan handed back by hand is held to the same confirmed selection as a saved
+one; a half-applied older build is told to keep its undo and plan only the rest; a number an agent
+held only in the old non-routing shape is named when a bind starts routing it; and the brand repaint
+leaves a tint or tone as it was only when that makes the text readable, saying so honestly, and
+repaints every spelling of a colour, not only the six-digit hex.
+
 ## 3.84.1 — the phone agent answers, the repaint tells the truth, and the build waits to be told
 
 **A phone agent you connect now actually answers.** Connecting a number to a voice agent wrote 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.84.1
+**Version:** 3.84.3
 
 ---