@autobe/agent 0.22.1 → 0.23.0

package/lib/agent/src/utils/backoffRetry.d.ts

@@ -1,22 +0,0 @@
-export interface RetryOptions {
-    /** Maximum number of retry attempts (default: 5) */
-    maxRetries: number;
-    /** Base delay in milliseconds (default: 2000) */
-    baseDelay: number;
-    /** Maximum delay in milliseconds (default: 60_000) */
-    maxDelay: number;
-    /** Jitter factor for randomization (0-1, default: 0.3) */
-    jitter: number;
-    /** Function to determine if error should trigger retry (default: isRetryError) */
-    handleError: (error: any) => boolean;
-}
-/**
- * @param fn Function to Apply the retry logic.
- * @param maxRetries How many time to try. Max Retry is 5.
- * @returns
- */
-export declare function randomBackoffRetry<T>(fn: () => Promise<T>, options?: Partial<RetryOptions>): Promise<T>;
-export declare function randomBackoffStrategy(props: {
-    count: number;
-    error: unknown;
-}): number;

package/lib/agent/src/utils/backoffRetry.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"backoffRetry.js","sourceRoot":"","sources":["../../../../src/utils/backoffRetry.ts"],"names":[],"mappings":";;;;;;;;;;;AAqBA,gDAgCC;AAED,sDAoBC;AA3DD;;;;GAIG;AACH,SAAsB,kBAAkB;yDACtC,EAAoB,EACpB,UAAiC,EAAE;QAEnC,MAAM,EACJ,UAAU,GAAG,CAAC,EACd,SAAS,GAAG,IAAK,EACjB,QAAQ,GAAG,KAAM,EACjB,MAAM,GAAG,GAAG,EACZ,WAAW,GAAG,YAAY,GAC3B,GAAG,OAAO,CAAC;QAEZ,IAAI,SAAkB,CAAC;QAEvB,KAAK,IAAI,OAAO,GAAG,CAAC,EAAE,OAAO,GAAG,UAAU,EAAE,OAAO,EAAE,EAAE,CAAC;YACtD,IAAI,CAAC;gBACH,OAAO,MAAM,EAAE,EAAE,CAAC;YACpB,CAAC;YAAC,OAAO,GAAG,EAAE,CAAC;gBACb,SAAS,GAAG,GAAG,CAAC;gBAEhB,IAAI,OAAO,KAAK,UAAU,GAAG,CAAC;oBAAE,MAAM,GAAG,CAAC;gBAE1C,IAAI,CAAC,WAAW,CAAC,GAAG,CAAC;oBAAE,MAAM,GAAG,CAAC;gBAEjC,MAAM,SAAS,GAAG,IAAI,CAAC,GAAG,CAAC,SAAS,GAAG,CAAC,IAAI,OAAO,EAAE,QAAQ,CAAC,CAAC;gBAC/D,MAAM,KAAK,GAAG,SAAS,GAAG,CAAC,CAAC,GAAG,IAAI,CAAC,MAAM,EAAE,GAAG,MAAM,CAAC,CAAC;gBAEvD,MAAM,IAAI,OAAO,CAAC,CAAC,GAAG,EAAE,EAAE,CAAC,UAAU,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC,CAAC;YACrD,CAAC;QACH,CAAC;QAED,MAAM,SAAS,CAAC;IAClB,CAAC;CAAA;AAED,SAAgB,qBAAqB,CAAC,KAGrC;IACC,MAAM,EAAE,KAAK,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IAC/B,IAAI,KAAK,GAAG,CAAC,EAAE,CAAC;QACd,MAAM,KAAK,CAAC;IACd,CAAC;IAED,IAAI,YAAY,CAAC,KAAK,CAAC,KAAK,KAAK,EAAE,CAAC;QAClC,MAAM,KAAK,CAAC;IACd,CAAC;IAED,MAAM,SAAS,GAAG,IAAK,CAAC;IACxB,MAAM,QAAQ,GAAG,KAAM,CAAC;IACxB,MAAM,MAAM,GAAG,GAAG,CAAC;IACnB,MAAM,SAAS,GAAG,IAAI,CAAC,GAAG,CAAC,SAAS,GAAG,CAAC,IAAI,KAAK,EAAE,QAAQ,CAAC,CAAC;IAC7D,MAAM,KAAK,GAAG,SAAS,GAAG,CAAC,CAAC,GAAG,IAAI,CAAC,MAAM,EAAE,GAAG,MAAM,CAAC,CAAC;IAEvD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,SAAS,YAAY,CAAC,KAAU;;IAC9B,+BAA+B;IAC/B,IACE,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,IAAI,MAAK,oBAAoB;QACpC,CAAA,MAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,KAAK,0CAAE,IAAI,MAAK,oBAAoB,EAC3C,CAAC;QACD,OAAO,KAAK,CAAC;IACf,CAAC;IAED,gCAAgC;IAChC,IACE,CAAC,OAAO,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,MAAM,CAAA,KAAK,QAAQ,IAAI,KAAK,CAAC,MAAM,IAAI,GAAG,CAAC;QAC1D,CAAA,MAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,KAAK,0CAAE,IAAI,MAAK,cAAc,EACrC,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IAED,cAAc;IACd,IAAI,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,MAAM,MAAK,GAAG,EAAE,CAAC;QAC1B,OAAO,IAAI,CAAC;IACd,CAAC;IAED,8BAA8B;IAC9B,MAAM,IAAI,GAAG,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,IAAI,MAAI,MAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,KAAK,0CAAE,IAAI,CAAA,CAAC;IAC/C,IACE;QACE,gBAAgB;QAChB,yBAAyB;QACzB,WAAW;QACX,YAAY;QACZ,OAAO;KACR,CAAC,QAAQ,CAAC,IAAI,CAAC,EAChB,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IAED,iBAAiB;IACjB,IAAI,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,OAAO,MAAK,YAAY,IAAI,CAAA,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,IAAI,MAAK,YAAY,EAAE,CAAC;QACpE,OAAO,IAAI,CAAC;IACd,CAAC;IAED,IACE,MAAC,KAAK,aAAL,KAAK,uBAAL,KAAK,CAAE,OAAkB,0CAAE,UAAU,CACpC,2EAA2E,CAC5E,EACD,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IAED,OAAO,KAAK,CAAC;AACf,CAAC"}

