@autobe/agent 0.6.0 → 0.7.1

package/lib/index.mjs

@@ -97,8 +97,8 @@ class AutoBeAnalyzeAgent {
                 vendor: ctx.vendor,
                 config: {
                     locale: ctx.config?.locale,
-                    systemPrompt: {
-                        describe: () => "Answer only 'completion' or 'failure'."
+                    executor: {
+                        describe: null
                     }
                 },
                 tokenUsage: ctx.usage(),
@@ -155,21 +155,20 @@ class AutoBeAnalyzeAgent {
             });
             const filenames = Object.keys(this.fileMap).join(",");
             const command = `Please proceed with the review of these files only.: ${filenames}`;
-            const [review] = await reviewer.conversate(command);
+            const response = await reviewer.conversate(command);
+            const review = response.find((el => el.type === "assistantMessage"));
             if (review) {
-                if (review.type === "assistantMessage") {
-                    this.ctx.dispatch({
-                        type: "analyzeReview",
-                        review: review.text,
-                        created_at: (new Date).toISOString(),
-                        step: this.ctx.state().analyze?.step ?? 0
-                    });
-                    return this.conversate(JSON.stringify({
-                        user_query: content,
-                        message: `THIS IS ANSWER OF REVIEW AGENT. FOLLOW THIS INSTRUCTIONS. AND DON'T REQUEST ANYTHING.`,
-                        review: review.text
-                    }), retry - 1);
-                }
+                this.ctx.dispatch({
+                    type: "analyzeReview",
+                    review: review.text,
+                    created_at: (new Date).toISOString(),
+                    step: this.ctx.state().analyze?.step ?? 0
+                });
+                return this.conversate(JSON.stringify({
+                    user_query: content,
+                    message: `THIS IS ANSWER OF REVIEW AGENT. FOLLOW THIS INSTRUCTIONS. AND DON'T REQUEST ANYTHING.`,
+                    review: review.text
+                }), retry - 1);
             }
             return `COMPLETE WITHOUT REVIEW`;
         }
@@ -179,7 +178,7 @@ class AutoBeAnalyzeAgent {
 
 function createController$1(props) {
     assertSchemaModel(props.model);
-    const application = collection$9[props.model];
+    const application = collection$c[props.model];
     return {
         protocol: "class",
         name: "Planning",
@@ -204,7 +203,7 @@ function createController$1(props) {
     };
 }
 
-const claude$9 = {
+const claude$c = {
     model: "claude",
     options: {
         reference: true,
@@ -450,7 +449,7 @@ const claude$9 = {
     } ]
 };
 
-const collection$9 = {
+const collection$c = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -696,10 +695,10 @@ const collection$9 = {
             }))()
         } ]
     },
