@autobe/agent 0.17.1 → 0.19.1

package/lib/agent/src/orchestrate/realize/orchestrateRealizeWrite.js

@@ -0,0 +1,345 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || (function () {
+    var ownKeys = function(o) {
+        ownKeys = Object.getOwnPropertyNames || function (o) {
+            var ar = [];
+            for (var k in o) if (Object.prototype.hasOwnProperty.call(o, k)) ar[ar.length] = k;
+            return ar;
+        };
+        return ownKeys(o);
+    };
+    return function (mod) {
+        if (mod && mod.__esModule) return mod;
+        var result = {};
+        if (mod != null) for (var k = ownKeys(mod), i = 0; i < k.length; i++) if (k[i] !== "default") __createBinding(result, mod, k[i]);
+        __setModuleDefault(result, mod);
+        return result;
+    };
+})();
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.orchestrateRealizeWrite = orchestrateRealizeWrite;
+const __typia_transform__validateReport = __importStar(require("typia/lib/internal/_validateReport.js"));
+const typia_1 = __importDefault(require("typia"));
+const assertSchemaModel_1 = require("../../context/assertSchemaModel");
+const getTestScenarioArtifacts_1 = require("../test/compile/getTestScenarioArtifacts");
+const transformRealizeWriteHistories_1 = require("./histories/transformRealizeWriteHistories");
+const replaceImportStatements_1 = require("./utils/replaceImportStatements");
+function orchestrateRealizeWrite(ctx, props) {
+    return __awaiter(this, void 0, void 0, function* () {
+        var _a, _b, _c;
+        const artifacts = yield (0, getTestScenarioArtifacts_1.getTestScenarioArtifacts)(ctx, {
+            endpoint: props.scenario.operation,
+            dependencies: [],
+        });
+        const pointer = {
+            value: null,
+        };
+        const { tokenUsage } = yield ctx.conversate({
+            source: "realizeWrite",
+            histories: (0, transformRealizeWriteHistories_1.transformRealizeWriteHistories)({
+                state: ctx.state(),
+                scenario: props.scenario,
+                artifacts,
+                authorization: props.authorization,
+                totalAuthorizations: props.totalAuthorizations,
+            }),
+            controller: createController({
+                model: ctx.model,
+                build: (next) => {
+                    pointer.value = next;
+                },
+            }),
+            enforceFunctionCall: true,
+            message: [
+                `Write complete, production-ready TypeScript code that strictly follows these rules:`,
+                "",
+                `DO NOT:`,
+                `- Use the native \`Date\` type anywhere`,
+                `- Use \`as\` for type assertions`,
+                ``,
+                `DO:`,
+                `- Write all date/datetime values as \`string & tags.Format<'date-time'>\``,
+                `- Generate UUIDs using \`v4()\` and type as \`string & tags.Format<'uuid'>\``,
+                `- Resolve types properly without assertions`,
+                `- Type all functions with clear parameter and return types`,
+                `6. Do not skip validations or default values where necessary.`,
+                `7. Follow functional, immutable, and consistent code structure.`,
+                "",
+                `Use \`@nestia/e2e\` test structure if relevant.`,
+            ].join("\n"),
+        });
+        if (pointer.value === null)
+            throw new Error("Failed to write code.");
+        pointer.value.implementationCode = yield (0, replaceImportStatements_1.replaceImportStatements)(ctx)(artifacts, pointer.value.implementationCode, (_a = props.authorization) === null || _a === void 0 ? void 0 : _a.payload.name);
+        const event = {
+            type: "realizeWrite",
+            location: props.scenario.location,
+            content: pointer.value.implementationCode,
+            tokenUsage,
+            completed: ++props.progress.completed,
+            total: props.progress.total,
+            step: (_c = (_b = ctx.state().analyze) === null || _b === void 0 ? void 0 : _b.step) !== null && _c !== void 0 ? _c : 0,
+            created_at: new Date().toISOString(),
+        };
+        ctx.dispatch(event);
+        return event;
+    });
+}
+function createController(props) {
+    (0, assertSchemaModel_1.assertSchemaModel)(props.model);
+    const application = collection[props.model];
+    return {
+        protocol: "class",
+        name: "Write code",
+        application,
+        execute: {
+            coding: (next) => {
+                props.build(next);
+            },
+        },
+    };
+}
+const claude = {
+    model: "claude",
+    options: {
+        reference: true,
+        separate: null
+    },
+    functions: [
+        {
+            name: "coding",
+            parameters: {
+                description: "Current Type: {@link IAutoBeRealizeWriteApplication.IProps}",
+                type: "object",
+                properties: {
+                    plan: {
+                        description: "Step 1.\n\n\uD83E\uDDE0 Provider Function Implementation Plan\n\nThis field outlines the strategic plan for implementing the provider\nfunction according to the Realize Coder Agent specification. Before\nwriting the actual code, think through the logic and structure.\n\nThe plan follows a SCHEMA-FIRST APPROACH:\n\n\uD83D\uDCCB STEP 1 - PRISMA SCHEMA VERIFICATION:\n\nDO:\n- Examine the actual Prisma schema model definition\n- List EVERY field that exists in the model with exact types\n- Explicitly note fields that DO NOT exist\n\nDO NOT:\n- Assume common fields exist without verification\n- Use fields like deleted_at, created_by, updated_by, is_deleted, is_active without checking\n\n\uD83D\uDCCB STEP 2 - FIELD INVENTORY:\n\n- List ONLY fields confirmed to exist in schema\n- Example: \"Verified fields in user model: id (String), email (String),\n  created_at (DateTime), updated_at (DateTime)\"\n- Example: \"Fields that DO NOT exist: deleted_at, is_active, created_by\"\n\n\uD83D\uDCCB STEP 3 - FIELD ACCESS STRATEGY:\n\n- Plan which verified fields will be used in select, update, create\n  operations\n- For complex operations with type errors, plan to use separate queries\n  instead of nested operations\n\n\uD83D\uDCCB STEP 4 - TYPE COMPATIBILITY:\n\n- Plan DateTime to ISO string conversions using toISOStringSafe()\n- Plan handling of nullable vs required fields\n\n\uD83D\uDCCB STEP 5 - IMPLEMENTATION APPROACH:\n\n- \uD83E\uDDE9 Required business entities (e.g., users, posts, logs) and their\n  relationships\n- \uD83D\uDEE0 Operations needed to fulfill the business scenario (e.g., fetch,\n  create, update) using ONLY verified fields\n- \uD83D\uDD04 Data dependencies between steps (e.g., use userId to fetch related\n  data)\n- \u2705 Validation points (based on business rules, not field presence)\n- \uD83D\uDEA7 Error and edge cases that must be handled explicitly (e.g., missing\n  records)\n- \uD83C\uDFD7 Structure: always a single `async function`, using only `parameters`\n  and `body`\n\n\u26A0\uFE0F Important Constraints:\n\n- Do NOT perform input validation \u2014 assume `parameters` and `body` are\n  already valid\n- Use `typia.random<T>()` with an explanatory comment if logic can't be\n  implemented\n- Never use `any` or make assumptions without sufficient context\n- Use only allowed imports \u2014 DTOs and Prisma types\n- Use `MyGlobal.prisma` for DB access and respect Prisma typing rules\n\n\u26A0\uFE0F TypeScript-specific considerations:\n\n- Do **not** use native `Date` objects directly; always convert all dates\n  using `toISOStringSafe()` and brand as `string &\n  tags.Format<'date-time'>`. This rule applies throughout all phases.\n- Prefer `satisfies` for DTO conformance instead of unsafe `as` casts\n- Avoid weak typing such as `any`, `as any`, or `satisfies any`\n- Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where\n  applicable\n\n\u2705 Example Structure:\n\n```ts\nexport async function doSomething(\n  user: { id: string & tags.Format<\"uuid\">; type: string },\n  parameters: IParams,\n  body: IBody\n): Promise<IReturn> {\n  const { id } = parameters;\n  const { name } = body;\n  const user = await MyGlobal.prisma.users.findFirst({ where: { id } });\n  if (!user) throw new Error(\"User not found\");\n  ...\n  return result;\n}\n```\n\n\uD83D\uDD0D Feasibility Analysis Requirement:\n\n- Before generating any code, the agent **must analyze** whether the\n  requested implementation is **feasible based on the given Prisma schema\n  and DTO types**.\n- If required fields or relationships are **missing or incompatible**, the\n  plan should explicitly state that the implementation is **not\n  possible** with the current schema/DTO, and no code should be generated\n  in later stages.\n- In such cases, only a detailed **comment in the `implementationCode`**\n  should be returned explaining why the logic cannot be implemented.\n\n\uD83D\uDD25 Error Handling Plan:\n\nIf an error is expected or encountered during implementation:\n\n- Clearly document the error message(s) and TypeScript error codes.\n- Analyze the root cause (e.g., type mismatch, missing field, nullability\n  issue).\n- Define concrete steps to resolve the issue, such as:\n\n  - Adjusting type declarations or using Prisma-generated input types.\n  - Using `?? undefined` to normalize nullable fields.\n  - Applying correct relation handling (e.g., `connect` instead of direct\n      foreign key assignment).\n  - Ensuring all date fields use `.toISOString()` and proper branding.\n- Include fallback or workaround plans if a direct fix is complex.\n- If no error is present, simply omit this section.\n\nThis plan ensures the function will:\n\n- Respect the global architecture and coding conventions\n- Be safe, predictable, and aligned with upstream logic",
+                        type: "string"
+                    },
+                    prisma_schemas: {
+                        description: "Step 2.\n\nThe Prisma schema string that will be used to validate the implementation\nlogic in this file.\n\nYou must **explicitly specify only the relevant models and fields** from\nyour full schema that are used in this implementation. This ensures that\nyour logic is aligned with the expected database structure without\naccidentally introducing unrelated fields or models.\n\n\u26A0\uFE0F Important: The value of this field must be a valid Prisma schema\nstring containing only the models used in this code \u2014 not the entire\nschema.\n\nThis acts as a safeguard against:\n\n- Forgetting required fields used in this implementation\n- Including fields or models that are not actually used",
+                        type: "string"
+                    },
+                    draft_without_date_type: {
+                        description: "Step 3.\n\nDraft WITHOUT using native Date type.\n\nThis is the initial drafting phase where you outline the basic skeleton\nof the function.\n\nDO NOT: Use the native Date type.\n\n- The function signature must correctly include `user`, `parameters`, and\n  `body` arguments.\n- Design the main flow of business logic, such as DB fetches and early\n  returns based on conditions.\n- Mark any incomplete or missing parts clearly with placeholders (e.g.,\n  comments or temporary values).\n\nImport rules:\n\nDO NOT:\n- Add any new import statements manually\n- Write import statements directly (this causes compile errors)\n\nNote: All necessary imports are provided globally or by the system automatically.\n\n\u2705 Requirements:\n\n- Avoid using the `any` type at all costs to ensure type safety.\n- NEVER declare variables with `: Date` type\n- ALWAYS use `string & tags.Format<'date-time'>` for date values\n- Use `toISOStringSafe(new Date())` for current timestamps\n- Maintain a single-function structure; avoid using classes.",
+                        type: "string"
+                    },
+                    review: {
+                        description: "Step 4.\n\nA refined version of the draft with improved completeness.\n\n- Replace placeholder logic with real DTO-conformant operations.\n- Add error handling (`throw new Error(...)`) where necessary.\n- Begin resolving structural or type mismatches.\n\n\u2705 Requirements:\n\n- Use `satisfies` to ensure DTO conformity.\n- Avoid unsafe `as` casts unless only for branding or literal narrowing.\n- Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).\n- Ensure all object keys strictly conform to the expected type definitions.",
+                        type: "string"
+                    },
+                    withCompilerFeedback: {
+                        description: "\uD83D\uDEE0 Phase 4-2: With compiler feedback (optional)\n\nA correction pass that applies fixes for compile-time errors that arose\nduring the review stage (if any).\n\n\u2705 Must:\n\n- Only include this field if TypeScript errors are detected in the Review\n  phase.\n- Resolve all TypeScript errors without using `as any`.\n- Provide safe brand casting only if required (e.g., `as string &\n  tags.Format<'uuid'>`).\n- If no TypeScript errors exist, this field MUST contain the text: \"No\n  TypeScript errors detected - skipping this phase\"",
+                        type: "string"
+                    },
+                    implementationCode: {
+                        description: "Step 5.\n\nThe complete and fully correct TypeScript function implementation.\n\n- Passes strict type checking without errors.\n- Uses only safe branding or literal type assertions.\n- Converts all date values properly using `toISOStringSafe()`.\n- Follows DTO structures using `satisfies`.\n- Avoids any weak typing such as `any`, `as any`, or `satisfies any`.\n- Uses only allowed imports (e.g., from `../api/structures` and\n  `MyGlobal.prisma`).\n- NEVER creates intermediate variables for Prisma operations.\n\n\u26A0\uFE0F Fallback Behavior:\n\n- If the `plan` phase explicitly determines that the requested logic is\n  **not feasible** due to mismatches or limitations in the provided\n  Prisma schema and DTO types:\n\n  - The implementation must still return a syntactically valid function.\n  - In such cases, return mock data using `typia.random<T>()` wrapped in the\n      correct structure, along with a comment explaining the limitation.\n\n  Example fallback:\n\n```ts\n  // \u26A0\uFE0F Cannot implement logic due to missing relation between A and B\n  export async function someFunction(...) {\n    return typia.random<IReturn>(); // mocked output\n  }\n```\n\n\u26A0\uFE0F Prohibited Practices:\n\n- Do NOT add or modify import statements manually. Imports are handled\n  automatically by the system.\n- Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.\n- Do NOT assign native `Date` objects directly; always convert them using\n  `toISOStringSafe()`.\n- Do NOT use unsafe type assertions except for safe branding or literal\n  narrowing.\n- Do NOT write code outside the single async function structure (e.g., no\n  classes or multiple functions).\n- Do NOT perform any input validation \u2014 assume all inputs are already\n  validated.\n- Do NOT use dynamic import expressions (`import()`); all imports must be\n  static.\n- Do NOT use Prisma-generated input types; always use types from\n  `../api/structures`.\n- Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.\n- Do NOT escape newlines or quotes in the implementation string (e.g., no\n  `\\\\n` or `\\\"`); use a properly formatted template literal with actual\n  line breaks instead.",
+                        type: "string"
+                    }
+                },
+                required: [
+                    "plan",
+                    "prisma_schemas",
+                    "draft_without_date_type",
+                    "review",
+                    "withCompilerFeedback",
+                    "implementationCode"
+                ],
+                additionalProperties: false,
+                $defs: {}
+            },
+            validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prisma_schemas && "string" === typeof input.draft_without_date_type && "string" === typeof input.review && "string" === typeof input.withCompilerFeedback && "string" === typeof input.implementationCode; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
+                    path: _path + ".plan",
+                    expected: "string",
+                    value: input.plan
+                }), "string" === typeof input.prisma_schemas || _report(_exceptionable, {
+                    path: _path + ".prisma_schemas",
+                    expected: "string",
+                    value: input.prisma_schemas
+                }), "string" === typeof input.draft_without_date_type || _report(_exceptionable, {
+                    path: _path + ".draft_without_date_type",
+                    expected: "string",
+                    value: input.draft_without_date_type
+                }), "string" === typeof input.review || _report(_exceptionable, {
+                    path: _path + ".review",
+                    expected: "string",
+                    value: input.review
+                }), "string" === typeof input.withCompilerFeedback || _report(_exceptionable, {
+                    path: _path + ".withCompilerFeedback",
+                    expected: "string",
+                    value: input.withCompilerFeedback
+                }), "string" === typeof input.implementationCode || _report(_exceptionable, {
+                    path: _path + ".implementationCode",
+                    expected: "string",
+                    value: input.implementationCode
+                })].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: "IAutoBeRealizeWriteApplication.IProps",
+                        value: input
+                    })) && _vo0(input, _path + "", true) || _report(true, {
+                        path: _path + "",
+                        expected: "IAutoBeRealizeWriteApplication.IProps",
+                        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 = {
+    chatgpt: {
+        model: "chatgpt",
+        options: {
+            reference: true,
+            strict: false,
+            separate: null
+        },
+        functions: [
+            {
+                name: "coding",
+                parameters: {
+                    description: "Current Type: {@link IAutoBeRealizeWriteApplication.IProps}",
+                    type: "object",
+                    properties: {
+                        plan: {
+                            description: "Step 1.\n\n\uD83E\uDDE0 Provider Function Implementation Plan\n\nThis field outlines the strategic plan for implementing the provider\nfunction according to the Realize Coder Agent specification. Before\nwriting the actual code, think through the logic and structure.\n\nThe plan follows a SCHEMA-FIRST APPROACH:\n\n\uD83D\uDCCB STEP 1 - PRISMA SCHEMA VERIFICATION:\n\nDO:\n- Examine the actual Prisma schema model definition\n- List EVERY field that exists in the model with exact types\n- Explicitly note fields that DO NOT exist\n\nDO NOT:\n- Assume common fields exist without verification\n- Use fields like deleted_at, created_by, updated_by, is_deleted, is_active without checking\n\n\uD83D\uDCCB STEP 2 - FIELD INVENTORY:\n\n- List ONLY fields confirmed to exist in schema\n- Example: \"Verified fields in user model: id (String), email (String),\n  created_at (DateTime), updated_at (DateTime)\"\n- Example: \"Fields that DO NOT exist: deleted_at, is_active, created_by\"\n\n\uD83D\uDCCB STEP 3 - FIELD ACCESS STRATEGY:\n\n- Plan which verified fields will be used in select, update, create\n  operations\n- For complex operations with type errors, plan to use separate queries\n  instead of nested operations\n\n\uD83D\uDCCB STEP 4 - TYPE COMPATIBILITY:\n\n- Plan DateTime to ISO string conversions using toISOStringSafe()\n- Plan handling of nullable vs required fields\n\n\uD83D\uDCCB STEP 5 - IMPLEMENTATION APPROACH:\n\n- \uD83E\uDDE9 Required business entities (e.g., users, posts, logs) and their\n  relationships\n- \uD83D\uDEE0 Operations needed to fulfill the business scenario (e.g., fetch,\n  create, update) using ONLY verified fields\n- \uD83D\uDD04 Data dependencies between steps (e.g., use userId to fetch related\n  data)\n- \u2705 Validation points (based on business rules, not field presence)\n- \uD83D\uDEA7 Error and edge cases that must be handled explicitly (e.g., missing\n  records)\n- \uD83C\uDFD7 Structure: always a single `async function`, using only `parameters`\n  and `body`\n\n\u26A0\uFE0F Important Constraints:\n\n- Do NOT perform input validation \u2014 assume `parameters` and `body` are\n  already valid\n- Use `typia.random<T>()` with an explanatory comment if logic can't be\n  implemented\n- Never use `any` or make assumptions without sufficient context\n- Use only allowed imports \u2014 DTOs and Prisma types\n- Use `MyGlobal.prisma` for DB access and respect Prisma typing rules\n\n\u26A0\uFE0F TypeScript-specific considerations:\n\n- Do **not** use native `Date` objects directly; always convert all dates\n  using `toISOStringSafe()` and brand as `string &\n  tags.Format<'date-time'>`. This rule applies throughout all phases.\n- Prefer `satisfies` for DTO conformance instead of unsafe `as` casts\n- Avoid weak typing such as `any`, `as any`, or `satisfies any`\n- Use branded types (e.g., `tags.Format<'uuid'>`) and literal unions where\n  applicable\n\n\u2705 Example Structure:\n\n```ts\nexport async function doSomething(\n  user: { id: string & tags.Format<\"uuid\">; type: string },\n  parameters: IParams,\n  body: IBody\n): Promise<IReturn> {\n  const { id } = parameters;\n  const { name } = body;\n  const user = await MyGlobal.prisma.users.findFirst({ where: { id } });\n  if (!user) throw new Error(\"User not found\");\n  ...\n  return result;\n}\n```\n\n\uD83D\uDD0D Feasibility Analysis Requirement:\n\n- Before generating any code, the agent **must analyze** whether the\n  requested implementation is **feasible based on the given Prisma schema\n  and DTO types**.\n- If required fields or relationships are **missing or incompatible**, the\n  plan should explicitly state that the implementation is **not\n  possible** with the current schema/DTO, and no code should be generated\n  in later stages.\n- In such cases, only a detailed **comment in the `implementationCode`**\n  should be returned explaining why the logic cannot be implemented.\n\n\uD83D\uDD25 Error Handling Plan:\n\nIf an error is expected or encountered during implementation:\n\n- Clearly document the error message(s) and TypeScript error codes.\n- Analyze the root cause (e.g., type mismatch, missing field, nullability\n  issue).\n- Define concrete steps to resolve the issue, such as:\n\n  - Adjusting type declarations or using Prisma-generated input types.\n  - Using `?? undefined` to normalize nullable fields.\n  - Applying correct relation handling (e.g., `connect` instead of direct\n      foreign key assignment).\n  - Ensuring all date fields use `.toISOString()` and proper branding.\n- Include fallback or workaround plans if a direct fix is complex.\n- If no error is present, simply omit this section.\n\nThis plan ensures the function will:\n\n- Respect the global architecture and coding conventions\n- Be safe, predictable, and aligned with upstream logic",
+                            type: "string"
+                        },
+                        prisma_schemas: {
+                            description: "Step 2.\n\nThe Prisma schema string that will be used to validate the implementation\nlogic in this file.\n\nYou must **explicitly specify only the relevant models and fields** from\nyour full schema that are used in this implementation. This ensures that\nyour logic is aligned with the expected database structure without\naccidentally introducing unrelated fields or models.\n\n\u26A0\uFE0F Important: The value of this field must be a valid Prisma schema\nstring containing only the models used in this code \u2014 not the entire\nschema.\n\nThis acts as a safeguard against:\n\n- Forgetting required fields used in this implementation\n- Including fields or models that are not actually used",
+                            type: "string"
+                        },
+                        draft_without_date_type: {
+                            description: "Step 3.\n\nDraft WITHOUT using native Date type.\n\nThis is the initial drafting phase where you outline the basic skeleton\nof the function.\n\nDO NOT: Use the native Date type.\n\n- The function signature must correctly include `user`, `parameters`, and\n  `body` arguments.\n- Design the main flow of business logic, such as DB fetches and early\n  returns based on conditions.\n- Mark any incomplete or missing parts clearly with placeholders (e.g.,\n  comments or temporary values).\n\nImport rules:\n\nDO NOT:\n- Add any new import statements manually\n- Write import statements directly (this causes compile errors)\n\nNote: All necessary imports are provided globally or by the system automatically.\n\n\u2705 Requirements:\n\n- Avoid using the `any` type at all costs to ensure type safety.\n- NEVER declare variables with `: Date` type\n- ALWAYS use `string & tags.Format<'date-time'>` for date values\n- Use `toISOStringSafe(new Date())` for current timestamps\n- Maintain a single-function structure; avoid using classes.",
+                            type: "string"
+                        },
+                        review: {
+                            description: "Step 4.\n\nA refined version of the draft with improved completeness.\n\n- Replace placeholder logic with real DTO-conformant operations.\n- Add error handling (`throw new Error(...)`) where necessary.\n- Begin resolving structural or type mismatches.\n\n\u2705 Requirements:\n\n- Use `satisfies` to ensure DTO conformity.\n- Avoid unsafe `as` casts unless only for branding or literal narrowing.\n- Use `toISOStringSafe()` for all date conversions (NOT `.toISOString()`).\n- Ensure all object keys strictly conform to the expected type definitions.",
+                            type: "string"
+                        },
+                        withCompilerFeedback: {
+                            description: "\uD83D\uDEE0 Phase 4-2: With compiler feedback (optional)\n\nA correction pass that applies fixes for compile-time errors that arose\nduring the review stage (if any).\n\n\u2705 Must:\n\n- Only include this field if TypeScript errors are detected in the Review\n  phase.\n- Resolve all TypeScript errors without using `as any`.\n- Provide safe brand casting only if required (e.g., `as string &\n  tags.Format<'uuid'>`).\n- If no TypeScript errors exist, this field MUST contain the text: \"No\n  TypeScript errors detected - skipping this phase\"",
+                            type: "string"
+                        },
+                        implementationCode: {
+                            description: "Step 5.\n\nThe complete and fully correct TypeScript function implementation.\n\n- Passes strict type checking without errors.\n- Uses only safe branding or literal type assertions.\n- Converts all date values properly using `toISOStringSafe()`.\n- Follows DTO structures using `satisfies`.\n- Avoids any weak typing such as `any`, `as any`, or `satisfies any`.\n- Uses only allowed imports (e.g., from `../api/structures` and\n  `MyGlobal.prisma`).\n- NEVER creates intermediate variables for Prisma operations.\n\n\u26A0\uFE0F Fallback Behavior:\n\n- If the `plan` phase explicitly determines that the requested logic is\n  **not feasible** due to mismatches or limitations in the provided\n  Prisma schema and DTO types:\n\n  - The implementation must still return a syntactically valid function.\n  - In such cases, return mock data using `typia.random<T>()` wrapped in the\n      correct structure, along with a comment explaining the limitation.\n\n  Example fallback:\n\n```ts\n  // \u26A0\uFE0F Cannot implement logic due to missing relation between A and B\n  export async function someFunction(...) {\n    return typia.random<IReturn>(); // mocked output\n  }\n```\n\n\u26A0\uFE0F Prohibited Practices:\n\n- Do NOT add or modify import statements manually. Imports are handled\n  automatically by the system.\n- Do NOT use `any`, `as any`, or `satisfies any` to bypass type checking.\n- Do NOT assign native `Date` objects directly; always convert them using\n  `toISOStringSafe()`.\n- Do NOT use unsafe type assertions except for safe branding or literal\n  narrowing.\n- Do NOT write code outside the single async function structure (e.g., no\n  classes or multiple functions).\n- Do NOT perform any input validation \u2014 assume all inputs are already\n  validated.\n- Do NOT use dynamic import expressions (`import()`); all imports must be\n  static.\n- Do NOT use Prisma-generated input types; always use types from\n  `../api/structures`.\n- Do NOT use `Object.prototype.hasOwnProperty.call()` for field checks.\n- Do NOT escape newlines or quotes in the implementation string (e.g., no\n  `\\\\n` or `\\\"`); use a properly formatted template literal with actual\n  line breaks instead.",
+                            type: "string"
+                        }
+                    },
+                    required: [
+                        "plan",
+                        "prisma_schemas",
+                        "draft_without_date_type",
+                        "review",
+                        "withCompilerFeedback",
+                        "implementationCode"
+                    ],
+                    additionalProperties: false,
+                    $defs: {}
+                },
+                validate: (() => { const _io0 = input => "string" === typeof input.plan && "string" === typeof input.prisma_schemas && "string" === typeof input.draft_without_date_type && "string" === typeof input.review && "string" === typeof input.withCompilerFeedback && "string" === typeof input.implementationCode; const _vo0 = (input, _path, _exceptionable = true) => ["string" === typeof input.plan || _report(_exceptionable, {
+                        path: _path + ".plan",
+                        expected: "string",
+                        value: input.plan
+                    }), "string" === typeof input.prisma_schemas || _report(_exceptionable, {
+                        path: _path + ".prisma_schemas",
+                        expected: "string",
+                        value: input.prisma_schemas
+                    }), "string" === typeof input.draft_without_date_type || _report(_exceptionable, {
+                        path: _path + ".draft_without_date_type",
+                        expected: "string",
+                        value: input.draft_without_date_type
+                    }), "string" === typeof input.review || _report(_exceptionable, {
+                        path: _path + ".review",
+                        expected: "string",
+                        value: input.review
+                    }), "string" === typeof input.withCompilerFeedback || _report(_exceptionable, {
+                        path: _path + ".withCompilerFeedback",
+                        expected: "string",
+                        value: input.withCompilerFeedback
+                    }), "string" === typeof input.implementationCode || _report(_exceptionable, {
+                        path: _path + ".implementationCode",
+                        expected: "string",
+                        value: input.implementationCode
+                    })].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: "IAutoBeRealizeWriteApplication.IProps",
+                            value: input
+                        })) && _vo0(input, _path + "", true) || _report(true, {
+                            path: _path + "",
+                            expected: "IAutoBeRealizeWriteApplication.IProps",
+                            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,
+    llama: claude,
+    deepseek: claude,
+    "3.1": claude,
+};
+//# sourceMappingURL=orchestrateRealizeWrite.js.map

package/lib/agent/src/orchestrate/realize/orchestrateRealizeWrite.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"orchestrateRealizeWrite.js","sourceRoot":"","sources":["../../../../../src/orchestrate/realize/orchestrateRealizeWrite.ts"],"names":[],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAiBA,0DAuEC;;AAlFD,kDAA0B;AAG1B,uEAAoE;AACpE,uFAAoF;AAEpF,+FAA4F;AAG5F,6EAA0E;AAE1E,SAAsB,uBAAuB,CAC3C,GAAyB,EACzB,KAKC;;;QAED,MAAM,SAAS,GACb,MAAM,IAAA,mDAAwB,EAAC,GAAG,EAAE;YAClC,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YAClC,YAAY,EAAE,EAAE;SACjB,CAAC,CAAC;QACL,MAAM,OAAO,GAA2D;YACtE,KAAK,EAAE,IAAI;SACZ,CAAC;QACF,MAAM,EAAE,UAAU,EAAE,GAAG,MAAM,GAAG,CAAC,UAAU,CAAC;YAC1C,MAAM,EAAE,cAAc;YACtB,SAAS,EAAE,IAAA,+DAA8B,EAAC;gBACxC,KAAK,EAAE,GAAG,CAAC,KAAK,EAAE;gBAClB,QAAQ,EAAE,KAAK,CAAC,QAAQ;gBACxB,SAAS;gBACT,aAAa,EAAE,KAAK,CAAC,aAAa;gBAClC,mBAAmB,EAAE,KAAK,CAAC,mBAAmB;aAC/C,CAAC;YACF,UAAU,EAAE,gBAAgB,CAAC;gBAC3B,KAAK,EAAE,GAAG,CAAC,KAAK;gBAChB,KAAK,EAAE,CAAC,IAAI,EAAE,EAAE;oBACd,OAAO,CAAC,KAAK,GAAG,IAAI,CAAC;gBACvB,CAAC;aACF,CAAC;YACF,mBAAmB,EAAE,IAAI;YACzB,OAAO,EAAE;gBACP,qFAAqF;gBACrF,EAAE;gBACF,SAAS;gBACT,yCAAyC;gBACzC,kCAAkC;gBAClC,EAAE;gBACF,KAAK;gBACL,2EAA2E;gBAC3E,8EAA8E;gBAC9E,6CAA6C;gBAC7C,4DAA4D;gBAC5D,+DAA+D;gBAC/D,iEAAiE;gBACjE,EAAE;gBACF,iDAAiD;aAClD,CAAC,IAAI,CAAC,IAAI,CAAC;SACb,CAAC,CAAC;QACH,IAAI,OAAO,CAAC,KAAK,KAAK,IAAI;YAAE,MAAM,IAAI,KAAK,CAAC,uBAAuB,CAAC,CAAC;QAErE,OAAO,CAAC,KAAK,CAAC,kBAAkB,GAAG,MAAM,IAAA,iDAAuB,EAAC,GAAG,CAAC,CACnE,SAAS,EACT,OAAO,CAAC,KAAK,CAAC,kBAAkB,EAChC,MAAA,KAAK,CAAC,aAAa,0CAAE,OAAO,CAAC,IAAI,CAClC,CAAC;QAEF,MAAM,KAAK,GAA4B;YACrC,IAAI,EAAE,cAAc;YACpB,QAAQ,EAAE,KAAK,CAAC,QAAQ,CAAC,QAAQ;YACjC,OAAO,EAAE,OAAO,CAAC,KAAK,CAAC,kBAAkB;YACzC,UAAU;YACV,SAAS,EAAE,EAAE,KAAK,CAAC,QAAQ,CAAC,SAAS;YACrC,KAAK,EAAE,KAAK,CAAC,QAAQ,CAAC,KAAK;YAC3B,IAAI,EAAE,MAAA,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,OAAO,0CAAE,IAAI,mCAAI,CAAC;YACpC,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;SACrC,CAAC;QACF,GAAG,CAAC,QAAQ,CAAC,KAAK,CAAC,CAAC;QACpB,OAAO,KAAK,CAAC;IACf,CAAC;CAAA;AAED,SAAS,gBAAgB,CAAiC,KAGzD;IACC,IAAA,qCAAiB,EAAC,KAAK,CAAC,KAAK,CAAC,CAAC;IAE/B,MAAM,WAAW,GAA2B,UAAU,CACpD,KAAK,CAAC,KAAK,CACwD,CAAC;IAEtE,OAAO;QACL,QAAQ,EAAE,OAAO;QACjB,IAAI,EAAE,YAAY;QAClB,WAAW;QACX,OAAO,EAAE;YACP,MAAM,EAAE,CAAC,IAAI,EAAE,EAAE;gBACf,KAAK,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;YACpB,CAAC;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/agent/src/orchestrate/realize/structures/IAutoBeRealizeAuthorizationApplication.d.ts

@@ -0,0 +1,92 @@
+import { CamelPattern, PascalPattern } from "@autobe/interface";
+export interface IAutoBeRealizeAuthorizationApplication {
+    createDecorator: (next: IAutoBeRealizeAuthorizationApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeAuthorizationApplication {
+    interface IProps {
+        /**
+         * Authentication Provider function configuration containing the function
+         * name and implementation code. The Provider handles JWT token
+         * verification, role validation, and database queries to authenticate
+         * users.
+         */
+        provider: IAutoBeRealizeAuthorizationApplication.IProvider;
+        /**
+         * Authentication Decorator configuration containing the decorator name and
+         * implementation code. The Decorator integrates with NestJS parameter
+         * decorators to automatically inject authenticated user data into
+         * Controller methods.
+         */
+        decorator: IAutoBeRealizeAuthorizationApplication.IDecorator;
+        /**
+         * Authentication Payload Type configuration containing the payload type
+         * name and implementation code. The Payload Type is used to define the
+         * structure of the authenticated user data that will be injected into
+         * Controller methods when using the decorator. It serves as the TypeScript
+         * type for the parameter in Controller method signatures.
+         */
+        payload: IAutoBeRealizeAuthorizationApplication.IPayloadType;
+    }
+    interface IProvider {
+        /**
+         * The name of the authentication Provider function in {role}Authorize
+         * format (e.g., adminAuthorize, userAuthorize). This function will be
+         * called by the decorator to verify JWT tokens and return authenticated
+         * user information for the specified role.
+         *
+         * DO: Use camelCase naming convention.
+         */
+        name: string & CamelPattern;
+        /**
+         * Complete TypeScript code for the authentication Provider function. Must
+         * include: JWT token verification using jwtAuthorize function, role type
+         * checking against payload.type, database query using
+         * MyGlobal.prisma.{tableName} pattern to verify user existence, and proper
+         * error handling with ForbiddenException and UnauthorizedException. The
+         * function should return the authenticated user payload data.
+         */
+        content: string;
+    }
+    interface IDecorator {
+        /**
+         * The name of the Decorator to be generated in {Role}Auth format (e.g.,
+         * AdminAuth, UserAuth). This decorator will be used as a parameter
+         * decorator in Controller methods to automatically authenticate and
+         * authorize users for the specific role, injecting the authenticated user
+         * payload as a method parameter.
+         *
+         * DO: Use PascalCase naming convention.
+         */
+        name: string & PascalPattern;
+        /**
+         * Complete TypeScript code for the authentication Decorator implementation.
+         * Must include: SwaggerCustomizer integration to add bearer token security
+         * schema to API documentation, createParamDecorator implementation that
+         * calls the corresponding Provider function for authentication, Singleton
+         * pattern using tstl library for efficient decorator instance management,
+         * and proper TypeScript typing for the ParameterDecorator interface.
+         */
+        content: string;
+    }
+    interface IPayloadType {
+        /**
+         * The name of the Payload type to be generated in {Role}Payload format
+         * (e.g., AdminPayload, UserPayload). This type defines the structure of the
+         * authenticated user data that will be injected into Controller methods
+         * when using the decorator.
+         *
+         * DO: Use PascalCase naming convention.
+         */
+        name: string & PascalPattern;
+        /**
+         * Complete TypeScript code for the Payload type interface in {Role}Payload
+         * format (e.g., AdminPayload, UserPayload). Must include: id field with
+         * UUID format validation, type field as role discriminator, and proper
+         * typia tags for validation. This interface defines the structure of the
+         * authenticated user data that will be injected into Controller methods
+         * when using the decorator and serves as the TypeScript type for the
+         * parameter in Controller method signatures.
+         */
+        content: string;
+    }
+}

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeAuthorizationApplication.js.map

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

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeAuthorizationCorrectApplication.d.ts

@@ -0,0 +1,27 @@
+import { IAutoBeRealizeAuthorizationApplication } from "./IAutoBeRealizeAuthorizationApplication";
+export interface IAutoBeRealizeAuthorizationCorrectApplication {
+    correctDecorator: (next: IAutoBeRealizeAuthorizationCorrectApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeAuthorizationCorrectApplication {
+    interface IProps extends IAutoBeRealizeAuthorizationApplication.IProps {
+        /**
+         * Step 1: TypeScript compilation error analysis and diagnosis.
+         *
+         * AI identifies and categorizes all compilation errors (type mismatches,
+         * import issues, syntax errors) by component (providers/decorator/payload).
+         * Lists specific error messages with their locations and types for
+         * systematic troubleshooting.
+         */
+        error_analysis: string;
+        /**
+         * Step 2: Solution guidance and fix recommendations.
+         *
+         * AI provides clear, actionable instructions on how to resolve each
+         * identified error. Includes specific steps like "add property X to
+         * interface Y", "update import path from A to B", or "change type from C to
+         * D". Focus on guidance rather than generating complete code
+         * implementations.
+         */
+        solution_guidance: string;
+    }
+}

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeAuthorizationCorrectApplication.js.map

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

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeCorrectApplication.d.ts

@@ -0,0 +1,79 @@
+import { IAutoBeRealizeWriteApplication } from "./IAutoBeRealizeWriteApplication";
+export interface IAutoBeRealizeCorrectApplication {
+    review: (props: IAutoBeRealizeCorrectApplication.IProps) => void;
+}
+export declare namespace IAutoBeRealizeCorrectApplication {
+    interface IProps extends IAutoBeRealizeWriteApplication.IProps {
+        /**
+         * Compilation Error Analysis and Resolution Strategy
+         *
+         * This field contains a detailed analysis of TypeScript compilation errors
+         * that occurred during the previous compilation attempt, along with
+         * specific strategies to resolve each error.
+         *
+         * The analysis MUST include:
+         *
+         * 📊 ERROR BREAKDOWN:
+         *
+         * - List of all TypeScript error codes encountered (e.g., TS2339, TS2345)
+         * - Exact error messages and the lines/files where they occurred
+         * - Categorization of errors by type (type mismatch, missing property, etc.)
+         *
+         * 🔍 ROOT CAUSE ANALYSIS:
+         *
+         * - Why each error occurred (e.g., incorrect type assumptions, missing
+         *   fields)
+         * - Relationship between errors (e.g., cascading errors from a single issue)
+         * - Common patterns identified across multiple errors
+         *
+         * 🛠 RESOLUTION STRATEGY:
+         *
+         * - Specific fixes for each error type
+         * - Priority order for addressing errors (fix critical errors first)
+         * - Alternative approaches if the direct fix is not possible
+         *
+         * 📝 SCHEMA VERIFICATION:
+         *
+         * - Re-verification of Prisma schema fields actually available
+         * - Identification of assumed fields that don't exist
+         * - Correct field types and relationships
+         *
+         * ⚠️ COMMON ERROR PATTERNS TO CHECK:
+         *
+         * - Using non-existent fields (e.g., deleted_at, created_by)
+         * - Type mismatches in Prisma operations
+         * - Incorrect date handling (using Date instead of string)
+         * - Missing required fields in create/update operations
+         * - Incorrect relation handling in nested operations
+         *
+         * 🎯 CORRECTION APPROACH:
+         *
+         * - Remove references to non-existent fields
+         * - Fix type conversions (especially dates with toISOStringSafe())
+         * - Simplify complex nested operations into separate queries
+         * - Add missing required fields
+         * - Use correct Prisma input types
+         *
+         * Example structure:
+         *
+         *     Errors Found:
+         *     1. TS2339: Property 'deleted_at' does not exist on type 'User'
+         *        - Cause: Field assumed but not in schema
+         *        - Fix: Remove all deleted_at references
+         *
+         *     2. TS2345: Type 'Date' is not assignable to type 'string'
+         *        - Cause: Direct Date assignment without conversion
+         *        - Fix: Use toISOStringSafe() for all date values
+         *
+         *     Resolution Plan:
+         *     1. First, remove all non-existent field references
+         *     2. Then, fix all date type conversions
+         *     3. Finally, adjust Prisma query structures
+         *
+         * This analysis ensures the review process addresses all compilation errors
+         * systematically and produces error-free code in the corrected
+         * implementation.
+         */
+        errorAnalysis: string;
+    }
+}

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeCorrectApplication.js

@@ -0,0 +1,3 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=IAutoBeRealizeCorrectApplication.js.map

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeCorrectApplication.js.map

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

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.d.ts

@@ -0,0 +1,38 @@
+import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
+export declare namespace IAutoBeRealizeScenarioApplication {
+    interface IProps {
+        /** The OpenAPI operation to be realized. */
+        operation: AutoBeOpenApi.IOperation;
+        /**
+         * The name of the function to be generated.
+         *
+         * Derived from the Swagger path and method. The function name must be
+         * written in snake_case. It serves as the entry point in both code
+         * generation and test code.
+         *
+         * Once the function is generated, the function name and file name will be
+         * the same. The generated file will be located at
+         * `src/providers/${function_name}.ts`.
+         */
+        functionName: string;
+        /** For example, `src/providers/${function_name}.ts`. */
+        location: string;
+        /**
+         * List of scenario descriptions for test code generation.
+         *
+         * Each scenario describes the expected behavior of the function under
+         * certain conditions. Used as a basis for TDD-style automated test
+         * generation.
+         */
+        testScenarios: string[];
+        /**
+         * Optional decorator event for customizing code generation behavior.
+         *
+         * Provides additional metadata or instructions that can modify how the
+         * function implementation is generated. Can include custom annotations,
+         * middleware configurations, or special handling directives that affect the
+         * final code output.
+         */
+        decoratorEvent?: AutoBeRealizeAuthorization;
+    }
+}

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.js

@@ -0,0 +1,3 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=IAutoBeRealizeScenarioApplication.js.map

package/lib/agent/src/orchestrate/realize/structures/IAutoBeRealizeScenarioApplication.js.map

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