package/lib/agent/src/utils/divideArray.d.ts

@@ -1,4 +0,0 @@
-export declare function divideArray<T>(props: {
-    array: T[];
-    capacity: number;
-}): T[][];

package/lib/agent/src/utils/divideArray.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"divideArray.js","sourceRoot":"","sources":["../../../../src/utils/divideArray.ts"],"names":[],"mappings":";;AAAA,kCAeC;AAfD,SAAgB,WAAW,CAAI,KAAuC;IACpE,IAAI,KAAK,CAAC,QAAQ,IAAI,CAAC,EAAE,CAAC;QACxB,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC;IACzD,CAAC;IACD,IAAI,MAAM,CAAC,KAAK,CAAC,KAAK,CAAC,QAAQ,CAAC,EAAE,CAAC;QACjC,MAAM,IAAI,SAAS,CAAC,qCAAqC,CAAC,CAAC;IAC7D,CAAC;IACD,IAAI,KAAK,CAAC,QAAQ,KAAK,QAAQ,EAAE,CAAC;QAChC,MAAM,IAAI,KAAK,CAAC,qCAAqC,CAAC,CAAC;IACzD,CAAC;IAED,MAAM,IAAI,GAAW,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,GAAG,KAAK,CAAC,QAAQ,CAAC,CAAC;IACpE,MAAM,QAAQ,GAAW,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,KAAK,CAAC,MAAM,GAAG,IAAI,CAAC,CAAC;IAC9D,MAAM,OAAO,GAAQ,KAAK,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC;IACzC,OAAO,KAAK,CAAC,IAAI,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE,GAAG,EAAE,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC,EAAE,QAAQ,CAAC,CAAC,CAAC;AACzE,CAAC"}

package/lib/agent/src/utils/emplaceMap.d.ts

@@ -1 +0,0 @@
-export declare function emplaceMap<Key, T>(dict: Map<Key, T>, key: Key, generator: () => T): T;

package/lib/agent/src/utils/emplaceMap.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"emplaceMap.js","sourceRoot":"","sources":["../../../../src/utils/emplaceMap.ts"],"names":[],"mappings":";;AAAA,gCAaC;AAbD,SAAgB,UAAU,CACxB,IAAiB,EACjB,GAAQ,EACR,SAAkB;IAElB,MAAM,MAAM,GAAkB,IAAI,CAAC,GAAG,CAAC,GAAG,CAAC,CAAC;IAC5C,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;QACzB,OAAO,MAAM,CAAC;IAChB,CAAC;IAED,MAAM,KAAK,GAAM,SAAS,EAAE,CAAC;IAC7B,IAAI,CAAC,GAAG,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC;IACrB,OAAO,KAAK,CAAC;AACf,CAAC"}

