@golemui/gui-mcp 1.2.0 → 1.2.1

package/CHANGELOG.md

@@ -1,3 +1,34 @@
+## 1.2.1-rc.0 (2026-08-11)
+
+### 🩹 Fixes
+
+- date time intermediate states and commit on blur ([#265](https://github.com/golemui/golemui/pull/265))
+- **gui-mcp:** warn on half-configured boolean validators; document validation traps ([#262](https://github.com/golemui/golemui/pull/262))
+
+### ❤️ Thank You
+
+- Raúl Jiménez @Elecash
+
+## 1.2.0 (2026-08-04)
+
+### 🚀 Features
+
+- **mcp:** add golemui-mcp CLI subcommands for skills ([58b9c21f](https://github.com/golemui/golemui/commit/58b9c21f))
+
+### 🩹 Fixes
+
+- dependencies and type graph ([#241](https://github.com/golemui/golemui/pull/241))
+- **gui-mcp:** resolve @golemui/dx in the dx_check_code type graph ([8afa41db](https://github.com/golemui/golemui/commit/8afa41db))
+- **gui-validators:** make initValidators fail loudly on unknown configs ([#237](https://github.com/golemui/golemui/pull/237))
+- **mcp:** correct lit and vanilla submit event names in DX grounding ([47cf777f](https://github.com/golemui/golemui/commit/47cf777f))
+- **core:** make WithWidget and WidgetLoaders public-only ([#228](https://github.com/golemui/golemui/pull/228))
+
+### ❤️ Thank You
+
+- Mud Scientist @mudscientist
+- Raúl Jiménez @Elecash
+- Raúl Jiménez @Elecash
+
 ## 1.1.1-rc.3 (2026-08-04)
 
 This was a version bump only for gui-mcp to align it with other projects, there were no code changes.

package/cli.js

@@ -5,8 +5,8 @@ import { fileURLToPath } from "node:url";
 import { Server } from "@modelcontextprotocol/sdk/server/index.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { ListToolsRequestSchema, CallToolRequestSchema } from "@modelcontextprotocol/sdk/types.js";
-import { d as checkDxCode, r as resolveDxFramework, f as listDxFactoriesCatalog, b as DX_LIST_FACTORIES_TOOL, g as getDxSpec, a as DX_GET_SPEC_TOOL, D as DX_CHECK_CODE_TOOL } from "./list-dx-factories-BLhvXI07.js";
-import { v as validateFormDefinition, c as JSON_VALIDATE_FORM_DEFINITION_TOOL, g as generateFromJsonSchema, a as JSON_GENERATE_FROM_SCHEMA_TOOL, d as generateFromOpenapi, J as JSON_GENERATE_FROM_OPENAPI_TOOL, f as getWidgetSpec, b as JSON_GET_WIDGET_SPEC_TOOL, e as getConcept, G as GET_CONCEPT_TOOL } from "./get-concept-DRFSt-XX.js";
+import { d as checkDxCode, r as resolveDxFramework, f as listDxFactoriesCatalog, b as DX_LIST_FACTORIES_TOOL, g as getDxSpec, a as DX_GET_SPEC_TOOL, D as DX_CHECK_CODE_TOOL } from "./list-dx-factories-Td5MhXfg.js";
+import { v as validateFormDefinition, c as JSON_VALIDATE_FORM_DEFINITION_TOOL, g as generateFromJsonSchema, a as JSON_GENERATE_FROM_SCHEMA_TOOL, d as generateFromOpenapi, J as JSON_GENERATE_FROM_OPENAPI_TOOL, f as getWidgetSpec, b as JSON_GET_WIDGET_SPEC_TOOL, e as getConcept, G as GET_CONCEPT_TOOL } from "./get-concept-CnyfqgLF.js";
 const USAGE = `Usage: golemui-mcp [command]
 
 Validate GolemUI forms from the command line (no MCP client needed).
@@ -21,7 +21,7 @@ Commands:
 
 Output: a single JSON result on stdout.
   validate-json → { valid, errors, warnings, expressionWarnings, interpolationWarnings }
-  check-dx      → { ok, diagnostics, expressionWarnings }
+  check-dx      → { ok, diagnostics, expressionWarnings, validatorWarnings }
 
 Exit codes: 0 = valid/ok · 1 = invalid (fix the reported problems and re-run) ·
 2 = usage or file error.
@@ -110,7 +110,7 @@ const dxTools = [
   defineTool(DX_GET_SPEC_TOOL, getDxSpec),
   defineTool(DX_CHECK_CODE_TOOL, checkDxCode)
 ];
-const JSON_INSTRUCTIONS = '1. Starting from an existing schema? Use a generator — both return a pre-validated definition, so check the returned `unmapped` list and surface anything left over to the user. For a raw JSON Schema (e.g. an API request body), call `json_generate_from_schema`. For an OpenAPI 3.x spec, call `json_generate_from_openapi`: pass `operation` as "METHOD /path" (e.g. "POST /users") or an exact operationId, plus the spec as a parsed `document` or a `documentUrl` to fetch — it resolves the operation\'s request body, dereferences `$ref`s, and falls back to the operation\'s parameters when there is no request body.\n2. Building or editing by hand? Look up a single widget with `json_get_widget_spec` (its `kind`, `props`, and `validator` shape), and cross-cutting behavior that spans widgets — conditional rendering, per-state prop overrides — with `get_concept`.\n3. ALWAYS finish by calling `json_validate_form_definition`. It checks the definition against the bundled JSON Schemas and returns `{ valid, errors, warnings, expressionWarnings }`. Treat `errors` as blocking: fix them and re-validate until `valid` is true. `warnings` (likely-custom widgets) and `expressionWarnings` (linted reactive expressions) are advisory — surface them, but they do not flip `valid`.\n\n';
+const JSON_INSTRUCTIONS = '1. Starting from an existing schema? Use a generator — both return a pre-validated definition, so check the returned `unmapped` list and surface anything left over to the user. For a raw JSON Schema (e.g. an API request body), call `json_generate_from_schema`. For an OpenAPI 3.x spec, call `json_generate_from_openapi`: pass `operation` as "METHOD /path" (e.g. "POST /users") or an exact operationId, plus the spec as a parsed `document` or a `documentUrl` to fetch — it resolves the operation\'s request body, dereferences `$ref`s, and falls back to the operation\'s parameters when there is no request body.\n2. Building or editing by hand? Look up a single widget with `json_get_widget_spec` (its `kind`, `props`, and `validator` shape), and cross-cutting behavior that spans widgets — conditional rendering, per-state prop overrides, validation rules and error messages — with `get_concept`. Before writing a mandatory checkbox or gating a button on `$formIsInvalid`, call `get_concept({ concept: "validation" })` — both have non-obvious traps.\n3. ALWAYS finish by calling `json_validate_form_definition`. It checks the definition against the bundled JSON Schemas and returns `{ valid, errors, warnings, expressionWarnings }`. Treat `errors` as blocking: fix them and re-validate until `valid` is true. `warnings` (likely-custom widgets) and `expressionWarnings` (linted reactive expressions) are advisory — surface them, but they do not flip `valid`.\n\n';
 const jsonTools = [
   defineTool(JSON_VALIDATE_FORM_DEFINITION_TOOL, validateFormDefinition),
   defineTool(JSON_GENERATE_FROM_SCHEMA_TOOL, generateFromJsonSchema),

package/dx/dx-lint.d.ts

@@ -1,10 +1,11 @@
 import { ExpressionFinding } from '../shared/lint/reactive-expressions';
+import { BooleanValidatorFinding } from '../shared/lint/boolean-validator';
 import { DxDiagnostic } from './typecheck';
 import type * as TS from 'typescript';
 /**
  * Static lints over a `gui.*` DX snippet that the TypeScript compiler cannot catch.
  *
- * The compiler is the truthful gate for *type* errors, but two real defects slip past
+ * The compiler is the truthful gate for *type* errors, but three real defects slip past
  * it because the code is structurally valid TypeScript:
  *
  *  1. **Misplaced `include`/`exclude` (the silent no-op).** Spreading a factory result
@@ -19,9 +20,17 @@ import type * as TS from 'typescript';
  *     `json_validate_form_definition` path uses ({@link checkReactiveExpression}), so the two
  *     surfaces share one set of rules. Reported as non-blocking `expressionWarnings`,
  *     mirroring the JSON path.
+ *
+ *  3. **The mandatory-checkbox trap.** On `gui.inputs.checkbox`/`gui.inputs.booleanInput`,
+ *     a validator with only half of the `required: true` + `const: true` pair type-checks
+ *     but validates something the author almost never means (`required` alone passes
+ *     `false`; `const` alone passes the pristine `undefined`). Shares the JSON path's rule
+ *     engine ({@link checkBooleanValidatorRules}). Reported as non-blocking
+ *     `validatorWarnings` — either half alone is legal, just rarely intended.
  */
 export interface DxLintResult {
     diagnostics: DxDiagnostic[];
     expressionWarnings: ExpressionFinding[];
+    validatorWarnings: BooleanValidatorFinding[];
 }
 export declare function lintDxSnippet(ts: typeof TS, sourceText: string, lineOffset: number): DxLintResult;

package/dx/typecheck.d.ts

@@ -1,4 +1,5 @@
 import { ExpressionFinding } from '../shared/lint/reactive-expressions';
+import { BooleanValidatorFinding } from '../shared/lint/boolean-validator';
 /**
  * In-process TypeScript type-check of a `gui.*` DX snippet against the real `@golemui`
  * type graph. This is the *truthful* gate: the arena spike proved that regex and even
@@ -32,6 +33,12 @@ export interface DxCheckResult {
      * etc.), linted by the same engine as the JSON path. Advisory — they do not flip `ok`.
      */
     expressionWarnings: ExpressionFinding[];
+    /**
+     * Non-blocking boolean-validator findings (a `checkbox`/`booleanInput` validator with only
+     * half of the `required: true` + `const: true` pair — the mandatory-checkbox trap), linted
+     * by the same rule engine as the JSON path. Advisory — they do not flip `ok`.
+     */
+    validatorWarnings: BooleanValidatorFinding[];
 }
 /**
  * Type-check a `gui.*` DX snippet against the real `@golemui` types.