@autobe/agent 0.25.5 → 0.25.6

package/src/orchestrate/interface/histories/transformInterfaceGroupHistories.ts

@@ -5,7 +5,7 @@ import { v7 } from "uuid";
 import { AutoBeSystemPromptConstant } from "../../../constants/AutoBeSystemPromptConstant";
 import { AutoBeState } from "../../../context/AutoBeState";
 import { transformInterfaceAssetHistories } from "./transformInterfaceAssetHistories";
-import { transformInterfaceCommonPrerequisiteHistories } from "./transformInterfaceCommonPrerequisiteHistories";
+import { transformInterfaceCommonHistories } from "./transformInterfaceCommonHistories";
 
 export const transformInterfaceGroupHistories = (props: {
   state: AutoBeState;
@@ -13,9 +13,7 @@ export const transformInterfaceGroupHistories = (props: {
 }): Array<
   IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage
 > => {
-  const prerequisite = transformInterfaceCommonPrerequisiteHistories(
-    props.state,
-  );
+  const prerequisite = transformInterfaceCommonHistories(props.state);
   if (prerequisite !== null) return prerequisite;
 
   return [
@@ -39,15 +37,18 @@ export const transformInterfaceGroupHistories = (props: {
       text: StringUtil.trim`
         ## API Design Instructions
 
-        The following API-specific instructions were extracted by AI from
-        the user's utterances. These focus ONLY on API interface design aspects
+        The following API-specific instructions were extracted from
+        the user's requirements. These focus on API interface design aspects
         such as endpoint patterns, request/response formats, DTO schemas,
         and operation specifications.
 
-        Apply these instructions when organizing API endpoints into logical groups.
-        Consider how to structure and categorize endpoints based on business domains,
-        resource types, or functional areas. If the instructions are not relevant
-        to endpoint grouping and organization, you may ignore them.
+        Follow these instructions when organizing API endpoints.
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
       `,

package/src/orchestrate/interface/histories/transformInterfaceOperationHistories.ts

@@ -47,15 +47,18 @@ export const transformInterfaceOperationHistories = (props: {
       text: StringUtil.trim`
         ## API Design Instructions
 
-        The following API-specific instructions were extracted by AI from
-        the user's utterances. These focus ONLY on API interface design aspects
+        The following API-specific instructions were extracted from
+        the user's requirements. These focus on API interface design aspects
         such as endpoint patterns, request/response formats, DTO schemas,
         and operation specifications.
 
-        Apply these instructions when designing the detailed operation specifications
-        for each endpoint. Consider parameter types, request/response structures,
-        error handling, and API behavior patterns. If the instructions are not
-        relevant to the operations you need to implement, you may ignore them.
+        Follow these instructions when designing operation specifications. 
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
 

package/src/orchestrate/interface/histories/transformInterfaceSchemaHistories.ts

@@ -28,15 +28,18 @@ export const transformInterfaceSchemaHistories = (props: {
     text: StringUtil.trim`
       ## API Design Instructions
 
-      The following API-specific instructions were extracted by AI from
-      the user's utterances. These focus ONLY on API interface design aspects
+      The following API-specific instructions were extracted from
+      the user's requirements. These focus on API interface design aspects
       such as endpoint patterns, request/response formats, DTO schemas,
       and operation specifications.
 
-      Apply these instructions when creating JSON schema components for the operations.
-      Focus on data structure design, field naming conventions, validation rules,
-      and type definitions. If the instructions are not relevant to the schema
-      components you need to create, you may ignore them.
+      Follow these instructions when creating JSON schema components. 
+      Carefully distinguish between:
+      - Suggestions or recommendations (consider these as guidance)
+      - Direct specifications or explicit commands (these must be followed exactly)
+      
+      When instructions contain direct specifications or explicit design decisions, 
+      follow them precisely even if you believe you have better alternatives.
 
       ${props.instruction}
 

package/src/orchestrate/interface/orchestrateInterface.ts

@@ -17,7 +17,7 @@ import { HashMap, Pair } from "tstl";
 import { v7 } from "uuid";
 
 import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeApplicationProps } from "../../context/IAutoBeApplicationProps";
+import { IAutoBeFacadeApplicationProps } from "../../context/IAutoBeFacadeApplicationProps";
 import { predicateStateMessage } from "../../utils/predicateStateMessage";
 import { orchestrateInterfaceAuthorizations } from "./orchestrateInterfaceAuthorizations";
 import { orchestrateInterfaceComplement } from "./orchestrateInterfaceComplement";
@@ -32,7 +32,7 @@ import { JsonSchemaFactory } from "./utils/JsonSchemaFactory";
 export const orchestrateInterface =
   <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>) =>
   async (
-    props: IAutoBeApplicationProps,
+    props: IAutoBeFacadeApplicationProps,
   ): Promise<AutoBeAssistantMessageHistory | AutoBeInterfaceHistory> => {
     // PREDICATION
     const start: Date = new Date();

package/src/orchestrate/prisma/histories/transformPrismaComponentsHistories.ts

@@ -85,12 +85,17 @@ export const transformPrismaComponentsHistories = (
 
         ## Database Design Instructions
 
-        The following database-specific instructions were extracted by AI from
-        the user's utterances. These focus ONLY on database schema design aspects
+        The following database-specific instructions were extracted from
+        the user's requirements. These focus on database schema design aspects
         such as table structure, relationships, constraints, and indexing strategies.
 
-        Reference these instructions when designing namespace components and 
-        DB table names.
+        Follow these instructions when designing namespace components and DB table names. 
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
       `,

package/src/orchestrate/prisma/histories/transformPrismaSchemaHistories.ts

@@ -39,13 +39,16 @@ export const transformPrismaSchemaHistories = (props: {
       text: StringUtil.trim`
         ## Database Design Instructions
 
-        The following database-specific instructions were extracted by AI from
-        the user's utterances. These focus ONLY on database schema design aspects
+        The following database-specific instructions were extracted from
+        the user's requirements. These focus on database schema design aspects
         such as table structure, relationships, constraints, and indexing strategies.
 
-        Reference these instructions when designing the DB schema for this specific
-        component. If the instruction is not related to the current domain or
-        component, you may ignore it.
+        Follow these instructions when designing the DB schema. Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
 

package/src/orchestrate/prisma/orchestratePrisma.ts

@@ -13,7 +13,7 @@ import { ILlmSchema } from "@samchon/openapi";
 import { v7 } from "uuid";
 
 import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeApplicationProps } from "../../context/IAutoBeApplicationProps";
+import { IAutoBeFacadeApplicationProps } from "../../context/IAutoBeFacadeApplicationProps";
 import { predicateStateMessage } from "../../utils/predicateStateMessage";
 import { orchestratePrismaComponents } from "./orchestratePrismaComponent";
 import { orchestratePrismaCorrect } from "./orchestratePrismaCorrect";
@@ -22,7 +22,7 @@ import { orchestratePrismaSchemas } from "./orchestratePrismaSchemas";
 
 export const orchestratePrisma = async <Model extends ILlmSchema.Model>(
   ctx: AutoBeContext<Model>,
-  props: IAutoBeApplicationProps,
+  props: IAutoBeFacadeApplicationProps,
 ): Promise<AutoBePrismaHistory | AutoBeAssistantMessageHistory> => {
   // PREDICATION
   const start: Date = new Date();

package/src/orchestrate/realize/orchestrateRealize.ts

@@ -13,7 +13,7 @@ import { ILlmSchema } from "@samchon/openapi";
 import { v7 } from "uuid";
 
 import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeApplicationProps } from "../../context/IAutoBeApplicationProps";
+import { IAutoBeFacadeApplicationProps } from "../../context/IAutoBeFacadeApplicationProps";
 import { executeCachedBatch } from "../../utils/executeCachedBatch";
 import { predicateStateMessage } from "../../utils/predicateStateMessage";
 import { compileRealizeFiles } from "./internal/compileRealizeFiles";
@@ -27,7 +27,7 @@ import { generateRealizeScenario } from "./utils/generateRealizeScenario";
 export const orchestrateRealize =
   <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>) =>
   async (
-    props: IAutoBeApplicationProps,
+    props: IAutoBeFacadeApplicationProps,
   ): Promise<AutoBeAssistantMessageHistory | AutoBeRealizeHistory> => {
     // PREDICATION
     const document: AutoBeOpenApi.IDocument | undefined =

package/src/orchestrate/test/histories/transformTestScenarioHistories.ts

@@ -53,16 +53,19 @@ export const transformTestScenarioHistories = (props: {
       text: StringUtil.trim`
         ## Instructions
 
-        The following e2e-test-specific instructions were extracted by AI from
+        The following e2e-test-specific instructions were extracted from
         the user's requirements and conversations. These instructions focus
         exclusively on test-related aspects such as test coverage priorities,
         specific edge cases to validate, business logic verification strategies,
         and critical user workflows that must be tested.
         
-        Apply these instructions when generating test scenarios to ensure the
-        tests align with the user's testing requirements and expectations.
-        If any instructions are not relevant to the target API operations,
-        you may ignore them.
+        Follow these instructions when generating test scenarios.
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
 

package/src/orchestrate/test/histories/transformTestScenarioReviewHistories.ts

@@ -43,16 +43,19 @@ export function transformTestScenarioReviewHistories(props: {
       text: StringUtil.trim`
         ## Instructions
 
-        The following e2e-test-specific instructions were extracted by AI from
+        The following e2e-test-specific instructions were extracted from
         the user's requirements and conversations. These instructions focus
         exclusively on test-related aspects such as test coverage priorities,
         specific edge cases to validate, business logic verification strategies,
         and critical user workflows that must be tested.
         
-        Apply these instructions when reviewing test scenarios to ensure the
-        tests align with the user's testing requirements and expectations.
-        If any instructions are not relevant to the target API operations,
-        you may ignore them.
+        Follow these instructions when reviewing test scenarios.
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
 

package/src/orchestrate/test/histories/transformTestWriteHistories.ts

@@ -48,16 +48,19 @@ export async function transformTestWriteHistories<
 
         ## Instructions
 
-        The following e2e-test-specific instructions were extracted by AI from
+        The following e2e-test-specific instructions were extracted from
         the user's requirements and conversations. These instructions focus
         exclusively on test-related aspects such as test data generation strategies,
         assertion patterns, error handling approaches, and specific validation logic
         that should be implemented in the test code.
         
-        Apply these instructions when implementing the e2e test function to ensure
-        the test code aligns with the user's testing requirements and expectations.
-        If any instructions are not relevant to the target test scenario,
-        you may ignore them.
+        Follow these instructions when implementing the e2e test function.
+        Carefully distinguish between:
+        - Suggestions or recommendations (consider these as guidance)
+        - Direct specifications or explicit commands (these must be followed exactly)
+        
+        When instructions contain direct specifications or explicit design decisions, 
+        follow them precisely even if you believe you have better alternatives.
 
         ${props.instruction}
 

package/src/orchestrate/test/orchestrateTest.ts

@@ -11,7 +11,7 @@ import { ILlmSchema } from "@samchon/openapi";
 import { v7 } from "uuid";
 
 import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeApplicationProps } from "../../context/IAutoBeApplicationProps";
+import { IAutoBeFacadeApplicationProps } from "../../context/IAutoBeFacadeApplicationProps";
 import { predicateStateMessage } from "../../utils/predicateStateMessage";
 import { orchestrateTestCorrect } from "./orchestrateTestCorrect";
 import { orchestrateTestScenario } from "./orchestrateTestScenario";
@@ -21,7 +21,7 @@ import { IAutoBeTestWriteResult } from "./structures/IAutoBeTestWriteResult";
 export const orchestrateTest =
   <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>) =>
   async (
-    props: IAutoBeApplicationProps,
+    props: IAutoBeFacadeApplicationProps,
   ): Promise<AutoBeAssistantMessageHistory | AutoBeTestHistory> => {
     // PREDICATION
     const start: Date = new Date();

package/lib/context/IAutoBeApplication.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"IAutoBeApplication.js","sourceRoot":"","sources":["../../src/context/IAutoBeApplication.ts"],"names":[],"mappings":""}

package/lib/context/IAutoBeApplicationProps.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"IAutoBeApplicationProps.js","sourceRoot":"","sources":["../../src/context/IAutoBeApplicationProps.ts"],"names":[],"mappings":""}

package/lib/context/IAutoBeApplicationResult.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"IAutoBeApplicationResult.js","sourceRoot":"","sources":["../../src/context/IAutoBeApplicationResult.ts"],"names":[],"mappings":""}

package/lib/orchestrate/interface/histories/transformInterfaceCommonPrerequisiteHistories.d.ts

@@ -1,3 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeState } from "../../../context/AutoBeState";
-export declare const transformInterfaceCommonPrerequisiteHistories: (state: AutoBeState) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage> | null;

package/lib/orchestrate/interface/histories/transformInterfaceCommonPrerequisiteHistories.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformInterfaceCommonPrerequisiteHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceCommonPrerequisiteHistories.ts"],"names":[],"mappings":";;;AACA,+BAA0B;AAInB,MAAM,6CAA6C,GAAG,CAC3D,KAAkB,EAGX,EAAE;IACT,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI;QACxB,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE;oBACJ,4CAA4C;oBAC5C,mCAAmC;oBACnC,8CAA8C;iBAC/C,CAAC,IAAI,CAAC,GAAG,CAAC;aACZ;SACF,CAAC;SACC,IAAI,KAAK,CAAC,MAAM,KAAK,IAAI;QAC5B,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE;oBACJ,mDAAmD;oBACnD,mCAAmC;oBACnC,qDAAqD;iBACtD,CAAC,IAAI,CAAC,GAAG,CAAC;aACZ;SACF,CAAC;SACC,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,KAAK,CAAC,MAAM,CAAC,IAAI;QAC/C,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE;oBACJ,kDAAkD;oBAClD,sCAAsC;oBACtC,mCAAmC;oBACnC,wDAAwD;iBACzD,CAAC,IAAI,CAAC,GAAG,CAAC;aACZ;SACF,CAAC;SACC,IAAI,KAAK,CAAC,MAAM,CAAC,QAAQ,CAAC,IAAI,KAAK,SAAS;QAC/C,OAAO;YACL;gBACE,EAAE,EAAE,IAAA,SAAE,GAAE;gBACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;gBACpC,IAAI,EAAE,eAAe;gBACrB,IAAI,EAAE;oBACJ,kDAAkD;oBAClD,sCAAsC;oBACtC,mCAAmC;oBACnC,wDAAwD;iBACzD,CAAC,IAAI,CAAC,GAAG,CAAC;aACZ;SACF,CAAC;IACJ,OAAO,IAAI,CAAC;AACd,CAAC,CAAC;AA5DW,QAAA,6CAA6C,iDA4DxD"}