package/lib/agent/src/utils/executeCachedBatch.d.ts

@@ -1 +0,0 @@
-export declare const executeCachedBatch: <T>(tasks: Array<(user: string) => Promise<T>>, promptCacheKey?: string) => Promise<T[]>;

package/lib/agent/src/utils/executeCachedBatch.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"executeCachedBatch.js","sourceRoot":"","sources":["../../../../src/utils/executeCachedBatch.ts"],"names":[],"mappings":";;;;;;;;;;;;AAAA,+BAA0B;AAEnB,MAAM,kBAAkB,GAAG,CAChC,KAA0C,EAC1C,cAAuB,EACT,EAAE;IAChB,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IAElC,cAAc,aAAd,cAAc,cAAd,cAAc,IAAd,cAAc,GAAK,IAAA,SAAE,GAAE,EAAC;IACxB,MAAM,KAAK,GAAM,MAAM,KAAK,CAAC,CAAC,CAAE,CAAC,cAAc,CAAC,CAAC;IACjD,MAAM,IAAI,GAAQ,MAAM,OAAO,CAAC,GAAG,CACjC,KAAK,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CACnD,CAAC;IACF,OAAO,CAAC,KAAK,EAAE,GAAG,IAAI,CAAC,CAAC;AAC1B,CAAC,CAAA,CAAC;AAZW,QAAA,kBAAkB,sBAY7B"}

package/lib/agent/src/utils/predicateStateMessage.d.ts

@@ -1,4 +0,0 @@
-import { AutoBeState } from "../context/AutoBeState";
-type StepName = "analyze" | "prisma" | "interface" | "test" | "realize";
-export declare const predicateStateMessage: (state: AutoBeState, future: StepName) => string | null;
-export {};