-    claude: claude$9,
-    llama: claude$9,
-    deepseek: claude$9,
-    3.1: claude$9,
+    claude: claude$c,
+    llama: claude$c,
+    deepseek: claude$c,
+    3.1: claude$c,
     "3.0": {
         model: "3.0",
         options: {
@@ -952,8 +951,8 @@ const AutoBeAnalyzeReviewer = (ctx, input) => {
         vendor: ctx.vendor,
         controllers: [],
         config: {
-            systemPrompt: {
-                describe: () => "Answer only 'completion' or 'failure'."
+            executor: {
+                describe: null
             },
             locale: ctx.config?.locale
         },
@@ -961,7 +960,7 @@ const AutoBeAnalyzeReviewer = (ctx, input) => {
             id: v4(),
             created_at: (new Date).toISOString(),
             type: "systemMessage",
-            text: "# Reviewer Agent Operating Guidelines\n\n## Core Principles\n\n* **Only review the document currently being viewed.**\n* Even if there is a section that implies another document, **ignore it.**\n* Even if the current page is a table of contents, **do not request the creation of any other pages.**\n* If a new document is referenced even though the current document is not a table of contents page that begins with `00`,\n  **instruct the planner to clear all content and rewrite the document.**\n* Other documents will be brought in by other agents, so do **not** request the creation of any files other than the current one.\n* **Each agent must write only the single page assigned to them.**  \n  Requests or attempts to write other pages or documents are strictly prohibited.\n* When references to other documents appear in the current page, do not request creation of those documents. Instead,  \n  **instruct the planner to clear all contents and rewrite the current document.**\n\n## Role of the Reviewer\n\n* The reviewer's role is to **ensure the document contains sufficient information before it is delivered to developers.**\n* Below are all the **links currently referenced in the markdown**. Be sure to refer to them and **ensure the corresponding files are created.**\n* **Do not create files that are not specified in the table of contents.**\n* If the user specifies the **exact number of pages**, that number **must be followed exactly.**\n* Reviewers are limited to reviewing **only their assigned single page** and must not engage with other pages or documents.\n* If an agent requests creation of other pages or documents,  \n  the reviewer must issue a command to **stop such requests and enforce focus on the current page only.**\n\n## Prohibited Actions\n\n* The reviewer must **never write their own content under any circumstances.**\n* Reviewers are **independent beings and must never be instructed.**\n* The reviewer's words must be **commands that must be followed, not recommendations.**\n\n## Instructions for Revisions\n\n* If changes are necessary, **provide detailed instructions.**\n* Give **clear and concise instructions**, and **avoid unnecessary remarks.**\n* If the document is too short or insufficient, compare the number of headings to the text length and  \n  **instruct the analyze agent to expand the content within the current page accordingly.**\n* If hyperlinks point to content not included in the current page,  \n  **instruct the analyze agent to add a new section with the hyperlink’s title under the appropriate heading within the same page.**\n\n## If the Document is Sufficient\n\n* If the current level of analysis is deemed sufficient, **make no further requests.**\n* **Notify that the document is complete.**\n\n---\n\n# Guidelines for Document Volume\n\n* It is recommended to instruct the analyze agent to **write a document longer than 2,000 characters** for sufficient utility.\n* If the document is too short, indicate how many characters it currently has and how many more are needed.\n* However, in the case of the table of contents page, it is free from the volume limit.\n* Rather than simply telling them to increase the text, **compare the number of headings to the text length**,\n  and if they want to double the amount, **instruct them to do so accordingly.**\n* When referencing something from the table of contents, clearly **state the name of the section**.\n\n---\n\n# Q\\&A Guidelines\n\n* If the analyze agent asks a question, **the reviewer must answer on behalf of the user.**\n* **Never ask any questions.**\n* **Only give commands.**\n\n---\n\n# Guidelines for Hyperlinks\n\n* Even if a document is high quality, if it contains **incomplete hyperlinks**, it is considered **incomplete**.\n* If a hyperlink points to **content that has not yet been written**, the document is **incomplete regardless of its quality**.\n* However, **incomplete hyperlinks to external documents (outside the current page)** are **allowed**.\n  In such cases, assume that other agents will write those documents and move on without strict enforcement.\n* If a hyperlink points to a **heading within the same document** (i.e., an anchor/fragment link):\n\n  * That heading **must exist** in the document.\n  * If it does not exist, instruct the **analyze agent** to **create a new section with the same title as the hyperlink** and\n    **insert it under the appropriate heading**.\n* If a hyperlink points to an **external document**, and the current document is **not a table of contents page starting with `00`**,\n  the rule above still applies—**incomplete external links are allowed** and do **not** require clearing or rewriting the document.\n\n---\n\n# Review Completion Conditions\n\n* When the document is determined to be complete, clearly give the following instruction:\n  **The analyze agent has a tool called 'abort,' so instruct them to call it to stop the review.**\n* This instruction must only be given **when all the following conditions are met**:\n\n  * All sections listed in the table of contents are **fully written**.\n  * All referenced hyperlinks are **resolved**.\n* If there are still sections to write or links unresolved,\n  instruct the analyze agent to continue writing,\n  including the **specific section title** and a **brief explanation** of what content is needed.\n\n---\n\n# Additional Requirements for Page-Based Work Division\n\n* Each agent must write and review **only their assigned single page** out of the total pages specified.\n* Under no circumstances should an agent request or attempt to create documents beyond their assigned page.\n* If an agent attempts to request content outside their page, immediately command them to **focus solely on the current page.**\n* All document length and content sufficiency checks and corrections must be done within the single assigned page.\n* If multiple pages exist, the total number of pages must be strictly adhered to, and no extra pages should be created.\n* This strict page-level division must be enforced to maintain clear boundaries of responsibility and simplify review workflows.\n\n---\n\n**All these guidelines must be strictly enforced during the document creation and review process. Any violations require immediate correction or rewriting commands.**"
+            text: "# Reviewer Agent Operating Guidelines\n\n## Core Principles\n\n* **Only review the document currently being viewed.**\n* Even if there is a section that implies another document, **ignore it.**\n* Even if the current page is a table of contents, **do not request the creation of any other pages.**\n* If a new document is referenced even though the current document is not a table of contents page that begins with `00`,\n  **instruct the planner to clear all content and rewrite the document.**\n* Other documents will be brought in by other agents, so do **not** request the creation of any files other than the current one.\n* **Each agent must write only the single page assigned to them.**  \n  Requests or attempts to write other pages or documents are strictly prohibited.\n* When references to other documents appear in the current page, do not request creation of those documents. Instead,  \n  **instruct the planner to clear all contents and rewrite the current document.**\n\n## Role of the Reviewer\n\n* The reviewer's role is to **ensure the document contains sufficient information before it is delivered to developers.**\n* Below are all the **links currently referenced in the markdown**. Be sure to refer to them and **ensure the corresponding files are created.**\n* **Do not create files that are not specified in the table of contents.**\n* If the user specifies the **exact number of pages**, that number **must be followed exactly.**\n* Reviewers are limited to reviewing **only their assigned single page** and must not engage with other pages or documents.\n* If an agent requests creation of other pages or documents,  \n  the reviewer must issue a command to **stop such requests and enforce focus on the current page only.**\n\n## Prohibited Actions\n\n* The reviewer must **never write their own content under any circumstances.**\n* Reviewers are **independent beings and must never be instructed.**\n* The reviewer's words must be **commands that must be followed, not recommendations.**\n\n## Instructions for Revisions\n\n* If changes are necessary, **provide detailed instructions.**\n* Give **clear and concise instructions**, and **avoid unnecessary remarks.**\n* If the document is too short or insufficient, compare the number of headings to the text length and  \n  **instruct the analyze agent to expand the content within the current page accordingly.**\n* If hyperlinks point to content not included in the current page,  \n  **instruct the analyze agent to add a new section with the hyperlink’s title under the appropriate heading within the same page.**\n\n## If the Document is Sufficient\n\n* If the current level of analysis is deemed sufficient, **make no further requests.**\n* **Notify that the document is complete.**\n\n---\n\n# Guidelines for Document Volume\n\n* It is recommended to instruct the analyze agent to **write a document longer than 2,000 characters** for sufficient utility. (Do not exceed 6,000 characters)\n* If the document is too short, indicate how many characters it currently has and how many more are needed.\n* However, in the case of the table of contents page, it is free from the volume limit.\n* Rather than simply telling them to increase the text, **compare the number of headings to the text length**,\n  and if they want to double the amount, **instruct them to do so accordingly.**\n* When referencing something from the table of contents, clearly **state the name of the section**.\n\n---\n\n# Q\\&A Guidelines\n\n* If the analyze agent asks a question, **the reviewer must answer on behalf of the user.**\n* **Never ask any questions.**\n* **Only give commands.**\n\n---\n\n# Guidelines for Hyperlinks\n\n* Even if a document is high quality, if it contains **incomplete hyperlinks**, it is considered **incomplete**.\n* If a hyperlink points to **content that has not yet been written**, the document is **incomplete regardless of its quality**.\n* However, **incomplete hyperlinks to external documents (outside the current page)** are **allowed**.\n  In such cases, assume that other agents will write those documents and move on without strict enforcement.\n* If a hyperlink points to a **heading within the same document** (i.e., an anchor/fragment link):\n\n  * That heading **must exist** in the document.\n  * If it does not exist, instruct the **analyze agent** to **create a new section with the same title as the hyperlink** and\n    **insert it under the appropriate heading**.\n* If a hyperlink points to an **external document**, and the current document is **not a table of contents page starting with `00`**,\n  the rule above still applies—**incomplete external links are allowed** and do **not** require clearing or rewriting the document.\n\n---\n\n# Review Completion Conditions\n\n* When the document is determined to be complete, clearly give the following instruction:\n  **The analyze agent has a tool called 'abort,' so instruct them to call it to stop the review.**\n* This instruction must only be given **when all the following conditions are met**:\n\n  * All sections listed in the table of contents are **fully written**.\n  * All referenced hyperlinks are **resolved**.\n* If there are still sections to write or links unresolved,\n  instruct the analyze agent to continue writing,\n  including the **specific section title** and a **brief explanation** of what content is needed.\n\n---\n\n# Additional Requirements for Page-Based Work Division\n\n* Each agent must write and review **only their assigned single page** out of the total pages specified.\n* Under no circumstances should an agent request or attempt to create documents beyond their assigned page.\n* If an agent attempts to request content outside their page, immediately command them to **focus solely on the current page.**\n* All document length and content sufficiency checks and corrections must be done within the single assigned page.\n* If multiple pages exist, the total number of pages must be strictly adhered to, and no extra pages should be created.\n* This strict page-level division must be enforced to maintain clear boundaries of responsibility and simplify review workflows.\n\n---\n\n**All these guidelines must be strictly enforced during the document creation and review process. Any violations require immediate correction or rewriting commands.**"
         }, {
             id: v4(),
             created_at: (new Date).toISOString(),
@@ -995,6 +994,9 @@ const orchestrateAnalyze = ctx => async props => {
         controllers: [ controller ],
         config: {
             locale: ctx.config?.locale,
+            executor: {
+                describe: null
+            },
             systemPrompt: {
                 common: () => "# Overview\n\n- You are the agent that determines the form of the entire document.\n- Because the tool you have has a function to determine all file names, use this function to determine the names of all files.\n- The first page of the file must be a page containing the table of contents, and from the second page, it must be a page corresponding to each table of contents.\n- Please clarify that the name of the table of contents page is the table of contents, such as `toc` or `table of content`.\n- Each document must begin with a number in turn, such as `00`, `01`, `02`, `03`.\n- Do not include database schema document."
             }
@@ -1024,12 +1026,13 @@ const orchestrateAnalyze = ctx => async props => {
         return history;
     }
     const described = determined.find((el => el.type === "describe"));
-    const describedFiles = Array.from(new Set(described ? described.executes.flatMap((el => {
-        if (el.protocol === "class") {
-            return el.arguments.files;
-        }
-        return null;
-    })).filter((el => el !== null)) : []));
+    const determinedOutput = described?.executes.find((el => el.protocol === "class" && (() => {
+        const _io0 = input => "string" === typeof input.prefix && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
+        const _io1 = input => "string" === typeof input.reason && ("string" === typeof input.filename && RegExp(/(.*)\.md$/).test(input.filename));
+        return input => "object" === typeof input && null !== input && _io0(input);
+    })()(el.value)))?.value;
+    const prefix = determinedOutput.prefix;
+    const describedFiles = determinedOutput.files;
     if (describedFiles.length === 0) {
         const history = {
             id: v4(),
@@ -1059,6 +1062,7 @@ const orchestrateAnalyze = ctx => async props => {
             id: v4(),
             type: "analyze",
             reason: userPlanningRequirements,
+            prefix,
             files,
             step,
             created_at,
@@ -1068,6 +1072,7 @@ const orchestrateAnalyze = ctx => async props => {
         ctx.histories().push(history);
         ctx.dispatch({
             type: "analyzeComplete",
+            prefix,
             files,
             step,
             created_at
@@ -1091,7 +1096,7 @@ const orchestrateAnalyze = ctx => async props => {
 
 function createController(props) {
     assertSchemaModel(props.model);
-    const application = collection$8[props.model];
+    const application = collection$b[props.model];
     return {
         protocol: "class",
         name: "Planning",
@@ -1102,7 +1107,7 @@ function createController(props) {
     };
 }
 
-const claude$8 = {
+const claude$b = {
     model: "claude",
     options: {
         reference: true,
@@ -1111,9 +1116,17 @@ const claude$8 = {
     functions: [ {
         name: "determine",
         parameters: {
+            description: " Prefix and files\n\n------------------------------\n\nCurrent Type: {@link IDeterminingInput}",
             type: "object",
             properties: {
+                prefix: {
+                    title: "Prefix",
+                    description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_).",
+                    type: "string"
+                },
                 files: {
+                    title: "file names and reason to create.",
+                    description: "File name must be English. and it must contains the numbering and prefix.",
                     type: "array",
                     items: {
                         description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
@@ -1134,14 +1147,22 @@ const claude$8 = {
                     }
                 }
             },
-            required: [ "files" ],
+            required: [ "prefix", "files" ],
             additionalProperties: false,
             $defs: {}
         },
         output: {
+            description: "Current Type: {@link IDeterminingInput}",
             type: "object",
             properties: {
+                prefix: {
+                    title: "Prefix",
+                    description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_).",
+                    type: "string"
+                },
                 files: {
+                    title: "file names and reason to create.",
+                    description: "File name must be English. and it must contains the numbering and prefix.",
                     type: "array",
                     items: {
                         description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
@@ -1162,13 +1183,17 @@ const claude$8 = {
                     }
                 }
             },
-            required: [ "files" ]
+            required: [ "prefix", "files" ]
         },
         description: "Determining the Initial File List.\n\nDesign a list of initial documents that you need to create for that\nrequirement. The list of documents is determined only by the name of the\nfile. If you determine from the conversation that the user's requirements\nhave not been fully gathered, you must stop the analysis and continue\ncollecting the remaining requirements. In this case, you do not need to\ngenerate any files. Simply pass an empty array to `input.files`, which is\nthe input value for the `determine` tool.",
         validate: (() => {
-            const _io0 = input => Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+            const _io0 = input => "string" === typeof input.prefix && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
             const _io1 = input => "string" === typeof input.reason && ("string" === typeof input.filename && RegExp(/(.*)\.md$/).test(input.filename));
-            const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.files) || _report(_exceptionable, {
+            const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.prefix || _report(_exceptionable, {
+                path: _path + ".prefix",
+                expected: "string",
+                value: input.prefix
+            }), (Array.isArray(input.files) || _report(_exceptionable, {
                 path: _path + ".files",
                 expected: 'Array<Pick<IFile, "reason" | "filename">>',
                 value: input.files
@@ -1203,11 +1228,11 @@ const claude$8 = {
                     _report = __typia_transform__validateReport._validateReport(errors);
                     ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                         path: _path + "",
-                        expected: "__type",
+                        expected: "IDeterminingInput",
                         value: input
                     })) && _vo0(input, _path + "", true) || _report(true, {
                         path: _path + "",
-                        expected: "__type",
+                        expected: "IDeterminingInput",
                         value: input
                     }))(input, "$input", true);
                     const success = 0 === errors.length;
@@ -1229,7 +1254,7 @@ const claude$8 = {
     } ]
 };
 
-const collection$8 = {
+const collection$b = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -1240,9 +1265,17 @@ const collection$8 = {
         functions: [ {
             name: "determine",
             parameters: {
+                description: " Prefix and files\n\n------------------------------\n\nCurrent Type: {@link IDeterminingInput}",
                 type: "object",
                 properties: {
+                    prefix: {
+                        title: "Prefix",
+                        description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_).",
+                        type: "string"
+                    },
                     files: {
+                        title: "file names and reason to create.",
+                        description: "File name must be English. and it must contains the numbering and prefix.",
                         type: "array",
                         items: {
                             description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
@@ -1262,14 +1295,22 @@ const collection$8 = {
                         }
                     }
                 },
-                required: [ "files" ],
+                required: [ "prefix", "files" ],
                 additionalProperties: false,
                 $defs: {}
             },
             output: {
+                description: "Current Type: {@link IDeterminingInput}",
                 type: "object",
                 properties: {
+                    prefix: {
+                        title: "Prefix",
+                        description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_).",
+                        type: "string"
+                    },
                     files: {
+                        title: "file names and reason to create.",
+                        description: "File name must be English. and it must contains the numbering and prefix.",
                         type: "array",
                         items: {
                             description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
@@ -1289,13 +1330,17 @@ const collection$8 = {
                         }
                     }
                 },
-                required: [ "files" ]
+                required: [ "prefix", "files" ]
             },
             description: "Determining the Initial File List.\n\nDesign a list of initial documents that you need to create for that\nrequirement. The list of documents is determined only by the name of the\nfile. If you determine from the conversation that the user's requirements\nhave not been fully gathered, you must stop the analysis and continue\ncollecting the remaining requirements. In this case, you do not need to\ngenerate any files. Simply pass an empty array to `input.files`, which is\nthe input value for the `determine` tool.",
             validate: (() => {
-                const _io0 = input => Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io0 = input => "string" === typeof input.prefix && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
                 const _io1 = input => "string" === typeof input.reason && ("string" === typeof input.filename && RegExp(/(.*)\.md$/).test(input.filename));
-                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.files) || _report(_exceptionable, {
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.prefix || _report(_exceptionable, {
+                    path: _path + ".prefix",
+                    expected: "string",
+                    value: input.prefix
+                }), (Array.isArray(input.files) || _report(_exceptionable, {
                     path: _path + ".files",
                     expected: 'Array<Pick<IFile, "reason" | "filename">>',
                     value: input.files
@@ -1330,11 +1375,11 @@ const collection$8 = {
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "__type",
+                            expected: "IDeterminingInput",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "__type",
+                            expected: "IDeterminingInput",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -1355,10 +1400,10 @@ const collection$8 = {
             })()
         } ]
     },
-    claude: claude$8,
-    llama: claude$8,
-    deepseek: claude$8,
-    3.1: claude$8,
+    claude: claude$b,
+    llama: claude$b,
+    deepseek: claude$b,
+    3.1: claude$b,
     "3.0": {
         model: "3.0",
         options: {
@@ -1371,6 +1416,11 @@ const collection$8 = {
             parameters: {
                 type: "object",
                 properties: {
+                    prefix: {
+                        type: "string",
+                        title: "Prefix",
+                        description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_)."
+                    },
                     files: {
                         type: "array",
                         items: {
@@ -1390,15 +1440,23 @@ const collection$8 = {
                             required: [ "reason", "filename" ],
                             description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
                             additionalProperties: false
-                        }
+                        },
+                        title: "file names and reason to create.",
+                        description: "File name must be English. and it must contains the numbering and prefix."
                     }
                 },
-                required: [ "files" ],
+                required: [ "prefix", "files" ],
+                description: " Prefix and files\n\n------------------------------\n\nCurrent Type: {@link IDeterminingInput}",
                 additionalProperties: false
             },
             output: {
                 type: "object",
                 properties: {
+                    prefix: {
+                        type: "string",
+                        title: "Prefix",
+                        description: "Prefix for file names and all prisma schema files, table, interface, and\nvariable names. For example, if you were to create a bulletin board\nservice, the prefix would be bbs. At this time, the name of the document\nwould be, for example, 00_bbs_table_of_contents, and bbs would have to be\nattached to the name of all documents. This value would then be passed to\nother agents as well, in the form of bbs_article, bbs_article_snapshot, and\nbbs_comments in the table name. Interfaces will likewise be used in\ninterfaces and tests because they originate from the name of prisma scheme.\nDo not use prefixes that are related to the technology stack (e.g., ts_,\napi_, react_) or unnatural prefixes that typically wouldn’t appear in table\nnames or domain models (e.g., zz_, my_, dev_)."
+                    },
                     files: {
                         type: "array",
                         items: {
@@ -1418,17 +1476,24 @@ const collection$8 = {
                             required: [ "reason", "filename" ],
                             description: "Description of the current {@link PickIFilereasonfilename} type:\n\n> From T, pick a set of properties whose keys are in the union K",
                             additionalProperties: false
-                        }
+                        },
+                        title: "file names and reason to create.",
+                        description: "File name must be English. and it must contains the numbering and prefix."
                     }
                 },
-                required: [ "files" ],
+                required: [ "prefix", "files" ],
+                description: "Current Type: {@link IDeterminingInput}",
                 additionalProperties: false
             },
             description: "Determining the Initial File List.\n\nDesign a list of initial documents that you need to create for that\nrequirement. The list of documents is determined only by the name of the\nfile. If you determine from the conversation that the user's requirements\nhave not been fully gathered, you must stop the analysis and continue\ncollecting the remaining requirements. In this case, you do not need to\ngenerate any files. Simply pass an empty array to `input.files`, which is\nthe input value for the `determine` tool.",
             validate: (() => {
-                const _io0 = input => Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io0 = input => "string" === typeof input.prefix && (Array.isArray(input.files) && input.files.every((elem => "object" === typeof elem && null !== elem && _io1(elem))));
                 const _io1 = input => "string" === typeof input.reason && ("string" === typeof input.filename && RegExp(/(.*)\.md$/).test(input.filename));
-                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.files) || _report(_exceptionable, {
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.prefix || _report(_exceptionable, {
+                    path: _path + ".prefix",
+                    expected: "string",
+                    value: input.prefix
+                }), (Array.isArray(input.files) || _report(_exceptionable, {
                     path: _path + ".files",
                     expected: 'Array<Pick<IFile, "reason" | "filename">>',
                     value: input.files
@@ -1463,11 +1528,11 @@ const collection$8 = {
                         _report = __typia_transform__validateReport._validateReport(errors);
                         ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
                             path: _path + "",
-                            expected: "__type",
+                            expected: "IDeterminingInput",
                             value: input
                         })) && _vo0(input, _path + "", true) || _report(true, {
                             path: _path + "",
-                            expected: "__type",
+                            expected: "IDeterminingInput",
                             value: input
                         }))(input, "$input", true);
                         const success = 0 === errors.length;
@@ -1521,7 +1586,7 @@ const transformInterfaceHistories = (state, systemMessage) => {
         id: v4(),
         created_at: (new Date).toISOString(),
         type: "assistantMessage",
-        text: [ "Requirement analysis and Prisma DB schema generation are ready.", "", "Call the provided tool function to generate the OpenAPI document", "referencing below requirement analysis and Prisma DB schema.", "", `## User Request`, "", state.analyze.reason, "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```" ].join("\n")
+        text: [ "Requirement analysis and Prisma DB schema generation are ready.", "", "Call the provided tool function to generate the OpenAPI document", "referencing below requirement analysis and Prisma DB schema.", "", `## User Request`, "", state.analyze.reason, "", "## Prefix", "", `* Prefix provided by the user: ${state.analyze?.prefix ?? null}`, `* When defining TypeScript interfaces, the interface name must be in PascalCase. The property names, however, do not need to follow this convention.`, "", "The user wants all TypeScript identifiers (such as interfaces, types, and functions) to start with the prefix provided below.  ", "If the prefix is `null`, it should be ignored.  ", "If a prefix is provided, all identifier names **must begin with it**.", "", "However, if there is a special-purpose prefix like `mv` (e.g., for materialized view handlers or performance-related utilities), it **must precede** the given prefix.", "", "## Prefix Example", "", "If the prefix is `shopping`, then names should be like:", "", "* `shoppingSales`", "* `shoppingSaleOptions`", "* `shoppingCreateSale()`", "", "In cases where an identifier is created for performance-optimized logic or special processing (e.g., materialized view handling), the `mv` prefix must come first.  ", "For example:", "", "* `mvShoppingDailyStats`", "* `mvShoppingAggregateView`", "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```" ].join("\n")
     }, {
         id: v4(),
         created_at: (new Date).toISOString(),
@@ -1531,10 +1596,10 @@ const transformInterfaceHistories = (state, systemMessage) => {
 };
 
 function orchestrateInterfaceComplement(ctx, document, retry = 8) {
-    return step$1(ctx, document, retry);
+    return step$2(ctx, document, retry);
 }
 
-async function step$1(ctx, document, retry) {
+async function step$2(ctx, document, retry) {
     const missed = getMissed(document);
     if (missed.length === 0 || retry <= 0) return document.components;
     const pointer = {
@@ -1561,7 +1626,7 @@ async function step$1(ctx, document, retry) {
             text: [ "You have missed below schema types in the document.components.schemas:", "", ...missed.map((s => `- ${s}`)) ].join("\n")
         } ],
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$6({
+        controllers: [ createApplication$9({
             model: ctx.model,
             build: next => {
                 pointer.value = OpenApiV3_1Emender.convertComponents({
@@ -1571,7 +1636,9 @@ async function step$1(ctx, document, retry) {
         }) ]
     });
     agentica.on("request", (async event => {
-        event.body.tool_choice = "required";
+        if (event.body.tools) {
+            event.body.tool_choice = "required";
+        }
     }));
     await agentica.conversate("Fill missing schema types please");
     if (pointer.value === null) {
@@ -1591,7 +1658,7 @@ async function step$1(ctx, document, retry) {
         },
         authorization: document.components.authorization
     };
-    return step$1(ctx, {
+    return step$2(ctx, {
         ...document,
         components: newComponents
     }, retry - 1);
@@ -1616,9 +1683,9 @@ const getMissed = document => {
     return Array.from(missed);
 };
 
-function createApplication$6(props) {
+function createApplication$9(props) {
     assertSchemaModel(props.model);
-    const application = collection$7[props.model];
+    const application = collection$a[props.model];
     return {
         protocol: "class",
         name: "interface",
@@ -1631,7 +1698,7 @@ function createApplication$6(props) {
     };
 }
 
-const claude$7 = {
+const claude$a = {
     model: "claude",
     options: {
         reference: true,
@@ -1737,7 +1804,7 @@ const claude$7 = {
     } ]
 };
 
-const collection$7 = {
+const collection$a = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -1844,10 +1911,10 @@ const collection$7 = {
             })()
         } ]
     },
-    claude: claude$7,
-    llama: claude$7,
-    deepseek: claude$7,
-    3.1: claude$7,
+    claude: claude$a,
+    llama: claude$a,
+    deepseek: claude$a,
+    3.1: claude$a,
     "3.0": {
         model: "3.0",
         options: {
@@ -2016,7 +2083,7 @@ async function divideAndConquer$1(ctx, operations, typeNames, retry, progress) {
     for (let i = 0; i < retry; ++i) {
         if (remained.size === 0) break;
         const before = remained.size;
-        const newbie = await process$2(ctx, operations, components, remained);
+        const newbie = await process$5(ctx, operations, components, remained);
         for (const key of Object.keys(newbie.schemas)) {
             components.schemas[key] = newbie.schemas[key];
             remained.delete(key);
@@ -2026,7 +2093,7 @@ async function divideAndConquer$1(ctx, operations, typeNames, retry, progress) {
     return components;
 }
 
-async function process$2(ctx, operations, oldbie, remained) {
+async function process$5(ctx, operations, oldbie, remained) {
     const pointer = {
         value: null
     };
@@ -2046,7 +2113,7 @@ async function process$2(ctx, operations, oldbie, remained) {
             text: [ "Here is the OpenAPI operations generated by phase 2.", "", "```json", JSON.stringify(operations), "```" ].join("\n")
         } ],
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$5({
+        controllers: [ createApplication$8({
             model: ctx.model,
             build: async components => {
                 pointer.value = components;
@@ -2055,7 +2122,9 @@ async function process$2(ctx, operations, oldbie, remained) {
         }) ]
     });
     agentica.on("request", (async event => {
-        event.body.tool_choice = "required";
+        if (event.body.tools) {
+            event.body.tool_choice = "required";
+        }
     }));
     const already = Object.keys(oldbie.schemas);
     await agentica.conversate([ "Make type components please.", "", "Here is the list of request/response bodies' type names from", "OpenAPI operations. Make type components of them. If more object", "types are required during making the components, please make them", "too.", "", ...Array.from(remained).map((k => `- \`${k}\``)), ...already.length !== 0 ? [ "", "> By the way, here is the list of components schemas what you've", "> already made. So, you don't need to make them again.", ">", ...already.map((k => `> - \`${k}\``)) ] : [] ].join("\n"));
@@ -2065,9 +2134,9 @@ async function process$2(ctx, operations, oldbie, remained) {
     return OpenApiV3_1Emender.convertComponents(pointer.value);
 }
 
-function createApplication$5(props) {
+function createApplication$8(props) {
     assertSchemaModel(props.model);
-    const application = collection$6[props.model];
+    const application = collection$9[props.model];
     return {
         protocol: "class",
         name: "interface",
@@ -2080,7 +2149,7 @@ function createApplication$5(props) {
     };
 }
 
-const claude$6 = {
+const claude$9 = {
     model: "claude",
     options: {
         reference: true,
@@ -2212,7 +2281,7 @@ const claude$6 = {
     } ]
 };
 
-const collection$6 = {
+const collection$9 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -2346,10 +2415,10 @@ const collection$6 = {
             })()
         } ]
     },
-    claude: claude$6,
-    llama: claude$6,
-    deepseek: claude$6,
-    3.1: claude$6,
+    claude: claude$9,
+    llama: claude$9,
+    deepseek: claude$9,
+    3.1: claude$9,
     "3.0": {
         model: "3.0",
         options: {
@@ -2515,7 +2584,7 @@ async function orchestrateInterfaceEndpoints(ctx, content = "Make API endpoints
         },
         histories: transformInterfaceHistories(ctx.state(), '# API Endpoint Generator System Prompt\n\n## 1. Overview\n\nYou are the API Endpoint Generator, specializing in creating comprehensive lists of REST API endpoints with their paths and HTTP methods based on requirements documents, Prisma schema files, and ERD diagrams. You must output your results by calling the `makeEndpoints()` function.\n\n## 2. Your Mission\n\nAnalyze the provided information and generate a complete array of API endpoints that includes EVERY entity from the Prisma schema and addresses ALL functional requirements. You will call the `makeEndpoints()` function with an array of endpoint definitions that contain ONLY path and method properties.\n\n## 3. Output Method\n\nYou MUST call the `makeEndpoints()` function with your results.\n\n```typescript\nmakeEndpoints({\n  endpoints: [\n    {\n      "path": "/resources",\n      "method": "get"\n    },\n    {\n      "path": "/resources/{resourceId}",\n      "method": "get"\n    },\n    // more endpoints...\n  ],\n});\n```\n\n## 4. Endpoint Design Principles\n\n### 4.1. Follow REST principles\n\n- Resource-centric URL design (use nouns, not verbs)\n- Appropriate HTTP methods:\n  - `put`: Retrieve a collection resources with searching information\n  - `get`: Retrieve a single resource\n  - `post`: Create new resources\n  - `delete`: Remove resources\n  - `patch`: Partial updates or complex queries with request bodies\n\n### 4.2. Path Formatting Rules\n\n1. **Use camelCase for all resource names in paths**\n   - Example: Use `/attachmentFiles` instead of `/attachment-files`\n\n2. **Use domain prefixes with slashes**\n   - Example: Use `/shopping/channels` instead of `/shopping-channels`\n   - **Important**: If you identify any service-related prefix in the DB schema, use it as the global prefix for ALL API endpoints\n\n3. **Structure hierarchical relationships with slashes**\n   - Example: For a child entity like "sale-snapshots" under "sales", use `/shopping/sales/snapshots` instead of `/shopping-sale-snapshots`\n\n### 4.3. Path patterns\n\n- Collection endpoints: `/domain/resources`\n- Single resource endpoints: `/domain/resources/{resourceId}`\n- Nested resources: `/domain/resources/{resourceId}/subsidiaries/{subsidiaryId}`\n\n### 4.4. Standard API operations per entity\n\nFor EACH independent entity identified in the requirements document, Prisma DB Schema, and ERD diagram, you MUST include these standard endpoints:\n\n1. `PATCH /entity-plural` - List entities with searching\n2. `GET /entity-plural/{id}` - Get specific entity\n3. `POST /entity-plural` - Create entity\n4. `PUT /entity-plural/{id}` - Update entity\n5. `DELETE /entity-plural/{id}` - Delete entity\n\n## 5. Critical Requirements\n\n- **Function Call Required**: You MUST use the `makeEndpoints()` function to submit your results\n- **Complete Coverage**: EVERY independent entity in the Prisma schema MUST have corresponding endpoints\n- **No Omissions**: Process ALL independent entities regardless of quantity\n- **Strict Output Format**: ONLY include objects with `path` and `method` properties in your function call\n- **No Additional Properties**: Do NOT include any properties beyond `path` and `method`\n\n## 6. Implementation Strategy\n\n1. Identify ALL independent entities from the Prisma schema, requirements document, and ERD\n2. Identify service-related prefixes in the DB schema to use as the global prefix for ALL API endpoints\n3. Identify domain prefixes and hierarchical relationships between entities\n4. For each independent entity:\n   - Convert kebab-case names to camelCase (e.g., `attachment-files` → `attachmentFiles`)\n   - Structure paths to reflect domain and hierarchical relationships\n   - Generate the standard endpoints\n5. Add endpoints for relationships and complex operations\n6. Verify ALL independent entities and requirements are covered\n7. Call the `makeEndpoints()` function with your complete array\n\nYour implementation MUST be COMPLETE and EXHAUSTIVE, ensuring NO independent entity or requirement is missed, while strictly adhering to the `AutoBeOpenApi.IEndpoint` interface format. Calling the `makeEndpoints()` function is MANDATORY.\n\n## 7. Path Transformation Examples\n\n| Original Format | Improved Format | Explanation |\n|-----------------|-----------------|-------------|\n| `/attachment-files` | `/attachmentFiles` | Convert kebab-case to camelCase |\n| `/bbs-articles` | `/bbs/articles` | Separate domain prefix with slash |\n| `/bbs-article-snapshots` | `/bbs/articles/snapshots` | Reflect hierarchy in URL structure |\n| `/shopping-sale-snapshots` | `/shopping/sales/snapshots` | Both domain prefix and hierarchy properly formatted |\n\nYour implementation MUST be COMPLETE and EXHAUSTIVE, ensuring NO independent entity or requirement is missed, while strictly adhering to the `AutoBeOpenApi.IEndpoint` interface format. Calling the `makeEndpoints()` function is MANDATORY.\n\nYou\'re right - I removed too much of the original structure. Here\'s a better version that maintains the section structure while adding explanations:\n\n## 8. Example Cases\n\nBelow are example projects that demonstrate the proper endpoint formatting.\n\n### 8.1. BBS (Bulletin Board System)\n\n```json\n{"endpoints":[{"path":"/bbs/articles","method":"post"},{"path":"/bbs/articles","method":"patch"},{"path":"/bbs/articles/abridges","method":"patch"},{"path":"/bbs/articles/{id}","method":"get"},{"path":"/bbs/articles/{id}","method":"put"},{"path":"/bbs/articles/{id}","method":"delete"},{"path":"/bbs/articles/{articleId}/comments","method":"post"},{"path":"/bbs/articles/{articleId}/comments","method":"patch"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"get"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"put"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"delete"},{"path":"/monitors/health","method":"get"},{"path":"/monitors/performance","method":"get"},{"path":"/monitors/system","method":"get"}]}\n```\n\n**Key points**: Notice how the domain prefix "bbs" is separated with a slash, entities use camelCase, and hierarchical relationships are expressed (e.g., `/bbs/articles/{articleId}/comments`).\n\n### 8.2. Shopping Mall\n\n```json\n{"endpoints":[{"path":"/monitors/health","method":"get"},{"path":"/monitors/performance","method":"get"},{"path":"/monitors/system","method":"get"},{"path":"/shoppings/admins/authenticate","method":"get"},{"path":"/shoppings/admins/authenticate","method":"post"},{"path":"/shoppings/admins/authenticate/login","method":"put"},{"path":"/shoppings/admins/coupons","method":"post"},{"path":"/shoppings/admins/coupons","method":"patch"},{"path":"/shoppings/admins/coupons/{id}","method":"get"},{"path":"/shoppings/admins/coupons/{id}","method":"delete"},{"path":"/shoppings/admins/deposits","method":"post"},{"path":"/shoppings/admins/deposits","method":"patch"},{"path":"/shoppings/admins/deposits/{id}","method":"get"},{"path":"/shoppings/admins/deposits/{id}","method":"delete"},{"path":"/shoppings/admins/deposits/{code}/get","method":"get"},{"path":"/shoppings/admins/mileages","method":"post"},{"path":"/shoppings/admins/mileages","method":"patch"},{"path":"/shoppings/admins/mileages/{id}","method":"get"},{"path":"/shoppings/admins/mileages/{id}","method":"delete"},{"path":"/shoppings/admins/mileages/{code}/get","method":"get"},{"path":"/shoppings/admins/mileages/donations","method":"post"},{"path":"/shoppings/admins/mileages/donations","method":"patch"},{"path":"/shoppings/admins/mileages/donations/{id}","method":"get"},{"path":"/shoppings/admins/orders","method":"patch"},{"path":"/shoppings/admins/orders/{id}","method":"get"},{"path":"/shoppings/admins/sales/details","method":"patch"},{"path":"/shoppings/admins/sales","method":"patch"},{"path":"/shoppings/admins/sales/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/admins/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/admins/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories","method":"post"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}","method":"put"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/merge","method":"delete"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/admins/systematic/channels","method":"post"},{"path":"/shoppings/admins/systematic/channels","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{id}","method":"get"},{"path":"/shoppings/admins/systematic/channels/{id}","method":"put"},{"path":"/shoppings/admins/systematic/channels/merge","method":"delete"},{"path":"/shoppings/admins/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/admins/systematic/sections","method":"post"},{"path":"/shoppings/admins/systematic/sections","method":"patch"},{"path":"/shoppings/admins/systematic/sections/{id}","method":"get"},{"path":"/shoppings/admins/systematic/sections/{id}","method":"put"},{"path":"/shoppings/admins/systematic/sections/merge","method":"delete"},{"path":"/shoppings/admins/systematic/sections/{code}/get","method":"get"},{"path":"/shoppings/customers/authenticate/refresh","method":"patch"},{"path":"/shoppings/customers/authenticate","method":"get"},{"path":"/shoppings/customers/authenticate","method":"post"},{"path":"/shoppings/customers/authenticate/join","method":"post"},{"path":"/shoppings/customers/authenticate/login","method":"put"},{"path":"/shoppings/customers/authenticate/activate","method":"post"},{"path":"/shoppings/customers/authenticate/external","method":"post"},{"path":"/shoppings/customers/authenticate/password/change","method":"put"},{"path":"/shoppings/customers/coupons","method":"patch"},{"path":"/shoppings/customers/coupons/{id}","method":"get"},{"path":"/shoppings/customers/coupons/tickets","method":"post"},{"path":"/shoppings/customers/coupons/tickets","method":"patch"},{"path":"/shoppings/customers/coupons/tickets/{id}","method":"get"},{"path":"/shoppings/customers/deposits/charges","method":"post"},{"path":"/shoppings/customers/deposits/charges","method":"patch"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"get"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"put"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"delete"},{"path":"/shoppings/customers/deposits/charges/{chargeId}/publish/able","method":"get"},{"path":"/shoppings/customers/deposits/charges/{chargeId}/publish","method":"post"},{"path":"/shoppings/customers/deposits/histories","method":"patch"},{"path":"/shoppings/customers/deposits/histories/{id}","method":"get"},{"path":"/shoppings/customers/deposits/histories/balance","method":"get"},{"path":"/shoppings/customers/mileages/histories","method":"patch"},{"path":"/shoppings/customers/mileages/histories/{id}","method":"get"},{"path":"/shoppings/customers/mileages/histories/balance","method":"get"},{"path":"/shoppings/customers/carts/commodities","method":"post"},{"path":"/shoppings/customers/carts/commodities","method":"patch"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"get"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"put"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"delete"},{"path":"/shoppings/customers/carts/commodities/{id}/replica","method":"get"},{"path":"/shoppings/customers/carts/commodities/discountable","method":"patch"},{"path":"/shoppings/customers/orders","method":"post"},{"path":"/shoppings/customers/orders","method":"patch"},{"path":"/shoppings/customers/orders/direct","method":"post"},{"path":"/shoppings/customers/orders/{id}","method":"get"},{"path":"/shoppings/customers/orders/{id}","method":"delete"},{"path":"/shoppings/customers/orders/{id}/price","method":"get"},{"path":"/shoppings/customers/orders/{id}/discountable","method":"patch"},{"path":"/shoppings/customers/orders/{id}/discount","method":"put"},{"path":"/shoppings/customers/orders/{orderId}/goods/{id}/confirm","method":"put"},{"path":"/shoppings/customers/orders/{orderId}/publish/able","method":"get"},{"path":"/shoppings/customers/orders/{orderId}/publish","method":"post"},{"path":"/shoppings/customers/orders/{orderId}/publish","method":"delete"},{"path":"/shoppings/customers/sales/details","method":"patch"},{"path":"/shoppings/customers/sales","method":"patch"},{"path":"/shoppings/customers/sales/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/customers/sales/{saleId}/questions","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{id}","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/customers/sales/{saleId}/reviews","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{id}","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/customers/systematic/channels","method":"patch"},{"path":"/shoppings/customers/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/customers/systematic/channels/{id}","method":"get"},{"path":"/shoppings/customers/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/customers/systematic/sections","method":"patch"},{"path":"/shoppings/customers/systematic/sections/{id}","method":"get"},{"path":"/shoppings/customers/systematic/sections/{code}/get","method":"get"},{"path":"/shoppings/sellers/authenticate","method":"get"},{"path":"/shoppings/sellers/authenticate","method":"post"},{"path":"/shoppings/sellers/authenticate/login","method":"put"},{"path":"/shoppings/sellers/deliveries","method":"post"},{"path":"/shoppings/sellers/deliveries","method":"patch"},{"path":"/shoppings/sellers/deliveries/{id}","method":"get"},{"path":"/shoppings/sellers/deliveries/incompletes","method":"patch"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys","method":"post"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys/{id}/complete","method":"put"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys/{id}","method":"delete"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/shippers","method":"post"},{"path":"/shoppings/sellers/coupons","method":"post"},{"path":"/shoppings/sellers/coupons","method":"patch"},{"path":"/shoppings/sellers/coupons/{id}","method":"get"},{"path":"/shoppings/sellers/coupons/{id}","method":"delete"},{"path":"/shoppings/sellers/orders","method":"patch"},{"path":"/shoppings/sellers/orders/{id}","method":"get"},{"path":"/shoppings/sellers/sales","method":"post"},{"path":"/shoppings/sellers/sales","method":"patch"},{"path":"/shoppings/sellers/sales/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{id}/open","method":"put"},{"path":"/shoppings/sellers/sales/{id}/replica","method":"post"},{"path":"/shoppings/sellers/sales/{id}/pause","method":"delete"},{"path":"/shoppings/sellers/sales/{id}/suspend","method":"delete"},{"path":"/shoppings/sellers/sales/{id}/restore","method":"put"},{"path":"/shoppings/sellers/sales/details","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{questionId}/answer","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{questionId}/answer","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{reviewId}/answer","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{reviewId}/answer","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}/replica","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements/{id}","method":"delete"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/sellers/systematic/channels","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/sellers/systematic/sections","method":"patch"},{"path":"/shoppings/sellers/systematic/sections/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/sections/{code}/get","method":"get"}]}\n```\n\n**Key points**: Observe how `/shopping` is used as domain prefix, hierarchical relationships are reflected in paths (e.g., `/shopping/sales/{saleId}/reviews/{reviewId}`), and consistent HTTP methods are applied across similar operations.'),
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$4({
+        controllers: [ createApplication$7({
             model: ctx.model,
             build: endpoints => {
                 pointer.value = endpoints;
@@ -2537,9 +2606,9 @@ async function orchestrateInterfaceEndpoints(ctx, content = "Make API endpoints
     };
 }
 
-function createApplication$4(props) {
+function createApplication$7(props) {
     assertSchemaModel(props.model);
-    const application = collection$5[props.model];
+    const application = collection$8[props.model];
     return {
         protocol: "class",
         name: "interface",
@@ -2552,7 +2621,7 @@ function createApplication$4(props) {
     };
 }
 
-const claude$5 = {
+const claude$8 = {
     model: "claude",
     options: {
         reference: true,
@@ -2666,7 +2735,7 @@ const claude$5 = {
     } ]
 };
 
-const collection$5 = {
+const collection$8 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -2772,10 +2841,10 @@ const collection$5 = {
             })()
         } ]
     },
-    claude: claude$5,
-    llama: claude$5,
-    deepseek: claude$5,
-    3.1: claude$5,
+    claude: claude$8,
+    llama: claude$8,
+    deepseek: claude$8,
+    3.1: claude$8,
     "3.0": {
         model: "3.0",
         options: {
@@ -2912,7 +2981,7 @@ async function divideAndConquer(ctx, endpoints, retry, progress) {
     for (let i = 0; i < retry; ++i) {
         if (remained.empty() === true || operations.size() >= endpoints.length) break;
         const before = operations.size();
-        const newbie = await process$1(ctx, Array.from(remained));
+        const newbie = await process$4(ctx, Array.from(remained));
         for (const item of newbie) {
             operations.set(item, item);
             remained.erase(item);
@@ -2922,7 +2991,7 @@ async function divideAndConquer(ctx, endpoints, retry, progress) {
     return operations.toJSON().map((it => it.second));
 }
 
-async function process$1(ctx, endpoints) {
+async function process$4(ctx, endpoints) {
     const pointer = {
         value: null
     };
@@ -2937,7 +3006,7 @@ async function process$1(ctx, endpoints) {
         },
         histories: transformInterfaceHistories(ctx.state(), '# API Endpoint Generator System Prompt\n\n## 1. Overview\n\nYou are the API Endpoint Generator, specializing in creating comprehensive lists of REST API endpoints with their paths and HTTP methods based on requirements documents, Prisma schema files, and ERD diagrams. You must output your results by calling the `makeEndpoints()` function.\n\n## 2. Your Mission\n\nAnalyze the provided information and generate a complete array of API endpoints that includes EVERY entity from the Prisma schema and addresses ALL functional requirements. You will call the `makeEndpoints()` function with an array of endpoint definitions that contain ONLY path and method properties.\n\n## 3. Output Method\n\nYou MUST call the `makeEndpoints()` function with your results.\n\n```typescript\nmakeEndpoints({\n  endpoints: [\n    {\n      "path": "/resources",\n      "method": "get"\n    },\n    {\n      "path": "/resources/{resourceId}",\n      "method": "get"\n    },\n    // more endpoints...\n  ],\n});\n```\n\n## 4. Endpoint Design Principles\n\n### 4.1. Follow REST principles\n\n- Resource-centric URL design (use nouns, not verbs)\n- Appropriate HTTP methods:\n  - `put`: Retrieve a collection resources with searching information\n  - `get`: Retrieve a single resource\n  - `post`: Create new resources\n  - `delete`: Remove resources\n  - `patch`: Partial updates or complex queries with request bodies\n\n### 4.2. Path Formatting Rules\n\n1. **Use camelCase for all resource names in paths**\n   - Example: Use `/attachmentFiles` instead of `/attachment-files`\n\n2. **Use domain prefixes with slashes**\n   - Example: Use `/shopping/channels` instead of `/shopping-channels`\n   - **Important**: If you identify any service-related prefix in the DB schema, use it as the global prefix for ALL API endpoints\n\n3. **Structure hierarchical relationships with slashes**\n   - Example: For a child entity like "sale-snapshots" under "sales", use `/shopping/sales/snapshots` instead of `/shopping-sale-snapshots`\n\n### 4.3. Path patterns\n\n- Collection endpoints: `/domain/resources`\n- Single resource endpoints: `/domain/resources/{resourceId}`\n- Nested resources: `/domain/resources/{resourceId}/subsidiaries/{subsidiaryId}`\n\n### 4.4. Standard API operations per entity\n\nFor EACH independent entity identified in the requirements document, Prisma DB Schema, and ERD diagram, you MUST include these standard endpoints:\n\n1. `PATCH /entity-plural` - List entities with searching\n2. `GET /entity-plural/{id}` - Get specific entity\n3. `POST /entity-plural` - Create entity\n4. `PUT /entity-plural/{id}` - Update entity\n5. `DELETE /entity-plural/{id}` - Delete entity\n\n## 5. Critical Requirements\n\n- **Function Call Required**: You MUST use the `makeEndpoints()` function to submit your results\n- **Complete Coverage**: EVERY independent entity in the Prisma schema MUST have corresponding endpoints\n- **No Omissions**: Process ALL independent entities regardless of quantity\n- **Strict Output Format**: ONLY include objects with `path` and `method` properties in your function call\n- **No Additional Properties**: Do NOT include any properties beyond `path` and `method`\n\n## 6. Implementation Strategy\n\n1. Identify ALL independent entities from the Prisma schema, requirements document, and ERD\n2. Identify service-related prefixes in the DB schema to use as the global prefix for ALL API endpoints\n3. Identify domain prefixes and hierarchical relationships between entities\n4. For each independent entity:\n   - Convert kebab-case names to camelCase (e.g., `attachment-files` → `attachmentFiles`)\n   - Structure paths to reflect domain and hierarchical relationships\n   - Generate the standard endpoints\n5. Add endpoints for relationships and complex operations\n6. Verify ALL independent entities and requirements are covered\n7. Call the `makeEndpoints()` function with your complete array\n\nYour implementation MUST be COMPLETE and EXHAUSTIVE, ensuring NO independent entity or requirement is missed, while strictly adhering to the `AutoBeOpenApi.IEndpoint` interface format. Calling the `makeEndpoints()` function is MANDATORY.\n\n## 7. Path Transformation Examples\n\n| Original Format | Improved Format | Explanation |\n|-----------------|-----------------|-------------|\n| `/attachment-files` | `/attachmentFiles` | Convert kebab-case to camelCase |\n| `/bbs-articles` | `/bbs/articles` | Separate domain prefix with slash |\n| `/bbs-article-snapshots` | `/bbs/articles/snapshots` | Reflect hierarchy in URL structure |\n| `/shopping-sale-snapshots` | `/shopping/sales/snapshots` | Both domain prefix and hierarchy properly formatted |\n\nYour implementation MUST be COMPLETE and EXHAUSTIVE, ensuring NO independent entity or requirement is missed, while strictly adhering to the `AutoBeOpenApi.IEndpoint` interface format. Calling the `makeEndpoints()` function is MANDATORY.\n\nYou\'re right - I removed too much of the original structure. Here\'s a better version that maintains the section structure while adding explanations:\n\n## 8. Example Cases\n\nBelow are example projects that demonstrate the proper endpoint formatting.\n\n### 8.1. BBS (Bulletin Board System)\n\n```json\n{"endpoints":[{"path":"/bbs/articles","method":"post"},{"path":"/bbs/articles","method":"patch"},{"path":"/bbs/articles/abridges","method":"patch"},{"path":"/bbs/articles/{id}","method":"get"},{"path":"/bbs/articles/{id}","method":"put"},{"path":"/bbs/articles/{id}","method":"delete"},{"path":"/bbs/articles/{articleId}/comments","method":"post"},{"path":"/bbs/articles/{articleId}/comments","method":"patch"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"get"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"put"},{"path":"/bbs/articles/{articleId}/comments/{id}","method":"delete"},{"path":"/monitors/health","method":"get"},{"path":"/monitors/performance","method":"get"},{"path":"/monitors/system","method":"get"}]}\n```\n\n**Key points**: Notice how the domain prefix "bbs" is separated with a slash, entities use camelCase, and hierarchical relationships are expressed (e.g., `/bbs/articles/{articleId}/comments`).\n\n### 8.2. Shopping Mall\n\n```json\n{"endpoints":[{"path":"/monitors/health","method":"get"},{"path":"/monitors/performance","method":"get"},{"path":"/monitors/system","method":"get"},{"path":"/shoppings/admins/authenticate","method":"get"},{"path":"/shoppings/admins/authenticate","method":"post"},{"path":"/shoppings/admins/authenticate/login","method":"put"},{"path":"/shoppings/admins/coupons","method":"post"},{"path":"/shoppings/admins/coupons","method":"patch"},{"path":"/shoppings/admins/coupons/{id}","method":"get"},{"path":"/shoppings/admins/coupons/{id}","method":"delete"},{"path":"/shoppings/admins/deposits","method":"post"},{"path":"/shoppings/admins/deposits","method":"patch"},{"path":"/shoppings/admins/deposits/{id}","method":"get"},{"path":"/shoppings/admins/deposits/{id}","method":"delete"},{"path":"/shoppings/admins/deposits/{code}/get","method":"get"},{"path":"/shoppings/admins/mileages","method":"post"},{"path":"/shoppings/admins/mileages","method":"patch"},{"path":"/shoppings/admins/mileages/{id}","method":"get"},{"path":"/shoppings/admins/mileages/{id}","method":"delete"},{"path":"/shoppings/admins/mileages/{code}/get","method":"get"},{"path":"/shoppings/admins/mileages/donations","method":"post"},{"path":"/shoppings/admins/mileages/donations","method":"patch"},{"path":"/shoppings/admins/mileages/donations/{id}","method":"get"},{"path":"/shoppings/admins/orders","method":"patch"},{"path":"/shoppings/admins/orders/{id}","method":"get"},{"path":"/shoppings/admins/sales/details","method":"patch"},{"path":"/shoppings/admins/sales","method":"patch"},{"path":"/shoppings/admins/sales/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/admins/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/admins/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/admins/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/admins/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories","method":"post"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}","method":"put"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/merge","method":"delete"},{"path":"/shoppings/admins/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/admins/systematic/channels","method":"post"},{"path":"/shoppings/admins/systematic/channels","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{id}","method":"get"},{"path":"/shoppings/admins/systematic/channels/{id}","method":"put"},{"path":"/shoppings/admins/systematic/channels/merge","method":"delete"},{"path":"/shoppings/admins/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/admins/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/admins/systematic/sections","method":"post"},{"path":"/shoppings/admins/systematic/sections","method":"patch"},{"path":"/shoppings/admins/systematic/sections/{id}","method":"get"},{"path":"/shoppings/admins/systematic/sections/{id}","method":"put"},{"path":"/shoppings/admins/systematic/sections/merge","method":"delete"},{"path":"/shoppings/admins/systematic/sections/{code}/get","method":"get"},{"path":"/shoppings/customers/authenticate/refresh","method":"patch"},{"path":"/shoppings/customers/authenticate","method":"get"},{"path":"/shoppings/customers/authenticate","method":"post"},{"path":"/shoppings/customers/authenticate/join","method":"post"},{"path":"/shoppings/customers/authenticate/login","method":"put"},{"path":"/shoppings/customers/authenticate/activate","method":"post"},{"path":"/shoppings/customers/authenticate/external","method":"post"},{"path":"/shoppings/customers/authenticate/password/change","method":"put"},{"path":"/shoppings/customers/coupons","method":"patch"},{"path":"/shoppings/customers/coupons/{id}","method":"get"},{"path":"/shoppings/customers/coupons/tickets","method":"post"},{"path":"/shoppings/customers/coupons/tickets","method":"patch"},{"path":"/shoppings/customers/coupons/tickets/{id}","method":"get"},{"path":"/shoppings/customers/deposits/charges","method":"post"},{"path":"/shoppings/customers/deposits/charges","method":"patch"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"get"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"put"},{"path":"/shoppings/customers/deposits/charges/{id}","method":"delete"},{"path":"/shoppings/customers/deposits/charges/{chargeId}/publish/able","method":"get"},{"path":"/shoppings/customers/deposits/charges/{chargeId}/publish","method":"post"},{"path":"/shoppings/customers/deposits/histories","method":"patch"},{"path":"/shoppings/customers/deposits/histories/{id}","method":"get"},{"path":"/shoppings/customers/deposits/histories/balance","method":"get"},{"path":"/shoppings/customers/mileages/histories","method":"patch"},{"path":"/shoppings/customers/mileages/histories/{id}","method":"get"},{"path":"/shoppings/customers/mileages/histories/balance","method":"get"},{"path":"/shoppings/customers/carts/commodities","method":"post"},{"path":"/shoppings/customers/carts/commodities","method":"patch"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"get"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"put"},{"path":"/shoppings/customers/carts/commodities/{id}","method":"delete"},{"path":"/shoppings/customers/carts/commodities/{id}/replica","method":"get"},{"path":"/shoppings/customers/carts/commodities/discountable","method":"patch"},{"path":"/shoppings/customers/orders","method":"post"},{"path":"/shoppings/customers/orders","method":"patch"},{"path":"/shoppings/customers/orders/direct","method":"post"},{"path":"/shoppings/customers/orders/{id}","method":"get"},{"path":"/shoppings/customers/orders/{id}","method":"delete"},{"path":"/shoppings/customers/orders/{id}/price","method":"get"},{"path":"/shoppings/customers/orders/{id}/discountable","method":"patch"},{"path":"/shoppings/customers/orders/{id}/discount","method":"put"},{"path":"/shoppings/customers/orders/{orderId}/goods/{id}/confirm","method":"put"},{"path":"/shoppings/customers/orders/{orderId}/publish/able","method":"get"},{"path":"/shoppings/customers/orders/{orderId}/publish","method":"post"},{"path":"/shoppings/customers/orders/{orderId}/publish","method":"delete"},{"path":"/shoppings/customers/sales/details","method":"patch"},{"path":"/shoppings/customers/sales","method":"patch"},{"path":"/shoppings/customers/sales/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/customers/sales/{saleId}/questions","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/questions/{id}","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/customers/sales/{saleId}/reviews","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/reviews/{id}","method":"post"},{"path":"/shoppings/customers/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/customers/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/customers/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/customers/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/customers/systematic/channels","method":"patch"},{"path":"/shoppings/customers/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/customers/systematic/channels/{id}","method":"get"},{"path":"/shoppings/customers/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/customers/systematic/sections","method":"patch"},{"path":"/shoppings/customers/systematic/sections/{id}","method":"get"},{"path":"/shoppings/customers/systematic/sections/{code}/get","method":"get"},{"path":"/shoppings/sellers/authenticate","method":"get"},{"path":"/shoppings/sellers/authenticate","method":"post"},{"path":"/shoppings/sellers/authenticate/login","method":"put"},{"path":"/shoppings/sellers/deliveries","method":"post"},{"path":"/shoppings/sellers/deliveries","method":"patch"},{"path":"/shoppings/sellers/deliveries/{id}","method":"get"},{"path":"/shoppings/sellers/deliveries/incompletes","method":"patch"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys","method":"post"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys/{id}/complete","method":"put"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/journeys/{id}","method":"delete"},{"path":"/shoppings/sellers/deliveries/{deliveryId}/shippers","method":"post"},{"path":"/shoppings/sellers/coupons","method":"post"},{"path":"/shoppings/sellers/coupons","method":"patch"},{"path":"/shoppings/sellers/coupons/{id}","method":"get"},{"path":"/shoppings/sellers/coupons/{id}","method":"delete"},{"path":"/shoppings/sellers/orders","method":"patch"},{"path":"/shoppings/sellers/orders/{id}","method":"get"},{"path":"/shoppings/sellers/sales","method":"post"},{"path":"/shoppings/sellers/sales","method":"patch"},{"path":"/shoppings/sellers/sales/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{id}/open","method":"put"},{"path":"/shoppings/sellers/sales/{id}/replica","method":"post"},{"path":"/shoppings/sellers/sales/{id}/pause","method":"delete"},{"path":"/shoppings/sellers/sales/{id}/suspend","method":"delete"},{"path":"/shoppings/sellers/sales/{id}/restore","method":"put"},{"path":"/shoppings/sellers/sales/details","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{questionId}/answer","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{questionId}/answer","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/questions","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/abridges","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/questions/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{reviewId}/answer","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{reviewId}/answer","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{inquiryId}/comments/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/reviews","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/abridges","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/reviews/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}/replica","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/snapshots/{id}/flip","method":"get"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements","method":"post"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements","method":"patch"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements/{id}","method":"put"},{"path":"/shoppings/sellers/sales/{saleId}/units/{unitId}/stocks/{stockId}/supplements/{id}","method":"delete"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/channels/{channelCode}/categories/{id}/invert","method":"get"},{"path":"/shoppings/sellers/systematic/channels","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/hierarchical","method":"patch"},{"path":"/shoppings/sellers/systematic/channels/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/channels/{code}/get","method":"get"},{"path":"/shoppings/sellers/systematic/sections","method":"patch"},{"path":"/shoppings/sellers/systematic/sections/{id}","method":"get"},{"path":"/shoppings/sellers/systematic/sections/{code}/get","method":"get"}]}\n```\n\n**Key points**: Observe how `/shopping` is used as domain prefix, hierarchical relationships are reflected in paths (e.g., `/shopping/sales/{saleId}/reviews/{reviewId}`), and consistent HTTP methods are applied across similar operations.'),
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$3({
+        controllers: [ createApplication$6({
             model: ctx.model,
             build: endpoints => {
                 pointer.value = endpoints;
@@ -2946,16 +3015,18 @@ async function process$1(ctx, endpoints) {
         }) ]
     });
     agentica.on("request", (async event => {
-        event.body.tool_choice = "required";
+        if (event.body.tools) {
+            event.body.tool_choice = "required";
+        }
     }));
     await agentica.conversate([ "Make API operations for below endpoints:", "", "```json", JSON.stringify(Array.from(endpoints), null, 2), "```" ].join("\n"));
     if (pointer.value === null) throw new Error("Failed to create operations.");
     return pointer.value;
 }
 
-function createApplication$3(props) {
+function createApplication$6(props) {
     assertSchemaModel(props.model);
-    const application = collection$4[props.model];
+    const application = collection$7[props.model];
     application.functions[0].validate = next => {
         const result = (() => {
             const _io0 = input => Array.isArray(input.operations) && input.operations.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
@@ -3245,7 +3316,7 @@ function createApplication$3(props) {
     };
 }
 
-const claude$4 = {
+const claude$7 = {
     model: "claude",
     options: {
         reference: true,
@@ -3757,7 +3828,7 @@ const claude$4 = {
     } ]
 };
 
-const collection$4 = {
+const collection$7 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -4260,10 +4331,10 @@ const collection$4 = {
             })()
         } ]
     },
-    claude: claude$4,
-    llama: claude$4,
-    deepseek: claude$4,
-    3.1: claude$4,
+    claude: claude$7,
+    llama: claude$7,
+    deepseek: claude$7,
+    3.1: claude$7,
     "3.0": {
         model: "3.0",
         options: {
@@ -4809,9 +4880,7 @@ const orchestrateInterface = ctx => async props => {
 
 const orchestrateRealize = ctx => async props => null;
 
-const orchestrateTest = ctx => async props => null;
-
-const transformPrismaComponentsHistories = state => {
+const transformPrismaComponentsHistories = (state, prefix = null) => {
     if (state.analyze === null) return [ {
         id: v4(),
         created_at: (new Date).toISOString(),
@@ -4827,7 +4896,7 @@ const transformPrismaComponentsHistories = state => {
         id: v4(),
         created_at: (new Date).toISOString(),
         type: "assistantMessage",
-        text: [ "Here is the requirement analysis report.", "", "Call the provided tool function to generate Prisma DB schema", "referencing below requirement analysis report.", "", "## User Request", state.analyze.reason, "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```" ].join("\n")
+        text: [ "Here is the requirement analysis report.", "", "Call the provided tool function to generate Prisma DB schema", "referencing below requirement analysis report.", "", "## User Request", state.analyze.reason, "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```", "## Prefix", "", `* Prefix provided by the user: ${prefix}`, "", "The user wants all database schema (table) names to start with the prefix provided below.", "If the prefix is `null`, it should be ignored.", "If a prefix is provided, all table names **must begin with it**.", "However, if there is a special-purpose prefix like `mv` (for materialized views), it **must precede** the given prefix.", "", "## Prefix Example", "", "If the prefix is `shopping`, then table names should be like:", "", "* `shopping_sales`", "* `shopping_sale_options`", "", "In cases where a table is created for performance optimization purposes (e.g., materialized views), the `mv_` prefix must come first.", "For example:", "", "* `mv_shopping_daily_stats`" ].join("\n")
     } ];
 };
 
@@ -4836,15 +4905,16 @@ async function orchestratePrismaComponents(ctx, content = "Please extract files
     const pointer = {
         value: null
     };
+    const prefix = ctx.state().analyze?.prefix ?? null;
     const agentica = new MicroAgentica({
         model: ctx.model,
         vendor: ctx.vendor,
         config: {
             ...ctx.config ?? {}
         },
-        histories: transformPrismaComponentsHistories(ctx.state()),
+        histories: transformPrismaComponentsHistories(ctx.state(), prefix),
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$2({
+        controllers: [ createApplication$5({
             model: ctx.model,
             build: next => {
                 pointer.value = next;
@@ -4868,9 +4938,9 @@ async function orchestratePrismaComponents(ctx, content = "Please extract files
     };
 }
 
-function createApplication$2(props) {
+function createApplication$5(props) {
     assertSchemaModel(props.model);
-    const application = collection$3[props.model];
+    const application = collection$6[props.model];
     return {
         protocol: "class",
         name: "Prisma Extract Files and Tables",
@@ -4883,7 +4953,7 @@ function createApplication$2(props) {
     };
 }
 
-const claude$3 = {
+const claude$6 = {
     model: "claude",
     options: {
         reference: true,
@@ -5008,7 +5078,7 @@ const claude$3 = {
     } ]
 };
 
-const collection$3 = {
+const collection$6 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -5133,10 +5203,10 @@ const collection$3 = {
             })()
         } ]
     },
-    claude: claude$3,
-    llama: claude$3,
-    deepseek: claude$3,
-    3.1: claude$3,
+    claude: claude$6,
+    llama: claude$6,
+    deepseek: claude$6,
+    3.1: claude$6,
     "3.0": {
         model: "3.0",
         options: {
@@ -5294,10 +5364,10 @@ function orchestratePrismaCorrect(ctx, application, retry = 8) {
         return true;
     }));
     application.files = application.files.filter((f => f.models.length !== 0));
-    return step(ctx, application);
+    return step$1(ctx, application);
 }
 
-async function step(ctx, application, life) {
+async function step$1(ctx, application, life) {
     const result = await ctx.compiler.prisma.validate(application);
     if (result.success) return result;
     const schemas = await ctx.compiler.prisma.write(application);
@@ -5322,7 +5392,7 @@ async function step(ctx, application, life) {
         },
         histories: transformPrismaCorrectHistories(result),
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication$1({
+        controllers: [ createApplication$4({
             model: ctx.model,
             build: next => {
                 pointer.value = next;
@@ -5357,14 +5427,14 @@ async function step(ctx, application, life) {
         step: ctx.state().analyze?.step ?? 0,
         created_at: (new Date).toISOString()
     });
-    return step(ctx, {
+    return step$1(ctx, {
         files: correction.files
     });
 }
 
-function createApplication$1(props) {
+function createApplication$4(props) {
     assertSchemaModel(props.model);
-    const application = collection$2[props.model];
+    const application = collection$5[props.model];
     return {
         protocol: "class",
         name: "Prisma Compiler",
@@ -5377,7 +5447,7 @@ function createApplication$1(props) {
     };
 }
 
-const claude$2 = {
+const claude$5 = {
     model: "claude",
     options: {
         reference: true,
@@ -5922,7 +5992,7 @@ const claude$2 = {
     } ]
 };
 
-const collection$2 = {
+const collection$5 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -6449,10 +6519,10 @@ const collection$2 = {
             })()
         } ]
     },
-    claude: claude$2,
-    llama: claude$2,
-    deepseek: claude$2,
-    3.1: claude$2,
+    claude: claude$5,
+    llama: claude$5,
+    deepseek: claude$5,
+    3.1: claude$5,
     "3.0": {
         model: "3.0",
         options: {
@@ -7020,7 +7090,7 @@ async function orchestratePrismaSchemas(ctx, components) {
     const total = components.reduce(((acc, c) => acc + c.tables.length), 0);
     let i = 0;
     return await Promise.all(components.map((async c => {
-        const result = await process(ctx, {
+        const result = await process$3(ctx, {
             filename: c.filename,
             tables: c.tables,
             entireTables
@@ -7038,7 +7108,7 @@ async function orchestratePrismaSchemas(ctx, components) {
     })));
 }
 
-async function process(ctx, component) {
+async function process$3(ctx, component) {
     const pointer = {
         value: null
     };
@@ -7050,7 +7120,7 @@ async function process(ctx, component) {
         },
         histories: transformPrismaSchemaHistories(ctx.state().analyze, component),
         tokenUsage: ctx.usage(),
-        controllers: [ createApplication({
+        controllers: [ createApplication$3({
             model: ctx.model,
             build: next => {
                 pointer.value = next;
@@ -7068,9 +7138,9 @@ async function process(ctx, component) {
     return pointer.value;
 }
 
-function createApplication(props) {
+function createApplication$3(props) {
     assertSchemaModel(props.model);
-    const application = collection$1[props.model];
+    const application = collection$4[props.model];
     return {
         protocol: "class",
         name: "Prisma Generator",
@@ -7083,7 +7153,7 @@ function createApplication(props) {
     };
 }
 
-const claude$1 = {
+const claude$4 = {
     model: "claude",
     options: {
         reference: true,
@@ -7661,7 +7731,7 @@ const claude$1 = {
     } ]
 };
 
-const collection$1 = {
+const collection$4 = {
     chatgpt: {
         model: "chatgpt",
         options: {
@@ -8220,10 +8290,10 @@ const collection$1 = {
             })()
         } ]
     },
-    claude: claude$1,
-    llama: claude$1,
-    deepseek: claude$1,
-    3.1: claude$1,
+    claude: claude$4,
+    llama: claude$4,
+    deepseek: claude$4,
+    3.1: claude$4,
     "3.0": {
         model: "3.0",
         options: {
@@ -8848,6 +8918,1496 @@ const orchestratePrisma = ctx => async props => {
     return history;
 };
 
+const transformTestCorrectHistories = (apiFiles, dtoFiles) => [ {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: '# Compiler Error Fix System Prompt\n\nYou are an expert TypeScript compiler error fixing agent specializing in resolving compilation errors in E2E test code that follows the `@nestia/e2e` testing framework conventions.\n\n## Your Role\n\n- Analyze the provided TypeScript code with compilation errors and generate the corrected version.  \n- Focus specifically on the error location, message, and problematic code segment.  \n- Maintain all existing functionality while resolving only the compilation issues.  \n- Follow the established code patterns and conventions from the original E2E test code.  \n- Use provided API Files and DTO Files to resolve module and type declaration issues.  \n- **CRITICAL**: Apply comprehensive fixes to prevent circular error loops by addressing all related import issues in a single pass.\n\n## Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided  \n- All thinking and responses must be in the working language  \n- All model/field names must be in English regardless of working language \n\n## Input Format\n\nYou will receive:  \n\n1. **Original Code**: TypeScript E2E test code with compilation errors  \n2. **Error Information**:  \n   - Exact character position of the error  \n   - Detailed error message from TypeScript compiler  \n   - The specific problematic code segment  \n3. **Instructions**: Specific guidance on what needs to be fixed  \n4. **API Files**: Reference files containing available API functions and their paths  \n5. **DTO Files**: Reference files containing available types and their import paths  \n\n## Code Fixing Guidelines\n\n### 1. Module Resolution Errors (CRITICAL PRIORITY)\n\n#### Universal Module Import Pattern Recognition and Fix:\n\n**ALWAYS scan the ENTIRE code for ALL import statements that match these patterns and fix them ALL at once:**\n\n```typescript\n// WRONG PATTERNS - Fix ALL of these in one pass:\nimport api from "@nestia/PROJECT-api";\nimport api from "@wrtnlabs/PROJECT-api"; \nimport api from "@anyorganization/PROJECT-api";\nimport { Type } from "@nestia/PROJECT-api/lib/structures/Type";\nimport { Type } from "@wrtnlabs/PROJECT-api/lib/structures/Type";\nimport { Type } from "@anyorganization/PROJECT-api/lib/structures/Type";\n\n// CORRECT PATTERN - Replace with:\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { Type } from "@ORGANIZATION/PROJECT-api/lib/structures/Type";\n```\n\n#### Comprehensive Module Fix Strategy:\n\n1. **Pattern Detection**: Look for ANY import that contains:  \n   - `@[anything]/[project-name]-api` → Replace `@[anything]` with `@ORGANIZATION`  \n   - `@[project-name]-api` (missing org prefix) → Add `@ORGANIZATION/` prefix  \n\n2. **Common Error Patterns to Fix ALL AT ONCE**:  \n\n```typescript\n// Error Pattern 1: Wrong organization name\nCannot find module \'@wrtnlabs/template-api\'\nCannot find module \'@nestia/template-api\'\nCannot find module \'@anyorg/template-api\'\n// Fix: Replace with @ORGANIZATION/template-api\n\n// Error Pattern 2: Missing organization prefix  \nCannot find module \'@template-api\'\nCannot find module \'template-api\'\n// Fix: Add @ORGANIZATION/ prefix\n\n// Error Pattern 3: Structure imports with wrong org\nCannot find module \'@wrtnlabs/template-api/lib/structures/IType\'\nCannot find module \'@nestia/template-api/lib/structures/IType\'\n// Fix: Replace with @ORGANIZATION/template-api/lib/structures/IType\n```  \n\n3. **Comprehensive Import Scan and Fix**:  \n   - **BEFORE fixing the reported error**, scan ALL import statements in the code  \n   - Identify ALL imports that follow incorrect patterns  \n   - Fix ALL of them simultaneously to prevent error loops  \n   - Ensure consistent `@ORGANIZATION/PROJECT-api` pattern throughout  \n\n#### Module Resolution Fix Examples:\n\n```typescript\n// BEFORE (Multiple wrong patterns in same file):\nimport api from "@nestia/template-api";\nimport { IBbsArticle } from "@wrtnlabs/template-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@template-api/lib/structures/IAttachmentFile";\n\n// AFTER (All fixed consistently):\nimport api from "@ORGANIZATION/template-api";\nimport { IBbsArticle } from "@ORGANIZATION/template-api/lib/structures/IBbsArticle";\nimport { IAttachmentFile } from "@ORGANIZATION/template-api/lib/structures/IAttachmentFile";\n```  \n\n### 2. Error Loop Prevention Strategy\n\n**CRITICAL**: To prevent 1 → 2 → 3 → 1 error loops:  \n\n1. **Holistic Code Analysis**: Before fixing the specific error, analyze ALL import statements in the entire code  \n2. **Batch Import Fixes**: Fix ALL import-related issues in a single pass, not just the reported error  \n3. **Pattern Consistency**: Ensure ALL imports follow the same `@ORGANIZATION/PROJECT-api` pattern  \n4. **Preemptive Fixes**: Look for and fix potential related errors that might surface after the current fix  \n\n**Implementation Approach**:  \n\n```typescript\n// Step 1: Scan entire code for ALL these patterns\nconst problemPatterns = [\n  /@[^/]+\\/[^-]+-api(?!\\/)/g,           // Wrong org prefix\n  /@[^-]+-api(?!\\/)/g,                  // Missing org prefix  \n  /from\\s+["\']@[^/]+\\/[^-]+-api/g,      // Wrong org in imports\n  /from\\s+["\']@[^-]+-api/g              // Missing org in imports\n];\n\n// Step 2: Replace ALL matches with @ORGANIZATION/PROJECT-api pattern\n// Step 3: Then fix the specific reported error\n```  \n\n### 3. API Function Usage Corrections\n\n- Ensure proper `import api from "@ORGANIZATION/PROJECT-api";` format (verify against API Files)  \n- Fix API function call patterns to follow:  \n\n  ```ts\n  api.functional.[...].methodName(...)\n  ```  \n\n- Correct connection parameter usage (avoid adding extra properties):  \n\n  ```ts\n  // Correct\n  await api.functional.bbs.articles.post(connection, { body: articleBody });\n  ```  \n\n- **Cross-reference API Files** to ensure function paths and method names are accurate  \n\n### 4. DTO Type Import Corrections\n\n- Fix import statements to use proper format based on **DTO Files**:  \n\n  ```ts\n  import { ITypeName } from "@ORGANIZATION/PROJECT-api/lib/structures/[...].ts";\n  ```  \n\n- Ensure `@ORGANIZATION` prefix is maintained in import paths  \n- **Verify type names and paths** against provided DTO Files  \n- Correct missing or incorrect type imports  \n- Fix type annotation errors  \n\n### 5. Test Function Structure Fixes\n\n- Ensure test functions follow the pattern:  \n\n  ```ts\n  export async function test_api_xxx(...): Promise<void> { ... }\n  ```  \n\n- Fix async/await usage errors  \n- Correct function parameter types (especially `connection: api.IConnection`)  \n\n### 6. Test Validator Usage Corrections\n\n- Fix `TestValidator` method calls:  \n\n  ```ts\n  TestValidator.equals("title", exceptionFunction)(expected)(actual);\n  TestValidator.predicate("title")(condition);\n  TestValidator.error("title")(task);\n  ```  \n\n- Correct currying function usage  \n- Fix assertion patterns  \n\n### 7. Typia Assert Corrections\n\n- Ensure proper `typia.assert<T>(value)` usage  \n- Fix generic type parameters  \n- Correct assertion patterns for response validation  \n\n### 8. Array Type Corrections\n\n```\nerror: Argument of type \'IBbsArticleComment[]\' is not assignable to parameter of type \'never[]\'.\n```  \n\n- To Resolve above Array parameter Error, If you declare empty array like `[]`, You must define the type of array together.  \n\nExample:  \n\n  ```typescript\n  TestValidator.equals("message")(\n      [] as IBbsArticleComment[],\n    )(data);\n  ```  \n\n### 9. Common TypeScript Error Fixes\n\n- **Import/Export errors**: Fix module resolution issues using API Files and DTO Files as reference  \n- **Type mismatches**: Align variable types with expected interfaces from DTO Files  \n- **Missing properties**: Add required properties to objects  \n- **Async/Promise errors**: Fix Promise handling and async function signatures  \n- **Generic type errors**: Correct generic type parameters  \n- **Null/undefined handling**: Add proper null checks or optional chaining  \n- **Interface compliance**: Ensure objects conform to their declared interfaces  \n\n## Error Resolution Strategy\n\n1. **Full Code Analysis**: FIRST perform comprehensive analysis of ENTIRE codebase for ALL potential TypeScript issues  \n2. **Error Chain Identification**: Identify cascading error patterns and relationships between different parts of code  \n3. **Holistic Fix Planning**: Plan fixes for ALL related errors that could cause loops, not just the reported error  \n4. **Reference File Consultation**:  \n   - For module errors: Consult API Files for correct import paths  \n   - For type errors: Consult DTO Files for correct type import paths  \n   - For function calls: Verify method signatures and parameters  \n5. **Batch Error Resolution**: Fix ALL identified issues simultaneously in logical groups:  \n   - All import/module issues together  \n   - All type declaration issues together  \n   - All function signature issues together  \n   - All usage/call site issues together  \n6. **Context Preservation**: Maintain the original test logic and flow  \n7. **Comprehensive Validation**: Ensure no new compilation errors or cascading issues are introduced  \n8. **Pattern Consistency**: Keep existing code style and conventions throughout all fixes  \n\n## Output Requirements\n\n- Return **only** the corrected TypeScript code  \n- Maintain all original functionality and test logic  \n- Preserve code formatting and style  \n- Ensure the fix addresses ALL related compilation errors (not just the reported one)  \n- **CRITICAL**: Fix ALL import pattern issues in a single pass to prevent error loops  \n- Do not add explanations, comments, or additional features  \n\n## Priority Error Handling\n\n1. **Comprehensive Analysis** (HIGHEST priority):  \n   - Scan ENTIRE codebase for ALL potential TypeScript compilation issues  \n   - Identify cascading error patterns and relationships  \n   - Map error chains that commonly cause loops (import → type → usage → validation)  \n\n2. **Batch Error Resolution** (CRITICAL):  \n   - Group related errors into logical fix batches:  \n     - **Module/Import Batch**: All import paths, module resolution, missing dependencies  \n     - **Type Batch**: All type declarations, interfaces, generic constraints  \n     - **Function Batch**: All function signatures, parameters, return types  \n     - **Usage Batch**: All variable assignments, method calls, property access  \n     - **Test Batch**: All TestValidator calls, assertion patterns, validation logic  \n   - Fix entire batches simultaneously to prevent cascading failures  \n\n3. **Specific Error Resolution**:  \n   - After comprehensive fixes, verify the originally reported error is resolved  \n   - Use DTO Files for type corrections and API Files for function signatures  \n   - Ensure consistency with established patterns  \n\n4. **General TypeScript Compilation**:  \n   - Apply standard TypeScript error resolution techniques  \n   - Maintain type safety throughout all fixes  \n\n## Error Loop Prevention Protocol\n\n**MANDATORY STEPS to prevent error loops:**  \n\n1. **Pre-Analysis**: Before fixing reported error, scan entire code for ALL import statements  \n2. **Pattern Matching**: Identify ALL imports matching problematic patterns:  \n   - `@[anything-except-ORGANIZATION]/[project]-api`  \n   - Missing `@ORGANIZATION/` prefix  \n   - Inconsistent organization naming  \n3. **Comprehensive Fix**: Replace ALL problematic imports with correct `@ORGANIZATION/PROJECT-api` pattern  \n4. **Validation**: Ensure ALL imports in the file follow consistent pattern  \n5. **Specific Fix**: Then address the specific reported compilation error  \n\n**Example of Comprehensive Fix Approach:**  \n\n```typescript\n// Input code with multiple potential issues:\nimport api from "@nestia/template-api";                    // Issue 1\nimport { IBbsArticle } from "@wrtnlabs/template-api/lib/structures/IBbsArticle";  // Issue 2  \nimport { IUser } from "@template-api/lib/structures/IUser";  // Issue 3\n\n// Output: ALL issues fixed simultaneously:\nimport api from "@ORGANIZATION/template-api";\nimport { IBbsArticle } from "@ORGANIZATION/template-api/lib/structures/IBbsArticle";\nimport { IUser } from "@ORGANIZATION/template-api/lib/structures/IUser";\n```'
+}, {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "assistantMessage",
+    text: [ "You are the world's best TypeScript compiler error fixer.", "You will be given a **TypeScript code** with compilation errors, and your job is to fix the errors.", "", "## Rules", "- Follow the base E2E test style strictly. Never use other frameworks like Jest or Mocha.", "- Use `TestValidator.equals(...)` and `typia.assert(...)` to verify results.", "- Use `api.functional.XXX` for all API calls. These are defined in API Files.", "- Use helper functions like `generate_random_xxx(...)` **only if** they already exist in the base test imports.", "- Do not invent new helpers or use utilities that are not explicitly shown.", "- Keep all tests deterministic and reliable.", "", "## File References", "### API Files", "```typescript", JSON.stringify(apiFiles, null, 2), "```", "", "### DTO Files", "```typescript", JSON.stringify(dtoFiles, null, 2), "```", "", "Now Fix the E2E test function based on the given error information.", "Only output a single `async function` named `test_api_{...}`. No explanation, no commentary." ].join("\n")
+} ];
+
+async function orchestrateTestCorrect(ctx, codes, retry = 8) {
+    const testFiles = Object.fromEntries(codes.map((({filename, content}) => [ `test/features/api/${filename}`, content ])));
+    const retainedFiles = Object.fromEntries(Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => !filename.startsWith("test/features/api"))));
+    const mergedFiles = {
+        ...retainedFiles,
+        ...testFiles
+    };
+    const files = Object.fromEntries(Object.entries(mergedFiles).filter((([filename]) => filename.endsWith(".ts") && !filename.startsWith("test/benchmark/") || filename.endsWith(".json"))));
+    const response = await step(ctx, files, retry);
+    const event = {
+        ...response,
+        type: "testValidate",
+        files: {
+            ...mergedFiles,
+            ...response.files
+        }
+    };
+    return event;
+}
+
+async function step(ctx, files, life) {
+    const result = await ctx.compiler.typescript({
+        files
+    });
+    if (result.type === "success") {
+        return {
+            type: "testValidate",
+            created_at: (new Date).toISOString(),
+            files,
+            result,
+            step: ctx.state().interface?.step ?? 0
+        };
+    }
+    if (result.type === "exception") {
+        ctx.dispatch({
+            type: "testValidate",
+            created_at: (new Date).toISOString(),
+            files,
+            result,
+            step: ctx.state().interface?.step ?? 0
+        });
+        throw new Error(JSON.stringify(result.error, null, 2));
+    }
+    const diagnostics = {};
+    result.diagnostics.forEach((d => {
+        if (d.file === null) return;
+        diagnostics[d.file] = diagnostics[d.file] ?? [];
+        diagnostics[d.file].push(d);
+    }));
+    if (Object.keys(diagnostics).length === 0) {
+        return {
+            type: "testValidate",
+            created_at: (new Date).toISOString(),
+            files,
+            result: {
+                ...result,
+                type: "success"
+            },
+            step: ctx.state().interface?.step ?? 0
+        };
+    }
+    ctx.dispatch({
+        type: "testValidate",
+        created_at: (new Date).toISOString(),
+        files,
+        result,
+        step: ctx.state().interface?.step ?? 0
+    });
+    if (life <= 0) return {
+        type: "testValidate",
+        created_at: (new Date).toISOString(),
+        files,
+        result,
+        step: ctx.state().interface?.step ?? 0
+    };
+    const validate = await Promise.all(Object.entries(diagnostics).map((async ([filename, d]) => {
+        const code = files[filename];
+        const response = await process$2(ctx, d, code);
+        ctx.dispatch({
+            type: "testCorrect",
+            created_at: (new Date).toISOString(),
+            files: {
+                ...files,
+                [filename]: response.content
+            },
+            result,
+            solution: response.solution,
+            think_without_compile_error: response.think_without_compile_error,
+            think_again_with_compile_error: response.think_again_with_compile_error,
+            step: ctx.state().interface?.step ?? 0
+        });
+        return [ filename, response.content ];
+    })));
+    const newFiles = {
+        ...files,
+        ...Object.fromEntries(validate)
+    };
+    return step(ctx, newFiles, life - 1);
+}
+
+async function process$2(ctx, diagnostics, code) {
+    const pointer = {
+        value: null
+    };
+    const apiFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
+        [filename]: content
+    })), {});
+    const dtoFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/structures/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
+        [filename]: content
+    })), {});
+    const agentica = new MicroAgentica({
+        model: ctx.model,
+        vendor: {
+            ...ctx.vendor
+        },
+        config: {
+            ...ctx.config ?? {}
+        },
+        histories: transformTestCorrectHistories(apiFiles, dtoFiles),
+        controllers: [ createApplication$2({
+            model: ctx.model,
+            build: next => {
+                pointer.value = next;
+            }
+        }) ]
+    });
+    agentica.on("request", (async event => {
+        if (event.body.tools) event.body.tool_choice = "required";
+    }));
+    await agentica.conversate([ "Fix the compilation error in the provided code.", "", "## Original Code", "```typescript", code, "```", "", diagnostics.map((diagnostic => {
+        if (diagnostic.start === undefined || diagnostic.length === undefined) return "";
+        return [ "## Error Information", `- Position: Characters ${diagnostic.start} to ${diagnostic.start + diagnostic.length}`, `- Error Message: ${diagnostic.messageText}`, `- Problematic Code: \`${code.substring(diagnostic.start, diagnostic.start + diagnostic.length)}\``, "" ].join("\n");
+    })), "## Instructions", "1. Focus on the specific error location and message", "2. Provide the corrected TypeScript code", "3. Ensure the fix resolves the compilation error", "", "Return only the fixed code without explanations." ].join("\n"));
+    if (pointer.value === null) throw new Error("Failed to modify test code.");
+    return pointer.value;
+}
+
+function createApplication$2(props) {
+    assertSchemaModel(props.model);
+    const application = collection$3[props.model];
+    return {
+        protocol: "class",
+        name: "Modify Test Code",
+        application,
+        execute: {
+            correctTestCode: next => {
+                props.build(next);
+            }
+        }
+    };
+}
+
+const claude$3 = {
+    model: "claude",
+    options: {
+        reference: true,
+        separate: null
+    },
+    functions: [ {
+        name: "correctTestCode",
+        parameters: {
+            description: "Current Type: {@link ICorrectTestFunctionProps}",
+            type: "object",
+            properties: {
+                think_without_compile_error: {
+                    description: "Step 1: Initial self-reflection on the source code without compiler error\ncontext.\n\nThe AI agent analyzes the previously generated test code to identify\npotential issues, relying solely on its understanding of TypeScript syntax,\ntesting patterns, and best practices.\n\nThis encourages the agent to develop independent debugging skills before\nbeing influenced by external error messages.",
+                    type: "string"
+                },
+                think_again_with_compile_error: {
+                    description: "Step 2: Re-evaluation of the code with compiler error messages as\nadditional context.\n\nAfter the initial analysis, the AI agent reviews the same code again, this\ntime incorporating the specific TypeScript compiler error messages.\n\nThis allows the agent to correlate its initial observations with concrete\ncompilation failures and refine its understanding of what went wrong.",
+                    type: "string"
+                },
+                solution: {
+                    title: "Step 3: Concrete action plan for fixing the identified issues",
+                    description: "Step 3: Concrete action plan for fixing the identified issues.\n\nBased on the analysis from steps 1 and 2, the AI agent formulates a\nspecific, step-by-step solution strategy.\n\nThis should include what changes need to be made, why those changes are\nnecessary, and how they will resolve the compilation errors while\nmaintaining the test's intended functionality.",
+                    type: "string"
+                },
+                content: {
+                    title: "Step 4: The corrected TypeScript test code",
+                    description: "Step 4: The corrected TypeScript test code.\n\nThe final, properly fixed TypeScript code that should compile without\nerrors.\n\nThis represents the implementation of the solution plan from step 3,\ncontaining all necessary corrections to make the test code syntactically\nvalid and functionally correct.",
+                    type: "string"
+                }
+            },
+            required: [ "think_without_compile_error", "think_again_with_compile_error", "solution", "content" ],
+            additionalProperties: false,
+            $defs: {}
+        },
+        validate: (() => {
+            const _io0 = input => "string" === typeof input.think_without_compile_error && "string" === typeof input.think_again_with_compile_error && "string" === typeof input.solution && "string" === typeof input.content;
+            const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.think_without_compile_error || _report(_exceptionable, {
+                path: _path + ".think_without_compile_error",
+                expected: "string",
+                value: input.think_without_compile_error
+            }), "string" === typeof input.think_again_with_compile_error || _report(_exceptionable, {
+                path: _path + ".think_again_with_compile_error",
+                expected: "string",
+                value: input.think_again_with_compile_error
+            }), "string" === typeof input.solution || _report(_exceptionable, {
+                path: _path + ".solution",
+                expected: "string",
+                value: input.solution
+            }), "string" === typeof input.content || _report(_exceptionable, {
+                path: _path + ".content",
+                expected: "string",
+                value: input.content
+            }) ].every((flag => flag));
+            const __is = input => "object" === typeof input && null !== input && _io0(input);
+            let errors;
+            let _report;
+            return input => {
+                if (false === __is(input)) {
+                    errors = [];
+                    _report = __typia_transform__validateReport._validateReport(errors);
+                    ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                        path: _path + "",
+                        expected: "ICorrectTestFunctionProps",
+                        value: input
+                    })) && _vo0(input, _path + "", true) || _report(true, {
+                        path: _path + "",
+                        expected: "ICorrectTestFunctionProps",
+                        value: input
+                    }))(input, "$input", true);
+                    const success = 0 === errors.length;
+                    return success ? {
+                        success,
+                        data: input
+                    } : {
+                        success,
+                        errors,
+                        data: input
+                    };
+                }
+                return {
+                    success: true,
+                    data: input
+                };
+            };
+        })()
+    } ]
+};
+
+const collection$3 = {
+    chatgpt: {
+        model: "chatgpt",
+        options: {
+            reference: true,
+            strict: false,
+            separate: null
+        },
+        functions: [ {
+            name: "correctTestCode",
+            parameters: {
+                description: "Current Type: {@link ICorrectTestFunctionProps}",
+                type: "object",
+                properties: {
+                    think_without_compile_error: {
+                        description: "Step 1: Initial self-reflection on the source code without compiler error\ncontext.\n\nThe AI agent analyzes the previously generated test code to identify\npotential issues, relying solely on its understanding of TypeScript syntax,\ntesting patterns, and best practices.\n\nThis encourages the agent to develop independent debugging skills before\nbeing influenced by external error messages.",
+                        type: "string"
+                    },
+                    think_again_with_compile_error: {
+                        description: "Step 2: Re-evaluation of the code with compiler error messages as\nadditional context.\n\nAfter the initial analysis, the AI agent reviews the same code again, this\ntime incorporating the specific TypeScript compiler error messages.\n\nThis allows the agent to correlate its initial observations with concrete\ncompilation failures and refine its understanding of what went wrong.",
+                        type: "string"
+                    },
+                    solution: {
+                        title: "Step 3: Concrete action plan for fixing the identified issues",
+                        description: "Step 3: Concrete action plan for fixing the identified issues.\n\nBased on the analysis from steps 1 and 2, the AI agent formulates a\nspecific, step-by-step solution strategy.\n\nThis should include what changes need to be made, why those changes are\nnecessary, and how they will resolve the compilation errors while\nmaintaining the test's intended functionality.",
+                        type: "string"
+                    },
+                    content: {
+                        title: "Step 4: The corrected TypeScript test code",
+                        description: "Step 4: The corrected TypeScript test code.\n\nThe final, properly fixed TypeScript code that should compile without\nerrors.\n\nThis represents the implementation of the solution plan from step 3,\ncontaining all necessary corrections to make the test code syntactically\nvalid and functionally correct.",
+                        type: "string"
+                    }
+                },
+                required: [ "think_without_compile_error", "think_again_with_compile_error", "solution", "content" ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            validate: (() => {
+                const _io0 = input => "string" === typeof input.think_without_compile_error && "string" === typeof input.think_again_with_compile_error && "string" === typeof input.solution && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.think_without_compile_error || _report(_exceptionable, {
+                    path: _path + ".think_without_compile_error",
+                    expected: "string",
+                    value: input.think_without_compile_error
+                }), "string" === typeof input.think_again_with_compile_error || _report(_exceptionable, {
+                    path: _path + ".think_again_with_compile_error",
+                    expected: "string",
+                    value: input.think_again_with_compile_error
+                }), "string" === typeof input.solution || _report(_exceptionable, {
+                    path: _path + ".solution",
+                    expected: "string",
+                    value: input.solution
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "ICorrectTestFunctionProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "ICorrectTestFunctionProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    },
+    claude: claude$3,
+    llama: claude$3,
+    deepseek: claude$3,
+    3.1: claude$3,
+    "3.0": {
+        model: "3.0",
+        options: {
+            constraint: true,
+            recursive: 3,
+            separate: null
+        },
+        functions: [ {
+            name: "correctTestCode",
+            parameters: {
+                type: "object",
+                properties: {
+                    think_without_compile_error: {
+                        type: "string",
+                        description: "Step 1: Initial self-reflection on the source code without compiler error\ncontext.\n\nThe AI agent analyzes the previously generated test code to identify\npotential issues, relying solely on its understanding of TypeScript syntax,\ntesting patterns, and best practices.\n\nThis encourages the agent to develop independent debugging skills before\nbeing influenced by external error messages."
+                    },
+                    think_again_with_compile_error: {
+                        type: "string",
+                        description: "Step 2: Re-evaluation of the code with compiler error messages as\nadditional context.\n\nAfter the initial analysis, the AI agent reviews the same code again, this\ntime incorporating the specific TypeScript compiler error messages.\n\nThis allows the agent to correlate its initial observations with concrete\ncompilation failures and refine its understanding of what went wrong."
+                    },
+                    solution: {
+                        type: "string",
+                        title: "Step 3: Concrete action plan for fixing the identified issues",
+                        description: "Step 3: Concrete action plan for fixing the identified issues.\n\nBased on the analysis from steps 1 and 2, the AI agent formulates a\nspecific, step-by-step solution strategy.\n\nThis should include what changes need to be made, why those changes are\nnecessary, and how they will resolve the compilation errors while\nmaintaining the test's intended functionality."
+                    },
+                    content: {
+                        type: "string",
+                        title: "Step 4: The corrected TypeScript test code",
+                        description: "Step 4: The corrected TypeScript test code.\n\nThe final, properly fixed TypeScript code that should compile without\nerrors.\n\nThis represents the implementation of the solution plan from step 3,\ncontaining all necessary corrections to make the test code syntactically\nvalid and functionally correct."
+                    }
+                },
+                required: [ "think_without_compile_error", "think_again_with_compile_error", "solution", "content" ],
+                description: "Current Type: {@link ICorrectTestFunctionProps}",
+                additionalProperties: false
+            },
+            validate: (() => {
+                const _io0 = input => "string" === typeof input.think_without_compile_error && "string" === typeof input.think_again_with_compile_error && "string" === typeof input.solution && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.think_without_compile_error || _report(_exceptionable, {
+                    path: _path + ".think_without_compile_error",
+                    expected: "string",
+                    value: input.think_without_compile_error
+                }), "string" === typeof input.think_again_with_compile_error || _report(_exceptionable, {
+                    path: _path + ".think_again_with_compile_error",
+                    expected: "string",
+                    value: input.think_again_with_compile_error
+                }), "string" === typeof input.solution || _report(_exceptionable, {
+                    path: _path + ".solution",
+                    expected: "string",
+                    value: input.solution
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "ICorrectTestFunctionProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "ICorrectTestFunctionProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    }
+};
+
+const transformTestProgressHistories = (apiFiles, dtoFiles) => [ {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "systemMessage",
+    text: '# E2E Test Code Generator System Prompt\n\nYou are an expert E2E (End-to-End) test automation engineer specializing in generating test code directly from user scenarios using API functions and TypeScript DTO types.\n\n## Your Role\n\n- Analyze the given user scenario and generate complete E2E test code (max 300 lines).  \n- Use only the **provided API functions and DTO types** to implement realistic, maintainable, and deterministic test flows.  \n- Write tests in **TypeScript** using the `@nestia/e2e` testing style — do **not** use other test frameworks (e.g., Jest, Mocha).  \n- **Focus on simplicity and correctness** - avoid complex type manipulations and ensure all imports match the provided API structure.  \n- When generating E2E test code, you must perform extremely strict type checking.  \n\n## Default Working Language: English\n\n- Use the language specified by user in messages as the working language when explicitly provided  \n- All thinking and responses must be in the working language  \n- All model/field names must be in English regardless of working language  \n\n\n## Input Format\n\nYou will receive:\n\n1. **User Scenario**: A textual description of a business use-case or user flow  \n2. **Filename**: The desired filename for the test file  \n3. **API Files**: A collection of functions exposed by the system under test  \n4. **DTO Files**: TypeScript types used in request/response payloads of API functions  \n\n## Test Generation Guidelines\n\n### 1. API Function Usage\n\n- Must use `import api from "@ORGANIZATION/PROJECT-api";` to import api functions.  \n  - Never use other import statement like `import api from "@PROJECT/api"`  \n- **Only use API functions that are explicitly listed in the provided API Files** - do not assume functions exist.  \n- **Carefully match function names and paths** from the provided API structure.  \n- Connection parameter should be used as-is without modification:  \n\n  ```ts\n  // Correct Usage\n  await api.functional.bbs.articles.post(connection, { body: articleBody });\n\n  // Incorrect - Don\'t modify connection\n  const slowConnection = { ...connection, simulate: { delay: 4000 } };\n  ```  \n\n- API functions follow this pattern: `api.functional.[...].methodName(...)`  \n- For example, if file path is `src/api/functional/bbs/articles/comments/index.ts` and function is `postByArticleId`, use `api.functional.bbs.articles.comments.postByArticleId(...)`  \n\n### 2. DTO Type Usage\n\n- **Import DTO types exactly as provided** in the DTO Files section.  \n- Use the exact import path: `import { ITypeName } from "@ORGANIZATION/PROJECT-api/lib/structures/[exact-path]";`  \n- **Do not assume property names or structures** - only use properties that are explicitly defined in the provided DTO types.  \n- **Ensure all required properties are included** when creating request objects.  \n\nExample:  \n\n  ```ts\n  import { IBbsArticle } from "@ORGANIZATION/PROJECT-api/lib/structures/IBbsArticle";\n  ```  \n\n### 3. Type Safety and Error Prevention\n\n- **Always verify that functions and types exist** in the provided files before using them.  \n- **Use simple, direct type assertions** - avoid complex type manipulations.  \n- **Check for required vs optional properties** in DTO types before creating objects.  \n- **Use only documented API methods** - don\'t assume method existence.  \n\n### 4. Scenario Coverage\n\n- Fully implement the test scenario by chaining relevant API calls.  \n- If the scenario involves data creation, create prerequisite data using corresponding APIs.  \n- Include positive test cases (happy paths) and negative test cases when appropriate.  \n- **Keep test logic simple and straightforward** - avoid overly complex flows.  \n\n## Code Structure & Style\n\n### Test Function Structure\n\n```ts\nexport async function test_api_xxx(connection: api.IConnection): Promise<void> {\n  // Simple, clear test implementation\n}\n```\n\n### Validation Guidelines\n\n- Use `TestValidator` for validations as defined below  \n- Use `typia.assert` for type validations as defined below  \n- **Ensure proper function signatures** when using TestValidator methods  \n- **Verify all required properties** are included when creating test objects  \n\n### Test Validator Definition\n\n```ts\n/**\n * Test validator.\n *\n * `TestValidator` is a collection gathering E2E validation functions.\n *\n */\nexport declare namespace TestValidator {\n    /**\n     * Test whether condition is satisfied.\n     *\n     * @param title Title of error message when condition is not satisfied\n     * @return Currying function\n     */\n    const predicate: (title: string) => <T extends boolean | (() => boolean) | (() => Promise<boolean>)>(condition: T) => T extends () => Promise<boolean> ? Promise<void> : void;\n    /**\n     * Test whether two values are equal.\n     *\n     * If you want to validate `covers` relationship,\n     * call smaller first and then larger.\n     *\n     * Otherwise you wanna non equals validator, combine with {@link error}.\n     *\n     * @param title Title of error message when different\n     * @param exception Exception filter for ignoring some keys\n     * @returns Currying function\n     */\n    const equals: (title: string, exception?: (key: string) => boolean) => <T>(x: T) => (y: T) => void;\n    /**\n     * Test whether error occurs.\n     *\n     * If error occurs, nothing would be happened.\n     *\n     * However, no error exists, then exception would be thrown.\n     *\n     * @param title Title of exception because of no error exists\n     */\n    const error: (title: string) => <T>(task: () => T) => T extends Promise<any> ? Promise<void> : void;\n    const httpError: (title: string) => (...statuses: number[]) => <T>(task: () => T) => T extends Promise<any> ? Promise<void> : void;\n    function proceed(task: () => Promise<any>): Promise<Error | null>;\n    function proceed(task: () => any): Error | null;\n    /**\n     * Validate index API.\n     *\n     * Test whether two indexed values are equal.\n     *\n     * If two values are different, then exception would be thrown.\n     *\n     * @param title Title of error message when different\n     * @return Currying function\n     *\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_search.ts\n     */\n    const index: (title: string) => <Solution extends IEntity<any>>(expected: Solution[]) => <Summary extends IEntity<any>>(gotten: Summary[], trace?: boolean) => void;\n    /**\n     * Valiate search options.\n     *\n     * Test a pagination API supporting search options.\n     *\n     * @param title Title of error message when searching is invalid\n     * @returns Currying function\n     *\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_search.ts\n     */\n    const search: (title: string) => <Entity extends IEntity<any>, Request>(getter: (input: Request) => Promise<Entity[]>) => (total: Entity[], sampleCount?: number) => <Values extends any[]>(props: ISearchProps<Entity, Values, Request>) => Promise<void>;\n    interface ISearchProps<Entity extends IEntity<any>, Values extends any[], Request> {\n        fields: string[];\n        values(entity: Entity): Values;\n        filter(entity: Entity, values: Values): boolean;\n        request(values: Values): Request;\n    }\n    /**\n     * Validate sorting options.\n     *\n     * Test a pagination API supporting sorting options.\n     *\n     * You can validate detailed sorting options both ascending and descending orders\n     * with multiple fields. However, as it forms a complicate currying function,\n     * I recommend you to see below example code before using.\n     *\n     * @param title Title of error message when sorting is invalid\n     * @example https://github.com/samchon/nestia-template/blob/master/src/test/features/api/bbs/test_api_bbs_article_index_sort.ts\n     */\n    const sort: (title: string) => <T extends object, Fields extends string, Sortable extends Array<`-${Fields}` | `+${Fields}`> = Array<`-${Fields}` | `+${Fields}`>>(getter: (sortable: Sortable) => Promise<T[]>) => (...fields: Fields[]) => (comp: (x: T, y: T) => number, filter?: (elem: T) => boolean) => (direction: "+" | "-", trace?: boolean) => Promise<void>;\n    type Sortable<Literal extends string> = Array<`-${Literal}` | `+${Fields}`>;\n}\ninterface IEntity<Type extends string | number | bigint> {\n    id: Type;\n}\nexport {};\n```\n\n### Typia Assert Definition\n\n```ts\n/**\n * Asserts a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, just input parameter would be returned.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise you want to know all the errors, {@link validate} is the way to go.\n * Also, if you want to automatically cast the parametric value to the type `T`\n * when no problem (perform the assertion guard of type).\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @returns Parametric input value\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\nexport declare function assert<T>(input: T, errorFactory?: undefined | ((props: TypeGuardError.IProps) => Error)): T;\n/**\n * Asserts a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, just input parameter would be returned.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise, you want to know all the errors, {@link validate} is the way to go.\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @returns Parametric input value casted as `T`\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\nexport declare function assert<T>(input: unknown, errorFactory?: undefined | ((props: TypeGuardError.IProps) => Error)): T;\n/**\n * Assertion guard of a value type.\n *\n * Asserts a parametric value type and throws a {@link TypeGuardError} with detailed\n * reason, if the parametric value is not following the type `T`. Otherwise, the\n * value is following the type `T`, nothing would be returned, but the input value\n * would be automatically casted to the type `T`. This is the concept of\n * "Assertion Guard" of a value type.\n *\n * If what you want is not asserting but just knowing whether the parametric value is\n * following the type `T` or not, you can choose the {@link is} function instead.\n * Otherwise you want to know all the errors, {@link validate} is the way to go.\n * Also, if you want to returns the parametric value when no problem, you can use\n * {@link assert} function instead.\n *\n * On the other and, if you don\'t want to allow any superfluous property that is not\n * enrolled to the type `T`, you can use {@link assertGuardEquals} function instead.\n *\n * @template T Type of the input value\n * @param input A value to be asserted\n * @param errorFactory Custom error factory. Default is `TypeGuardError`\n * @throws A {@link TypeGuardError} instance with detailed reason\n *\n */\n```\n\n### Example Format:\n\n```ts\nimport { TestValidator } from "@nestia/e2e";\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { IExampleDto } from "@ORGANIZATION/PROJECT-api/lib/structures/IExampleDto";\nimport typia from "typia";\n\nexport async function test_api_example_flow(connection: api.IConnection): Promise<void> {\n  const input: IExampleDto = { ... }; // construct valid input\n\n  const result = await api.functional.example.post(connection, input);\n\n  typia.assert(result); // ensure response matches expected type\n  TestValidator.equals("result", exceptFunction)(result.someField);\n}\n\n```  \n\n```ts\nexport async function test_api_hub_cart_commodity_at(\n  connection: api.IConnection,\n): Promise<void> {\n  await test_api_hub_admin_login(pool);\n  await test_api_hub_seller_join(pool);\n  await test_api_hub_customer_create(pool);\n\n  const sale: IHubSale = await generate_random_sale(pool, "approved");\n  const commodity: IHubCartCommodity = await generate_random_cart_commodity(\n    pool,\n    sale,\n  );\n\n  const read: IHubCartCommodity =\n    await HubApi.functional.hub.customers.carts.commodities.at(\n      pool.customer,\n      null,\n      commodity.id,\n    );\n  TestValidator.equals("at", exceptSaleKeys)(commodity)(read);\n}\n\nexport const exceptSaleKeys = (key: string): boolean =>\n  key === "aggregate" || key === "swagger" || key.endsWith("_at");\n\n```  \n\n### Import Guidelines\n\n- **Only import what you actually use**  \n- **Verify all imports exist** in the provided API and DTO files  \n- **Use exact import paths** as specified in the file structure  \n\n```ts\nimport { TestValidator } from "@nestia/e2e";\nimport api from "@ORGANIZATION/PROJECT-api";\nimport { ISimpleDto } from "@ORGANIZATION/PROJECT-api/lib/structures/ISimpleDto";\nimport typia from "typia";\n```  \n\n### Data Construction\n\n- **Create simple, valid test data** that matches the DTO structure exactly  \n- **Include all required properties** as defined in the DTO  \n- **Use literal values** rather than complex data generation  \n\n```ts\n// Simple, clear data construction\nconst articleInput: IBbsArticleInput = {\n  title: "Test Article",\n  body: "Test article content",\n  // Include all required properties from the DTO\n};\n```  \n\n## Error Prevention Rules\n\n### 1. Type Matching\n\n- Always ensure function parameters match the expected types from API definitions  \n- Verify that all required properties are included in request objects  \n- Don\'t use properties that aren\'t defined in the DTO types  \n\n### 2. Import Validation\n\n- Only import functions and types that exist in the provided files  \n- Use exact import paths without assumptions  \n- **Follow the exact TestValidator and typia.assert usage patterns** as defined in their type definitions  \n\n### 3. Simple Logic\n\n- Avoid complex type manipulations and filtering functions  \n- Use straightforward validation patterns  \n- Don\'t use TypeScript directives like `@ts-expect-error` or `@ts-ignore`  \n\n### 4. Null Safety\n\n- Check for null/undefined values before using them  \n- Use optional chaining when appropriate  \n- Handle potential null returns from API calls  \n\n```ts\n// Safe null handling\nif (result && result.data) {\n  typia.assert<IExpectedType>(result.data);\n}\n```  \n\n### 5. Type Safety\n\n- If you declare empty array like `[]`, You must define the type of array together.  \n\nExample:  \n\n  ```typescript\n  const emptyArray: IBbsArticle[] = [];\n\n  TestValidator.equals("message")(\n      [] as IBbsArticleComment[],\n    )(data);\n  ```\n\n\n## Output Format\n\nReturn the following:  \n\n1. **Filename**: Suggested filename for the test (from input)  \n2. **Full Test Code**: A TypeScript file (max 300 lines) containing the E2E test  \n3. **Test Explanation**: Brief paragraph explaining what the test does and how it maps to the scenario  \n4. **Execution Notes**: Any setup steps or dependencies required to run the test  \n\n## Best Practices\n\n- **Keep tests simple and readable** - prioritize clarity over cleverness  \n- **Use only provided API functions and DTO types** - no assumptions  \n- **Create minimal but meaningful tests** that cover the core scenario  \n- **Make tests deterministic** with predictable data and flows  \n- **Include clear comments** for complex business logic only  \n- **Follow naming conventions** (`test_api_[feature]_[action]`)  \n- **Validate inputs and outputs** with simple, direct assertions  \n\n## Error Handling\n\n- If the scenario lacks sufficient detail, ask for clarification   \n- If no matching API function is found for a step, mention it and suggest alternatives from the provided API list  \n- If a required DTO property is missing or unclear, request the complete DTO definition  \n- **Always verify that all used functions and types exist** in the provided files before generating code'
+}, {
+    id: v4(),
+    created_at: (new Date).toISOString(),
+    type: "assistantMessage",
+    text: [ "You are the world's best E2E test code generator.", "You will be given a **scenario**, and your job is to generate the corresponding **E2E test code** using only the provided API functions and DTOs.", "", "## Rules", "- Follow the base E2E test style strictly. Never use other frameworks like Jest or Mocha.", "- Use `TestValidator.equals(...)` and `typia.assert(...)` to verify results.", "- Use `HubApi.functional.XXX` for all API calls. These are defined in API Files.", "- Use helper functions like `generate_random_xxx(...)` **only if** they already exist in the base test imports.", "- Do not invent new helpers or use utilities that are not explicitly shown.", "- Keep all tests deterministic and reliable.", "", "## File References", "### API Files", "```typescript", JSON.stringify(apiFiles, null, 2), "```", "", "### DTO Files", "```typescript", JSON.stringify(dtoFiles, null, 2), "```", "", "Now generate the E2E test function based on the given scenario.", "Only output a single `async function` named `test_api_{...}`. No explanation, no commentary." ].join("\n")
+} ];
+
+async function orchestrateTestProgress(ctx, scenarios) {
+    const start = new Date;
+    let complete = 0;
+    const events = await Promise.all(scenarios.map((async scenario => {
+        const code = await process$1(ctx, scenario);
+        const event = {
+            type: "testProgress",
+            created_at: start.toISOString(),
+            filename: `${code.domain}/${scenario.functionName}.ts`,
+            content: code.content,
+            completed: ++complete,
+            total: scenarios.length,
+            step: ctx.state().interface?.step ?? 0
+        };
+        ctx.dispatch(event);
+        return event;
+    })));
+    return events;
+}
+
+async function process$1(ctx, scenario) {
+    const pointer = {
+        value: null
+    };
+    const apiFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
+        [filename]: content
+    })), {});
+    const dtoFiles = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("src/api/structures/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
+        [filename]: content
+    })), {});
+    const agentica = new MicroAgentica({
+        model: ctx.model,
+        vendor: ctx.vendor,
+        config: {
+            ...ctx.config ?? {}
+        },
+        histories: transformTestProgressHistories(apiFiles, dtoFiles),
+        controllers: [ createApplication$1({
+            model: ctx.model,
+            build: next => {
+                pointer.value = next;
+            }
+        }) ]
+    });
+    agentica.on("request", (async event => {
+        if (event.body.tools) event.body.tool_choice = "required";
+    }));
+    await agentica.conversate([ "Create test code for below scenario:", "", "```json", JSON.stringify(scenario, null, 2), "```" ].join("\n"));
+    if (pointer.value === null) throw new Error("Failed to create test code.");
+    return pointer.value;
+}
+
+function createApplication$1(props) {
+    assertSchemaModel(props.model);
+    const application = collection$2[props.model];
+    return {
+        protocol: "class",
+        name: "Create Test Code",
+        application,
+        execute: {
+            createTestCode: next => {
+                props.build(next);
+            }
+        }
+    };
+}
+
+const claude$2 = {
+    model: "claude",
+    options: {
+        reference: true,
+        separate: null
+    },
+    functions: [ {
+        name: "createTestCode",
+        parameters: {
+            description: "Current Type: {@link ICreateTestCodeProps}",
+            type: "object",
+            properties: {
+                plan: {
+                    title: "Strategic approach for test implementation",
+                    description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines.",
+                    type: "string"
+                },
+                domain: {
+                    title: "Functional domain classification for test organization",
+                    description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
+                    type: "string"
+                },
+                content: {
+                    title: "Complete TypeScript E2E test implementation",
+                    description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
+                    type: "string"
+                }
+            },
+            required: [ "plan", "domain", "content" ],
+            additionalProperties: false,
+            $defs: {}
+        },
+        validate: (() => {
+            const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
+            const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
+                path: _path + ".plan",
+                expected: "string",
+                value: input.plan
+            }), "string" === typeof input.domain || _report(_exceptionable, {
+                path: _path + ".domain",
+                expected: "string",
+                value: input.domain
+            }), "string" === typeof input.content || _report(_exceptionable, {
+                path: _path + ".content",
+                expected: "string",
+                value: input.content
+            }) ].every((flag => flag));
+            const __is = input => "object" === typeof input && null !== input && _io0(input);
+            let errors;
+            let _report;
+            return input => {
+                if (false === __is(input)) {
+                    errors = [];
+                    _report = __typia_transform__validateReport._validateReport(errors);
+                    ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                        path: _path + "",
+                        expected: "ICreateTestCodeProps",
+                        value: input
+                    })) && _vo0(input, _path + "", true) || _report(true, {
+                        path: _path + "",
+                        expected: "ICreateTestCodeProps",
+                        value: input
+                    }))(input, "$input", true);
+                    const success = 0 === errors.length;
+                    return success ? {
+                        success,
+                        data: input
+                    } : {
+                        success,
+                        errors,
+                        data: input
+                    };
+                }
+                return {
+                    success: true,
+                    data: input
+                };
+            };
+        })()
+    } ]
+};
+
+const collection$2 = {
+    chatgpt: {
+        model: "chatgpt",
+        options: {
+            reference: true,
+            strict: false,
+            separate: null
+        },
+        functions: [ {
+            name: "createTestCode",
+            parameters: {
+                description: "Current Type: {@link ICreateTestCodeProps}",
+                type: "object",
+                properties: {
+                    plan: {
+                        title: "Strategic approach for test implementation",
+                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines.",
+                        type: "string"
+                    },
+                    domain: {
+                        title: "Functional domain classification for test organization",
+                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system',
+                        type: "string"
+                    },
+                    content: {
+                        title: "Complete TypeScript E2E test implementation",
+                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following",
+                        type: "string"
+                    }
+                },
+                required: [ "plan", "domain", "content" ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            validate: (() => {
+                const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
+                    path: _path + ".plan",
+                    expected: "string",
+                    value: input.plan
+                }), "string" === typeof input.domain || _report(_exceptionable, {
+                    path: _path + ".domain",
+                    expected: "string",
+                    value: input.domain
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "ICreateTestCodeProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "ICreateTestCodeProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    },
+    claude: claude$2,
+    llama: claude$2,
+    deepseek: claude$2,
+    3.1: claude$2,
+    "3.0": {
+        model: "3.0",
+        options: {
+            constraint: true,
+            recursive: 3,
+            separate: null
+        },
+        functions: [ {
+            name: "createTestCode",
+            parameters: {
+                type: "object",
+                properties: {
+                    plan: {
+                        type: "string",
+                        title: "Strategic approach for test implementation",
+                        description: "Strategic approach for test implementation.\n\nDefine the high-level strategy and logical flow for testing the given\nscenario. Focus on test methodology, data preparation, and assertion\nstrategy.\n\n### Critical Requirements\n\n- Must follow the Test Generation Guildelines.\n- Must Planning the test code Never occur the typescript compile error.\n\n### Planning Elements:\n\n#### Test Methodology\n\n- Identify test scenario type (CRUD operation, authentication flow,\n  validation test)\n- Define test data requirements and preparation strategy\n- Plan positive/negative test cases and edge cases\n- Design assertion logic and validation points\n\n#### Execution Strategy\n\n- Outline step-by-step test execution flow\n- Plan error handling and exception scenarios\n- Define cleanup and teardown procedures\n- Identify dependencies and prerequisites\n\n### Example Plan:\n\n    Test Strategy: Article Creation Validation\n    1. Prepare valid article data with required fields\n    2. Execute POST request to create article\n    3. Validate response structure and data integrity\n    4. Test error scenarios (missing fields, invalid data)\n    5. Verify database state changes\n    6. Reconsider the plan if it doesn't follow the Test Generation\n       Guildelines."
+                    },
+                    domain: {
+                        type: "string",
+                        title: "Functional domain classification for test organization",
+                        description: 'Functional domain classification for test organization.\n\nDetermines file structure and test categorization based on API\nfunctionality. Used for organizing tests into logical groups and directory\nhierarchies.\n\n### Naming Rules:\n\n- Lowercase English words only\n- Singular nouns (e.g., "article", "user", "comment")\n- Kebab-case for compound words (e.g., "user-profile", "payment-method")\n- Match primary API resource being tested\n- Domain Name must be named only one word.\n\n### Domain Examples:\n\n- `article` → Article management operations\n- `comment` → Comment-related functionality\n- `auth` → Authentication and authorization\n- `user` → User management operations\n- `payment` → Payment processing\n- `notification` → Notification system'
+                    },
+                    content: {
+                        type: "string",
+                        title: "Complete TypeScript E2E test implementation",
+                        description: "Complete TypeScript E2E test implementation.\n\nGenerate fully functional, compilation-error-free test code following"
+                    }
+                },
+                required: [ "plan", "domain", "content" ],
+                description: "Current Type: {@link ICreateTestCodeProps}",
+                additionalProperties: false
+            },
+            validate: (() => {
+                const _io0 = input => "string" === typeof input.plan && "string" === typeof input.domain && "string" === typeof input.content;
+                const _vo0 = (input, _path, _exceptionable = true) => [ "string" === typeof input.plan || _report(_exceptionable, {
+                    path: _path + ".plan",
+                    expected: "string",
+                    value: input.plan
+                }), "string" === typeof input.domain || _report(_exceptionable, {
+                    path: _path + ".domain",
+                    expected: "string",
+                    value: input.domain
+                }), "string" === typeof input.content || _report(_exceptionable, {
+                    path: _path + ".content",
+                    expected: "string",
+                    value: input.content
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "ICreateTestCodeProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "ICreateTestCodeProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    }
+};
+
+const transformTestScenarioHistories = (state, endponits, files) => {
+    if (state.analyze === null) return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Requirement analysis is not yet completed.", "Don't call the any tool function,", "but say to process the requirement analysis." ].join(" ")
+    } ]; else if (state.prisma === null) return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Prisma DB schema generation is not yet completed.", "Don't call the any tool function,", "but say to process the Prisma DB schema generation." ].join(" ")
+    } ]; else if (state.analyze.step !== state.prisma.step) return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Prisma DB schema generation has not been updated", "for the latest requirement analysis.", "Don't call the any tool function,", "but say to re-process the Prisma DB schema generation." ].join(" ")
+    } ]; else if (state.prisma.compiled.type !== "success") return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Prisma DB schema generation has not been updated", "for the latest requirement analysis.", "Don't call the any tool function,", "but say to re-process the Prisma DB schema generation." ].join(" ")
+    } ]; else if (state.interface === null) return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Interface generation is not yet completed.", "Don't call the any tool function,", "but say to process the interface generation." ].join(" ")
+    } ];
+    return [ {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: "# System Prompt: User Scenario Generator for API Endpoints\n\n## Role Definition\nYou are a world-class User Experience Analyst and Business Scenario Expert who specializes in analyzing API endpoints to generate comprehensive user scenarios from a pure user perspective. Your scenarios will be used as documentation and comments in test code to help developers understand the real-world user context behind each test.\n\n## Primary Objective\nGenerate all possible scenarios that real users might experience with a single given API endpoint, focusing exclusively on user intentions, motivations, and behaviors rather than technical testing perspectives.\n\n## Core Constraints\n\n### Single Endpoint Limitation\n- Each scenario must be completely achievable using ONLY the provided endpoint\n- Do NOT create scenarios that require multiple API calls or dependencies on other endpoints\n- Each user journey must be self-contained and complete within this single endpoint interaction\n\n### Practicality Constraint for Scenario Quantity\n\n- Do NOT generate an excessive number of test scenarios for trivial endpoints.\n- If the endpoint is a simple read-only operation that returns a static or predictable object (e.g. `{ cpu: number, system: number }`), limit scenarios to those that reflect meaningful variations in user context, not in raw input permutations.\n- Avoid producing multiple user error or edge case scenarios when they provide no additional business insight.\n- Prioritize business relevance over theoretical input diversity.\n- The goal is to maximize scenario value, not quantity.\n\n\n## Scenario Generation Principles\n\n### 1. Pure User-Centric Perspective\n- Focus entirely on what users want to achieve through the API\n- Consider real business contexts and user motivations\n- Emphasize user intent and expected value over technical implementation\n- Write as if documenting actual user stories for product requirements\n\n### 2. Comprehensive Single-Endpoint Coverage\nConsider all the following perspectives when generating scenarios for the single endpoint:\n\n#### A. Happy Path User Journeys\n- Most common and expected user behaviors\n- Standard workflows that lead to successful user outcomes\n- Primary business use cases users perform with this endpoint\n\n#### B. Alternative User Approaches\n- Valid but different ways users might achieve their goals\n- Scenarios using optional parameters or different input combinations\n- Less common but legitimate user behaviors within normal boundaries\n\n#### C. User Error Situations\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations\n\n#### D. Boundary User Behaviors\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n#### E. Contextual User Situations\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n### 3. Scenario Writing Format for Test Documentation\nWrite each scenario using the following structure optimized for test code comments:\n\n```\n**Scenario**: [Clear, descriptive title from user perspective]\n\n**User Context**: [Who is the user and why are they performing this action]\n\n**User Goal**: [What the user wants to accomplish]\n\n**User Actions**: [Specific steps the user takes with this endpoint]\n\n**Expected Experience**: [What the user expects to happen and how they'll know it worked]\n\n**Business Value**: [Why this scenario matters to the business]\n\n**Input Test Files**: [The test file names required for combining this scenario. If you have multiple files, connect them with commas.]\n```\n\n## Scenario Generation Checklist for Single Endpoint\n\n### Data Input Perspective\n- [ ] User providing complete, valid data\n- [ ] User missing required fields (intentionally or accidentally)\n- [ ] User sending incorrectly formatted data\n- [ ] User using boundary values (maximum/minimum)\n- [ ] User including special characters or multilingual content\n\n### User Permission Perspective\n- [ ] Users with appropriate permissions\n- [ ] Users with insufficient permissions\n- [ ] Unauthenticated users attempting access\n- [ ] Users with expired authentication\n\n### Resource State Perspective\n- [ ] User interacting when target resource exists\n- [ ] User interacting when target resource doesn't exist\n- [ ] User interacting with resources in various states\n- [ ] User encountering resources modified by others\n\n### User Experience Perspective\n- [ ] Users with realistic data volumes\n- [ ] Users performing time-sensitive operations\n- [ ] Users with different technical skill levels\n- [ ] Users in different business contexts\n\n### Business Context Perspective\n- [ ] Users following standard business processes\n- [ ] Users encountering business rule violations\n- [ ] Users in exceptional business situations\n- [ ] Users with varying business needs\n\n## Output Requirements for Test Documentation\n\nEach scenario must provide sufficient detail for developers to understand:\n\n1. **User Story Context**: Clear understanding of who the user is and their motivation\n2. **Business Justification**: Why this scenario matters for the product\n3. **User Behavior Pattern**: How real users would naturally interact with the endpoint\n4. **Success Criteria**: How users measure successful completion of their goal\n5. **Function Name Guidance**: Clear enough description to derive meaningful test function names\n\n## Quality Standards for Test Code Comments\n\n- Write scenarios that help developers empathize with real users\n- Focus on business value and user outcomes, not technical mechanics\n- Provide enough context that a developer can understand the user's situation\n- Ensure scenarios reflect realistic business situations\n- Make each scenario distinct and valuable for understanding user needs\n- Use language that both technical and non-technical stakeholders can understand\n\n## Guidelines\n\n- Avoid mentioning test code, assertions, or technical implementation details\n- Write purely from the user's perspective using narrative language\n- Create realistic scenarios that reflect actual business situations\n- Ensure scenarios are comprehensive yet practical for a single endpoint\n- Focus on user value and business outcomes\n- Make scenarios detailed enough to understand full user context\n\n## Expected Input\nYou will receive a single API endpoint specification including:\n- HTTP method and endpoint path\n- Request/response schemas\n- Authentication requirements\n- Parameter definitions\n- Business context when available\n\n## Expected Output\nFor the given API endpoint, provide:\n- Categorized user scenarios covering all perspectives mentioned above\n- Each scenario following the specified format for test documentation\n- Scenarios that are complete and achievable with only the single provided endpoint\n- Clear mapping between user intentions and the specific API operation\n- Sufficient detail to understand both user context and business value\n\n## Working Language\n- Default working language: English\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- Maintain consistent perspective and tone throughout all scenarios"
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "# Result of Analyze Agent", "- The following document contains the user requirements that were extracted through conversations with the user by the Analyze Agent.", "- The database schema was designed based on these requirements, so you may refer to this document when writing test code or reviewing the schema.", "", `## User Request`, "", `- ${state.analyze.reason}`, "", `## Requirement Analysis Report`, "", "```json", JSON.stringify(state.analyze.files), "```" ].join("\n")
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "# Result of Prisma Agent", "- Given the following database schema and entity-relationship diagram, write appropriate test code to validate the constraints and relationships defined in the schema. For example, if there is a unique column, include a test that ensures its uniqueness.", "- The test code should strictly adhere to the schema and relationships—no violations of constraints should occur.", "- Use the information from the schema and diagram to design meaningful and accurate test cases.", "", "## Prisma DB Schema", "```json", JSON.stringify(state.prisma.schemas), "```", "", "## Entity Relationship Diagrams", "```json", JSON.stringify(state.prisma.compiled.diagrams), "```" ].join("\n")
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "# Result of Interfaced Agent", "- OpenAPI document generation is ready.", "", "Call the provided tool function to generate the user scenarios", "referencing below OpenAPI document.", "", `## OpenAPI Document`, "```json", JSON.stringify(state.interface.document), "```" ].join("\n")
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: "# System Prompt: User Scenario Generator for API Endpoints\n\n## Role Definition\nYou are a world-class User Experience Analyst and Business Scenario Expert who specializes in analyzing API endpoints to generate comprehensive user scenarios from a pure user perspective. Your scenarios will be used as documentation and comments in test code to help developers understand the real-world user context behind each test.\n\n## Primary Objective\nGenerate all possible scenarios that real users might experience with a single given API endpoint, focusing exclusively on user intentions, motivations, and behaviors rather than technical testing perspectives.\n\n## Core Constraints\n\n### Single Endpoint Limitation\n- Each scenario must be completely achievable using ONLY the provided endpoint\n- Do NOT create scenarios that require multiple API calls or dependencies on other endpoints\n- Each user journey must be self-contained and complete within this single endpoint interaction\n\n### Practicality Constraint for Scenario Quantity\n\n- Do NOT generate an excessive number of test scenarios for trivial endpoints.\n- If the endpoint is a simple read-only operation that returns a static or predictable object (e.g. `{ cpu: number, system: number }`), limit scenarios to those that reflect meaningful variations in user context, not in raw input permutations.\n- Avoid producing multiple user error or edge case scenarios when they provide no additional business insight.\n- Prioritize business relevance over theoretical input diversity.\n- The goal is to maximize scenario value, not quantity.\n\n\n## Scenario Generation Principles\n\n### 1. Pure User-Centric Perspective\n- Focus entirely on what users want to achieve through the API\n- Consider real business contexts and user motivations\n- Emphasize user intent and expected value over technical implementation\n- Write as if documenting actual user stories for product requirements\n\n### 2. Comprehensive Single-Endpoint Coverage\nConsider all the following perspectives when generating scenarios for the single endpoint:\n\n#### A. Happy Path User Journeys\n- Most common and expected user behaviors\n- Standard workflows that lead to successful user outcomes\n- Primary business use cases users perform with this endpoint\n\n#### B. Alternative User Approaches\n- Valid but different ways users might achieve their goals\n- Scenarios using optional parameters or different input combinations\n- Less common but legitimate user behaviors within normal boundaries\n\n#### C. User Error Situations\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations\n\n#### D. Boundary User Behaviors\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n#### E. Contextual User Situations\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n### 3. Scenario Writing Format for Test Documentation\nWrite each scenario using the following structure optimized for test code comments:\n\n```\n**Scenario**: [Clear, descriptive title from user perspective]\n\n**User Context**: [Who is the user and why are they performing this action]\n\n**User Goal**: [What the user wants to accomplish]\n\n**User Actions**: [Specific steps the user takes with this endpoint]\n\n**Expected Experience**: [What the user expects to happen and how they'll know it worked]\n\n**Business Value**: [Why this scenario matters to the business]\n\n**Input Test Files**: [The test file names required for combining this scenario. If you have multiple files, connect them with commas.]\n```\n\n## Scenario Generation Checklist for Single Endpoint\n\n### Data Input Perspective\n- [ ] User providing complete, valid data\n- [ ] User missing required fields (intentionally or accidentally)\n- [ ] User sending incorrectly formatted data\n- [ ] User using boundary values (maximum/minimum)\n- [ ] User including special characters or multilingual content\n\n### User Permission Perspective\n- [ ] Users with appropriate permissions\n- [ ] Users with insufficient permissions\n- [ ] Unauthenticated users attempting access\n- [ ] Users with expired authentication\n\n### Resource State Perspective\n- [ ] User interacting when target resource exists\n- [ ] User interacting when target resource doesn't exist\n- [ ] User interacting with resources in various states\n- [ ] User encountering resources modified by others\n\n### User Experience Perspective\n- [ ] Users with realistic data volumes\n- [ ] Users performing time-sensitive operations\n- [ ] Users with different technical skill levels\n- [ ] Users in different business contexts\n\n### Business Context Perspective\n- [ ] Users following standard business processes\n- [ ] Users encountering business rule violations\n- [ ] Users in exceptional business situations\n- [ ] Users with varying business needs\n\n## Output Requirements for Test Documentation\n\nEach scenario must provide sufficient detail for developers to understand:\n\n1. **User Story Context**: Clear understanding of who the user is and their motivation\n2. **Business Justification**: Why this scenario matters for the product\n3. **User Behavior Pattern**: How real users would naturally interact with the endpoint\n4. **Success Criteria**: How users measure successful completion of their goal\n5. **Function Name Guidance**: Clear enough description to derive meaningful test function names\n\n## Quality Standards for Test Code Comments\n\n- Write scenarios that help developers empathize with real users\n- Focus on business value and user outcomes, not technical mechanics\n- Provide enough context that a developer can understand the user's situation\n- Ensure scenarios reflect realistic business situations\n- Make each scenario distinct and valuable for understanding user needs\n- Use language that both technical and non-technical stakeholders can understand\n\n## Guidelines\n\n- Avoid mentioning test code, assertions, or technical implementation details\n- Write purely from the user's perspective using narrative language\n- Create realistic scenarios that reflect actual business situations\n- Ensure scenarios are comprehensive yet practical for a single endpoint\n- Focus on user value and business outcomes\n- Make scenarios detailed enough to understand full user context\n\n## Expected Input\nYou will receive a single API endpoint specification including:\n- HTTP method and endpoint path\n- Request/response schemas\n- Authentication requirements\n- Parameter definitions\n- Business context when available\n\n## Expected Output\nFor the given API endpoint, provide:\n- Categorized user scenarios covering all perspectives mentioned above\n- Each scenario following the specified format for test documentation\n- Scenarios that are complete and achievable with only the single provided endpoint\n- Clear mapping between user intentions and the specific API operation\n- Sufficient detail to understand both user context and business value\n\n## Working Language\n- Default working language: English\n- Use the language specified by user in messages as the working language when explicitly provided\n- All thinking and responses must be in the working language\n- Maintain consistent perspective and tone throughout all scenarios"
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ `This is a description of different APIs.`, `Different APIs may have to be called to create one.`, `Check which functions have been developed.`, "```json", JSON.stringify(endponits, null, 2), "```" ].join("\n")
+    }, {
+        id: v4(),
+        created_at: (new Date).toISOString(),
+        type: "systemMessage",
+        text: [ "Below is basically the generated test code,", "which is a test to verify that the API is simply called and successful.", "Since there is already an automatically generated API,", "when a user requests to create a test scenario, two or more APIs must be combined,", "but a test in which the currently given endpoint is the main must be created.", '"Input Test Files" should be selected from the list of files here.', "```json", JSON.stringify(files, null, 2), "```" ].join("\n")
+    } ];
+};
+
+async function orchestrateTestScenario(ctx) {
+    const files = Object.entries(ctx.state().interface?.files ?? {}).filter((([filename]) => filename.startsWith("test/features/api/"))).reduce(((acc, [filename, content]) => Object.assign(acc, {
+        [filename]: content
+    })), {});
+    const operations = ctx.state().interface?.document.operations ?? [];
+    const endpoints = operations.map((it => ({
+        method: it.method,
+        path: it.path,
+        summary: it.summary,
+        description: it.description,
+        parameters: it.parameters,
+        requestBody: it.requestBody,
+        responseBody: it.responseBody
+    })));
+    const start = new Date;
+    let completed = 0;
+    const scenarios = await Promise.all(endpoints.map((async (endpoint, i, arr) => {
+        const endponits = arr.filter(((_el, j) => i !== j));
+        const rows = await process(ctx, endpoint, endponits, files);
+        ctx.dispatch({
+            type: "testScenario",
+            scenarios: rows,
+            total: rows.flatMap((el => el.scenarios)).length,
+            step: ctx.state().test?.step ?? 0,
+            completed,
+            created_at: start.toISOString()
+        });
+        return rows;
+    })));
+    return {
+        type: "testScenario",
+        scenarios: scenarios.flat(),
+        total: scenarios.flat().flatMap((el => el.scenarios)).length,
+        step: ctx.state().test?.step ?? 0,
+        completed,
+        created_at: start.toISOString()
+    };
+}
+
+async function process(ctx, endpoint, endpoints, files) {
+    const pointer = {
+        value: null
+    };
+    const agentica = new MicroAgentica({
+        model: ctx.model,
+        vendor: ctx.vendor,
+        config: {
+            ...ctx.config ?? {
+                locale: "en-US"
+            },
+            systemPrompt: {
+                describe: () => "Answer only 'completion' or 'failure'."
+            }
+        },
+        tokenUsage: ctx.usage(),
+        histories: [ ...transformTestScenarioHistories(ctx.state(), endpoints, files) ],
+        controllers: [ createApplication({
+            model: ctx.model,
+            build: next => {
+                pointer.value = next.scenarios;
+            }
+        }) ]
+    });
+    agentica.on("request", (async event => {
+        if (event.body.tools) event.body.tool_choice = "required";
+    }));
+    await agentica.conversate([ "Make User Scenarios for below endpoint:", "", "```json", JSON.stringify(endpoint, null, 2), "```" ].join("\n"));
+    if (pointer.value === null) throw new Error("Failed to make scenarios.");
+    return pointer.value;
+}
+
+function createApplication(props) {
+    assertSchemaModel(props.model);
+    const application = collection$1[props.model];
+    return {
+        protocol: "class",
+        name: "Make User Scenarios",
+        application,
+        execute: {
+            makeScenario: next => {
+                props.build(next);
+            }
+        }
+    };
+}
+
+const claude$1 = {
+    model: "claude",
+    options: {
+        reference: true,
+        separate: null
+    },
+    functions: [ {
+        name: "makeScenario",
+        parameters: {
+            description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+            type: "object",
+            properties: {
+                scenarios: {
+                    title: "Array of user scenarios",
+                    description: "Array of user scenarios.",
+                    type: "array",
+                    items: {
+                        description: "Current Type: {@link AutoBeTest.IScenario}",
+                        type: "object",
+                        properties: {
+                            endpoint: {
+                                description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                type: "object",
+                                properties: {
+                                    path: {
+                                        title: "HTTP path of the API operation",
+                                        description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                        type: "string"
+                                    },
+                                    method: {
+                                        title: "HTTP method of the API operation",
+                                        description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                        oneOf: [ {
+                                            const: "get"
+                                        }, {
+                                            const: "post"
+                                        }, {
+                                            const: "put"
+                                        }, {
+                                            const: "delete"
+                                        }, {
+                                            const: "patch"
+                                        } ]
+                                    }
+                                },
+                                required: [ "path", "method" ]
+                            },
+                            scenarios: {
+                                title: "Comprehensive collection of user-centric scenarios for the endpoint",
+                                description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
+                                type: "array",
+                                items: {
+                                    description: "Current Type: {@link AutoBeTest.Scenario}",
+                                    type: "object",
+                                    properties: {
+                                        functionName: {
+                                            title: "Descriptive function name derived from the user scenario",
+                                            description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
+                                            type: "string"
+                                        },
+                                        scenario: {
+                                            description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
+                                            type: "string"
+                                        }
+                                    },
+                                    required: [ "functionName", "scenario" ]
+                                }
+                            }
+                        },
+                        required: [ "endpoint", "scenarios" ]
+                    }
+                }
+            },
+            required: [ "scenarios" ],
+            additionalProperties: false,
+            $defs: {}
+        },
+        description: "Make user scenarios for the given endpoints.",
+        validate: (() => {
+            const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+            const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+            const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+            const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
+            const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<AutoBeTest.IScenario>",
+                value: input.scenarios
+            })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index3 + "]",
+                expected: "AutoBeTest.IScenario",
+                value: elem
+            })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index3 + "]",
+                expected: "AutoBeTest.IScenario",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<AutoBeTest.IScenario>",
+                value: input.scenarios
+            }) ].every((flag => flag));
+            const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".endpoint",
+                expected: "AutoBeOpenApi.IEndpoint",
+                value: input.endpoint
+            }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<AutoBeTest.Scenario>",
+                value: input.scenarios
+            })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index4 + "]",
+                expected: "AutoBeTest.Scenario",
+                value: elem
+            })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                path: _path + ".scenarios[" + _index4 + "]",
+                expected: "AutoBeTest.Scenario",
+                value: elem
+            }))).every((flag => flag)) || _report(_exceptionable, {
+                path: _path + ".scenarios",
+                expected: "Array<AutoBeTest.Scenario>",
+                value: input.scenarios
+            }) ].every((flag => flag));
+            const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                path: _path + ".path",
+                expected: "string",
+                value: input.path
+            }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                path: _path + ".method",
+                expected: '("delete" | "get" | "patch" | "post" | "put")',
+                value: input.method
+            }) ].every((flag => flag));
+            const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
+                path: _path + ".functionName",
+                expected: "string",
+                value: input.functionName
+            }), "string" === typeof input.scenario || _report(_exceptionable, {
+                path: _path + ".scenario",
+                expected: "string",
+                value: input.scenario
+            }) ].every((flag => flag));
+            const __is = input => "object" === typeof input && null !== input && _io0(input);
+            let errors;
+            let _report;
+            return input => {
+                if (false === __is(input)) {
+                    errors = [];
+                    _report = __typia_transform__validateReport._validateReport(errors);
+                    ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                        path: _path + "",
+                        expected: "IMakeScenarioProps",
+                        value: input
+                    })) && _vo0(input, _path + "", true) || _report(true, {
+                        path: _path + "",
+                        expected: "IMakeScenarioProps",
+                        value: input
+                    }))(input, "$input", true);
+                    const success = 0 === errors.length;
+                    return success ? {
+                        success,
+                        data: input
+                    } : {
+                        success,
+                        errors,
+                        data: input
+                    };
+                }
+                return {
+                    success: true,
+                    data: input
+                };
+            };
+        })()
+    } ]
+};
+
+const collection$1 = {
+    chatgpt: {
+        model: "chatgpt",
+        options: {
+            reference: true,
+            strict: false,
+            separate: null
+        },
+        functions: [ {
+            name: "makeScenario",
+            parameters: {
+                description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                type: "object",
+                properties: {
+                    scenarios: {
+                        title: "Array of user scenarios",
+                        description: "Array of user scenarios.",
+                        type: "array",
+                        items: {
+                            description: "Current Type: {@link AutoBeTest.IScenario}",
+                            type: "object",
+                            properties: {
+                                endpoint: {
+                                    description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                    type: "object",
+                                    properties: {
+                                        path: {
+                                            title: "HTTP path of the API operation",
+                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage.",
+                                            type: "string"
+                                        },
+                                        method: {
+                                            title: "HTTP method of the API operation",
+                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record",
+                                            type: "string",
+                                            enum: [ "get", "post", "put", "delete", "patch" ]
+                                        }
+                                    },
+                                    required: [ "path", "method" ]
+                                },
+                                scenarios: {
+                                    title: "Comprehensive collection of user-centric scenarios for the endpoint",
+                                    description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts",
+                                    type: "array",
+                                    items: {
+                                        description: "Current Type: {@link AutoBeTest.Scenario}",
+                                        type: "object",
+                                        properties: {
+                                            functionName: {
+                                                title: "Descriptive function name derived from the user scenario",
+                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions",
+                                                type: "string"
+                                            },
+                                            scenario: {
+                                                description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description",
+                                                type: "string"
+                                            }
+                                        },
+                                        required: [ "functionName", "scenario" ]
+                                    }
+                                }
+                            },
+                            required: [ "endpoint", "scenarios" ]
+                        }
+                    }
+                },
+                required: [ "scenarios" ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            description: "Make user scenarios for the given endpoints.",
+            validate: (() => {
+                const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+                const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
+                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.IScenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index3 + "]",
+                    expected: "AutoBeTest.IScenario",
+                    value: elem
+                })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index3 + "]",
+                    expected: "AutoBeTest.IScenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.IScenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.Scenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index4 + "]",
+                    expected: "AutoBeTest.Scenario",
+                    value: elem
+                })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index4 + "]",
+                    expected: "AutoBeTest.Scenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.Scenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                    path: _path + ".path",
+                    expected: "string",
+                    value: input.path
+                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                    path: _path + ".method",
+                    expected: '("delete" | "get" | "patch" | "post" | "put")',
+                    value: input.method
+                }) ].every((flag => flag));
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
+                    path: _path + ".functionName",
+                    expected: "string",
+                    value: input.functionName
+                }), "string" === typeof input.scenario || _report(_exceptionable, {
+                    path: _path + ".scenario",
+                    expected: "string",
+                    value: input.scenario
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "IMakeScenarioProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "IMakeScenarioProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    },
+    claude: claude$1,
+    llama: claude$1,
+    deepseek: claude$1,
+    3.1: claude$1,
+    "3.0": {
+        model: "3.0",
+        options: {
+            constraint: true,
+            recursive: 3,
+            separate: null
+        },
+        functions: [ {
+            name: "makeScenario",
+            parameters: {
+                type: "object",
+                properties: {
+                    scenarios: {
+                        type: "array",
+                        items: {
+                            type: "object",
+                            properties: {
+                                endpoint: {
+                                    type: "object",
+                                    properties: {
+                                        path: {
+                                            type: "string",
+                                            title: "HTTP path of the API operation",
+                                            description: "HTTP path of the API operation.\n\nThe URL path for accessing this API operation, using path parameters\nenclosed in curly braces (e.g., `/shoppings/customers/sales/{saleId}`).\n\nIt must be corresponded to the {@link parameters path parameters}.\n\nThe path structure should clearly indicate which database entity this\noperation is manipulating, helping to ensure all entities have\nappropriate API coverage."
+                                        },
+                                        method: {
+                                            type: "string",
+                                            enum: [ "get", "post", "put", "delete", "patch" ],
+                                            title: "HTTP method of the API operation",
+                                            description: "HTTP method of the API operation.\n\nNote that, if the API operation has {@link requestBody}, method must not\nbe `get`.\n\nAlso, even though the API operation has been designed to only get\ninformation, but it needs complicated request information, it must be\ndefined as `patch` method with {@link requestBody} data specification.\n\n- `get`: get information\n- `patch`: get information with complicated request data\n  ({@link requestBody})\n- `post`: create new record\n- `put`: update existing record\n- `delete`: remove record"
+                                        }
+                                    },
+                                    required: [ "path", "method" ],
+                                    description: "Target API endpoint for user scenario generation.\n\nThis represents the single API endpoint that will be analyzed to generate\ncomprehensive user scenarios. The endpoint contains all technical\nspecifications needed to understand user interactions, including HTTP\nmethods, paths, parameters, request/response schemas, and authentication\nrequirements.\n\n## Core Purpose\n\n- Serves as the foundation for user-centric scenario generation\n- Contains complete API specification for understanding user capabilities\n- Provides schema constraints for realistic user data generation\n- Defines authentication and permission requirements for user context\n\n## User Scenario Context\n\nThis endpoint information enables generation of scenarios that consider:\n\n- What users can realistically accomplish with this endpoint\n- How users would naturally interact with the API functionality\n- What business value users seek from this endpoint\n- What constraints and limitations users will encounter\n- How authentication affects user access patterns\n- What data formats users need to provide or expect to receive\n\n## Single Endpoint Constraint\n\nEach scenario generated must interact with ONLY this endpoint. Scenarios\nshould not assume or require calls to other endpoints, ensuring each user\njourney is complete and testable in isolation.\n\n------------------------------\n\nDescription of the current {@link AutoBeOpenApi.IEndpoint} type:\n\n> API endpoint information.",
+                                    additionalProperties: false
+                                },
+                                scenarios: {
+                                    type: "array",
+                                    items: {
+                                        type: "object",
+                                        properties: {
+                                            functionName: {
+                                                type: "string",
+                                                title: "Descriptive function name derived from the user scenario",
+                                                description: "Descriptive function name derived from the user scenario.\n\nThe function name serves as a concise, technical identifier that clearly\nrepresents the specific user scenario being described. It should be\nimmediately understandable and directly correspond to the user situation\nwithout requiring additional context.\n\n## Naming Convention\n\n- Must start with `test_` prefix (mandatory requirement)\n- Use snake_case formatting throughout\n- Include the primary user action (create, get, update, delete, list, etc.)\n- Specify the target resource (user, product, order, profile, etc.)\n- Add scenario-specific context (valid_data, invalid_email, not_found,\n  etc.)\n\n## Content Structure\n\nFunction names should follow this pattern:\n`test_[user_action]_[resource]_[scenario_context]`\n\nWhere:\n\n- `user_action`: What the user is trying to do\n- `resource`: What the user is interacting with\n- `scenario_context`: The specific situation or condition\n\n## User-Focused Examples\n\n- `test_create_user_profile_with_complete_information` - User providing all\n  available profile data\n- `test_retrieve_user_profile_when_profile_exists` - User accessing their\n  existing profile\n- `test_update_user_email_with_valid_new_address` - User changing their\n  email to a valid new one\n- `test_delete_user_account_when_user_lacks_permission` - User attempting\n  account deletion without authorization\n- `test_search_user_profiles_with_pagination_preferences` - User browsing\n  profiles with specific pagination\n\n## Clarity Guidelines\n\n- Prioritize clarity over brevity\n- Avoid technical jargon or implementation terms\n- Use terminology that reflects user perspective\n- Ensure the name alone conveys the user's intent\n- Make it understandable to non-technical stakeholders\n- Keep consistent with user scenario description\n\n## Single Endpoint Alignment\n\nFunction names must reflect scenarios that:\n\n- Accomplish user goals through this single endpoint only\n- Don't imply dependency on other API operations\n- Represent complete user interactions"
+                                            },
+                                            scenario: {
+                                                type: "string",
+                                                description: "Comprehensive user scenario description written from pure user\nperspective.\n\nThis describes a complete user journey, motivation, and expected outcome\nwhen interacting with the API endpoint. The description focuses entirely\non user intent, context, and natural behavior patterns rather than\ntechnical testing considerations.\n\n## User-Centric Writing Approach\n\n- Write as if describing a real person's experience and motivation\n- Focus on business context and user goals, not system functionality\n- Use natural language that business stakeholders would understand\n- Emphasize user value and expected benefits\n- Avoid technical terminology or implementation details\n\n## Required Content Elements\n\nEach scenario description must include:\n\n### 1. User Context and Motivation\n\n- Who is the user (role, background, current situation)\n- Why they need to perform this action (business motivation)\n- What problem they're trying to solve or goal they want to achieve\n- Any relevant background circumstances or constraints\n\n### 2. User Actions and Behavior\n\n- Specific steps the user takes to accomplish their goal\n- What information or data the user provides\n- How the user naturally approaches the interaction\n- Any decision-making process the user goes through\n\n### 3. User Expectations and Desired Outcomes\n\n- What the user expects to happen as a result\n- How the user will know if they were successful\n- What value or benefit the user expects to receive\n- How this fits into their broader workflow or objectives\n\n### 4. Business Impact and Value\n\n- How this scenario relates to business objectives\n- What business processes or workflows this supports\n- Why this user behavior matters to the organization\n- What risks or opportunities this scenario represents\n\n## Single Endpoint Constraint Integration\n\nEach scenario must:\n\n- Represent a complete user journey achievable through this single endpoint\n- Include all necessary context without referencing other API operations\n- Describe user expectations based solely on this endpoint's capabilities\n- Avoid scenarios that would logically require multiple API calls\n\n## Quality and Realism Standards\n\n- Base scenarios on realistic business situations\n- Include specific, concrete details rather than generic descriptions\n- Ensure scenarios reflect actual user behaviors and motivations\n- Make each scenario distinct and valuable for understanding user needs\n- Provide enough detail to understand full context without being verbose\n\n## User-Focused Example Scenarios\n\n- \"A busy project manager needs to quickly create a new team member's user\n  account during an onboarding meeting. They have all the necessary\n  information readily available and expect the account to be immediately\n  active so the new employee can start working right away.\"\n- \"A customer support representative is helping a customer who forgot their\n  login credentials. The customer provides their email address, and the\n  representative expects to quickly retrieve the associated account\n  information to assist with password recovery.\"\n- \"A system administrator discovers that a former employee's account is\n  still active after their departure. They need to immediately deactivate\n  this account for security purposes and expect confirmation that the\n  account can no longer be used to access company resources.\"\n\n## Language and Tone\n\n- Use active voice and present tense when describing user actions\n- Write in a narrative style that tells the user's story\n- Balance professional tone with human context\n- Ensure accessibility for both technical and non-technical readers\n- Maintain consistency in perspective throughout the description"
+                                            }
+                                        },
+                                        required: [ "functionName", "scenario" ],
+                                        description: "Current Type: {@link AutoBeTest.Scenario}",
+                                        additionalProperties: false
+                                    },
+                                    title: "Comprehensive collection of user-centric scenarios for the endpoint",
+                                    description: "Comprehensive collection of user-centric scenarios for the endpoint.\n\nEach scenario represents a realistic user journey, intention, or\nsituation when interacting with this specific API endpoint. All scenarios\nare written from the user's perspective, focusing on what they want to\nachieve and how they naturally interact with the API functionality.\n\n## Scenario Coverage Framework\n\nThe scenarios must comprehensively cover all user interaction patterns:\n\n### 1. Happy Path User Journeys\n\n- Primary business use cases that users commonly perform\n- Standard workflows leading to successful user outcomes\n- Typical user behaviors with valid inputs and proper permissions\n- Most frequent user intentions and expected interactions\n\n### 2. Alternative User Approaches\n\n- Valid alternative ways users might achieve their goals\n- User scenarios utilizing optional parameters or different input patterns\n- Less common but legitimate user behaviors within normal boundaries\n- User experimentation with available API features\n\n### 3. User Error Situations\n\n- Natural user mistakes with input data (incorrect formats, missing fields)\n- User attempts without proper authentication or authorization\n- User actions that violate business rules or constraints\n- User encounters with system limitations (rate limits, quotas)\n\n### 4. Boundary User Behaviors\n\n- User attempts with extreme values (minimum/maximum limits)\n- User submissions with empty, null, or unusual data\n- User inputs with special characters, long strings, or edge cases\n- User interactions testing system boundaries\n\n### 5. Contextual User Situations\n\n- User interactions when resources exist vs. don't exist\n- Different user roles attempting the same actions\n- Time-sensitive user scenarios (expired sessions, scheduled operations)\n- User attempts during various system states\n\n## User-Centric Quality Standards\n\nEach scenario must:\n\n- Focus entirely on user motivation, context, and expected outcomes\n- Describe realistic business situations users actually encounter\n- Include clear user intent and the value they seek\n- Specify user-provided data and user-expected results\n- Be complete within the single endpoint constraint\n- Provide sufficient context for understanding user behavior patterns\n- Avoid technical implementation details or testing terminology\n\n## Single Endpoint Constraint Application\n\nEvery scenario must:\n\n- Complete the entire user journey using only this one endpoint\n- Not depend on or reference other API endpoints\n- Include all necessary context within the scenario itself\n- Represent a complete, self-contained user interaction\n\n## Business Value Focus\n\nThese user scenarios ensure:\n\n- Understanding of real user needs and behaviors\n- Comprehensive coverage of user interaction patterns\n- Proper handling of user errors and edge cases\n- Appropriate user feedback and experience design\n- Business rule validation from user perspective\n- Security and permission handling for different user contexts"
+                                }
+                            },
+                            required: [ "endpoint", "scenarios" ],
+                            description: "Current Type: {@link AutoBeTest.IScenario}",
+                            additionalProperties: false
+                        },
+                        title: "Array of user scenarios",
+                        description: "Array of user scenarios."
+                    }
+                },
+                required: [ "scenarios" ],
+                description: " Properties containing the endpoints and user scenarios.\n\n------------------------------\n\nCurrent Type: {@link IMakeScenarioProps}",
+                additionalProperties: false
+            },
+            description: "Make user scenarios for the given endpoints.",
+            validate: (() => {
+                const _io0 = input => Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io1(elem)));
+                const _io1 = input => "object" === typeof input.endpoint && null !== input.endpoint && _io2(input.endpoint) && (Array.isArray(input.scenarios) && input.scenarios.every((elem => "object" === typeof elem && null !== elem && _io3(elem))));
+                const _io2 = input => "string" === typeof input.path && ("get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method);
+                const _io3 = input => "string" === typeof input.functionName && "string" === typeof input.scenario;
+                const _vo0 = (input, _path, _exceptionable = true) => [ (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.IScenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index3) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index3 + "]",
+                    expected: "AutoBeTest.IScenario",
+                    value: elem
+                })) && _vo1(elem, _path + ".scenarios[" + _index3 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index3 + "]",
+                    expected: "AutoBeTest.IScenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.IScenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo1 = (input, _path, _exceptionable = true) => [ ("object" === typeof input.endpoint && null !== input.endpoint || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                })) && _vo2(input.endpoint, _path + ".endpoint", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".endpoint",
+                    expected: "AutoBeOpenApi.IEndpoint",
+                    value: input.endpoint
+                }), (Array.isArray(input.scenarios) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.Scenario>",
+                    value: input.scenarios
+                })) && input.scenarios.map(((elem, _index4) => ("object" === typeof elem && null !== elem || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index4 + "]",
+                    expected: "AutoBeTest.Scenario",
+                    value: elem
+                })) && _vo3(elem, _path + ".scenarios[" + _index4 + "]", _exceptionable) || _report(_exceptionable, {
+                    path: _path + ".scenarios[" + _index4 + "]",
+                    expected: "AutoBeTest.Scenario",
+                    value: elem
+                }))).every((flag => flag)) || _report(_exceptionable, {
+                    path: _path + ".scenarios",
+                    expected: "Array<AutoBeTest.Scenario>",
+                    value: input.scenarios
+                }) ].every((flag => flag));
+                const _vo2 = (input, _path, _exceptionable = true) => [ "string" === typeof input.path || _report(_exceptionable, {
+                    path: _path + ".path",
+                    expected: "string",
+                    value: input.path
+                }), "get" === input.method || "post" === input.method || "put" === input.method || "delete" === input.method || "patch" === input.method || _report(_exceptionable, {
+                    path: _path + ".method",
+                    expected: '("delete" | "get" | "patch" | "post" | "put")',
+                    value: input.method
+                }) ].every((flag => flag));
+                const _vo3 = (input, _path, _exceptionable = true) => [ "string" === typeof input.functionName || _report(_exceptionable, {
+                    path: _path + ".functionName",
+                    expected: "string",
+                    value: input.functionName
+                }), "string" === typeof input.scenario || _report(_exceptionable, {
+                    path: _path + ".scenario",
+                    expected: "string",
+                    value: input.scenario
+                }) ].every((flag => flag));
+                const __is = input => "object" === typeof input && null !== input && _io0(input);
+                let errors;
+                let _report;
+                return input => {
+                    if (false === __is(input)) {
+                        errors = [];
+                        _report = __typia_transform__validateReport._validateReport(errors);
+                        ((input, _path, _exceptionable = true) => ("object" === typeof input && null !== input || _report(true, {
+                            path: _path + "",
+                            expected: "IMakeScenarioProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "IMakeScenarioProps",
+                            value: input
+                        }))(input, "$input", true);
+                        const success = 0 === errors.length;
+                        return success ? {
+                            success,
+                            data: input
+                        } : {
+                            success,
+                            errors,
+                            data: input
+                        };
+                    }
+                    return {
+                        success: true,
+                        data: input
+                    };
+                };
+            })()
+        } ]
+    }
+};
+
+const orchestrateTest = ctx => async props => {
+    const start = new Date;
+    ctx.dispatch({
+        type: "testStart",
+        created_at: start.toISOString(),
+        reason: props.reason,
+        step: ctx.state().analyze?.step ?? 0
+    });
+    const operations = ctx.state().interface?.document.operations ?? [];
+    if (operations.length === 0) {
+        const history = {
+            id: v4(),
+            type: "assistantMessage",
+            created_at: start.toISOString(),
+            completed_at: (new Date).toISOString(),
+            text: "Unable to write test code because there are no Operations, " + "please check if the Interface agent is called."
+        };
+        ctx.histories().push(history);
+        ctx.dispatch(history);
+        return history;
+    }
+    const scenarioEvent = await orchestrateTestScenario(ctx);
+    const scenarios = scenarioEvent.scenarios.map((scenario => scenario.scenarios)).flat();
+    const codes = await orchestrateTestProgress(ctx, scenarios);
+    const correct = await orchestrateTestCorrect(ctx, codes);
+    const history = {
+        type: "test",
+        id: v4(),
+        completed_at: (new Date).toISOString(),
+        created_at: start.toISOString(),
+        files: correct.files,
+        compiled: correct.result,
+        reason: "Step to the test generation referencing the interface",
+        step: ctx.state().interface?.step ?? 0
+    };
+    ctx.dispatch({
+        type: "testComplete",
+        created_at: start.toISOString(),
+        files: correct.files,
+        step: ctx.state().interface?.step ?? 0
+    });
+    ctx.state().test = history;
+    ctx.histories().push(history);
+    return history;
+};
+
 var StringUtil;
 
 (function(StringUtil) {
@@ -8927,7 +10487,7 @@ const createAutoBeController = props => {
                 };
             },
             test: async next => {
-                const r = await orchestrateTest()(next);
+                const r = await orchestrateTest(props.context)(next);
                 if (r.type === "test") return {
                     type: r.compiled.type,
                     description: r.compiled.type === "success" ? "Test functions have been generated successfully." : r.compiled.type === "failure" ? "Test functions are written, but compilation failed." : "Unexpected error occurred while writing test functions."