@golemui/gui-mcp 1.5.0 → 1.5.1

package/CHANGELOG.md

@@ -1,3 +1,31 @@
+## 1.5.1-rc.0 (2026-09-23)
+
+### 🩹 Fixes
+
+- **gui-mcp:** declare @golemui/dx as a dependency ([5d43a4f0](https://github.com/golemui/golemui/commit/5d43a4f0))
+- **gui-components:** show a restored mid-upload file as failed without emitting a change at mount ([f3597275](https://github.com/golemui/golemui/commit/f3597275))
+
+### ❤️ Thank You
+
+- Raúl Jiménez @Elecash
+
+## 1.5.0 (2026-09-14)
+
+### 🚀 Features
+
+- **gui-components:** surface upload errors via validation injection and icon retry button ([#357](https://github.com/golemui/golemui/pull/357))
+- **lit:** shim querySelector and export safeDefine for SSR ([#351](https://github.com/golemui/golemui/pull/351))
+- **vue:** nuxt support ([#335](https://github.com/golemui/golemui/pull/335))
+- **gui-components:** add file upload widgets ([#332](https://github.com/golemui/golemui/pull/332))
+
+### 🩹 Fixes
+
+- **gui-components:** add interrupted message and reconcile file upload queue ([#359](https://github.com/golemui/golemui/pull/359))
+
+### ❤️ Thank You
+
+- Raúl Jiménez @Elecash
+
 ## 1.5.0-rc.2 (2026-09-14)
 
 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-hQNWmAmY.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-CsLx7Y5b.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-D3u4qsn1.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-MFKfeD4D.js";
 const USAGE = `Usage: golemui-mcp [command]
 
 Validate GolemUI forms from the command line (no MCP client needed).

package/{get-concept-CsLx7Y5b.js → get-concept-MFKfeD4D.js}

@@ -2888,13 +2888,15 @@ const NOTES = {
   fileUpload: [
     "Single-file upload rendered as a one-line input: the box is the drop target and holds the upload button; while the file uploads the box itself becomes the progress bar; once done it shows the file name with a remove button.",
     'REQUIRES a host transport in the form init config: `dependencies: { uploadService: { upload(file, { id, path, onProgress, signal }) => Promise<unknown>, remove?(item) => Promise<void> } }` (a sibling of `dependencies.markdown`). Keep the object reference stable — a new config identity re-initializes the form. Without it the widget renders disabled with an inline error. Call `get_concept({ concept: "host-services" })`.',
-    'The value is a plain envelope, never the `File`: `{ id, name, size, type, status: "uploading" | "uploaded" | "error", error?, data? }` where `data` is exactly what `upload` resolved with. Preload from the server with `status: "uploaded"`. Removing awaits `uploadService.remove(item)` (when provided) before clearing. An item restored with `status: "uploading"` cannot resume — the `File` only existed in the session that picked it — so the widget commits it back as `"error"` with `props.interruptedMessage` (default: `{name} was not uploaded. Remove it and pick the file again.`).',
+    'The value is a plain envelope, never the `File`: `{ id, name, size, type, status: "uploading" | "uploaded" | "error", error?, data? }` where `data` is exactly what `upload` resolved with. Preload from the server with `status: "uploaded"`. Removing awaits `uploadService.remove(item)` (when provided) before clearing. An item restored with `status: "uploading"` cannot resume — the `File` only existed in the session that picked it — so the widget shows it as failed with `props.interruptedMessage` (default: `{name} was not uploaded. Remove it and pick the file again.`) but leaves the stored value untouched: no `change` fires until the user removes it.',
+    'Server file cleanup is the HOST\'s job. `uploadService.remove` runs only on an explicit user removal and when this widget replaces its file with a new pick (not awaited, failure only logged). A deleted repeater row, a field pruned by a state, `setData`, a config replacement or an abandoned form all leave the file on the server — the widget cannot know which of those makes it unwanted. Treat every `upload` result as provisional and reconcile server files against the submitted value (promote what the payload references, sweep the rest, e.g. with a TTL). Call `get_concept({ concept: "host-services" })`.',
     'Validate with a `fileValidator`: `{ type: "file", required, blockPendingUploads }`. `blockPendingUploads` defaults to true and fails while the file is uploading or failed, so an unfinished upload cannot be submitted. Message keys: `invalid`, `required`, `pendingUploads`.',
     '`props.accept` (`[".pdf", "image/*"]`) and `props.maxSize` (bytes) are checked BEFORE uploading; a refused or failed file stays in the box with retry/remove icon buttons — never dropped silently. The reason (server `reject(new Error(...))` message, or the default) surfaces in the standard error area below the input, like a date widget\'s invalid-date error. Text props: `buttonLabel`, `acceptMessage`, `maxSizeMessage`, `missingServiceMessage`, `removeAriaLabel`, `cancelAriaLabel`, `retryAriaLabel`, `uploadedMessage`, `removedMessage`, `failedMessage` (`{name}` token); icon overrides: `removeIcon`, `retryIcon`.'
   ],
   multiFileUpload: [
     "The array variant of `fileUpload`: same box, button, progress bar and `uploadService`. Files upload ONE AT A TIME; every finished file becomes a pill inside the box and the value is an array of envelopes.",
     "A failed file pauses the queue until it is retried or removed. The count is never silently blocked — cap it with `maxItems` so the user is told why.",
+    "Same cleanup contract as `fileUpload`: `uploadService.remove` runs only when the user removes a pill; every other way an envelope leaves the array keeps the file on the server, so the HOST reconciles uploads against the submitted value.",
     'Validate with a `filesValidator`: `{ type: "files", required, minItems, maxItems, blockPendingUploads }`. Message keys: `invalid`, `required`, `minItems`, `maxItems`, `pendingUploads`.'
   ],
   dropdown: [
@@ -3671,7 +3673,7 @@ const HOST_SERVICES_CONCEPT = {
   patterns: [
     {
       name: "Inject an upload transport for the file upload widgets",
-      description: "`uploadService.upload(file, ctx)` is called as soon as a file is picked; whatever it resolves with is stored verbatim in the field value as `item.data` (a URL, an id, an object). `ctx` carries the item `id`, the form `path`, an `onProgress(percentage)` callback for the progress bar, and an `AbortSignal` that fires when the user cancels. The optional `remove(item)` is awaited when the user removes an uploaded file, before the value is cleared; if it rejects the file stays with the error and a retry. Rejecting `upload` marks the file as failed (the message becomes `item.error`).",
+      description: "`uploadService.upload(file, ctx)` is called as soon as a file is picked; whatever it resolves with is stored verbatim in the field value as `item.data` (a URL, an id, an object). `ctx` carries the item `id`, the form `path`, an `onProgress(percentage)` callback for the progress bar, and an `AbortSignal` that fires when the user cancels. The optional `remove(item)` is awaited when the user removes an uploaded file, before the value is cleared; if it rejects the file stays with the error and a retry. Rejecting `upload` marks the file as failed (the message becomes `item.error`). Server file cleanup is the host's job, not the widget's: `remove` runs on exactly two paths — the explicit user removal above, and the single-file widget replacing its file with a new pick (not awaited, a failure is only logged). Every other way a value disappears leaves the file on the server: a deleted repeater row, a field pruned because its state hid it, `setData` or a config replacement, and a form the user abandons without submitting. The widget cannot tell which of those makes the file unwanted, so treat every `upload` result as provisional and reconcile server files against the submitted value (promote what the payload references, sweep the rest, e.g. with a TTL on unreferenced uploads). `remove` is a courtesy on the two paths above, not the cleanup mechanism.",
       example: {
         // Host side (TypeScript), not part of the form definition:
         // const uploadService = {
@@ -3700,7 +3702,8 @@ const HOST_SERVICES_CONCEPT = {
     "Keep the `dependencies` object reference stable (module level or memoized): the form re-initializes whenever its `config` identity changes, and an inline object literal in JSX or a template is a new identity on every render.",
     'A widget that needs a missing service does not break the form: `fileUpload` renders disabled with an inline "not configured" error and logs to the console; `markdown` renders blank.',
     "Never put a `File` object in the form value — the value is the plain envelope the widget builds from the `upload` result; form events and submit payloads deep-clone data, which turns non-plain objects into `{}`.",
-    "`dependencies` is merged shallowly: widget-set defaults, then the DX `formConfig.dependencies`, then the init config `dependencies`; the last one wins per key."
+    "`dependencies` is merged shallowly: widget-set defaults, then the DX `formConfig.dependencies`, then the init config `dependencies`; the last one wins per key.",
+    "The host owns server file cleanup. `uploadService.remove` is called only on an explicit user removal and when the single-file widget replaces its file; a deleted repeater row, a hidden-field prune, `setData`, a config replacement or an abandoned form all leave the file on the server. Treat uploads as provisional and reconcile them against the submitted value."
   ]
 };
 const CONCEPTS = {

package/json.js

@@ -1,4 +1,4 @@
-import { G, J, a, b, c, g, d, e, f, v } from "./get-concept-CsLx7Y5b.js";
+import { G, J, a, b, c, g, d, e, f, v } from "./get-concept-MFKfeD4D.js";
 export {
   G as GET_CONCEPT_TOOL,
   J as JSON_GENERATE_FROM_OPENAPI_TOOL,

package/lib.js

@@ -1,5 +1,5 @@
-import { G, J, a, b, c, g, d, e, f, v } from "./get-concept-CsLx7Y5b.js";
-import { D, a as a2, b as b2, c as c2, d as d2, e as e2, g as g2, l, f as f2, t } from "./list-dx-factories-hQNWmAmY.js";
+import { G, J, a, b, c, g, d, e, f, v } from "./get-concept-MFKfeD4D.js";
+import { D, a as a2, b as b2, c as c2, d as d2, e as e2, g as g2, l, f as f2, t } from "./list-dx-factories-D3u4qsn1.js";
 export {
   D as DX_CHECK_CODE_TOOL,
   a2 as DX_GET_SPEC_TOOL,

package/{list-dx-factories-hQNWmAmY.js → list-dx-factories-D3u4qsn1.js}

@@ -1,4 +1,4 @@
-import { h as checkReactiveExpression, i as checkBooleanValidatorRules } from "./get-concept-CsLx7Y5b.js";
+import { h as checkReactiveExpression, i as checkBooleanValidatorRules } from "./get-concept-MFKfeD4D.js";
 import { existsSync } from "node:fs";
 import { createRequire } from "node:module";
 import { resolve, join, dirname } from "node:path";
@@ -795,7 +795,8 @@ const INPUTS = [
     notes: [
       "Single-file upload rendered as a one-line input: the box is the drop target and holds the upload button; while the file uploads the box itself becomes the progress bar, and once done it shows the file name with a remove button.",
       "REQUIRES a host transport: pass `dependencies: { uploadService: { upload(file, { id, path, onProgress, signal }) => Promise<unknown>, remove?(item) => Promise<void> } }` in the init config (next to `markdown`). Keep the object reference stable (module level) — a new `config` identity re-initializes the form. Without it the widget renders disabled with an inline error.",
-      'The value is a plain envelope, never the `File`: `{ id, name, size, type, status: "uploading" | "uploaded" | "error", error?, data? }` where `data` is exactly what `upload` resolved with. Preload a value from the server with `status: "uploaded"`. Removing awaits `uploadService.remove(item)` (when provided) before clearing. An item restored with `status: "uploading"` cannot resume — the `File` only existed in the session that picked it — so the widget commits it back as `"error"` with `interruptedMessage` (default: `{name} was not uploaded. Remove it and pick the file again.`).',
+      'The value is a plain envelope, never the `File`: `{ id, name, size, type, status: "uploading" | "uploaded" | "error", error?, data? }` where `data` is exactly what `upload` resolved with. Preload a value from the server with `status: "uploaded"`. Removing awaits `uploadService.remove(item)` (when provided) before clearing. An item restored with `status: "uploading"` cannot resume — the `File` only existed in the session that picked it — so the widget shows it as failed with `interruptedMessage` (default: `{name} was not uploaded. Remove it and pick the file again.`) but leaves the stored value untouched: no `change` fires until the user removes it.',
+      "Server file cleanup is the HOST's job. `uploadService.remove` runs only on an explicit user removal and when this widget replaces its file with a new pick (not awaited, failure only logged). A deleted repeater row, a field pruned by a state, `setData`, a config replacement or an abandoned form all leave the file on the server — the widget cannot know which of those makes it unwanted. Treat every `upload` result as provisional and reconcile server files against the submitted value (promote what the payload references, sweep the rest, e.g. with a TTL).",
       "The validator auto-supplies `type: 'file'`. `blockPendingUploads` (default true) fails while the file is still uploading or failed, so a half-finished upload can never be submitted; message keys: `invalid`, `required`, `pendingUploads`.",
       '`accept` (`[".pdf", "image/*", "application/pdf"]`) and `maxSize` (bytes) are checked BEFORE uploading; a refused or failed file stays in the box with retry/remove icon buttons — it is never dropped silently. The reason (server `reject(new Error(...))` message, or the default) surfaces in the standard error area below the input, like a date widget\'s invalid-date error. Messages: `acceptMessage`, `maxSizeMessage`; accessible names: `removeAriaLabel`, `cancelAriaLabel`, `retryAriaLabel` (`{name}` token); icon overrides: `removeIcon`, `retryIcon`.'
     ]
@@ -809,6 +810,7 @@ const INPUTS = [
     notes: [
       "The array variant of `fileUpload` (same box, button, progress bar and `uploadService`). Files upload ONE AT A TIME; every finished file becomes a pill inside the box and the value is an array of envelopes.",
       "A failed file pauses the queue until it is retried or removed. The count is never silently blocked: cap it with `maxItems` so the user is told why.",
+      "Same cleanup contract as `fileUpload`: `uploadService.remove` runs only when the user removes a pill; every other way an envelope leaves the array keeps the file on the server, so the HOST reconciles uploads against the submitted value.",
       "The validator auto-supplies `type: 'files'`; rules: `required` (non-empty), `minItems`, `maxItems`, `blockPendingUploads` (default true); message keys: `invalid`, `required`, `minItems`, `maxItems`, `pendingUploads`."
     ]
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@golemui/gui-mcp",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "license": "MIT",
   "publishConfig": {
     "access": "public"
@@ -43,10 +43,11 @@
     "ajv": "^8.17.1",
     "ajv-formats": "^3.0.1",
     "typescript": "^5.9.2",
-    "@golemui/gui-schemas": "1.5.0",
-    "@golemui/gui-shared": "1.5.0",
-    "@golemui/gui-validators": "1.5.0",
-    "@golemui/core": "1.5.0",
+    "@golemui/gui-schemas": "1.5.1",
+    "@golemui/gui-shared": "1.5.1",
+    "@golemui/gui-validators": "1.5.1",
+    "@golemui/dx": "1.5.1",
+    "@golemui/core": "1.5.1",
     "@modelcontextprotocol/sdk": "^1.0.0",
     "zod": "^4.0.0",
     "@standard-schema/spec": "^1.0.0"