package/lib/agent/src/utils/predicateStateMessage.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"predicateStateMessage.js","sourceRoot":"","sources":["../../../../src/utils/predicateStateMessage.ts"],"names":[],"mappings":";;;AAAA,yCAA2C;AAMpC,MAAM,qBAAqB,GAAG,CACnC,KAAkB,EAClB,MAAgB,EACD,EAAE;IACjB,IAAI,MAAM,KAAK,SAAS;QAAE,OAAO,IAAI,CAAC;IACtC,IAAI,MAAM,KAAK,QAAQ;QAAE,OAAO,eAAe,CAAC,KAAK,CAAC,CAAC;IAEvD,MAAM,WAAW,GAAW,UAAU,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;IACvD,KAAK,MAAM,GAAG,IAAI,UAAU,CAAC,KAAK,CAAC,CAAC,EAAE,WAAW,CAAC;QAChD,IAAI,KAAK,CAAC,GAAG,CAAC,KAAK,IAAI;YAAE,OAAO,wBAAwB,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC;IAExE,MAAM,YAAY,GAAa,UAAU,CAAC,WAAW,GAAG,CAAC,CAAC,CAAC;IAC3D,IAAI,KAAK,CAAC,OAAQ,CAAC,IAAI,KAAK,KAAK,CAAC,YAAY,CAAE,CAAC,IAAI;QACnD,OAAO,oBAAoB,CAAC,YAAY,EAAE,SAAS,EAAE,KAAK,CAAC,CAAC;IAC9D,OAAO,IAAI,CAAC;AACd,CAAC,CAAC;AAfW,QAAA,qBAAqB,yBAehC;AAEF,MAAM,wBAAwB,GAAG,CAC/B,OAAiB,EACjB,OAAiB,EACT,EAAE;IACV,MAAM,YAAY,GAAW,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;IACzD,MAAM,YAAY,GAAW,UAAU,CAAC,OAAO,CAAC,OAAO,CAAC,CAAC;IACzD,MAAM,cAAc,GAAW,UAAU,CAAC,KAAK,CAC7C,YAAY,EACZ,YAAY,GAAG,CAAC,CACjB;SACE,GAAG,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,GAAG,KAAK,GAAG,CAAC,KAAK,iBAAiB,CAAC,IAAI,CAAC,EAAE,CAAC;SAChE,IAAI,CAAC,QAAQ,CAAC,CAAC;IAElB,MAAM,aAAa,GAAG,YAAY,CAAC,OAAO,CAAC,CAAC;IAE5C,OAAO,kBAAU,CAAC,IAAI,CAAA;MAClB,iBAAiB,CAAC,OAAO,CAAC;;SAEvB,aAAa;;MAEhB,cAAc;;sBAEE,YAAY,GAAG,CAAC;GACnC,CAAC;AACJ,CAAC,CAAC;AAEF,MAAM,oBAAoB,GAAG,CAC3B,YAAsB,EACtB,WAAqB,EACrB,KAAkB,EACV,EAAE;;IACV,MAAM,eAAe,GAAG,MAAA,KAAK,CAAC,YAAY,CAAC,0CAAE,IAAI,CAAC;IAClD,MAAM,cAAc,GAAG,MAAA,KAAK,CAAC,WAAW,CAAC,0CAAE,IAAI,CAAC;IAEhD,OAAO,kBAAU,CAAC,IAAI,CAAA;MAClB,UAAU,CAAC,YAAY,CAAC,sBAAsB,eAAe;;mCAEhC,cAAc;;oBAE7B,YAAY;GAC7B,CAAC;AACJ,CAAC,CAAC;AAEF,MAAM,eAAe,GAAG,CAAC,KAAkB,EAAiB,EAAE;IAC5D,IAAI,KAAK,CAAC,OAAO,KAAK,IAAI;QAAE,OAAO,IAAI,CAAC;IACxC,OAAO,kBAAU,CAAC,IAAI,CAAA;;;;;GAKrB,CAAC;AACJ,CAAC,CAAC;AAEF,MAAM,iBAAiB,GAA6B;IAClD,OAAO,EAAE,uBAAuB;IAChC,MAAM,EAAE,iBAAiB;IACzB,SAAS,EAAE,sBAAsB;IACjC,IAAI,EAAE,mBAAmB;IACzB,OAAO,EAAE,gBAAgB;CAC1B,CAAC;AAEF,MAAM,UAAU,GAA6B;IAC3C,OAAO,EAAE,uBAAuB;IAChC,MAAM,EAAE,iBAAiB;IACzB,SAAS,EAAE,eAAe;IAC1B,IAAI,EAAE,gBAAgB;IACtB,OAAO,EAAE,gBAAgB;CAC1B,CAAC;AAEF,MAAM,YAAY,GAA6B;IAC7C,OAAO,EAAE,sBAAsB;IAC/B,MAAM,EAAE,iBAAiB;IACzB,SAAS,EAAE,sBAAsB;IACjC,IAAI,EAAE,cAAc;IACpB,OAAO,EAAE,uBAAuB;CACjC,CAAC;AAEF,MAAM,UAAU,GAAe;IAC7B,SAAS;IACT,QAAQ;IACR,WAAW;IACX,MAAM;IACN,SAAS;CACV,CAAC"}

package/lib/interface/src/histories/contents/AutoBeAnalyzeFile.d.ts

