@productmaker/mcp 12.1.0 → 12.1.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/README.md +15 -0
- package/dist/http.js +1290 -869
- package/dist/stdio.js +1349 -829
- package/dist/ui/task-results-app.html +461 -0
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -309,6 +309,21 @@ The `base64` field was removed. MCP JSON-RPC transports truncate large tool argu
|
|
|
309
309
|
|
|
310
310
|
## Version history
|
|
311
311
|
|
|
312
|
+
### 12.1.2 — ChatGPT result metadata compatibility
|
|
313
|
+
|
|
314
|
+
- The result viewer reads ChatGPT's canonical `toolResponseMetadata` envelopes as well as direct metadata and standard MCP App notifications. Initial results and later updates retain the same media validation and cleanup.
|
|
315
|
+
- The bridge answers trusted parent JSON-RPC pings and accepts initialization only from its matching response, once. A host request reusing the same ID cannot initialize it.
|
|
316
|
+
- After changing a development connector's tool descriptors, refresh its tools in ChatGPT. A successful server deployment alone does not prove that the installed connector has discovered the new viewer.
|
|
317
|
+
- Hosted playback remains a separate release check; local bridge fixtures do not establish it.
|
|
318
|
+
|
|
319
|
+
### 12.1.1 — Real media in chat and service landing quote parity
|
|
320
|
+
|
|
321
|
+
- `get_task_status` attaches a read-only MCP App with the delivered ProductMaker images and playable videos, plus original native image bytes and protected download fallbacks. It never generates replacement media.
|
|
322
|
+
- Service video URLs, including clean and historical variants, use the existing signed proxy so chat tracking parameters cannot invalidate the storage signature.
|
|
323
|
+
- Service landing creation requires the same maximum estimated balance as the web intake. Provider retry authorization remains separate; an unknown balance does not block a confirmed build.
|
|
324
|
+
- Delivery analytics record response states and media counts through the shared MCP transport, without asset URLs or content. They measure server response delivery, not host rendering or video playback.
|
|
325
|
+
- Local protocol/browser evidence does not establish delivery in a deployed ChatGPT connector; hosted verification follows release.
|
|
326
|
+
|
|
312
327
|
### 12.1.0 — Independent service video creatives
|
|
313
328
|
|
|
314
329
|
- `hookVariants` keeps its 1–3 transport range; new requests create a complete independent video per quantity, with distinct commercial angle, script and visual direction respecting `notes`.
|