@elitedcs/ghl-mcp 3.89.0-beta.5 → 3.89.0-beta.6

package/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## 3.89.0-beta.6: Build only states what the account shows, and calendars open when the client is open
+
+This is a beta, for testers only. Found by running a full Wellness clinic client build in the cockpit.
+
+**Calendars open when the client is open.** The calendars Build creates now take their hours from the intake's Business Hours answer, for example Monday to Thursday 9am to 7pm, Friday 9am to 5pm and Saturday 9am to 1pm, instead of the template's Monday to Friday, 9am to 5pm. When the answer can be read more than one way, the calendars keep the template hours and the Build card says so. On a round-robin calendar, including one with a single person on it, GoHighLevel only offers a time when the person assigned is also available then, so the Build card reminds you to check each person's availability. When a calendar with the same name is already in the account, its hours are left as they are and the Build card says when they differ from the intake's.
+
+**The Build card only states what the account shows.** Build no longer calls someone on your staff list "a placeholder" because of their name: the people the staff step found in the account are treated as real, and a sentence saying otherwise is taken out. Build also no longer says a custom value is empty when it was filled: after building, it reads the account's custom values and lists only the ones that really are still empty, such as the business phone and the review link.
+
+**Brief no longer shows a clean check as a warning.** When the Brief's own check finds nothing wrong, nothing is shown and nothing is counted as an issue.
+
+**Verify's jobs use plain names.** Manual actions name custom values the way a person reads them, with the name GoHighLevel lists beside it, such as "Business phone (business_phone)" and "Owner first name (owner_first_name)", instead of the bare business_phone and owner_first_name. When Verify leaves out something the check said because the account shows otherwise, it now says that in a plain sentence.
+
+**Smaller fixes.** The client card no longer counts a step as done while it is still running. Two joined sentences in the Blueprint Review no longer show a double full stop. On "Build a client account", pressing Enter in the sub-account id or key field registers it, the same as clicking Register. The readiness check no longer lists "No Anthropic key saved" under "Needs you", since nothing is needed. The Wellness clinic question "How should clients prepare for the visit?" now says that its answer takes the place of the day-before reminder's usual "Please come about 10 minutes early" line, and that the booking confirmation already asks clients to come 10 minutes early.
+
 ## 3.89.0-beta.5: Build starts when you approve, Build reads its whole report, the handoff matches what was built, and honest win-back texts
 
 This is a beta, for testers only. Everything below is new since beta.4, found by running a full client build in the cockpit. Jobs you ticked on the Manual tasks list before this update may need ticking once more, because their wording changed.
@@ -18,7 +32,7 @@ This is a beta, for testers only. Everything below is new since beta.4, found by
 
 **The client handoff describes the review request the way it was built, in the client's own time.** The handoff page used to say review requests go out "after each visit" for every client. That is only true when the review request starts from a visit marked as showed. For a Wellness clinic it now says "A review request two weeks into their program, with your link", because the build asks two weeks after a program is sold and never after a trial alone. Where the review request starts when your team marks the work done, the page says so, and where the timing cannot be read it says "A review request, with your link". Dates and times on the handoff and on your agency detail page are now shown in the client's time zone from the intake, to the minute, for example "September 29, 2026 at 10:49 PM CDT", instead of UTC with milliseconds.
 
-**Wellness clinic texts say spots are limited only when the clinic said so.** The first win-back text told past leads they were "hearing about this before anyone else" and that "a small number" of trial spots had opened, even when the intake answered No to "Do trial spots really run out most weeks?". That wording now goes out only on a Yes. A No, or no answer, gets a plain version that still says who is texting, why they are hearing from the clinic, and the offer, with YES and N on their own lines. The second no-show text no longer says times were kept open. The day-before reminder already asks clients to come 10 minutes early, so the intake's prep question now asks for anything besides that, which stops the reminder saying it twice.
+**Wellness clinic texts say spots are limited only when the clinic said so.** The first win-back text told past leads they were "hearing about this before anyone else" and that "a small number" of trial spots had opened, even when the intake answered No to "Do trial spots really run out most weeks?". That wording now goes out only on a Yes. A No, or no answer, gets a plain version that still says who is texting, why they are hearing from the clinic, and the offer, with YES and N on their own lines. The second no-show text no longer says times were kept open. The intake's prep question now says its answer takes the place of the day-before reminder's usual line about arriving early, so include arriving early in the answer if you want the reminder to say it; that stops the reminder saying it twice.
 
 **Checking a workflow now catches what a message says and when it runs, not only broken ids.** In the rehearsal build, checking every workflow found nothing wrong, yet ten would have misfired. validate_workflow, the check that runs before every publish, and the account-wide audit the Verify step runs now also warn when: a message uses a custom value such as the booking link that is missing or still empty, so it would go out blank; a workflow a contact can trigger more than once (a reply, a missed call, an appointment change, a payment) only lets each contact through the first time; a Payment Received workflow has nothing saying which payment it is for, so it runs on every payment; a message sent when someone books says their payment or deposit was received. The account-wide audit also compares the workflows with each other: it warns when a message says "Reply YES" and no workflow answers a YES, and when a message promises "Reply N to opt out" but replying N does not stop the texts. A task step with nobody assigned now gets a warning too, telling you to add a staff member and pick them on that step. None of these block publishing, and when the check cannot read what it needs, it says so instead of guessing.
 

package/README.md

@@ -899,7 +899,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.89.0-beta.5
+**Version:** 3.89.0-beta.6
 
 ---