@@ -1,153 +0,0 @@
-/**
- * Interface representing a planning document file structure used by the Analyze
- * Agent in the AutoBE system.
- *
- * This interface defines the complete metadata and content structure for
- * documentation generated during the requirements analysis phase. The Analyze
- * Agent uses this structure to create comprehensive planning documents that
- * serve as blueprints for backend developers implementing the system.
- *
- * The documents created using this interface follow a waterfall model approach,
- * where each document builds upon previous ones to form a complete
- * specification before any code is written. These documents are designed to
- * remove all ambiguity and provide developers with actionable, specific
- * requirements.
- *
- * Key characteristics:
- *
- * - Single-pass document creation (no iterations or revisions)
- * - Production-ready specifications on first write
- * - Backend-focused content (no frontend UI/UX requirements)
- * - Minimum 2,000 characters for standard docs, 5,000-30,000+ for technical
- * - Uses EARS (Easy Approach to Requirements Syntax) format
- * - Includes comprehensive API specifications (40-50+ endpoints for complex
- *   systems)
- * - Complete database schemas and business logic
- *
- * @author Kakasoo
- * @since 0.1.0
- * @see IAutoBeAnalyzeWriteApplication - The application interface that uses this structure
- * @see AutoBeAnalyzeScenarioEvent - Event structure for multi-document scenarios
- * @see AutoBeAnalyzeRole - User role definitions used in authentication planning
- */
-export interface AutoBeAnalyzeFile extends AutoBeAnalyzeFile.Scenario {
-    /**
-     * Markdown file content. Only write the content of the file. Do not include
-     * any questions. This should contain only the contents of the file. Do not
-     * write down any questions or appreciation. For example, remove a sentence
-     * such as "Is it okay if we proceed with the table of contents? Please let me
-     * know if there is anything to add or exclude from the table of contents!"
-     *
-     * PROHIBITED content in markdown:
-     *
-     * - Questions to the reader (e.g., "Is there anything else to refine?")
-     * - Feedback requests (e.g., "Please review and let me know")
-     * - Interactive elements expecting responses
-     * - Meta-commentary about the document writing process
-     *
-     * The markdown must be a complete, standalone deliverable without any
-     * conversational elements. If clarification is needed, it should be requested
-     * outside the document content.
-     */
-    content: string;
-}
-export declare namespace AutoBeAnalyzeFile {
-    interface Scenario {
-        /**
-         * Describe briefly why you made this document, and if you have any plans
-         * for the next one. This helps maintain context between documents and
-         * ensures a logical flow in documentation creation. Example: "To define the
-         * core features and user needs for the e-commerce platform before moving on
-         * to detailed user flow documentation."
-         */
-        reason: string;
-        /**
-         * Filename to generate or overwrite. Should be descriptive and follow a
-         * consistent naming convention. Examples: "01-service-overview.md",
-         * "02-user-requirements.md", "03-business-model.md"
-         */
-        filename: `${string}.md`;
-        /**
-         * Document type that determines the structure and content guidelines. This
-         * helps the AI understand what kind of document to create and what sections
-         * or information should be included. Examples:
-         *
-         * - "requirement": Functional/non-functional requirements, acceptance
-         *   criteria
-         * - "user-story": User personas, scenarios, and journey descriptions
-         * - "user-flow": Step-by-step user interactions and decision points
-         * - "business-model": Revenue streams, cost structure, value propositions
-         * - "service-overview": High-level service description, goals, and scope
-         */
-        documentType?: string;
-        /**
-         * Outline or table of contents that guides the document structure. Each
-         * item represents a main section to be covered in the document. The AI will
-         * expand each section with appropriate content while maintaining the
-         * specified structure. Example: ["Executive Summary", "Problem Statement",
-         * "Target Users", "Core Features", "Success Metrics", "Implementation
-         * Timeline"]
-         */
-        outline?: string[];
-        /**
-         * Target audience for this document. Determines the language, technical
-         * depth, and focus areas of the content. If not specified, the document
-         * will be written for a general audience with balanced technical and
-         * business perspectives. Examples:
-         *
-         * - "development team": More technical details, implementation considerations
-         * - "business stakeholders": Focus on ROI, business value, market opportunity
-         * - "end users": User-friendly language, benefits, and use cases
-         * - "product managers": Balance of user needs, business goals, and
-         *   feasibility
-         * - "general": Accessible to all stakeholders (default if not specified)
-         */
-        audience?: string;
-        /**
-         * Key questions or concerns this document should address. Helps ensure the
-         * document covers all important aspects and doesn't miss critical
-         * information. The AI will make sure to answer these questions within the
-         * document content. Examples:
-         *
-         * - "What problem does this service solve?"
-         * - "Who are the primary and secondary users?"
-         * - "What are the main competitive advantages?"
-         * - "How will we measure success?"
-         * - "What are the potential risks and mitigation strategies?"
-         */
-        keyQuestions?: string[];
-        /**
-         * Level of detail expected in the document. Guides how deeply the AI should
-         * explore each topic and how much information to include. Examples:
-         *
-         * - "high-level overview": Brief, conceptual, focusing on the big picture
-         * - "detailed specification": Comprehensive, with specific examples and edge
-         *   cases
-         * - "executive summary": Concise, focusing on key points and decisions
-         * - "moderate detail": Balanced approach with essential details (default)
-         */
-        detailLevel?: string;
-        /**
-         * Related documents that this document references or builds upon. Helps
-         * maintain consistency across documentation and allows the AI to understand
-         * the broader context. These documents should already exist or be planned
-         * in the documentation roadmap. Examples: ["00-project-charter.md",
-         * "01-market-analysis.md", "02-competitor-research.md"]
-         */
-        relatedDocuments?: string[];
-        /**
-         * Specific constraints or requirements for the document. These are
-         * must-have elements or considerations that should be included regardless
-         * of other factors. The AI will ensure these constraints are met.
-         * Examples:
-         *
-         * - "Must include cost-benefit analysis"
-         * - "Focus on mobile-first user experience"
-         * - "Include measurable KPIs and success metrics"
-         * - "Address data privacy and security concerns"
-         * - "Consider scalability for 1M+ users"
-         * - "Include timeline and milestone recommendations"
-         */
-        constraints?: string[];
-    }
-}

