@autobe/agent 0.24.2 → 0.25.0

package/lib/orchestrate/analyze/histories/transformAnalyzeWriteHistories.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformAnalyzeWriteHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/analyze/histories/transformAnalyzeWriteHistories.ts"],"names":[],"mappings":";;;AAGA,yCAA2C;AAE3C,+BAA0B;AAKnB,MAAM,8BAA8B,GAAG,CAC5C,GAAyB,EACzB,QAAoC,EACpC,IAAgC,EAKhC,EAAE;;IAAC,OAAA;QACH,GAAG,GAAG;aACH,SAAS,EAAE;aACX,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,aAAa,IAAI,CAAC,CAAC,IAAI,KAAK,kBAAkB,CAAC;aACxE,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YACT,MAAM,IAAI,GACR,CAAC,CAAC,IAAI,KAAK,aAAa;gBACtB,CAAC,CAAC,CAAC,CAAC,QAAQ;qBACP,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,IAAI,KAAK,MAAM,CAAC;qBAClC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,IAAI,CAAC;qBACpB,IAAI,CAAC,IAAI,CAAC;gBACf,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;YACb,uCACK,CAAC,KACJ,IAAI,IACJ;QACJ,CAAC,CAAC;QACJ;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,imtCAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;wCAGe,IAAI,CAAC,SAAS,CAAC,MAAA,QAAQ,CAAC,QAAQ,mCAAI,OAAO,CAAC;;;;gDAIpC,QAAQ,CAAC,MAAM;;;;QAIvD,IAAI,CAAC,SAAS,CAAC,QAAQ,CAAC,KAAK,CAAC;;;;;;;;;QAS9B,IAAI,CAAC,SAAS,CACd,QAAQ,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,KAAK,IAAI,CAAC,QAAQ,CAAC,CAC3D;;;;;QAKC,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC;;KAEvB;SACF;KACF,CAAA;CAAA,CAAC;AAlEW,QAAA,8BAA8B,kCAkEzC"}
+{"version":3,"file":"transformAnalyzeWriteHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/analyze/histories/transformAnalyzeWriteHistories.ts"],"names":[],"mappings":";;;AAGA,yCAA2C;AAE3C,+BAA0B;AAKnB,MAAM,8BAA8B,GAAG,CAC5C,GAAyB,EACzB,KAIC,EAKD,EAAE;;IAAC,OAAA;QACH,GAAG,GAAG;aACH,SAAS,EAAE;aACX,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,IAAI,KAAK,aAAa,IAAI,CAAC,CAAC,IAAI,KAAK,kBAAkB,CAAC;aACxE,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE;YACT,MAAM,IAAI,GACR,CAAC,CAAC,IAAI,KAAK,aAAa;gBACtB,CAAC,CAAC,CAAC,CAAC,QAAQ;qBACP,MAAM,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,IAAI,KAAK,MAAM,CAAC;qBAClC,GAAG,CAAC,CAAC,EAAE,EAAE,EAAE,CAAC,EAAE,CAAC,IAAI,CAAC;qBACpB,IAAI,CAAC,IAAI,CAAC;gBACf,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC;YACb,uCACK,CAAC,KACJ,IAAI,IACJ;QACJ,CAAC,CAAC;QACJ;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,2vvCAA0C;SAC/C;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;wCAGe,IAAI,CAAC,SAAS,CAAC,MAAA,KAAK,CAAC,QAAQ,CAAC,QAAQ,mCAAI,OAAO,CAAC;;;;gDAI1C,KAAK,CAAC,QAAQ,CAAC,MAAM;;;;QAI7D,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC;;;;;;;;;QASpC,IAAI,CAAC,SAAS,CACd,KAAK,CAAC,QAAQ,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,QAAQ,KAAK,KAAK,CAAC,IAAI,CAAC,QAAQ,CAAC,CACvE;;;;;QAKC,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,IAAI,CAAC;;;;;;;;2BAQP,KAAK,CAAC,IAAI,CAAC,QAAQ;;;;;QAKtC,KAAK,CAAC,WAAW;KACpB;SACF;KACF,CAAA;CAAA,CAAC;AAjFW,QAAA,8BAA8B,kCAiFzC"}

package/lib/orchestrate/analyze/orchestrateAnalyze.js

@@ -23,12 +23,12 @@ const orchestrateAnalyze = (ctx) => (props) => __awaiter(void 0, void 0, void 0,
     ctx.dispatch({
         type: "analyzeStart",
         id: (0, uuid_1.v7)(),
-        reason: props.reason,
+        reason: props.instruction,
         step,
         created_at: startTime.toISOString(),
     });
     // Generate analysis scenario
-    const scenario = yield (0, orchestrateAnalyzeScenario_1.orchestrateAnalyzeScenario)(ctx);
+    const scenario = yield (0, orchestrateAnalyzeScenario_1.orchestrateAnalyzeScenario)(ctx, props.instruction);
     if (scenario.type === "assistantMessage")
         return ctx.assistantMessage(scenario);
     else
@@ -44,6 +44,7 @@ const orchestrateAnalyze = (ctx) => (props) => __awaiter(void 0, void 0, void 0,
             file,
             progress: writeProgress,
             promptCacheKey,
+            instruction: props.instruction,
         });
         return event.file;
     })));

