@elitedcs/ghl-mcp 3.68.0 → 3.70.0

package/CHANGELOG.md

@@ -1,5 +1,120 @@
 # Changelog
 
+## 3.70.0 — a clean validation now means something
+
+A subscriber built an Instagram-comment-to-DM workflow, ran `validate_workflow`, got
+back "0 issues, 0 warnings", published it, and watched the Create/Update Opportunity
+step do nothing: no card in the pipeline, no card on the contact, and the workflow
+carried on to the next step as if it had worked. They were right about why. The step
+had only a pipeline and a stage. GoHighLevel's own documentation lists Opportunity
+Name, Source and Status as mandatory for the combined Create/Update Opportunity step
+to create anything; with only pipeline and stage it moves a card the contact already
+has, and a brand-new lead has none. The
+validator was checking that every id existed. It never asked whether the step could
+do what its name says.
+
+**`validate_workflow` and `audit_workflows` now check what a step can do.** A
+Create/Update Opportunity step with only pipeline + stage and no opportunity in
+context comes back as a warning that says exactly that and names the fix. "In
+context" is worked out from the workflow itself: a create step earlier on the same
+path, a Find Opportunity step whose "Opportunity Found" branch the step sits in, or a
+trigger that fires on an opportunity. A step that carries an Opportunity Name and a
+Status is taken as one that creates and is left alone; a Name with no Status is
+reported as unverified with the thing to check. Before release the check ran against
+every workflow in five of our own accounts (106 workflows) and flagged none; the run
+is recorded in `docs/proofs/2026-08-26-validate-runtime-noop.md`. A path the validator
+cannot trace, or a field this version does not know, is reported as unverified rather
+than passed. `warnings_count` now includes these findings, the report says how many
+steps were checked (`actions_checked`), and `audit_workflows` lists them under
+`shape_warnings` with counts in its summary; `status` still flips only on an error,
+never on a warning. A `task_notification` step spelled with the underscore, which
+saves, validates and is skipped at runtime, is that kind of error now.
+
+**Claude now builds the right node.** GoHighLevel has separated Create Opportunity
+from Update Opportunity and is phasing the combined action out for new workflows. The
+builder knows the newer Create Opportunity node (`internal_create_opportunity`),
+validates it, normalizes it to the shape proven to create a card, and the reference
+material Claude reads before building a workflow now says which node creates a card
+and which one moves it, instead of pointing both jobs at the same node. (#57)
+
+## 3.69.0 — the cockpit hardened, and the plan you approved is the plan that runs
+
+Two items in this release exist because someone tried to break the cockpit
+before a customer did.
+
+**The cockpit refuses writes it did not ask for.** Command OS runs a small web
+server on your own machine. It only ever listened on 127.0.0.1, which keeps the
+internet out. It did not keep out a web page you happened to have open in another
+tab, which can post to localhost without asking and without showing you anything.
+Every route that changes something now checks three things before it acts: the
+request came to a host we serve, from an origin we serve (or from no browser at
+all), with a JSON body that a foreign page cannot send without a preflight we
+refuse. Tested against the real exploit shapes, including a plain HTML form with
+no JavaScript. (#17)
+
+**An approval is a decision, and decisions do not sync inbound.** The shared board
+mirrors a client's progress into their own sub-account so every seat sees the
+same thing. Progress still merges, last write wins. The human approve gate never
+moves because of anything read back from the client's CRM: their staff, a VA, or
+an ordinary "set custom value" workflow step cannot tick your safety checkbox.
+(#29)
+
+**Headless installs stopped burning an install slot on every restart.** An
+env-var install with no credentials file minted a fresh device id each boot and
+locked itself out after three. It now keeps a stable id. Existing installs keep
+their slot. (#33)
+
+**The plan you approved is the plan that runs.** `apply_build_plan` saves the
+approved plan on execute and a re-run reuses it with `useSavedPlan`; a new plan
+needs `replaceSavedPlan` and operator approval. A differently named plan while
+one is saved is refused, with the two valid moves named. Why: a re-run that
+re-authored the plan created a second pipeline beside the first. The handoff
+compares what was built against the saved plan. (#45, #51, #55)
+
+**`verify_funnel` is a write and leaves the free tier.** It submits the funnel's
+form with a test contact and can fire your automations, so it belongs with the
+writes. Free read-only count 112 → 111; the total is still 242 tools across 51
+modules. (#52)
+
+**Command OS, from two timed client builds.**
+- Spec sheets and an inspector for every module: promise, routes, writes,
+  verification, with an optional `note` on a step and `needs` on a verification.
+  The inspector fails a sheet that lies. (#35, #51)
+- A hard tool boundary for headless stage runs: a stage reaches exactly the
+  tools it declares, enforced by a computed deny list. The build stage carries
+  the plan guide in its prompt and runs on a 25-minute / 40-turn budget. (#45)
+- The review reads intake answers by contact id, tag, or form name, no more
+  search-index lag. (#45)
+- An already-open page notices a running stage and a finished stage on its own;
+  no manual reload, and a second seat sees the same. The page never refreshes
+  while you are typing. (#37, #46)
+- The handoff document is a designed web page with a print-to-PDF view: a client
+  copy and an operator copy, complete sentences, your agency's branding, a real
+  footer with page numbers, and unconfirmed items are never written as done.
+  (#36–#44, #47, #48)
+- Intake: multi-choice questions are checkboxes and save as a list; the
+  prefilled form is keyed the way the form reads it (two answers were silently
+  dropped before); values a link cannot carry are listed for the operator to set
+  by hand. "Is your sending email / domain set up?" is now "Is your sending
+  domain set up?" because browser autofill kept filling it with saved addresses;
+  existing installs keep the old field. (#51)
+- The verify stage may list funnels first and says plainly that the funnel check
+  submits one test contact. The intake stage may rename questions to the
+  agency's wording. (#51)
+
+The second-build fixes are unit-tested and were live-probed on the sandbox form.
+The third timed build, the proof that they hold together, has not run yet.
+
+**Smaller.** `get_courses` called a route GHL does not have, and the workflow
+builder is now actually watched by the health check (#34). The upgrade nudge no
+longer points at an older version than the one you run (#16, #19). Dependencies:
+zod 4, TypeScript 7, dotenv 17 and the Actions bumps, each built and tested
+before merging (#21–#27). CI: the automated checks were made trustworthy (#18);
+the GHL drift canary says plainly when it is not configured and carries the
+server's own reason instead of a guess (#30), and no longer logs a cache-save
+failure it cannot avoid (#32); each canary now has its own licence secrets after
+the two collided (#54).
+
 ## 3.68.0 — the checkup
 
 A subscriber asked the question this release is named after: "I'd love for you to

package/README.md

@@ -8,7 +8,7 @@ Works with **both the Claude Desktop App and Claude Code terminal** — your cho
 
 **License required.** Get it at [ghlcommand.com](https://ghlcommand.com?utm_source=npm&utm_medium=readme) — $97/mo, covering UNLIMITED GoHighLevel sub-accounts on up to 3 machines (never billed per account). **30-day time-back guarantee**: save 5+ hours on one client build or your first month back.
 
-**Try it FREE (read-only tier).** Grab an instant free key at [ghlcommand.com/free](https://ghlcommand.com/free?utm_source=npm&utm_medium=readme) — 112 read-only tools on your own GHL account once the two-step install is finished (the same install as the paid tier — upgrading later is just a license swap): the account-wide workflow audit (`audit_workflows` finds the silently broken references GHL never warns you about), account health, and every read across contacts, pipelines, funnels, and workflows. Write tools stay visible and answer with upgrade info. Buying later with the same email upgrades your key in place — 1 machine on free, 3 when you upgrade.
+**Try it FREE (read-only tier).** Grab an instant free key at [ghlcommand.com/free](https://ghlcommand.com/free?utm_source=npm&utm_medium=readme) — 111 read-only tools on your own GHL account once the two-step install is finished (the same install as the paid tier — upgrading later is just a license swap): the account-wide workflow audit (`audit_workflows` finds the silently broken references GHL never warns you about), account health, and every read across contacts, pipelines, funnels, and workflows. Write tools stay visible and answer with upgrade info. Buying later with the same email upgrades your key in place — 1 machine on free, 3 when you upgrade.
 
 **How this differs from HighLevel's official MCP.** HighLevel ships an official Anthropic MCP that reads and writes your CRM (contacts, conversations, calendars, opportunities, payments, social) over the public API — it's free and it's good; use it for that. What it *cannot* do, because the public API doesn't expose it: **build or edit workflows, build funnels/landing pages, or build forms.** That's exactly what GHL Command does — the programmatic Workflow Builder, funnel/page builder, form builder, deep workflow cloning, the silent-failure `audit_workflows`, and Blueprint (build a whole client account from one intake — ships as a guided skill that **installs itself automatically** with this package; nothing to download), all on GHL's internal APIs. **Official MCP = read/write your CRM. GHL Command = build and fix it.** They stack fine together.