dsh-artcraft-plugin-vectorcraft 0.1.0 → 0.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-artcraft-plugin-vectorcraft",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "private": false,
   "type": "module",
   "description": "DSH plugin: drive VectorCraft (vector art) headlessly through its own CLI and MCP server.",

package/src/kit/profiles.mjs

@@ -261,7 +261,10 @@ export const CRAFT_PROFILES = [
       cmdSeparator: '',
       cmdStyle: 'flag-params',
       cmdParamsFlag: '--params',
+      // VectorCraft renders documents and artifacts through one flag, so both
+      // names map to it: the kernel folds `export` into `save` when they match.
       saveFlag: '--export',
+      exportFlag: '--export',
     },
     reads: [
       { name: 'convert', verb: 'convert', summary: 'Open any readable format and export it to another.' },

package/src/kit/tools.js

@@ -364,7 +364,12 @@ export function createToolSet(runtime              )               {
       ...(profile.run.saveMode ?? 'flag') === 'flag'
         ? { save: { type: 'string', description: `Path to write the edited document to (${profile.extensions.join('/')}).` } }
         : {},
-      ...profile.run.exportFlag !== undefined && profile.run.exportFlag !== profile.run.saveFlag
+      // `export` is always advertised when the craft can render one. Where the
+      // craft writes documents and artifacts through the same flag (VectorCraft
+      // `--export`), the executor folds `export` into `save`; the parameter is
+      // still offered because naming the artifact is what a caller means, and
+      // withholding it only pushes them to `extraArgs`.
+      ...profile.run.exportFlag !== undefined
         ? { export: { type: 'string', description: 'Path to export a rendered artifact to (png/svg/pdf, or the app\'s native media type).' } }
         : {},
       ...profile.run.sampleFlag.length > 0