package/lib/orchestrate/analyze/orchestrateAnalyze.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestrateAnalyze.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyze.ts"],"names":[],"mappings":";;;;;;;;;;;;AAUA,+BAA0B;AAI1B,uEAAoE;AACpE,yEAAsE;AACtE,6EAA0E;AAC1E,uEAAoE;AAE7D,MAAM,kBAAkB,GAC7B,CAAiC,GAAyB,EAAE,EAAE,CAC9D,CACE,KAA8B,EACiC,EAAE;;IACjE,4BAA4B;IAC5B,MAAM,IAAI,GAAW,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC;IAC3D,MAAM,SAAS,GAAS,IAAI,IAAI,EAAE,CAAC;IAEnC,GAAG,CAAC,QAAQ,CAAC;QACX,IAAI,EAAE,cAAc;QACpB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM,EAAE,KAAK,CAAC,MAAM;QACpB,IAAI;QACJ,UAAU,EAAE,SAAS,CAAC,WAAW,EAAE;KACpC,CAAC,CAAC;IAEH,6BAA6B;IAC7B,MAAM,QAAQ,GACZ,MAAM,IAAA,uDAA0B,EAAC,GAAG,CAAC,CAAC;IACxC,IAAI,QAAQ,CAAC,IAAI,KAAK,kBAAkB;QACtC,OAAO,GAAG,CAAC,gBAAgB,CAAC,QAAQ,CAAC,CAAC;;QACnC,GAAG,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC;IAE5B,kBAAkB;IAClB,MAAM,aAAa,GAA4B;QAC7C,KAAK,EAAE,QAAQ,CAAC,KAAK,CAAC,MAAM;QAC5B,SAAS,EAAE,CAAC;KACb,CAAC;IACF,MAAM,QAAQ,GAAwB,MAAM,IAAA,uCAAkB,EAC5D,QAAQ,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;QACpD,MAAM,KAAK,GAA4B,MAAM,IAAA,iDAAuB,EAClE,GAAG,EACH;YACE,QAAQ;YACR,IAAI;YACJ,QAAQ,EAAE,aAAa;YACvB,cAAc;SACf,CACF,CAAC;QACF,OAAO,KAAK,CAAC,IAAI,CAAC;IACpB,CAAC,CAAA,CAAC,CACH,CAAC;IAEF,mBAAmB;IACnB,MAAM,cAAc,GAA4B;QAC9C,KAAK,EAAE,QAAQ,CAAC,MAAM;QACtB,SAAS,EAAE,CAAC;KACb,CAAC;IACF,MAAM,QAAQ,GAAwB,MAAM,IAAA,uCAAkB,EAC5D,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;QAC9C,IAAI,CAAC;YACH,MAAM,KAAK,GACT,MAAM,IAAA,mDAAwB,EAAC,GAAG,EAAE;gBAClC,QAAQ;gBACR,QAAQ,EAAE,QAAQ,EAAE,YAAY;gBAChC,MAAM,EAAE,IAAI;gBACZ,QAAQ,EAAE,cAAc;gBACxB,cAAc;aACf,CAAC,CAAC;YACL,uCACK,KAAK,CAAC,IAAI,KACb,OAAO,EAAE,KAAK,CAAC,OAAO,IACtB;QACJ,CAAC;QAAC,WAAM,CAAC;YACP,OAAO,IAAI,CAAC;QACd,CAAC;IACH,CAAC,CAAA,CAAC,CACH,CAAC;IAEF,wBAAwB;IACxB,OAAO,GAAG,CAAC,QAAQ,CAAC;QAClB,IAAI,EAAE,iBAAiB;QACvB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,KAAK,EAAE,QAAQ,CAAC,KAAK;QACrB,MAAM,EAAE,QAAQ,CAAC,MAAM;QACvB,KAAK,EAAE,QAAQ;QACf,IAAI;QACJ,OAAO,EAAE,IAAI,IAAI,EAAE,CAAC,OAAO,EAAE,GAAG,SAAS,CAAC,OAAO,EAAE;QACnD,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACrC,CAAgC,CAAC;AACpC,CAAC,CAAA,CAAC;AAjFS,QAAA,kBAAkB,sBAiF3B"}
+{"version":3,"file":"orchestrateAnalyze.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyze.ts"],"names":[],"mappings":";;;;;;;;;;;;AAUA,+BAA0B;AAI1B,uEAAoE;AACpE,yEAAsE;AACtE,6EAA0E;AAC1E,uEAAoE;AAE7D,MAAM,kBAAkB,GAC7B,CAAiC,GAAyB,EAAE,EAAE,CAC9D,CACE,KAA8B,EACiC,EAAE;;IACjE,4BAA4B;IAC5B,MAAM,IAAI,GAAW,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC;IAC3D,MAAM,SAAS,GAAS,IAAI,IAAI,EAAE,CAAC;IAEnC,GAAG,CAAC,QAAQ,CAAC;QACX,IAAI,EAAE,cAAc;QACpB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM,EAAE,KAAK,CAAC,WAAW;QACzB,IAAI;QACJ,UAAU,EAAE,SAAS,CAAC,WAAW,EAAE;KACpC,CAAC,CAAC;IAEH,6BAA6B;IAC7B,MAAM,QAAQ,GACZ,MAAM,IAAA,uDAA0B,EAAC,GAAG,EAAE,KAAK,CAAC,WAAW,CAAC,CAAC;IAC3D,IAAI,QAAQ,CAAC,IAAI,KAAK,kBAAkB;QACtC,OAAO,GAAG,CAAC,gBAAgB,CAAC,QAAQ,CAAC,CAAC;;QACnC,GAAG,CAAC,QAAQ,CAAC,QAAQ,CAAC,CAAC;IAE5B,kBAAkB;IAClB,MAAM,aAAa,GAA4B;QAC7C,KAAK,EAAE,QAAQ,CAAC,KAAK,CAAC,MAAM;QAC5B,SAAS,EAAE,CAAC;KACb,CAAC;IACF,MAAM,QAAQ,GAAwB,MAAM,IAAA,uCAAkB,EAC5D,QAAQ,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;QACpD,MAAM,KAAK,GAA4B,MAAM,IAAA,iDAAuB,EAClE,GAAG,EACH;YACE,QAAQ;YACR,IAAI;YACJ,QAAQ,EAAE,aAAa;YACvB,cAAc;YACd,WAAW,EAAE,KAAK,CAAC,WAAW;SAC/B,CACF,CAAC;QACF,OAAO,KAAK,CAAC,IAAI,CAAC;IACpB,CAAC,CAAA,CAAC,CACH,CAAC;IAEF,mBAAmB;IACnB,MAAM,cAAc,GAA4B;QAC9C,KAAK,EAAE,QAAQ,CAAC,MAAM;QACtB,SAAS,EAAE,CAAC;KACb,CAAC;IACF,MAAM,QAAQ,GAAwB,MAAM,IAAA,uCAAkB,EAC5D,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAO,cAAc,EAAE,EAAE;QAC9C,IAAI,CAAC;YACH,MAAM,KAAK,GACT,MAAM,IAAA,mDAAwB,EAAC,GAAG,EAAE;gBAClC,QAAQ;gBACR,QAAQ,EAAE,QAAQ,EAAE,YAAY;gBAChC,MAAM,EAAE,IAAI;gBACZ,QAAQ,EAAE,cAAc;gBACxB,cAAc;aACf,CAAC,CAAC;YACL,uCACK,KAAK,CAAC,IAAI,KACb,OAAO,EAAE,KAAK,CAAC,OAAO,IACtB;QACJ,CAAC;QAAC,WAAM,CAAC;YACP,OAAO,IAAI,CAAC;QACd,CAAC;IACH,CAAC,CAAA,CAAC,CACH,CAAC;IAEF,wBAAwB;IACxB,OAAO,GAAG,CAAC,QAAQ,CAAC;QAClB,IAAI,EAAE,iBAAiB;QACvB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,KAAK,EAAE,QAAQ,CAAC,KAAK;QACrB,MAAM,EAAE,QAAQ,CAAC,MAAM;QACvB,KAAK,EAAE,QAAQ;QACf,IAAI;QACJ,OAAO,EAAE,IAAI,IAAI,EAAE,CAAC,OAAO,EAAE,GAAG,SAAS,CAAC,OAAO,EAAE;QACnD,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACrC,CAAgC,CAAC;AACpC,CAAC,CAAA,CAAC;AAlFS,QAAA,kBAAkB,sBAkF3B"}

package/lib/orchestrate/analyze/orchestrateAnalyzeScenario.d.ts

@@ -1,4 +1,4 @@
 import { AutoBeAnalyzeScenarioEvent, AutoBeAssistantMessageHistory } from "@autobe/interface";
 import { ILlmSchema } from "@samchon/openapi";
 import { AutoBeContext } from "../../context/AutoBeContext";
-export declare const orchestrateAnalyzeScenario: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>) => Promise<AutoBeAnalyzeScenarioEvent | AutoBeAssistantMessageHistory>;
+export declare const orchestrateAnalyzeScenario: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, instruction: string) => Promise<AutoBeAnalyzeScenarioEvent | AutoBeAssistantMessageHistory>;

package/lib/orchestrate/analyze/orchestrateAnalyzeScenario.js

@@ -52,7 +52,7 @@ const typia_1 = __importDefault(require("typia"));
 const uuid_1 = require("uuid");
 const assertSchemaModel_1 = require("../../context/assertSchemaModel");
 const transformAnalyzeScenarioHistories_1 = require("./histories/transformAnalyzeScenarioHistories");
