@restforgejs/mcp-server 1.2.2 → 1.2.3

package/dist/tools/designer/list-plugins.js

@@ -4,30 +4,30 @@ import { execProcess } from '../../lib/exec.js';
 export function registerDesignerListPlugins(server) {
     server.registerTool('designer_list_plugins', {
         title: 'List Designer Plugins',
-        description: `List the RESTForge Designer frontend plugins available in the current environment, by running restforge-designer plugins list. Each plugin defines a frontend tech stack / template the designer can generate against.
-
-USE WHEN:
-- The user asks which designer plugins are available, or wants the catalog of frontend templates
-- The user asks things like "plugin apa yang tersedia", "daftar plugin designer", "list frontend plugins", "what designer plugins do I have", "tampilkan plugin frontend", "which frontend templates can I use"
-- Before initialising a project or generating frontend code, to choose which plugin to target
-- The user mentions designer plugins generically and wants an overview
-
-DO NOT USE FOR:
-- Inspecting the metadata, schema, or fields of ONE specific plugin -> use 'designer_inspect_plugin'
-- Validating a UDF payload against a plugin -> use 'designer_validate_payload'
-- Previewing the files a payload would generate -> use 'designer_preview_files'
-
-This tool wraps the RESTForge Designer CLI command: restforge-designer plugins list [--plugins-dir=<pluginsDir>], run in the given cwd.
-The CLI prints a table of available plugins (auto-detected, or from --plugins-dir when supplied). It does not modify any file and does not require a license.
-
-Preconditions:
-- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
-  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
-
-PRESENTATION GUIDANCE:
-- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
-- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "list the available plugins", "inspect a plugin", "generate the frontend code").
-- Speak in plain language. Summarise the plugins (names, count); do not paste raw CLI output unless the user explicitly asks.
+        description: `List the RESTForge Designer frontend plugins available in the current environment, by running restforge-designer plugins list. Each plugin defines a frontend tech stack / template the designer can generate against.
+
+USE WHEN:
+- The user asks which designer plugins are available, or wants the catalog of frontend templates
+- The user asks things like "plugin apa yang tersedia", "daftar plugin designer", "list frontend plugins", "what designer plugins do I have", "tampilkan plugin frontend", "which frontend templates can I use"
+- Before initialising a project or generating frontend code, to choose which plugin to target
+- The user mentions designer plugins generically and wants an overview
+
+DO NOT USE FOR:
+- Inspecting the metadata, schema, or fields of ONE specific plugin -> use 'designer_inspect_plugin'
+- Validating a UDF payload against a plugin -> use 'designer_validate_payload'
+- Previewing the files a payload would generate -> use 'designer_preview_files'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer plugins list [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI prints a table of available plugins (auto-detected, or from --plugins-dir when supplied). It does not modify any file and does not require a license.
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "list the available plugins", "inspect a plugin", "generate the frontend code").
+- Speak in plain language. Summarise the plugins (names, count); do not paste raw CLI output unless the user explicitly asks.
 - When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
         inputSchema: {
             cwd: z
@@ -58,16 +58,16 @@ PRESENTATION GUIDANCE:
                 content: [
                     {
                         type: 'text',
-                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
-
-Working directory: ${projectCwd}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Probe command: ${probe.command}
-Exit code: ${probe.exitCode}
-
-For the assistant:
-- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the available plugins can be listed.
-- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the available plugins can be listed.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
 - Once it is installed, retry listing the plugins.`,
                     },
                 ],
@@ -89,18 +89,18 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Listing Designer plugins did not complete — the command crashed or timed out.
-
-Working directory: ${projectCwd}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-
---- stderr ---
-${result.stderr}
---- end stderr ---
-
-For the assistant:
-- The Designer CLI did not finish (likely a crash or timeout), so there is no plugin list to report.
+                        text: `Listing Designer plugins did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+
+--- stderr ---
+${result.stderr}
+--- end stderr ---
+
+For the assistant:
+- The Designer CLI did not finish (likely a crash or timeout), so there is no plugin list to report.
 - Tell the user the list could not be retrieved and offer to retry. Do not mention internal tool names.`,
                     },
                 ],
@@ -116,22 +116,22 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Listing Designer plugins ran.
-
-Working directory: ${projectCwd}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-Exit code: ${result.exitCode}
-
---- stdout ---
-${result.stdout}
---- end stdout ---
-${stderrBlock}
-For the assistant:
-- The Designer CLI ran to completion. Read the CLI output above and classify the result:
-  (a) Positive result — the output is a table of available plugins. Summarise the plugins in plain language (names and how many) and, if the user is choosing one, suggest inspecting a specific plugin for its details.
-  (b) Actionable negative verdict — no plugins were found, or the plugins directory override could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Explain the situation (e.g. the plugins folder is empty or the override path is wrong) and offer next steps.
-- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
+                    text: `Listing Designer plugins ran.
+
+Working directory: ${projectCwd}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The Designer CLI ran to completion. Read the CLI output above and classify the result:
+  (a) Positive result — the output is a table of available plugins. Summarise the plugins in plain language (names and how many) and, if the user is choosing one, suggest inspecting a specific plugin for its details.
+  (b) Actionable negative verdict — no plugins were found, or the plugins directory override could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Explain the situation (e.g. the plugins folder is empty or the override path is wrong) and offer next steps.
+- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
 - Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
                 },
             ],

package/dist/tools/designer/preview-files.js

@@ -4,31 +4,36 @@ import { execProcess } from '../../lib/exec.js';
 export function registerDesignerPreviewFiles(server) {
     server.registerTool('designer_preview_files', {
         title: 'Preview Designer Files',
-        description: `Preview (dry-run) the frontend files that the RESTForge Designer would generate from a UI Definition File (UDF) payload, by running restforge-designer preview. This lists what would be produced WITHOUT writing anything to disk.
-
-USE WHEN:
-- The user asks which files would be generated, or wants a dry-run before generating frontend code
-- The user asks things like "file apa yang akan di-generate", "preview output frontend designer", "dry-run generate", "what files will the designer produce", "tunjukkan hasil generate tanpa menulis file", "preview the designer output"
-- Before actually generating the frontend code, to inspect the planned output and confirm it looks right
-- The user mentions a designer/frontend UDF payload and wants to see the resulting file layout first
-
-DO NOT USE FOR:
-- Validating that a UDF payload is structurally correct against the plugin schema -> use 'designer_validate_payload'
-- Actually generating and writing the frontend files (preview is read-only; the real generation tool writes files)
-- Listing the available designer plugins -> use 'designer_list_plugins'
-- Inspecting one plugin's metadata -> use 'designer_inspect_plugin'
-
-This tool wraps the RESTForge Designer CLI command: restforge-designer preview --payload=<payload> [--plugins-dir=<pluginsDir>], run in the given cwd.
-The CLI reads the UDF payload JSON, resolves the target plugin (auto-detected or from --plugins-dir), and prints the list of files it would generate. It does not modify any file and does not require a license.
-
-Preconditions:
-- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
-  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
-
-PRESENTATION GUIDANCE:
-- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
-- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "preview the generated files", "validate the UI definition", "generate the frontend code").
-- Speak in plain language. Summarise the planned file list; do not paste raw CLI output unless the user explicitly asks.
+        description: `Preview (dry-run) the frontend files that the RESTForge Designer would generate from a UI Definition File (UDF) payload, by running restforge-designer preview. This lists what would be produced WITHOUT writing anything to disk.
+
+USE WHEN:
+- The user asks which files would be generated, or wants a dry-run before generating frontend code
+- The user asks things like "file apa yang akan di-generate", "preview output frontend designer", "dry-run generate", "what files will the designer produce", "tunjukkan hasil generate tanpa menulis file", "preview the designer output"
+- Before actually generating the frontend code, to inspect the planned output and confirm it looks right
+- The user mentions a designer/frontend UDF payload and wants to see the resulting file layout first
+
+DO NOT USE FOR:
+- Validating that a UDF payload is structurally correct against the plugin schema -> use 'designer_validate_payload'
+- Actually generating and writing the frontend files (preview is read-only; the real generation tool writes files)
+- Listing the available designer plugins -> use 'designer_list_plugins'
+- Inspecting one plugin's metadata -> use 'designer_inspect_plugin'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer preview --payload=<payload> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI reads the UDF payload JSON, resolves the target plugin (auto-detected or from --plugins-dir), and prints the list of files it would generate. It does not modify any file and does not require a license.
+
+Cross-reference (grounding & on-ramp):
+- To ground the UDF shape before previewing or editing it (valid field types, required appConfig fields, enums, limits), use 'designer_get_udf_catalog' — the authoritative source of UDF structure.
+- If the UDF does not exist yet but a backend RDF does, the on-ramp is 'codegen_migrate_payload' (RDF -> split UDF set), then validate and preview that output.
+- Canonical UDF flow: codegen_migrate_payload -> designer_get_udf_catalog -> designer_validate_payload -> designer_preview_files -> designer_generate.
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "preview the generated files", "validate the UI definition", "generate the frontend code").
+- Speak in plain language. Summarise the planned file list; do not paste raw CLI output unless the user explicitly asks.
 - When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
         inputSchema: {
             cwd: z
@@ -63,17 +68,17 @@ PRESENTATION GUIDANCE:
                 content: [
                     {
                         type: 'text',
-                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
-
-Working directory: ${projectCwd}
-Payload: ${payload}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Probe command: ${probe.command}
-Exit code: ${probe.exitCode}
-
-For the assistant:
-- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the generated files can be previewed.
-- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before the generated files can be previewed.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
 - Once it is installed, retry the preview.`,
                     },
                 ],
@@ -95,19 +100,19 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Designer preview did not complete — the command crashed or timed out.
-
-Working directory: ${projectCwd}
-Payload: ${payload}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-
---- stderr ---
-${result.stderr}
---- end stderr ---
-
-For the assistant:
-- The Designer CLI did not finish (likely a crash or timeout), so there is no preview to report.
+                        text: `Designer preview did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+
+--- stderr ---
+${result.stderr}
+--- end stderr ---
+
+For the assistant:
+- The Designer CLI did not finish (likely a crash or timeout), so there is no preview to report.
 - Tell the user the preview could not be completed and offer to retry. Do not mention internal tool names.`,
                     },
                 ],
@@ -123,24 +128,24 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Designer preview ran.
-
-Working directory: ${projectCwd}
-Payload: ${payload}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-Exit code: ${result.exitCode}
-
---- stdout ---
-${result.stdout}
---- end stdout ---
-${stderrBlock}
-For the assistant:
-- The Designer CLI ran to completion. Read the CLI output above and classify the result:
-  (a) Positive result — the output lists the files that would be generated. Summarise the planned files in plain language (how many, what kinds) and offer the next step: generate the frontend code for real.
-  (b) Actionable negative verdict — the payload is invalid, the payload file was not found, or the target plugin / plugins directory could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Summarise the concrete problem (which path or field is wrong) and offer to retry after the user fixes it; validating the payload first can help pinpoint structural errors.
-- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
-- Soft note: if preview fails with an appConfig/plugin error (e.g. the plugin or app config "not found") while the SAME payload passes validation, the payload may rely on 'extends' / 'include' references that preview does not appear to merge the way validation does. As a possible workaround, suggest pointing the preview at a self-contained payload (inline appConfig and pages) or an already-merged file. This is a tentative hint, not a guaranteed rule — do not state it as certain or tie it to a specific version.
+                    text: `Designer preview ran.
+
+Working directory: ${projectCwd}
+Payload: ${payload}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The Designer CLI ran to completion. Read the CLI output above and classify the result:
+  (a) Positive result — the output lists the files that would be generated. Summarise the planned files in plain language (how many, what kinds) and offer the next step: generate the frontend code for real.
+  (b) Actionable negative verdict — the payload is invalid, the payload file was not found, or the target plugin / plugins directory could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Summarise the concrete problem (which path or field is wrong) and offer to retry after the user fixes it; validating the payload first can help pinpoint structural errors.
+- A non-zero exit code here means the CLI reported a negative verdict (case b), NOT that the tool failed. Never tell the user "the tool failed" for case (b).
+- Soft note: if preview fails with an appConfig/plugin error (e.g. the plugin or app config "not found") while the SAME payload passes validation, the payload may rely on 'extends' / 'include' references that preview does not appear to merge the way validation does. As a possible workaround, suggest pointing the preview at a self-contained payload (inline appConfig and pages) or an already-merged file. This is a tentative hint, not a guaranteed rule — do not state it as certain or tie it to a specific version.
 - Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
                 },
             ],

package/dist/tools/designer/preview-files.js.map

@@ -1 +1 @@
-{"version":3,"file":"preview-files.js","sourceRoot":"","sources":["../../../src/tools/designer/preview-files.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEpC,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,4BAA4B,CAAC,MAAiB;IAC5D,MAAM,CAAC,YAAY,CACjB,wBAAwB,EACxB;QACE,KAAK,EAAE,wBAAwB;QAC/B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;uGAyBoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,OAAO,EAAE,CAAC;iBACP,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,iEAAiE,CAAC;YAC9E,UAAU,EAAE,CAAC;iBACV,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,mGAAmG,CAAC;SACjH;QACD,WAAW,EAAE;YACX,KAAK,EAAE,wBAAwB;YAC/B,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,OAAO,EAAE,UAAU,EAAE,EAAE,EAAE;QACrC,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+EAA+E;QAC/E,oEAAoE;QACpE,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,CAAC,WAAW,CAAC,EAAE;YACnE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QACH,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC;YACnB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;2CAKgB;qBAC9B;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,aAAa,OAAO,EAAE,CAAC,CAAC;QACjD,IAAI,UAAU;YAAE,IAAI,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAEzD,MAAM,MAAM,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,IAAI,EAAE;YAC3D,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QAEH,yEAAyE;QACzE,sEAAsE;QACtE,IAAI,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,EAAE,CAAC;YAC3B,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;2GAK4F;qBAC9F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,+EAA+E;QAC/E,qFAAqF;QACrF,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;YAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;YAC5D,CAAC,CAAC,EAAE,CAAC;QACP,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;qBAEG,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;;kIAOqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}
+{"version":3,"file":"preview-files.js","sourceRoot":"","sources":["../../../src/tools/designer/preview-files.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AACxB,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEpC,OAAO,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AAEhD,MAAM,UAAU,4BAA4B,CAAC,MAAiB;IAC5D,MAAM,CAAC,YAAY,CACjB,wBAAwB,EACxB;QACE,KAAK,EAAE,wBAAwB;QAC/B,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uGA8BoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,OAAO,EAAE,CAAC;iBACP,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,iEAAiE,CAAC;YAC9E,UAAU,EAAE,CAAC;iBACV,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,EAAE;iBACV,QAAQ,CAAC,mGAAmG,CAAC;SACjH;QACD,WAAW,EAAE;YACX,KAAK,EAAE,wBAAwB;YAC/B,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,OAAO,EAAE,UAAU,EAAE,EAAE,EAAE;QACrC,MAAM,UAAU,GAAG,OAAO,CAAC,GAAG,CAAC,CAAC;QAEhC,+EAA+E;QAC/E,oEAAoE;QACpE,MAAM,KAAK,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,CAAC,WAAW,CAAC,EAAE;YACnE,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QACH,IAAI,CAAC,KAAK,CAAC,OAAO,EAAE,CAAC;YACnB,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;2CAKgB;qBAC9B;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,aAAa,OAAO,EAAE,CAAC,CAAC;QACjD,IAAI,UAAU;YAAE,IAAI,CAAC,IAAI,CAAC,iBAAiB,UAAU,EAAE,CAAC,CAAC;QAEzD,MAAM,MAAM,GAAG,MAAM,WAAW,CAAC,oBAAoB,EAAE,IAAI,EAAE;YAC3D,GAAG,EAAE,UAAU;YACf,OAAO,EAAE,MAAM;SAChB,CAAC,CAAC;QAEH,yEAAyE;QACzE,sEAAsE;QACtE,IAAI,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,EAAE,CAAC;YAC3B,OAAO;gBACL,OAAO,EAAE;oBACP;wBACE,IAAI,EAAE,MAAM;wBACZ,IAAI,EAAE;;qBAEC,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;2GAK4F;qBAC9F;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,+EAA+E;QAC/E,qFAAqF;QACrF,MAAM,WAAW,GAAG,MAAM,CAAC,MAAM;YAC/B,CAAC,CAAC,qBAAqB,MAAM,CAAC,MAAM,wBAAwB;YAC5D,CAAC,CAAC,EAAE,CAAC;QACP,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;;qBAEG,UAAU;WACpB,OAAO;eACH,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;;kIAOqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

package/dist/tools/designer/scaffold-plugin.js

@@ -4,31 +4,31 @@ import { execProcess } from '../../lib/exec.js';
 export function registerDesignerScaffoldPlugin(server) {
     server.registerTool('designer_scaffold_plugin', {
         title: 'Scaffold Designer Plugin',
-        description: `Scaffold a new custom RESTForge Designer frontend plugin from a template, by running restforge-designer plugins scaffold. This WRITES a new plugin folder to disk that the user can then customise.
-
-USE WHEN:
-- The user asks to create a new custom designer/frontend plugin from scratch
-- The user asks things like "buat plugin custom baru", "scaffold folder plugin designer", "mulai plugin frontend dari template", "create a new designer plugin", "scaffold a frontend plugin", "bikin plugin frontend baru"
-- The user wants a starter plugin folder they can edit to build their own frontend generator template
-- The user names a new plugin id and wants the folder structure generated for it
-
-DO NOT USE FOR:
-- Generating a frontend application from a UDF payload -> use 'designer_generate'
-- Initialising a project from an existing plugin -> use 'designer_init_project'
-- Listing the available plugins -> use 'designer_list_plugins'
-- Inspecting one existing plugin's metadata -> use 'designer_inspect_plugin'
-
-This tool wraps the RESTForge Designer CLI command: restforge-designer plugins scaffold --id=<id> --output=<output> [--plugins-dir=<pluginsDir>], run in the given cwd.
-The CLI creates a new plugin folder named after the given id under the output directory. It does NOT require a license (scaffolding is license-free).
-
-Preconditions:
-- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
-  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
-
-PRESENTATION GUIDANCE:
-- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
-- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "scaffold a new plugin", "list the available plugins", "generate the frontend code").
-- Speak in plain language. Confirm what was created and where; do not paste raw CLI output unless the user explicitly asks.
+        description: `Scaffold a new custom RESTForge Designer frontend plugin from a template, by running restforge-designer plugins scaffold. This WRITES a new plugin folder to disk that the user can then customise.
+
+USE WHEN:
+- The user asks to create a new custom designer/frontend plugin from scratch
+- The user asks things like "buat plugin custom baru", "scaffold folder plugin designer", "mulai plugin frontend dari template", "create a new designer plugin", "scaffold a frontend plugin", "bikin plugin frontend baru"
+- The user wants a starter plugin folder they can edit to build their own frontend generator template
+- The user names a new plugin id and wants the folder structure generated for it
+
+DO NOT USE FOR:
+- Generating a frontend application from a UDF payload -> use 'designer_generate'
+- Initialising a project from an existing plugin -> use 'designer_init_project'
+- Listing the available plugins -> use 'designer_list_plugins'
+- Inspecting one existing plugin's metadata -> use 'designer_inspect_plugin'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer plugins scaffold --id=<id> --output=<output> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI creates a new plugin folder named after the given id under the output directory. It does NOT require a license (scaffolding is license-free).
+
+Preconditions:
+- The 'restforge-designer' binary must be installed and reachable on PATH. This tool pre-checks that by running
+  'restforge-designer --version'; if the binary is missing, the response will surface that as a non-error precondition.
+
+PRESENTATION GUIDANCE:
+- Match the user's language. If the user writes in Indonesian, respond in Indonesian.
+- Never mention internal tool names in the reply to the user. Describe actions by what they do (e.g. "scaffold a new plugin", "list the available plugins", "generate the frontend code").
+- Speak in plain language. Confirm what was created and where; do not paste raw CLI output unless the user explicitly asks.
 - When a precondition is not met, frame it as a question or next-step suggestion rather than an error.`,
         inputSchema: {
             cwd: z
@@ -67,18 +67,18 @@ PRESENTATION GUIDANCE:
                 content: [
                     {
                         type: 'text',
-                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
-
-Working directory: ${projectCwd}
-Plugin id: ${id}
-Output: ${output}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Probe command: ${probe.command}
-Exit code: ${probe.exitCode}
-
-For the assistant:
-- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before a plugin can be scaffolded.
-- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
+                        text: `Precondition not met: the RESTForge Designer command-line tool is not installed or not on PATH.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Probe command: ${probe.command}
+Exit code: ${probe.exitCode}
+
+For the assistant:
+- The user needs to install RESTForge Designer (and ensure it is on the system PATH) before a plugin can be scaffolded.
+- When explaining to the user, say something like "the RESTForge Designer tool isn't installed or isn't on your PATH yet — please install it and try again". Do not mention internal tool names.
 - Once it is installed, retry scaffolding the plugin.`,
                     },
                 ],
@@ -104,24 +104,24 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Scaffolding the Designer plugin did not complete.
-
-Working directory: ${projectCwd}
-Plugin id: ${id}
-Output: ${output}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-Exit code: ${result.exitCode}
-
---- stdout ---
-${result.stdout}
---- end stdout ---
-${stderrBlock}
-For the assistant:
-- The scaffold did not finish successfully, so the plugin folder may not exist or may be partial. Read the CLI output above and explain the most likely cause to the user in plain language. Common causes:
-  * The output directory already exists or is not writable — suggest a different output path or clearing the existing folder.
-  * The plugin id is invalid (bad characters) — suggest a simpler id.
-  * Exit code -1 — the command crashed or timed out; offer to retry.
+                        text: `Scaffolding the Designer plugin did not complete.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The scaffold did not finish successfully, so the plugin folder may not exist or may be partial. Read the CLI output above and explain the most likely cause to the user in plain language. Common causes:
+  * The output directory already exists or is not writable — suggest a different output path or clearing the existing folder.
+  * The plugin id is invalid (bad characters) — suggest a simpler id.
+  * Exit code -1 — the command crashed or timed out; offer to retry.
 - Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
                     },
                 ],
@@ -136,23 +136,23 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Designer plugin scaffolded successfully.
-
-Working directory: ${projectCwd}
-Plugin id: ${id}
-Output: ${output}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-Exit code: ${result.exitCode}
-
---- stdout ---
-${result.stdout}
---- end stdout ---
-${stderrBlock}
-For the assistant:
-- Confirm to the user that the new plugin folder was created. Mention the plugin id and the output location in plain language.
-- The scaffold is a starting point: the user will edit the generated plugin files (templates, schema) to build their own frontend generator.
-- Suggest a sensible next step, e.g. inspecting or listing the plugins to confirm the new one is picked up, or authoring a UDF payload that targets it.
+                    text: `Designer plugin scaffolded successfully.
+
+Working directory: ${projectCwd}
+Plugin id: ${id}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- Confirm to the user that the new plugin folder was created. Mention the plugin id and the output location in plain language.
+- The scaffold is a starting point: the user will edit the generated plugin files (templates, schema) to build their own frontend generator.
+- Suggest a sensible next step, e.g. inspecting or listing the plugins to confirm the new one is picked up, or authoring a UDF payload that targets it.
 - Do not paste the raw CLI output unless the user explicitly asks. Do not mention internal tool names. Match the user's language.`,
                 },
             ],