@restforgejs/mcp-server 1.2.2 → 1.2.4

package/dist/tools/designer/init-project.js

@@ -4,31 +4,31 @@ import { execProcess } from '../../lib/exec.js';
 export function registerDesignerInitProject(server) {
     server.registerTool('designer_init_project', {
         title: 'Init Designer Project',
-        description: `Initialise a new frontend project from an existing RESTForge Designer plugin, by running restforge-designer init. This WRITES a new project scaffold (config + structure) to disk, ready for generating frontend code.
-
-USE WHEN:
-- The user asks to start/initialise a new frontend project based on a designer plugin
-- The user asks things like "init project frontend baru", "scaffold aplikasi dari plugin designer", "mulai project frontend dengan plugin X", "init a new frontend project", "set up a designer project from plugin <id>", "buat project frontend dari plugin"
-- The user has a plugin id in mind and wants the project skeleton (app config, auth settings, ports) created from it
-
-DO NOT USE FOR:
-- Generating frontend code from an existing UDF payload -> use 'designer_generate'
-- Creating a brand new custom plugin from a template -> use 'designer_scaffold_plugin'
-- Listing or inspecting available plugins -> use 'designer_list_plugins' / 'designer_inspect_plugin'
-
-This tool wraps the RESTForge Designer CLI command: restforge-designer init --plugin=<plugin> --output=<output> [optional flags], run in the given cwd.
-The --plugin and --output flags are always sent so the binary never drops into interactive prompt mode. Optional flags (app name/code, API URLs, auth settings, port, idle timeout, no-auth, overwrite, plugins dir, license) are forwarded only when supplied.
-This operation is license-gated: the RESTForge Designer license must be active for init to succeed.
-
-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.
-- A valid, active RESTForge Designer license is required (the operation is license-gated).
-
-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. "initialise the frontend project", "generate the frontend code", "scaffold a new plugin").
-- Speak in plain language. Confirm what was created and where; do not paste raw CLI output unless the user explicitly asks.
+        description: `Initialise a new frontend project from an existing RESTForge Designer plugin, by running restforge-designer init. This WRITES a new project scaffold (config + structure) to disk, ready for generating frontend code.
+
+USE WHEN:
+- The user asks to start/initialise a new frontend project based on a designer plugin
+- The user asks things like "init project frontend baru", "scaffold aplikasi dari plugin designer", "mulai project frontend dengan plugin X", "init a new frontend project", "set up a designer project from plugin <id>", "buat project frontend dari plugin"
+- The user has a plugin id in mind and wants the project skeleton (app config, auth settings, ports) created from it
+
+DO NOT USE FOR:
+- Generating frontend code from an existing UDF payload -> use 'designer_generate'
+- Creating a brand new custom plugin from a template -> use 'designer_scaffold_plugin'
+- Listing or inspecting available plugins -> use 'designer_list_plugins' / 'designer_inspect_plugin'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer init --plugin=<plugin> --output=<output> [optional flags], run in the given cwd.
+The --plugin and --output flags are always sent so the binary never drops into interactive prompt mode. Optional flags (app name/code, API URLs, auth settings, port, idle timeout, no-auth, overwrite, plugins dir, license) are forwarded only when supplied.
+This operation is license-gated: the RESTForge Designer license must be active for init to succeed.
+
+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.
+- A valid, active RESTForge Designer license is required (the operation is license-gated).
+
+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. "initialise the frontend project", "generate the frontend code", "scaffold a new plugin").
+- 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
@@ -118,18 +118,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: ${plugin}
-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 project can be initialised.
-- 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: ${plugin}
+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 project can be initialised.
+- 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 initialising the project.`,
                     },
                 ],
@@ -176,26 +176,26 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Initialising the Designer project did not complete.
-
-Working directory: ${projectCwd}
-Plugin: ${plugin}
-Output: ${output}
-Plugins dir: ${pluginsDir ?? 'auto-detect'}
-Command: ${result.command}
-Exit code: ${result.exitCode}
-
---- stdout ---
-${result.stdout}
---- end stdout ---
-${stderrBlock}
-For the assistant:
-- The init did not finish successfully, so the project 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 RESTForge Designer license is not active — this operation is license-gated. Suggest the user activate their RESTForge Designer license through the Designer desktop application or its own CLI, then retry. Do not name any internal tool.
-  * The output directory already exists and overwrite was not enabled — suggest retrying with overwrite, or choosing a different output path.
-  * The plugin id does not exist — suggest listing the available plugins to pick a valid id.
-  * The chosen plugin does not support init — soft note: not every plugin supports the 'init' feature. If the CLI says something like "does not support the init feature", suggest picking a plugin that does (the available plugins can be listed to find one). Do not hardcode or assert a permanent list of which plugins support init — treat it as something to confirm from the current plugin list rather than a fixed claim.
-  * Exit code -1 — the command crashed or timed out; offer to retry.
+                        text: `Initialising the Designer project did not complete.
+
+Working directory: ${projectCwd}
+Plugin: ${plugin}
+Output: ${output}
+Plugins dir: ${pluginsDir ?? 'auto-detect'}
+Command: ${result.command}
+Exit code: ${result.exitCode}
+
+--- stdout ---
+${result.stdout}
+--- end stdout ---
+${stderrBlock}
+For the assistant:
+- The init did not finish successfully, so the project 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 RESTForge Designer license is not active — this operation is license-gated. Suggest the user activate their RESTForge Designer license through the Designer desktop application or its own CLI, then retry. Do not name any internal tool.
+  * The output directory already exists and overwrite was not enabled — suggest retrying with overwrite, or choosing a different output path.
+  * The plugin id does not exist — suggest listing the available plugins to pick a valid id.
+  * The chosen plugin does not support init — soft note: not every plugin supports the 'init' feature. If the CLI says something like "does not support the init feature", suggest picking a plugin that does (the available plugins can be listed to find one). Do not hardcode or assert a permanent list of which plugins support init — treat it as something to confirm from the current plugin list rather than a fixed claim.
+  * 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.`,
                     },
                 ],
@@ -210,22 +210,22 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Designer project initialised successfully.
-
-Working directory: ${projectCwd}
-Plugin: ${plugin}
-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 frontend project was initialised. Mention the plugin and the output location in plain language.
-- Suggest the next step: author or supply a UDF payload and then generate the frontend code into the project. The usual flow is validate the payload, preview the files, then generate.
+                    text: `Designer project initialised successfully.
+
+Working directory: ${projectCwd}
+Plugin: ${plugin}
+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 frontend project was initialised. Mention the plugin and the output location in plain language.
+- Suggest the next step: author or supply a UDF payload and then generate the frontend code into the project. The usual flow is validate the payload, preview the files, then generate.
 - 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/inspect-plugin.js

@@ -4,30 +4,35 @@ import { execProcess } from '../../lib/exec.js';
 export function registerDesignerInspectPlugin(server) {
     server.registerTool('designer_inspect_plugin', {
         title: 'Inspect Designer Plugin',
-        description: `Inspect the metadata of a single RESTForge Designer frontend plugin (its schema, fields, components, and configuration), by running restforge-designer plugins inspect for a given plugin id.
-
-USE WHEN:
-- The user asks for the details, metadata, schema, or fields of one specific designer plugin
-- The user asks things like "detail plugin X", "metadata plugin", "schema plugin designer", "apa isi plugin vanilla-js-auth", "what's inside the vanilla-js-auth plugin", "tampilkan field plugin frontend ini", "show me the structure of plugin <id>"
-- Before authoring a UDF payload for a plugin, to learn which fields and components that plugin expects
-- The user names a specific plugin id and wants to understand what it provides
-
-DO NOT USE FOR:
-- Listing ALL available plugins -> use 'designer_list_plugins'
-- 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 inspect --plugin=<plugin> [--plugins-dir=<pluginsDir>], run in the given cwd.
-The CLI resolves the named plugin (auto-detected, or from --plugins-dir) and prints its metadata. 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. "inspect the plugin", "list the available plugins", "generate the frontend code").
-- Speak in plain language. Summarise the plugin metadata; do not paste raw CLI output unless the user explicitly asks.
+        description: `Inspect the metadata of a single RESTForge Designer frontend plugin (its schema, fields, components, and configuration), by running restforge-designer plugins inspect for a given plugin id.
+
+USE WHEN:
+- The user asks for the details, metadata, schema, or fields of one specific designer plugin
+- The user asks things like "detail plugin X", "metadata plugin", "schema plugin designer", "apa isi plugin vanilla-js-auth", "what's inside the vanilla-js-auth plugin", "tampilkan field plugin frontend ini", "show me the structure of plugin <id>"
+- Before authoring a UDF payload for a plugin, to learn which fields and components that plugin expects
+- The user names a specific plugin id and wants to understand what it provides
+
+DO NOT USE FOR:
+- Listing ALL available plugins -> use 'designer_list_plugins'
+- Validating a UDF payload against a plugin -> use 'designer_validate_payload'
+- Previewing the files a payload would generate -> use 'designer_preview_files'
+- The authoritative catalog of UDF structure and rules (valid field types, required appConfig fields, enums, limits) -> use 'designer_get_udf_catalog'
+
+This tool wraps the RESTForge Designer CLI command: restforge-designer plugins inspect --plugin=<plugin> [--plugins-dir=<pluginsDir>], run in the given cwd.
+The CLI resolves the named plugin (auto-detected, or from --plugins-dir) and prints its metadata. It does not modify any file and does not require a license.
+
+IMPORTANT — identity, not UDF structure:
+- This tool returns the IDENTITY/metadata of ONE plugin (its declared schema, fields, components, configuration). It is NOT the authoritative source of UDF structure and authoring rules. Do NOT infer the valid UDF field types, required appConfig fields, enums, or limits from this plugin metadata.
+- For the authoritative UDF structure and rules, use 'designer_get_udf_catalog' (serialized from the designer's own validator constants). Use plugin inspection to learn what a SPECIFIC plugin provides; use the catalog to learn the UDF rules that apply across the designer.
+
+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. "inspect the plugin", "list the available plugins", "generate the frontend code").
+- Speak in plain language. Summarise the plugin metadata; 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
@@ -62,17 +67,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}
-Plugin: ${plugin}
-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 inspected.
-- 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: ${plugin}
+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 inspected.
+- 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 inspecting the plugin.`,
                     },
                 ],
@@ -94,19 +99,19 @@ For the assistant:
                 content: [
                     {
                         type: 'text',
-                        text: `Inspecting the Designer plugin did not complete — the command crashed or timed out.
-
-Working directory: ${projectCwd}
-Plugin: ${plugin}
-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 metadata to report.
+                        text: `Inspecting the Designer plugin did not complete — the command crashed or timed out.
+
+Working directory: ${projectCwd}
+Plugin: ${plugin}
+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 metadata to report.
 - Tell the user the inspection could not be completed and offer to retry. Do not mention internal tool names.`,
                     },
                 ],
@@ -122,23 +127,23 @@ For the assistant:
             content: [
                 {
                     type: 'text',
-                    text: `Inspecting the Designer plugin ran.
-
-Working directory: ${projectCwd}
-Plugin: ${plugin}
-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 the plugin's metadata (its schema, fields, components). Summarise it in plain language so the user understands what the plugin expects, and offer the next step (e.g. author or validate a payload for it).
-  (b) Actionable negative verdict — the named plugin id does not exist, or the plugins directory override could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Tell the user the plugin id was not found (note: a "plugin not found" verdict often comes with a non-zero exit code, which is expected here) and suggest listing the available plugins to pick a valid id.
-- 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: `Inspecting the Designer plugin ran.
+
+Working directory: ${projectCwd}
+Plugin: ${plugin}
+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 the plugin's metadata (its schema, fields, components). Summarise it in plain language so the user understands what the plugin expects, and offer the next step (e.g. author or validate a payload for it).
+  (b) Actionable negative verdict — the named plugin id does not exist, or the plugins directory override could not be resolved. These are legitimate results to RELAY to the user, not tool malfunctions. Tell the user the plugin id was not found (note: a "plugin not found" verdict often comes with a non-zero exit code, which is expected here) and suggest listing the available plugins to pick a valid id.
+- 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/inspect-plugin.js.map

@@ -1 +1 @@
-{"version":3,"file":"inspect-plugin.js","sourceRoot":"","sources":["../../../src/tools/designer/inspect-plugin.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,6BAA6B,CAAC,MAAiB;IAC7D,MAAM,CAAC,YAAY,CACjB,yBAAyB,EACzB;QACE,KAAK,EAAE,yBAAyB;QAChC,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;uGAwBoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,MAAM,EAAE,CAAC;iBACN,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,iDAAiD,CAAC;YAC9D,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,yBAAyB;YAChC,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,EAAE,EAAE;QACpC,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;qDAK0B;qBACxC;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,SAAS,EAAE,YAAY,MAAM,EAAE,CAAC,CAAC;QAC1D,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;8GAK+F;qBACjG;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,kFAAkF;QAClF,kFAAkF;QAClF,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;kIAMqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}
+{"version":3,"file":"inspect-plugin.js","sourceRoot":"","sources":["../../../src/tools/designer/inspect-plugin.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,6BAA6B,CAAC,MAAiB;IAC7D,MAAM,CAAC,YAAY,CACjB,yBAAyB,EACzB;QACE,KAAK,EAAE,yBAAyB;QAChC,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uGA6BoF;QACjG,WAAW,EAAE;YACX,GAAG,EAAE,CAAC;iBACH,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,gEAAgE,CAAC;YAC7E,MAAM,EAAE,CAAC;iBACN,MAAM,EAAE;iBACR,GAAG,CAAC,CAAC,CAAC;iBACN,QAAQ,CAAC,iDAAiD,CAAC;YAC9D,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,yBAAyB;YAChC,YAAY,EAAE,IAAI;YAClB,cAAc,EAAE,IAAI;SACrB;KACF,EACD,KAAK,EAAE,EAAE,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,EAAE,EAAE;QACpC,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;iBACzB,KAAK,CAAC,OAAO;aACjB,KAAK,CAAC,QAAQ;;;;;qDAK0B;qBACxC;iBACF;gBACD,OAAO,EAAE,KAAK,EAAE,WAAW;aAC5B,CAAC;QACJ,CAAC;QAED,8DAA8D;QAC9D,MAAM,IAAI,GAAG,CAAC,SAAS,EAAE,SAAS,EAAE,YAAY,MAAM,EAAE,CAAC,CAAC;QAC1D,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;;;EAGvB,MAAM,CAAC,MAAM;;;;;8GAK+F;qBACjG;iBACF;gBACD,OAAO,EAAE,IAAI,EAAE,sCAAsC;aACtD,CAAC;QACJ,CAAC;QAED,kFAAkF;QAClF,kFAAkF;QAClF,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;UACrB,MAAM;eACD,UAAU,IAAI,aAAa;WAC/B,MAAM,CAAC,OAAO;aACZ,MAAM,CAAC,QAAQ;;;EAG1B,MAAM,CAAC,MAAM;;EAEb,WAAW;;;;;;kIAMqH;iBACvH;aACF;SACF,CAAC;IACJ,CAAC,CACF,CAAC;AACJ,CAAC"}

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.`,
                 },
             ],