-const orchestrateAnalyzeScenario = (ctx) => __awaiter(void 0, void 0, void 0, function* () {
+const orchestrateAnalyzeScenario = (ctx, instruction) => __awaiter(void 0, void 0, void 0, function* () {
     var _a, _b, _c;
     const start = new Date();
     const pointer = {
@@ -64,7 +64,7 @@ const orchestrateAnalyzeScenario = (ctx) => __awaiter(void 0, void 0, void 0, fu
             model: ctx.model,
             build: (value) => (pointer.value = value),
         }),
-        histories: (0, transformAnalyzeScenarioHistories_1.transformAnalyzeSceHistories)(ctx),
+        histories: (0, transformAnalyzeScenarioHistories_1.transformAnalyzeSceHistories)(ctx, instruction),
         enforceFunctionCall: false,
         message: utils_1.StringUtil.trim `
       Design a complete list of documents and user roles for this project.

package/lib/orchestrate/analyze/orchestrateAnalyzeScenario.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestrateAnalyzeScenario.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyzeScenario.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAQA,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,qGAA6F;AAGtF,MAAM,0BAA0B,GAAG,CAGxC,GAAyB,EAC4C,EAAE;;IACvE,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;IAC/B,MAAM,OAAO,GAA8D;QACzE,KAAK,EAAE,IAAI;KACZ,CAAC;IACF,MAAM,EAAE,SAAS,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;QACrD,MAAM,EAAE,iBAAiB;QACzB,UAAU,EAAE,gBAAgB,CAAQ;YAClC,KAAK,EAAE,GAAG,CAAC,KAAK;YAChB,KAAK,EAAE,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC;SAC1C,CAAC;QACF,SAAS,EAAE,IAAA,gEAA4B,EAAC,GAAG,CAAC;QAC5C,mBAAmB,EAAE,KAAK;QAC1B,OAAO,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;0CAIc,GAAG,CAAC,MAAM;KAC/C;KACF,CAAC,CAAC;IACH,IAAI,CAAA,MAAA,SAAS,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,0CAAE,IAAI,MAAK,kBAAkB;QAC/C,OAAO,gCACD,SAAS,CAAC,EAAE,CAAC,CAAC,CAAC,CAAsC,KACzD,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE,EAC/B,YAAY,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EACtC,EAAE,EAAE,IAAA,SAAE,GAAE,GAC+B,CAAC;SACvC,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI,EAAE,CAAC;QAChC,cAAc;QACd,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC;IACzD,CAAC;IACD,OAAO;QACL,IAAI,EAAE,iBAAiB;QACvB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;QAC5B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;QAChC,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;QAC1B,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;QAC1B,UAAU;QACV,IAAI,EAAE,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC;QAC3C,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;KAChC,CAAC;AACJ,CAAC,CAAA,CAAC;AA9CW,QAAA,0BAA0B,8BA8CrC;AAEF,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAC/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,SAAS;QACf,WAAW;QACX,OAAO,EAAE;YACP,OAAO,EAAE,CAAC,KAAK,EAAE,EAAE;gBACjB,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;YACrB,CAAC;SAC0C;KAC9C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAGJ;IACH,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}
+{"version":3,"file":"orchestrateAnalyzeScenario.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyzeScenario.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAQA,yCAA2C;AAG3C,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,qGAA6F;AAGtF,MAAM,0BAA0B,GAAG,CAGxC,GAAyB,EACzB,WAAmB,EACkD,EAAE;;IACvE,MAAM,KAAK,GAAS,IAAI,IAAI,EAAE,CAAC;IAC/B,MAAM,OAAO,GAA8D;QACzE,KAAK,EAAE,IAAI;KACZ,CAAC;IACF,MAAM,EAAE,SAAS,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;QACrD,MAAM,EAAE,iBAAiB;QACzB,UAAU,EAAE,gBAAgB,CAAQ;YAClC,KAAK,EAAE,GAAG,CAAC,KAAK;YAChB,KAAK,EAAE,CAAC,KAAK,EAAE,EAAE,CAAC,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC;SAC1C,CAAC;QACF,SAAS,EAAE,IAAA,gEAA4B,EAAC,GAAG,EAAE,WAAW,CAAC;QACzD,mBAAmB,EAAE,KAAK;QAC1B,OAAO,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;0CAIc,GAAG,CAAC,MAAM;KAC/C;KACF,CAAC,CAAC;IACH,IAAI,CAAA,MAAA,SAAS,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,0CAAE,IAAI,MAAK,kBAAkB;QAC/C,OAAO,gCACD,SAAS,CAAC,EAAE,CAAC,CAAC,CAAC,CAAsC,KACzD,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE,EAC/B,YAAY,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE,EACtC,EAAE,EAAE,IAAA,SAAE,GAAE,GAC+B,CAAC;SACvC,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI,EAAE,CAAC;QAChC,cAAc;QACd,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC;IACzD,CAAC;IACD,OAAO;QACL,IAAI,EAAE,iBAAiB;QACvB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,MAAM,EAAE,OAAO,CAAC,KAAK,CAAC,MAAM;QAC5B,QAAQ,EAAE,OAAO,CAAC,KAAK,CAAC,QAAQ;QAChC,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;QAC1B,KAAK,EAAE,OAAO,CAAC,KAAK,CAAC,KAAK;QAC1B,UAAU;QACV,IAAI,EAAE,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC;QAC3C,UAAU,EAAE,KAAK,CAAC,WAAW,EAAE;KAChC,CAAC;AACJ,CAAC,CAAA,CAAC;AA/CW,QAAA,0BAA0B,8BA+CrC;AAEF,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAC/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,SAAS;QACf,WAAW;QACX,OAAO,EAAE;YACP,OAAO,EAAE,CAAC,KAAK,EAAE,EAAE;gBACjB,KAAK,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC;YACrB,CAAC;SAC0C;KAC9C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAGJ;IACH,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}

package/lib/orchestrate/analyze/orchestrateAnalyzeWrite.d.ts

@@ -5,6 +5,7 @@ import { AutoBeContext } from "../../context/AutoBeContext";
 export declare const orchestrateAnalyzeWrite: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, props: {
     scenario: AutoBeAnalyzeScenarioEvent;
     file: AutoBeAnalyzeFile.Scenario;
+    instruction: string;
     progress: AutoBeProgressEventBase;
     promptCacheKey: string;
 }) => Promise<AutoBeAnalyzeWriteEvent>;

package/lib/orchestrate/analyze/orchestrateAnalyzeWrite.js

@@ -53,7 +53,7 @@ const assertSchemaModel_1 = require("../../context/assertSchemaModel");
 const transformAnalyzeWriteHistories_1 = require("./histories/transformAnalyzeWriteHistories");
 const orchestrateAnalyzeWrite = (ctx, props) => __awaiter(void 0, void 0, void 0, function* () {
     var _a, _b;
-    const { scenario, file, progress, promptCacheKey } = props;
+    const { file, progress, promptCacheKey } = props;
     const pointer = {
         value: null,
     };
@@ -63,7 +63,7 @@ const orchestrateAnalyzeWrite = (ctx, props) => __awaiter(void 0, void 0, void 0
             model: ctx.model,
             pointer,
         }),
-        histories: (0, transformAnalyzeWriteHistories_1.transformAnalyzeWriteHistories)(ctx, scenario, file),
+        histories: (0, transformAnalyzeWriteHistories_1.transformAnalyzeWriteHistories)(ctx, props),
         enforceFunctionCall: true,
         promptCacheKey,
         message: "Write requirement analysis report.",

package/lib/orchestrate/analyze/orchestrateAnalyzeWrite.js.map

@@ -1 +1 @@
-{"version":3,"file":"orchestrateAnalyzeWrite.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyzeWrite.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AASA,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,+FAA4F;AAGrF,MAAM,uBAAuB,GAAG,CACrC,GAAyB,EACzB,KAKC,EACiC,EAAE;;IACpC,MAAM,EAAE,QAAQ,EAAE,IAAI,EAAE,QAAQ,EAAE,cAAc,EAAE,GAAG,KAAK,CAAC;IAC3D,MAAM,OAAO,GAA2D;QACtE,KAAK,EAAE,IAAI;KACZ,CAAC;IACF,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;QAC1C,MAAM,EAAE,cAAc;QACtB,UAAU,EAAE,gBAAgB,CAAQ;YAClC,KAAK,EAAE,GAAG,CAAC,KAAK;YAChB,OAAO;SACR,CAAC;QACF,SAAS,EAAE,IAAA,+DAA8B,EAAC,GAAG,EAAE,QAAQ,EAAE,IAAI,CAAC;QAC9D,mBAAmB,EAAE,IAAI;QACzB,cAAc;QACd,OAAO,EAAE,oCAAoC;KAC9C,CAAC,CAAC;IACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;QACxB,MAAM,IAAI,KAAK,CAAC,kDAAkD,CAAC,CAAC;IAEtE,MAAM,KAAK,GAA4B;QACrC,IAAI,EAAE,cAAc;QACpB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,IAAI,kCACC,IAAI,KACP,OAAO,EAAE,OAAO,CAAC,KAAK,CAAC,OAAO,GAC/B;QACD,UAAU,EAAE,UAAU;QACtB,IAAI,EAAE,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC;QAC3C,KAAK,EAAE,QAAQ,CAAC,KAAK;QACrB,SAAS,EAAE,EAAE,QAAQ,CAAC,SAAS;QAC/B,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACrC,CAAC;IACF,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;IACpB,OAAO,KAAK,CAAC;AACf,CAAC,CAAA,CAAC;AA1CW,QAAA,uBAAuB,2BA0ClC;AAEF,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAC/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,UAAU;QAChB,WAAW;QACX,OAAO,EAAE;YACP,KAAK,EAAE,CAAO,KAAK,EAAE,EAAE;gBACrB,KAAK,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC;YAC9B,CAAC,CAAA;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAAoE;IAC3E,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}
+{"version":3,"file":"orchestrateAnalyzeWrite.js","sourceRoot":"","sources":["../../../src/orchestrate/analyze/orchestrateAnalyzeWrite.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AASA,kDAA0B;AAC1B,+BAA0B;AAG1B,uEAAoE;AACpE,+FAA4F;AAGrF,MAAM,uBAAuB,GAAG,CACrC,GAAyB,EACzB,KAMC,EACiC,EAAE;;IACpC,MAAM,EAAE,IAAI,EAAE,QAAQ,EAAE,cAAc,EAAE,GAAG,KAAK,CAAC;IACjD,MAAM,OAAO,GAA2D;QACtE,KAAK,EAAE,IAAI;KACZ,CAAC;IACF,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;QAC1C,MAAM,EAAE,cAAc;QACtB,UAAU,EAAE,gBAAgB,CAAQ;YAClC,KAAK,EAAE,GAAG,CAAC,KAAK;YAChB,OAAO;SACR,CAAC;QACF,SAAS,EAAE,IAAA,+DAA8B,EAAC,GAAG,EAAE,KAAK,CAAC;QACrD,mBAAmB,EAAE,IAAI;QACzB,cAAc;QACd,OAAO,EAAE,oCAAoC;KAC9C,CAAC,CAAC;IACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;QACxB,MAAM,IAAI,KAAK,CAAC,kDAAkD,CAAC,CAAC;IAEtE,MAAM,KAAK,GAA4B;QACrC,IAAI,EAAE,cAAc;QACpB,EAAE,EAAE,IAAA,SAAE,GAAE;QACR,IAAI,kCACC,IAAI,KACP,OAAO,EAAE,OAAO,CAAC,KAAK,CAAC,OAAO,GAC/B;QACD,UAAU,EAAE,UAAU;QACtB,IAAI,EAAE,CAAC,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC,CAAC,CAAC,GAAG,CAAC;QAC3C,KAAK,EAAE,QAAQ,CAAC,KAAK;QACrB,SAAS,EAAE,EAAE,QAAQ,CAAC,SAAS;QAC/B,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;KACrC,CAAC;IACF,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;IACpB,OAAO,KAAK,CAAC;AACf,CAAC,CAAA,CAAC;AA3CW,QAAA,uBAAuB,2BA2ClC;AAEF,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAC/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IACtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,UAAU;QAChB,WAAW;QACX,OAAO,EAAE;YACP,KAAK,EAAE,CAAO,KAAK,EAAE,EAAE;gBACrB,KAAK,CAAC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC;YAC9B,CAAC,CAAA;SACuC;KAC3C,CAAC;AACJ,CAAC;AAED,MAAM,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAGT,CAAC;AACJ,MAAM,UAAU,GAAG;IACjB,OAAO;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;KAAoE;IAC3E,MAAM;IACN,KAAK,EAAE,MAAM;IACb,QAAQ,EAAE,MAAM;IAChB,KAAK,EAAE,MAAM;CACd,CAAC"}

package/lib/orchestrate/facade/transformFacadeStateMessage.js

@@ -4,7 +4,7 @@ exports.transformFacadeStateMessage = transformFacadeStateMessage;
 const utils_1 = require("@autobe/utils");
 function transformFacadeStateMessage(state) {
     const currentState = getCurrentState(state);
-    return "<!--\nfilename: FACADE.md\n-->\n# AutoBE Main Agent System Prompt\n\nYou are the AutoBE Main Agent, an orchestrator for backend server development automation. Your role is to manage the conversation with users about their backend requirements and coordinate the execution of five specialized functional agents through function calling.\n\n## Core Responsibilities\n\n1. **Requirements Gathering**: Engage in detailed conversations with users to understand their backend server needs, asking clarifying questions about business logic, data models, API endpoints, and technical requirements.\n\n2. **Agent Orchestration**: Execute the appropriate functional agents in the correct sequence based on the development stage and user needs.\n\n3. **Progress Communication**: Keep users informed about the current development stage, what has been completed, and what steps remain.\n\n## Functional Agents Overview\n\nYou have access to five functional agents that must be executed in a specific order:\n\n1. **Analyze Agent** - Converts conversations into structured requirements specifications\n2. **Prisma Agent** - Generates database schemas and ERD documentation\n3. **Interface Agent** - Creates API interfaces with OpenAPI schemas and TypeScript code\n4. **Test Agent** - Generates comprehensive E2E test suites\n5. **Realize Agent** - Implements actual business logic for service providers\n\n## Execution Rules\n\n### 1. Sequential Dependencies\n\n- **analyze()**: Can only be called when sufficient requirements have been gathered.\n- **prisma()**: Requires successful completion of analyze()\n- **interface()**: Requires successful completion of prisma()\n- **test()**: Requires successful completion of interface()\n- **realize()**: Requires successful completion of interface()\n\n### 2. Requirements Gathering and analyze() Calling Criteria\n\n- Since users are not developers, it is okay if they do not understand technical terms like \u201Cendpoints\u201D or \u201Cdata models.\u201D  \n\n- Your job is to help users clearly express their intended **features** by asking many questions.  \n\n- Use examples and simple questions to guide them if they have trouble explaining.  \n\n- Break down features into smaller steps if needed to complete the planning gradually.  \n\n- For instance, ask questions like \u201CWhat tasks do you want to automate?\u201D, \u201CWhat roles do users have?\u201D, \u201CWhat screens or actions are involved?\u201D  \n\n- Even if the system requires many or complex APIs, it is not necessary to know all of them upfront. Focus on gathering core requirements step by step.  \n\n#### Conditions for Calling analyze()  \n- Call analyze() only when the user has clearly stated sufficient **features** and **requirements**, or  \n- The user explicitly delegates the planning to you by saying things like \u201CI\u2019ll leave the planning to you\u201D or \u201CPlease proceed as you see fit.\u201D  \n\n#### Pre-call Checks  \n- If requirements are insufficient for some features, do **not** call analyze() and keep asking questions until the specifications are complete.  \n- Continue asking actively and explain any technical terms in an easy-to-understand way.\n\n### 3. Requirements Gathering Phase\n\nBefore calling analyze(), ensure you have discussed:\n\n- System purpose and overall goals\n- Core features and functionalities\n- User roles and permissions\n- Main data entities and their relationships\n- Key business rules and constraints\n- API endpoints needed\n- Any specific technical requirements\n\nIf these aspects are unclear, continue the conversation to gather more details.\n\n### 4. Development Workflow\n\n1. Start by understanding the user's needs through conversation\n2. When requirements are sufficiently detailed, execute analyze()\n3. Review the analysis results with the user\n4. If approved, proceed with prisma() \u2192 interface() \u2192 test() \u2192 realize()\n5. At each stage, present results and get user confirmation before proceeding\n\n### 5. Handling Changes\n\n- If users request changes after agents have been executed, first understand the scope\n- For minor adjustments, you may re-run specific agents\n- For major changes, consider re-running analyze() to update the specification\n- Always explain the impact of changes on already generated code\n\n## Communication Guidelines\n\n1. **Be Transparent**: Clearly explain which agent is being executed and why\n2. **Show Progress**: Indicate completed steps and remaining work\n3. **Confirm Understanding**: Summarize requirements before executing agents\n4. **Request Approval**: Get user confirmation before moving to the next stage\n5. **Explain Results**: Briefly describe what each agent has generated\n\n## Current State\n\n{% STATE %}" /* AutoBeSystemPromptConstant.FACADE */.replace("{% STATE %}", utils_1.StringUtil.trim `
+    return "<!--\nfilename: FACADE.md\n-->\n# AutoBE Main Agent System Prompt\n\nYou are the AutoBE Main Agent, an orchestrator for backend server development automation. Your role is to manage the conversation with users about their backend requirements and coordinate the execution of five specialized functional agents through function calling.\n\n## Core Responsibilities\n\n1. **Requirements Gathering**: Engage in detailed conversations with users to understand their backend server needs, asking clarifying questions about business logic, data models, API endpoints, and technical requirements.\n\n2. **Agent Orchestration**: Execute the appropriate functional agents in the correct sequence based on the development stage and user needs.\n\n3. **Progress Communication**: Keep users informed about the current development stage, what has been completed, and what steps remain.\n\n## Functional Agents Overview\n\nYou have access to five functional agents that must be executed in a specific order:\n\n1. **Analyze Agent** - Converts conversations into structured requirements specifications\n2. **Prisma Agent** - Generates database schemas and ERD documentation\n3. **Interface Agent** - Creates API interfaces with OpenAPI schemas and TypeScript code\n4. **Test Agent** - Generates comprehensive E2E test suites\n5. **Realize Agent** - Implements actual business logic for service providers\n\n## Execution Rules\n\n### 1. Sequential Dependencies\n\n- **analyze()**: Can only be called when sufficient requirements have been gathered.\n- **prisma()**: Requires successful completion of analyze()\n- **interface()**: Requires successful completion of prisma()\n- **test()**: Requires successful completion of interface()\n- **realize()**: Requires successful completion of interface()\n\n### 2. Requirements Gathering and analyze() Calling Criteria\n\n- Since users are not developers, it is okay if they do not understand technical terms like \u201Cendpoints\u201D or \u201Cdata models.\u201D  \n\n- Your job is to help users clearly express their intended **features** by asking many questions.  \n\n- Use examples and simple questions to guide them if they have trouble explaining.  \n\n- Break down features into smaller steps if needed to complete the planning gradually.  \n\n- For instance, ask questions like \u201CWhat tasks do you want to automate?\u201D, \u201CWhat roles do users have?\u201D, \u201CWhat screens or actions are involved?\u201D  \n\n- Even if the system requires many or complex APIs, it is not necessary to know all of them upfront. Focus on gathering core requirements step by step.  \n\n#### Conditions for Calling analyze()  \n- Call analyze() only when the user has clearly stated sufficient **features** and **requirements**, or  \n- The user explicitly delegates the planning to you by saying things like \u201CI\u2019ll leave the planning to you\u201D or \u201CPlease proceed as you see fit.\u201D  \n\n#### Pre-call Checks  \n- If requirements are insufficient for some features, do **not** call analyze() and keep asking questions until the specifications are complete.  \n- Continue asking actively and explain any technical terms in an easy-to-understand way.\n\n### 3. Requirements Gathering Phase\n\nBefore calling analyze(), ensure you have discussed:\n\n- System purpose and overall goals\n- Core features and functionalities\n- User roles and permissions\n- Main data entities and their relationships\n- Key business rules and constraints\n- API endpoints needed\n- Any specific technical requirements\n\nIf these aspects are unclear, continue the conversation to gather more details.\n\n### 4. Development Workflow\n\n1. Start by understanding the user's needs through conversation\n2. When requirements are sufficiently detailed, execute analyze()\n3. Review the analysis results with the user\n4. If approved, proceed with prisma() \u2192 interface() \u2192 test() \u2192 realize()\n5. At each stage, present results and get user confirmation before proceeding\n\n### 5. Handling Changes\n\n- If users request changes after agents have been executed, first understand the scope\n- For minor adjustments, you may re-run specific agents\n- For major changes, consider re-running analyze() to update the specification\n- Always explain the impact of changes on already generated code\n\n## Agent Instruction Guidelines\n\nWhen calling each functional agent, you must provide specific instructions that:\n\n1. **Redefine and Clarify**: Transform the user's utterances into clear, actionable instructions for each agent phase\n2. **Provide Context**: Include relevant context from the conversation that helps the agent understand the business intent\n3. **Set Priorities**: Specify which aspects are most important based on user emphasis\n4. **Define Constraints**: Include any specific limitations or requirements mentioned by the user\n\n### IMPORTANT: Phase-Specific Instructions Only\n\n**You MUST extract ONLY the instructions relevant to each specific phase:**\n\n- **analyze()**: ONLY requirements-related instructions (features, business rules, user stories, functional specifications)\n- **prisma()**: ONLY database design instructions (schema structure, relationships, constraints, indexing strategies)\n- **interface()**: ONLY API and DTO schema instructions (endpoint patterns, request/response formats, operation specifications)\n- **test()**: ONLY testing strategy instructions (test scenarios, coverage priorities, edge cases to validate)\n- **realize()**: ONLY implementation instructions (business logic patterns, performance requirements, architectural decisions)\n\n**DO NOT include instructions meant for other phases. Each agent should receive ONLY its domain-specific guidance.**\n\n### CRITICAL: Never Fabricate User Requirements\n\n**ABSOLUTELY FORBIDDEN:**\n- **NEVER invent or create requirements the user didn't explicitly mention**\n- **NEVER expand simple requests into detailed specifications without user input**\n- **NEVER add features, functionalities, or details the user hasn't discussed**\n- **ONLY include instructions based on what the user ACTUALLY said**\n\nIf the user says \"Design an API\", do NOT create detailed specifications about platforms, features, or functionalities they never mentioned. Stick strictly to their actual words and requirements.\n\n### Instruction Examples\n\n- **For analyze()**: \"Focus on e-commerce features with emphasis on inventory management and order processing. User wants simple checkout flow.\"\n- **For prisma()**: \"Design schema prioritizing product catalog flexibility. User mentioned frequent category changes.\"\n- **For interface()**: \"Create RESTful APIs following shopping cart patterns. Emphasize mobile-friendly endpoints.\"\n- **For test()**: \"Generate comprehensive tests for payment scenarios. User concerned about transaction reliability.\"\n- **For realize()**: \"Implement with performance optimization for high-traffic scenarios. User expects 10K concurrent users.\"\n\n## Communication Guidelines\n\n1. **Be Transparent**: Clearly explain which agent is being executed and why\n2. **Show Progress**: Indicate completed steps and remaining work\n3. **Confirm Understanding**: Summarize requirements before executing agents\n4. **Request Approval**: Get user confirmation before moving to the next stage\n5. **Explain Results**: Briefly describe what each agent has generated\n6. **Clarify Instructions**: When calling agents, explain how you've interpreted user needs into specific instructions\n\n## Current State\n\n{% STATE %}" /* AutoBeSystemPromptConstant.FACADE */.replace("{% STATE %}", utils_1.StringUtil.trim `
       ## Current State
 
       The current execution status of each functional agent is shown below. 

package/lib/orchestrate/facade/transformFacadeStateMessage.js.map

@@ -1 +1 @@
-{"version":3,"file":"transformFacadeStateMessage.js","sourceRoot":"","sources":["../../../src/orchestrate/facade/transformFacadeStateMessage.ts"],"names":[],"mappings":";;AAKA,kEA0BC;AA/BD,yCAA2C;AAK3C,SAAgB,2BAA2B,CAAC,KAAkB;IAC5D,MAAM,YAAY,GAAkB,eAAe,CAAC,KAAK,CAAC,CAAC;IAC3D,OAAO,0sJAAkC,OAAO,CAC9C,aAAa,EACb,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;mBAeA,YAAY,CAAC,OAAO;kBACrB,YAAY,CAAC,MAAM;qBAChB,YAAY,CAAC,SAAS;gBAC3B,YAAY,CAAC,IAAI;mBACd,YAAY,CAAC,OAAO;KAClC,CACF,CAAC;AACJ,CAAC;AAED,SAAS,eAAe,CAAC,KAAkB;IACzC,MAAM,KAAK,GAAG,CACZ,GAEQ,EACR,EAAE;QACF,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI,IAAI,GAAG,KAAK,IAAI;YAAE,OAAO,MAAM,CAAC;aACrD,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,GAAG,CAAC,IAAI;YAAE,OAAO,YAAY,CAAC;;YACzD,OAAO,aAAa,CAAC;IAC5B,CAAC,CAAC;IACF,OAAO;QACL,OAAO,EAAE,KAAK,CAAC,OAAO,KAAK,IAAI,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,YAAY;QACvD,MAAM,EAAE,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC;QAC3B,SAAS,EAAE,KAAK,CAAC,KAAK,CAAC,SAAS,CAAC;QACjC,IAAI,EAAE,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC;QACvB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC;KAC9B,CAAC;AACJ,CAAC"}
+{"version":3,"file":"transformFacadeStateMessage.js","sourceRoot":"","sources":["../../../src/orchestrate/facade/transformFacadeStateMessage.ts"],"names":[],"mappings":";;AAKA,kEA0BC;AA/BD,yCAA2C;AAK3C,SAAgB,2BAA2B,CAAC,KAAkB;IAC5D,MAAM,YAAY,GAAkB,eAAe,CAAC,KAAK,CAAC,CAAC;IAC3D,OAAO,y7OAAkC,OAAO,CAC9C,aAAa,EACb,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;mBAeA,YAAY,CAAC,OAAO;kBACrB,YAAY,CAAC,MAAM;qBAChB,YAAY,CAAC,SAAS;gBAC3B,YAAY,CAAC,IAAI;mBACd,YAAY,CAAC,OAAO;KAClC,CACF,CAAC;AACJ,CAAC;AAED,SAAS,eAAe,CAAC,KAAkB;IACzC,MAAM,KAAK,GAAG,CACZ,GAEQ,EACR,EAAE;QACF,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI,IAAI,GAAG,KAAK,IAAI;YAAE,OAAO,MAAM,CAAC;aACrD,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,KAAK,GAAG,CAAC,IAAI;YAAE,OAAO,YAAY,CAAC;;YACzD,OAAO,aAAa,CAAC;IAC5B,CAAC,CAAC;IACF,OAAO;QACL,OAAO,EAAE,KAAK,CAAC,OAAO,KAAK,IAAI,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,YAAY;QACvD,MAAM,EAAE,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC;QAC3B,SAAS,EAAE,KAAK,CAAC,KAAK,CAAC,SAAS,CAAC;QACjC,IAAI,EAAE,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC;QACvB,OAAO,EAAE,KAAK,CAAC,KAAK,CAAC,OAAO,CAAC;KAC9B,CAAC;AACJ,CAAC"}

package/lib/orchestrate/interface/histories/transformInterfaceAssetHistories.js

@@ -19,7 +19,7 @@ const transformInterfaceAssetHistories = (state) => {
 
         ## User Request
 
-        ${analyze.reason}
+        ${analyze.instruction}
 
         ## Requirement Analysis Report
 
@@ -54,6 +54,7 @@ const transformInterfaceAssetHistories = (state) => {
         \`\`\`
 
         ## Entity Relationship Diagrams
+        
         \`\`\`json
         ${JSON.stringify(prisma.compiled.diagrams)}
         \`\`\`

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

@@ -1 +1 @@
-{"version":3,"file":"transformInterfaceAssetHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceAssetHistories.ts"],"names":[],"mappings":";;;AAMA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,gCAAgC,GAAG,CAC9C,KAAkB,EAGlB,EAAE;IACF,MAAM,OAAO,GAAyB,KAAK,CAAC,OAAQ,CAAC;IACrD,MAAM,MAAM,GAAwB,KAAK,CAAC,MAAO,CAAC;IAClD,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;UAQjB,OAAO,CAAC,MAAM;;;;;UAKd,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,KAAK,CAAC;;OAEhC;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;;;UAkBjB,IAAI,CAAC,SAAS,CAAC,MAAM,CAAC,OAAO,CAAC;;;;;UAK9B,IAAI,CAAC,SAAS,CACb,MAAM,CAAC,QAAgD,CAAC,QAAQ,CAClE;;OAEF;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA/DW,QAAA,gCAAgC,oCA+D3C"}
+{"version":3,"file":"transformInterfaceAssetHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceAssetHistories.ts"],"names":[],"mappings":";;;AAMA,yCAA2C;AAC3C,+BAA0B;AAInB,MAAM,gCAAgC,GAAG,CAC9C,KAAkB,EAGlB,EAAE;IACF,MAAM,OAAO,GAAyB,KAAK,CAAC,OAAQ,CAAC;IACrD,MAAM,MAAM,GAAwB,KAAK,CAAC,MAAO,CAAC;IAClD,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;UAQjB,OAAO,CAAC,WAAW;;;;;UAKnB,IAAI,CAAC,SAAS,CAAC,OAAO,CAAC,KAAK,CAAC;;OAEhC;SACF;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAkB;YACxB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;;;;;;;;;;UAkBjB,IAAI,CAAC,SAAS,CAAC,MAAM,CAAC,OAAO,CAAC;;;;;;UAM9B,IAAI,CAAC,SAAS,CACb,MAAM,CAAC,QAAgD,CAAC,QAAQ,CAClE;;OAEF;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AAhEW,QAAA,gCAAgC,oCAgE3C"}

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

@@ -1,4 +1,8 @@
 import { IAgenticaHistoryJson } from "@agentica/core";
 import { AutoBeAnalyzeRole } from "@autobe/interface";
 import { AutoBeState } from "../../../context/AutoBeState";
-export declare const transformInterfaceAuthorizationsHistories: (state: AutoBeState, role: AutoBeAnalyzeRole) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
+export declare const transformInterfaceAuthorizationsHistories: (props: {
+    state: AutoBeState;
+    role: AutoBeAnalyzeRole;
+    instruction: string;
+}) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/orchestrate/interface/histories/transformInterfaceAuthorizationsHistories.js

@@ -4,16 +4,16 @@ exports.transformInterfaceAuthorizationsHistories = void 0;
 const utils_1 = require("@autobe/utils");
 const uuid_1 = require("uuid");
 const transformInterfaceAssetHistories_1 = require("./transformInterfaceAssetHistories");
-const transformInterfaceAuthorizationsHistories = (state, role) => {
-    const analyze = state.analyze;
+const transformInterfaceAuthorizationsHistories = (props) => {
+    const analyze = props.state.analyze;
     return [
         {
             type: "systemMessage",
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
-            text: "<!--\nfilename: INTERFACE_AUTHORIZATION.md\n-->\n# Authorization API Operation Generator System Prompt\n\n## 1. Overview and Mission\n\nYou are the Authorization API Operation Generator, specializing in creating JWT-based **authentication and authorization ONLY** API operations for specific user roles. Your mission is to generate role-appropriate authentication operations plus additional operations that are clearly supported by the Prisma schema structure.\n\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the operations directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Authentication Scope Definition\n\n**INCLUDE (Authentication/Authorization Operations):**\n- Role-appropriate authentication flows (registration, login, refresh)\n- JWT token management\n- Password management operations (reset, change, etc.)\n- Account verification and security operations\n- Schema-supported additional authentication operations\n\n**EXCLUDE (User Management Operations):**\n- General profile retrieval and viewing\n- Profile information updates (except security-related)\n- User preference management\n- Non-security related account settings\n\n## 2. Operation Generation Rules\n\n### 2.1. Role-Based Essential Operations\n\nThe essential operations you generate MUST be based on the role's `kind` property:\n\n**Generation Logic:**\n```\nIF role.kind === \"guest\":\n    Generate: join, refresh (NO login - guests don't authenticate)\nELSE IF role.kind === \"member\" OR role.kind === \"admin\":\n    Generate: join, login, refresh\n```\n\n**Guest Users (`kind: \"guest\"`)** - Non-authenticated, temporary access:\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create temporary guest account and issue temporary tokens (Public)\n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh temporary access tokens (Valid refresh token)\n\n**Member Users (`kind: \"member\"`)** - Regular authenticated users:\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create new user account and issue initial JWT tokens (Public)\n- **Login**: `/auth/{roleName}/login` \u2192 `\"login\"` \u2192 Authenticate user and issue access tokens (Public)  \n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh access tokens using a valid refresh token (Valid refresh token)\n\n**Admin Users (`kind: \"admin\"`)** - System administrators (same as members):\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create new admin account and issue initial JWT tokens (Public)\n- **Login**: `/auth/{roleName}/login` \u2192 `\"login\"` \u2192 Authenticate admin and issue access tokens (Public)\n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh access tokens using a valid refresh token (Valid refresh token)\n\n### 2.2. Schema-Driven Additional Operations\n\n**Analyze the Prisma schema for the role's table and generate additional operations ONLY for features that are clearly supported by the schema fields.**\n\n**Generation Rule**: Only create operations for authentication features that have corresponding fields in the Prisma schema.\n\n**Conservative Approach**:\n- **If field exists in schema**: Generate corresponding operation\n- **If field missing**: Skip the operation entirely\n- **If unsure about field purpose**: Skip rather than assume\n\n**Schema Analysis Process**:\n1. **Identify Role Table**: Find the table corresponding to the role name\n2. **Check Role Kind**: Determine which essential operations to generate based on `kind`\n3. **Verify Essential Fields**: Confirm basic authentication fields exist for required operations\n4. **Scan for Additional Features**: Look for fields that indicate additional authentication capabilities\n5. **Generate Operations**: Create operations for confirmed capabilities only\n\n## 3. Naming and Response Rules\n\n### 3.1. Naming Conventions\n\n**Endpoint Path Conventions:**\n- Use RESTful resource-based paths with camelCase for role names and resource segments\n- Pattern: `/auth/{roleName}/{action}` or `/auth/{roleName}/{resource}/{action}`\n- Examples: `/auth/user/join`, `/auth/admin/login`, `/auth/user/password/reset`, `/auth/user/email/verify`\n\n**Function Name Conventions:**\n- Use camelCase starting with action verbs that clearly describe the operation\n- Make function names self-explanatory and business-oriented\n- Core operations: `join` (registration), `login` (authentication), `refresh` (token renewal)\n- Additional operations: `resetPassword`, `changePassword`, `verifyEmail`, `enableTwoFactor`\n\n**Path vs Function Name Relationship:**\n- **Path**: Describes the HTTP resource and REST endpoint (resource-oriented)\n- **Function Name**: Describes the business operation/action (action-oriented)\n- They should be related but NOT identical\n\n### 3.2. Response Body Type Naming\n\n**Authentication Operations** (where `authorizationType` is NOT null):\nFor operations with function names `login`, `join` and `refresh`, the response body `typeName` MUST follow this pattern:\n\n**Pattern**: `I{PascalPrefixName}{RoleName}.IAuthorized`\n\nWhere:\n- `{PascalPrefixName}` is the service prefix converted to PascalCase (provided in the prompt)\n- `{RoleName}` is the capitalized role name (e.g., \"User\", \"Admin\", \"Seller\")\n\n**Examples:**\n- For prefix \"shopping-mall\" and role \"user\" \u2192 `typeName: \"IShoppingMallUser.IAuthorized\"`\n- For prefix \"blog-cms\" and role \"admin\" \u2192 `typeName: \"IBlogCmsAdmin.IAuthorized\"`\n- For prefix \"ecommerce\" and role \"seller\" \u2192 `typeName: \"IEcommerceSeller.IAuthorized\"`\n\n**Non-Authentication Operations** (`authorizationType: null`):\nUse standard response type naming conventions.\n\n### 3.3. Description Requirements\n\n**Schema-Aware Descriptions** (5 paragraphs):\n\n1. **Purpose and functionality** referencing specific schema fields and role type\n2. **Implementation details** using confirmed available fields  \n3. **Role-specific integration** and business context\n4. **Security considerations** within schema constraints\n5. **Related operations** and authentication workflow integration\n\n**Field Reference Requirements:**\n- ONLY reference fields that ACTUALLY EXIST in the Prisma schema\n- NEVER assume common fields exist without verification\n- Use exact field names as they appear in the schema\n- Describe behavior based on available schema structure\n\n## 4. Output Format (Function Calling Interface)\n\nYou must return a structured output following the `IAutoBeInterfaceAuthorizationsApplication.IProps` interface:\n\n### TypeScript Interface\n\n```typescript\nexport namespace IAutoBeInterfaceAuthorizationsApplication {\n  export interface IProps {\n    operations: AutoBeOpenApi.IOperation[];  // Array of authorization operations\n  }\n}\n\n// Each operation follows the standard AutoBeOpenApi.IOperation structure\n```\n\n### Field Descriptions\n\n#### operations\nArray of authorization-related API operations. Each operation must include:\n- All standard `AutoBeOpenApi.IOperation` fields (specification, path, method, etc.)\n- Proper `authorizationType` values for auth operations (`\"join\"`, `\"login\"`, `\"refresh\"`, or `null`)\n- Appropriate `authorizationRole` for role-specific endpoints\n\n### Output Method\n\nYou MUST call the `makeOperations()` function with your authorization operations.\n\n## 5. Implementation Requirements\n\n### 5.1. Critical Requirements\n- **Role-Based Essential Operations**: Generate appropriate essential operations based on role `kind`\n- **Operation Uniqueness**: Each authentication operation MUST be unique per role\n- **Schema-Driven Additions**: Add operations only for schema-supported features\n- **Field Verification**: Reference actual field names from the schema for additional features\n- **Never Skip Required Essentials**: Always include the role-appropriate core operations\n- **Proper Naming**: Ensure endpoint paths and function names follow conventions and are distinct\n- **Authentication Response Types**: All authentication operations (authorizationType !== null) MUST use `I{PascalPrefixName}{RoleName}.IAuthorized` format for response body typeName\n- **Function Call Required**: Use the provided function with all generated operations\n\n### 5.2. Implementation Strategy\n\n1. **Analyze Role Kind FIRST**: Determine which essential operations to generate based on `role.kind`\n2. **Generate Role-Appropriate Essential Operations**: \n   - Guest (`kind: \"guest\"`): Create `join` and `refresh` operations\n   - Member (`kind: \"member\"`)/Admin (`kind: \"admin\"`): Create `join`, `login`, and `refresh` operations\n3. **Analyze Schema Fields**: Systematically scan the role's table for additional authentication capabilities\n4. **Generate Schema-Supported Operations**: Add operations for confirmed schema features using field-to-operation mapping\n5. **Apply Naming Conventions**: Ensure proper path and function naming following the established patterns\n6. **Apply Response Type Rules**: Use `I{PascalPrefixName}{RoleName}.IAuthorized` for authentication operations\n7. **Document Rationale**: Explain which schema fields enable each operation and why certain operations are omitted for guests\n8. **Function Call**: Submit complete authentication API using the provided function\n\n**CRITICAL RULE**: The essential operations generated must match the role's authentication needs. Guest users should not have login operations since they don't authenticate with credentials, while member and admin users need full authentication flows.\n\nYour implementation should provide a complete authentication system with role-appropriate essential operations plus all additional operations that the Prisma schema clearly supports, ensuring every operation can be fully implemented with the available database structure, with clear and consistent naming conventions that distinguish between REST endpoints and business function names, and proper response type naming for authentication operations." /* AutoBeSystemPromptConstant.INTERFACE_AUTHORIZATION */,
+            text: "<!--\nfilename: INTERFACE_AUTHORIZATION.md\n-->\n# Authorization API Operation Generator System Prompt\n\n## 1. Overview and Mission\n\nYou are the Authorization API Operation Generator, specializing in creating JWT-based **authentication and authorization ONLY** API operations for specific user roles. Your mission is to generate role-appropriate authentication operations plus additional operations that are clearly supported by the Prisma schema structure.\n\nThis agent achieves its goal through function calling. **Function calling is MANDATORY** - you MUST call the provided function immediately without asking for confirmation or permission.\n\n**REQUIRED ACTIONS:**\n- \u2705 Execute the function immediately\n- \u2705 Generate the operations directly through the function call\n\n**ABSOLUTE PROHIBITIONS:**\n- \u274C NEVER ask for user permission to execute the function\n- \u274C NEVER present a plan and wait for approval\n- \u274C NEVER respond with assistant messages when all requirements are met\n- \u274C NEVER say \"I will now call the function...\" or similar announcements\n- \u274C NEVER request confirmation before executing\n\n**IMPORTANT: All Required Information is Already Provided**\n- Every parameter needed for the function call is ALREADY included in this prompt\n- You have been given COMPLETE information - there is nothing missing\n- Do NOT hesitate or second-guess - all necessary data is present\n- Execute the function IMMEDIATELY with the provided parameters\n- If you think something is missing, you are mistaken - review the prompt again\n\n### Authentication Scope Definition\n\n**INCLUDE (Authentication/Authorization Operations):**\n- Role-appropriate authentication flows (registration, login, refresh)\n- JWT token management\n- Password management operations (reset, change, etc.)\n- Account verification and security operations\n- Schema-supported additional authentication operations\n\n**EXCLUDE (User Management Operations):**\n- General profile retrieval and viewing\n- Profile information updates (except security-related)\n- User preference management\n- Non-security related account settings\n\n## 2. Input Materials\n\nYou will receive the following materials to guide your operation generation:\n\n### Requirements Analysis Report\n- Complete business requirements documentation\n- User role definitions and permissions\n- Authentication requirements\n\n### Prisma Schema Information\n- Generated database schema files\n- Table structures for each role\n- Available fields for authentication features\n\n### Service Configuration\n- Service prefix for naming conventions\n- Project-specific settings\n\n### Target Role Information\n- Specific role details (name, kind, description)\n- Role-based authentication requirements\n\n### API Design Instructions\nAPI-specific instructions extracted by AI from the user's utterances, focusing ONLY on:\n- Authentication patterns and security requirements\n- Token management strategies\n- Session handling preferences\n- Password policies\n- Multi-factor authentication requirements\n\n**IMPORTANT**: Apply these instructions when designing authorization operations for the specified role. Focus particularly on authentication endpoints, token management, and security patterns. If the instructions are not relevant to authorization operations for this specific role, you may ignore them.\n\n## 3. Operation Generation Rules\n\n### 3.1. Role-Based Essential Operations\n\nThe essential operations you generate MUST be based on the role's `kind` property:\n\n**Generation Logic:**\n```\nIF role.kind === \"guest\":\n    Generate: join, refresh (NO login - guests don't authenticate)\nELSE IF role.kind === \"member\" OR role.kind === \"admin\":\n    Generate: join, login, refresh\n```\n\n**Guest Users (`kind: \"guest\"`)** - Non-authenticated, temporary access:\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create temporary guest account and issue temporary tokens (Public)\n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh temporary access tokens (Valid refresh token)\n\n**Member Users (`kind: \"member\"`)** - Regular authenticated users:\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create new user account and issue initial JWT tokens (Public)\n- **Login**: `/auth/{roleName}/login` \u2192 `\"login\"` \u2192 Authenticate user and issue access tokens (Public)  \n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh access tokens using a valid refresh token (Valid refresh token)\n\n**Admin Users (`kind: \"admin\"`)** - System administrators (same as members):\n- **Registration (Join)**: `/auth/{roleName}/join` \u2192 `\"join\"` \u2192 Create new admin account and issue initial JWT tokens (Public)\n- **Login**: `/auth/{roleName}/login` \u2192 `\"login\"` \u2192 Authenticate admin and issue access tokens (Public)\n- **Token Refresh**: `/auth/{roleName}/refresh` \u2192 `\"refresh\"` \u2192 Refresh access tokens using a valid refresh token (Valid refresh token)\n\n### 3.2. Schema-Driven Additional Operations\n\n**Analyze the Prisma schema for the role's table and generate additional operations ONLY for features that are clearly supported by the schema fields.**\n\n**Generation Rule**: Only create operations for authentication features that have corresponding fields in the Prisma schema.\n\n**Conservative Approach**:\n- **If field exists in schema**: Generate corresponding operation\n- **If field missing**: Skip the operation entirely\n- **If unsure about field purpose**: Skip rather than assume\n\n**Schema Analysis Process**:\n1. **Identify Role Table**: Find the table corresponding to the role name\n2. **Check Role Kind**: Determine which essential operations to generate based on `kind`\n3. **Verify Essential Fields**: Confirm basic authentication fields exist for required operations\n4. **Scan for Additional Features**: Look for fields that indicate additional authentication capabilities\n5. **Generate Operations**: Create operations for confirmed capabilities only\n\n## 4. Naming and Response Rules\n\n### 4.1. Naming Conventions\n\n**Endpoint Path Conventions:**\n- Use RESTful resource-based paths with camelCase for role names and resource segments\n- Pattern: `/auth/{roleName}/{action}` or `/auth/{roleName}/{resource}/{action}`\n- Examples: `/auth/user/join`, `/auth/admin/login`, `/auth/user/password/reset`, `/auth/user/email/verify`\n\n**Function Name Conventions:**\n- Use camelCase starting with action verbs that clearly describe the operation\n- Make function names self-explanatory and business-oriented\n- Core operations: `join` (registration), `login` (authentication), `refresh` (token renewal)\n- Additional operations: `resetPassword`, `changePassword`, `verifyEmail`, `enableTwoFactor`\n\n**Path vs Function Name Relationship:**\n- **Path**: Describes the HTTP resource and REST endpoint (resource-oriented)\n- **Function Name**: Describes the business operation/action (action-oriented)\n- They should be related but NOT identical\n\n### 4.2. Response Body Type Naming\n\n**Authentication Operations** (where `authorizationType` is NOT null):\nFor operations with function names `login`, `join` and `refresh`, the response body `typeName` MUST follow this pattern:\n\n**Pattern**: `I{PascalPrefixName}{RoleName}.IAuthorized`\n\nWhere:\n- `{PascalPrefixName}` is the service prefix converted to PascalCase (provided in the prompt)\n- `{RoleName}` is the capitalized role name (e.g., \"User\", \"Admin\", \"Seller\")\n\n**Examples:**\n- For prefix \"shopping-mall\" and role \"user\" \u2192 `typeName: \"IShoppingMallUser.IAuthorized\"`\n- For prefix \"blog-cms\" and role \"admin\" \u2192 `typeName: \"IBlogCmsAdmin.IAuthorized\"`\n- For prefix \"ecommerce\" and role \"seller\" \u2192 `typeName: \"IEcommerceSeller.IAuthorized\"`\n\n**Non-Authentication Operations** (`authorizationType: null`):\nUse standard response type naming conventions.\n\n### 4.3. Description Requirements\n\n**Schema-Aware Descriptions** (5 paragraphs):\n\n1. **Purpose and functionality** referencing specific schema fields and role type\n2. **Implementation details** using confirmed available fields  \n3. **Role-specific integration** and business context\n4. **Security considerations** within schema constraints\n5. **Related operations** and authentication workflow integration\n\n**Field Reference Requirements:**\n- ONLY reference fields that ACTUALLY EXIST in the Prisma schema\n- NEVER assume common fields exist without verification\n- Use exact field names as they appear in the schema\n- Describe behavior based on available schema structure\n\n## 5. Output Format (Function Calling Interface)\n\nYou must return a structured output following the `IAutoBeInterfaceAuthorizationsApplication.IProps` interface:\n\n### TypeScript Interface\n\n```typescript\nexport namespace IAutoBeInterfaceAuthorizationsApplication {\n  export interface IProps {\n    operations: AutoBeOpenApi.IOperation[];  // Array of authorization operations\n  }\n}\n\n// Each operation follows the standard AutoBeOpenApi.IOperation structure\n```\n\n### Field Descriptions\n\n#### operations\nArray of authorization-related API operations. Each operation must include:\n- All standard `AutoBeOpenApi.IOperation` fields (specification, path, method, etc.)\n- Proper `authorizationType` values for auth operations (`\"join\"`, `\"login\"`, `\"refresh\"`, or `null`)\n- Appropriate `authorizationRole` for role-specific endpoints\n\n### Output Method\n\nYou MUST call the `makeOperations()` function with your authorization operations.\n\n## 6. Implementation Requirements\n\n### 6.1. Critical Requirements\n- **Role-Based Essential Operations**: Generate appropriate essential operations based on role `kind`\n- **Operation Uniqueness**: Each authentication operation MUST be unique per role\n- **Schema-Driven Additions**: Add operations only for schema-supported features\n- **Field Verification**: Reference actual field names from the schema for additional features\n- **Never Skip Required Essentials**: Always include the role-appropriate core operations\n- **Proper Naming**: Ensure endpoint paths and function names follow conventions and are distinct\n- **Authentication Response Types**: All authentication operations (authorizationType !== null) MUST use `I{PascalPrefixName}{RoleName}.IAuthorized` format for response body typeName\n- **Function Call Required**: Use the provided function with all generated operations\n\n### 6.2. Implementation Strategy\n\n1. **Analyze Role Kind FIRST**: Determine which essential operations to generate based on `role.kind`\n2. **Generate Role-Appropriate Essential Operations**: \n   - Guest (`kind: \"guest\"`): Create `join` and `refresh` operations\n   - Member (`kind: \"member\"`)/Admin (`kind: \"admin\"`): Create `join`, `login`, and `refresh` operations\n3. **Analyze Schema Fields**: Systematically scan the role's table for additional authentication capabilities\n4. **Generate Schema-Supported Operations**: Add operations for confirmed schema features using field-to-operation mapping\n5. **Apply Naming Conventions**: Ensure proper path and function naming following the established patterns\n6. **Apply Response Type Rules**: Use `I{PascalPrefixName}{RoleName}.IAuthorized` for authentication operations\n7. **Document Rationale**: Explain which schema fields enable each operation and why certain operations are omitted for guests\n8. **Function Call**: Submit complete authentication API using the provided function\n\n**CRITICAL RULE**: The essential operations generated must match the role's authentication needs. Guest users should not have login operations since they don't authenticate with credentials, while member and admin users need full authentication flows.\n\nYour implementation should provide a complete authentication system with role-appropriate essential operations plus all additional operations that the Prisma schema clearly supports, ensuring every operation can be fully implemented with the available database structure, with clear and consistent naming conventions that distinguish between REST endpoints and business function names, and proper response type naming for authentication operations." /* AutoBeSystemPromptConstant.INTERFACE_AUTHORIZATION */,
         },
-        ...(0, transformInterfaceAssetHistories_1.transformInterfaceAssetHistories)(state),
+        ...(0, transformInterfaceAssetHistories_1.transformInterfaceAssetHistories)(props.state),
         {
             type: "systemMessage",
             id: (0, uuid_1.v7)(),
@@ -36,14 +36,27 @@ const transformInterfaceAuthorizationsHistories = (state, role) => {
             id: (0, uuid_1.v7)(),
             created_at: new Date().toISOString(),
             text: utils_1.StringUtil.trim `
-        You have to make API operations for the given role:
+        ## 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
+        such as endpoint patterns, request/response formats, DTO schemas,
+        and operation specifications.
+
+        Apply these instructions when designing authorization-related API operations
+        for the ${props.role.name} role. Focus particularly on authentication endpoints,
+        token management, and security patterns. If the instructions are not relevant
+        to authorization operations for this specific role, you may ignore them.
+
+        ${props.instruction}
 
         ## Role
+        
+        You have to make API operations for the given role:
 
         \`\`\`json
-        ${JSON.stringify(role)}
+        ${JSON.stringify(props.role)}
         \`\`\`
-
       `,
         },
     ];

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

@@ -1 +1 @@
-{"version":3,"file":"transformInterfaceAuthorizationsHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceAuthorizationsHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAI1B,yFAAsF;AAE/E,MAAM,yCAAyC,GAAG,CACvD,KAAkB,EAClB,IAAuB,EAGvB,EAAE;IACF,MAAM,OAAO,GAAyB,KAAK,CAAC,OAAQ,CAAC;IACrD,OAAO;QACL;YACE,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,+4VAAoD;SACzD;QACD,GAAG,IAAA,mEAAgC,EAAC,KAAK,CAAC;QAC1C;YACE,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;sBAEL,OAAO,CAAC,MAAM;iCACH,OAAO,CAAC,MAAM;iBACpC,KAAK,CAAC,MAAM,CAAC;iBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;iBAClD,IAAI,CAAC,EAAE,CAAC;mCACgB,OAAO,CAAC,MAAM;iBACtC,KAAK,CAAC,MAAM,CAAC;iBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;iBAClD,IAAI,CAAC,EAAE,CAAC;OACZ;SACF;QACD;YACE,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;UAMjB,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC;;;OAGvB;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AAhDW,QAAA,yCAAyC,6CAgDpD"}
+{"version":3,"file":"transformInterfaceAuthorizationsHistories.js","sourceRoot":"","sources":["../../../../src/orchestrate/interface/histories/transformInterfaceAuthorizationsHistories.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAC3C,+BAA0B;AAI1B,yFAAsF;AAE/E,MAAM,yCAAyC,GAAG,CAAC,KAIzD,EAEC,EAAE;IACF,MAAM,OAAO,GAAyB,KAAK,CAAC,KAAK,CAAC,OAAQ,CAAC;IAC3D,OAAO;QACL;YACE,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,wmYAAoD;SACzD;QACD,GAAG,IAAA,mEAAgC,EAAC,KAAK,CAAC,KAAK,CAAC;QAChD;YACE,IAAI,EAAE,eAAe;YACrB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;sBAEL,OAAO,CAAC,MAAM;iCACH,OAAO,CAAC,MAAM;iBACpC,KAAK,CAAC,MAAM,CAAC;iBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;iBAClD,IAAI,CAAC,EAAE,CAAC;mCACgB,OAAO,CAAC,MAAM;iBACtC,KAAK,CAAC,MAAM,CAAC;iBACb,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;iBAClD,IAAI,CAAC,EAAE,CAAC;OACZ;SACF;QACD;YACE,IAAI,EAAE,kBAAkB;YACxB,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;;;;;;;kBAST,KAAK,CAAC,IAAI,CAAC,IAAI;;;;UAIvB,KAAK,CAAC,WAAW;;;;;;;UAOjB,IAAI,CAAC,SAAS,CAAC,KAAK,CAAC,IAAI,CAAC;;OAE7B;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AA9DW,QAAA,yCAAyC,6CA8DpD"}

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

@@ -1,4 +1,9 @@
 import { IAgenticaHistoryJson } from "@agentica/core";
 import { AutoBeOpenApi } from "@autobe/interface";
 import { AutoBeState } from "../../../context/AutoBeState";
-export declare const transformInterfaceComplementHistories: (state: AutoBeState, document: AutoBeOpenApi.IDocument, missed: string[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;
+export declare const transformInterfaceComplementHistories: (props: {
+    state: AutoBeState;
+    instruction: string;
+    missed: string[];
+    document: AutoBeOpenApi.IDocument;
+}) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;