package/lib/interface/src/histories/contents/AutoBeAnalyzeFile.js

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

package/lib/interface/src/histories/contents/AutoBeAnalyzeFile.js.map

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

package/lib/orchestrate/realize/orchestrateRealizeScenario.d.ts

@@ -1,25 +0,0 @@
-import { AutoBeOpenApi, AutoBeRealizeAuthorization } from "@autobe/interface";
-import { ILlmSchema } from "@samchon/openapi";
-import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeRealizeScenarioResult } from "./structures/IAutoBeRealizeScenarioResult";
-/**
- * Generates a planning result that defines what kind of function should be
- * created, based solely on the provided Swagger (OpenAPI) operation — without
- * using an LLM.
- *
- * This function analyzes the structure of the OpenAPI operation (such as the
- * path, method, parameters, request/response schema, and descriptions) to
- * determine the appropriate function name, input/output types, and purpose of
- * the function.
- *
- * The result of this function (`RealizePlannerOutput`) will be passed to the
- * next step in the AutoBE pipeline, which is responsible for generating the
- * actual implementation code.
- *
- * @author Kakasoo
- * @param ctx - AutoBE context including model and configuration
- * @param operation - A single OpenAPI operation object to analyze and plan
- * @returns A planning object containing all structural information needed to
- *   generate the function
- */
-export declare const orchestrateRealizeScenario: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, operation: AutoBeOpenApi.IOperation, authorization?: AutoBeRealizeAuthorization) => IAutoBeRealizeScenarioResult;

package/src/orchestrate/realize/orchestrateRealizeScenario.ts

@@ -1,57 +0,0 @@
-import {
-  AutoBeOpenApi,
-  AutoBeRealizeAuthorization,
-  AutoBeTestFile,
-} from "@autobe/interface";
-import { ILlmSchema } from "@samchon/openapi";
-
-import { AutoBeContext } from "../../context/AutoBeContext";
-import { IAutoBeRealizeScenarioResult } from "./structures/IAutoBeRealizeScenarioResult";
-
-/**
- * Generates a planning result that defines what kind of function should be
- * created, based solely on the provided Swagger (OpenAPI) operation — without
- * using an LLM.
- *
- * This function analyzes the structure of the OpenAPI operation (such as the
- * path, method, parameters, request/response schema, and descriptions) to
- * determine the appropriate function name, input/output types, and purpose of
- * the function.
- *
- * The result of this function (`RealizePlannerOutput`) will be passed to the
- * next step in the AutoBE pipeline, which is responsible for generating the
- * actual implementation code.
- *
- * @author Kakasoo
- * @param ctx - AutoBE context including model and configuration
- * @param operation - A single OpenAPI operation object to analyze and plan
- * @returns A planning object containing all structural information needed to
- *   generate the function
- */
-export const orchestrateRealizeScenario = <Model extends ILlmSchema.Model>(
-  ctx: AutoBeContext<Model>,
-  operation: AutoBeOpenApi.IOperation,
-  authorization?: AutoBeRealizeAuthorization,
-): IAutoBeRealizeScenarioResult => {
-  const testFiles: AutoBeTestFile[] =
-    ctx
-      .state()
-      .test?.files.filter(
-        (el) =>
-          el.scenario.endpoint.method === operation.method &&
-          el.scenario.endpoint.path === operation.path,
-      ) ?? [];
-
-  const functionName = `${operation.method}_${operation.path
-    .replaceAll("/", "_")
-    .replaceAll("-", "_")
-    .replaceAll("{", "$")
-    .replaceAll("}", "")}`;
-  return {
-    operation: operation,
-    functionName: functionName,
-    location: `src/providers/${functionName}.ts`,
-    testFiles: testFiles,
-    decoratorEvent: authorization,
-  };
-};