@elitedcs/ghl-mcp 3.83.0 → 3.83.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +29 -0
- package/README.md +1 -1
- package/dist/index.js +136 -88
- package/package.json +2 -6
- package/skills/blueprint/README.md +5 -3
- package/skills/blueprint/SKILL.md +6 -6
- package/src/command-os/design/rules/check-static.mjs +0 -238
- package/src/command-os/design/rules/fixtures/claude-default.html +0 -55
- package/src/command-os/design/rules/fixtures/external-css.html +0 -7
- package/src/command-os/design/rules/fixtures/generator-run-1.html +0 -31
- package/src/command-os/design/rules/fixtures/house-clean.html +0 -59
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,35 @@
|
|
|
2
2
|
|
|
3
3
|
## Unreleased
|
|
4
4
|
|
|
5
|
+
## 3.83.2 — the static design-rule harness and its fixtures leave the package
|
|
6
|
+
|
|
7
|
+
A development harness and its four HTML fixtures were in the published package in
|
|
8
|
+
3.83.0 and 3.83.1. The harness reads static HTML, so it can only look at the design
|
|
9
|
+
rules that are visible without rendering a page, which is well under half of them.
|
|
10
|
+
Run on a real page it would look at much less than it appears to, so it does not
|
|
11
|
+
belong in an install.
|
|
12
|
+
|
|
13
|
+
They stay in the repository and keep running in CI. Nothing imported them and nothing
|
|
14
|
+
pointed at them in either earlier release. The design rules themselves
|
|
15
|
+
(`anti-default.json`, `web.json`, `anti-default-contract.mjs`) still ship, unchanged;
|
|
16
|
+
they are input to the design brief. The packaging guard now fails the build if the
|
|
17
|
+
harness or a fixture reappears in the package.
|
|
18
|
+
|
|
19
|
+
## 3.83.1 — the Blueprint skill stops asking for the funnel 3.83.0 removed
|
|
20
|
+
|
|
21
|
+
3.83.0 took funnels out of Blueprint installation, but the installed skill was not
|
|
22
|
+
updated with it. `skills/blueprint/SKILL.md` still listed `funnels` among the arrays
|
|
23
|
+
its plan must carry, and still asked "Build this funnel inside GoHighLevel, or as a
|
|
24
|
+
custom site you host?" with GoHighLevel as the stated default. The skill ships inside
|
|
25
|
+
the package, so anyone running Blueprint produced a plan carrying a key their own
|
|
26
|
+
plan format forbids and their own build step refuses.
|
|
27
|
+
|
|
28
|
+
The skill and its README now say plainly that Blueprint builds no funnel, page or
|
|
29
|
+
website, and that pages are a separate job after the account exists, on hosting the
|
|
30
|
+
member owns. A test pins the skill and the plan format together so they cannot
|
|
31
|
+
disagree again.
|
|
32
|
+
|
|
33
|
+
|
|
5
34
|
## 3.83.0 — a build you can check, and no funnel at the end of it
|
|
6
35
|
|
|
7
36
|
**Blueprint no longer builds a funnel, a page, or a website of any kind.** GoHighLevel's own page
|
package/README.md
CHANGED