@autobe/agent 0.22.0 → 0.23.0

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaComponentApplication.d.ts

@@ -1,121 +0,0 @@
-import { AutoBePrisma } from "@autobe/interface";
-import { tags } from "typia";
-export interface IAutoBePrismaComponentApplication {
-    /**
-     * Organizes database tables into domain-based components for Prisma schema
-     * generation.
-     *
-     * Takes business requirements and groups related tables into logical domains,
-     * with each component becoming a separate .prisma file.
-     */
-    extractComponents(props: IAutoBePrismaComponentApplication.IProps): void;
-}
-export declare namespace IAutoBePrismaComponentApplication {
-    interface IProps {
-        /**
-         * Initial thoughts on namespace classification criteria.
-         *
-         * Contains the AI agent's initial analysis and reasoning about how to
-         * organize tables into different business domains/namespaces.
-         *
-         * **Example:**
-         *
-         *     "Based on the business requirements, I identify several key domains:
-         *     - User-related entities should be grouped under 'Actors' namespace
-         *     - Product and sales information under 'Sales' namespace
-         *     - System configuration under 'Systematic' namespace"
-         */
-        thinking: string;
-        /**
-         * Review and refinement of the namespace classification.
-         *
-         * Contains the AI agent's review process, considering relationships between
-         * tables and potential improvements to the initial classification.
-         *
-         * **Example:**
-         *
-         *     "Upon review, I noticed that 'shopping_channel_categories' has strong
-         *     relationships with both channels and sales. However, since it primarily
-         *     defines the channel structure, it should remain in 'Systematic' namespace."
-         */
-        review: string;
-        /**
-         * Final decision on namespace classification.
-         *
-         * Contains the AI agent's final reasoning and rationale for the chosen
-         * namespace organization, explaining why this structure best serves the
-         * business requirements.
-         *
-         * **Example:**
-         *
-         *     "Final decision: Organize tables into 3 main namespaces:
-         *     1. Systematic - for channel and system configuration
-         *     2. Actors - for all user types (customers, citizens, administrators)
-         *     3. Sales - for product sales and related transactional data
-         *     This structure provides clear separation of concerns and follows DDD principles."
-         */
-        decision: string;
-        /**
-         * Array of domain components that group related database tables.
-         *
-         * Each component represents a business domain and becomes one Prisma schema
-         * file. Common domains include: Actors (users), Sales (products), Orders,
-         * Carts, etc.
-         *
-         * **Example:**
-         *
-         * ```typescript
-         * {
-         *   "components": [
-         *     {
-         *       "filename": "schema-02-systematic.prisma",
-         *       "namespace": "Systematic",
-         *       "thinking": "These tables all relate to system configuration and channel management. They form the foundation of the platform.",
-         *       "review": "Considering the relationships, shopping_channel_categories connects channels and sales, but it fundamentally defines channel structure.",
-         *       "rationale": "Grouping all system configuration tables together provides a clear foundation layer that other domains can reference.",
-         *       "tables": [
-         *         "shopping_channels",
-         *         "shopping_sections",
-         *         "shopping_channel_categories"
-         *       ]
-         *     },
-         *     {
-         *       "filename": "schema-03-actors.prisma",
-         *       "namespace": "Actors",
-         *       "thinking": "All user-related entities should be grouped together as they share authentication and identity patterns.",
-         *       "review": "While customers interact with sales, the customer entity itself is about identity, not transactions.",
-         *       "rationale": "This component groups all actor-related tables to maintain separation between identity management and business transactions.",
-         *       "tables": [
-         *         "shopping_customers",
-         *         "shopping_citizens",
-         *         "shopping_administrators"
-         *       ]
-         *     },
-         *     {
-         *       "filename": "schema-04-sales.prisma",
-         *       "namespace": "Sales",
-         *       "thinking": "Product catalog and sales-related tables belong together as they form the core commerce functionality.",
-         *       "review": "Sales snapshots are integral to the sales domain for tracking product history and price changes.",
-         *       "rationale": "Consolidating all sales-related tables enables coherent management of the entire product lifecycle.",
-         *       "tables": [
-         *         "shopping_sales",
-         *         "shopping_sale_snapshots",
-         *         "shopping_sale_units",
-         *         "shopping_sale_unit_options"
-         *       ]
-         *     }
-         *   ]
-         * }
-         * ```
-         *
-         * **Notes:**
-         *
-         * - Table names must follow snake_case convention with domain prefix (e.g.,
-         *   `shopping_customers`)
-         * - Each component becomes one `.prisma` file containing related models
-         * - Filename numbering indicates dependency order for schema generation
-         * - Namespace is used for documentation organization and domain grouping
-         */
-        components: AutoBePrisma.IComponent[] & tags.MinItems<1>;
-    }
-}

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaComponentApplication.js.map

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

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaCorrectApplication.d.ts

@@ -1,142 +0,0 @@
-import { AutoBePrisma } from "@autobe/interface";
-export interface IAutoBePrismaCorrectApplication {
-    /**
-     * Fixes validation errors in specific AutoBePrisma models while preserving
-     * ALL existing business logic and model descriptions.
-     *
-     * ## Core Rules
-     *
-     * 1. Fix ONLY validation errors in provided models - never remove business
-     *    descriptions
-     * 2. Apply minimal changes to error models only - preserve original design
-     *    intent
-     * 3. Return ONLY corrected models - unchanged models remain in original schema
-     * 4. Maintain referential integrity with unchanged models
-     *
-     * ## Targeted Scope
-     *
-     * - Process ONLY models with validation errors from IError[] array
-     * - Exclude models without errors from processing and output
-     * - Minimize context usage by returning corrected models only
-     * - Preserve unchanged models in their original state
-     *
-     * ## Fix Strategy
-     *
-     * - Resolve validation errors within specific models only
-     * - Fix field duplications, invalid references, and type mismatches
-     * - Update cross-model references without modifying target models
-     * - Ensure naming conventions and index rules compliance in corrected models
-     */
-    correctPrismaSchemaFiles(props: IAutoBePrismaCorrectApplication.IProps): void;
-}
-export declare namespace IAutoBePrismaCorrectApplication {
-    interface IProps {
-        /**
-         * Detailed execution plan for fixing `AutoBePrisma` validation errors in
-         * specific models.
-         *
-         * 🎯 Purpose: Enable systematic reasoning and step-by-step error resolution
-         * approach for targeted model validation issues
-         *
-         * 📋 Required Planning Content:
-         *
-         * 1. **Error Scope Analysis**
-         *
-         *    - List all validation errors from IAutoBePrismaValidation.IError[] array
-         *    - Extract unique table names from errors to identify affected models
-         *    - Categorize errors by type (field duplications, references, types,
-         *         indexes)
-         *    - Identify which models need correction vs. which remain unchanged
-         * 2. **Targeted Fix Strategy**
-         *
-         *    - Focus ONLY on models mentioned in validation errors
-         *    - Outline minimal changes needed for each affected model
-         *    - Plan cross-model reference updates (if any) without modifying non-error
-         *         models
-         *    - Ensure unchanged models maintain valid references to corrected models
-         * 3. **Model-Specific Fix Plan**
-         *
-         *    - Model-by-model modification plan for ONLY affected models
-         *    - Exact field additions, renames, or type corrections required
-         *    - Reference updates within corrected models only
-         *    - Index corrections limited to affected models
-         * 4. **Minimal Scope Validation**
-         *
-         *    - Confirm which models will be included in output (error models only)
-         *    - List models that will remain unchanged in original schema
-         *    - Identify cross-model dependencies without including unchanged models
-         *    - Preserve all business logic within corrected models
-         * 5. **Targeted Impact Assessment**
-         *
-         *    - Potential effects of fixes on unchanged models (reference validation)
-         *    - Verification points for corrected models only
-         *    - Ensure no new validation errors in targeted models
-         *    - Confirm minimal output scope compliance
-         *
-         * 💡 Example Planning Structure:
-         *
-         *     ## Error Scope
-         *     - Target Models: shopping_customers, shopping_orders (2 models only)
-         *     - Unchanged Models: All others remain in original schema
-         *
-         *     ## Targeted Fixes
-         *     - shopping_customers: Remove duplicate 'email' field
-         *     - shopping_orders: Update targetModel reference to 'shopping_customers'
-         *
-         *     ## Output Scope
-         *     - Return: Only shopping_customers and shopping_orders models
-         *     - Preserve: All other models unchanged in original schema
-         *
-         *     ## Cross-Model Impact
-         *     - Verify: shopping_orders still references shopping_customers correctly
-         *     - No changes needed in other models referencing these
-         */
-        planning: string;
-        /**
-         * ONLY the specific models that contain validation errors and need
-         * correction.
-         *
-         * 📥 Input Structure:
-         *
-         * - Contains ONLY models mentioned in IAutoBePrismaValidation.IError[] array
-         * - Each model has specific validation errors that need targeted correction
-         * - Models not mentioned in errors are excluded from this input
-         * - Represents minimal scope for error correction
-         *
-         * 🔍 Expected Validation Issues (Model-Specific):
-         *
-         * - Duplicate field/relation names within these specific models
-         * - Invalid foreign key references from these models to other models
-         * - Single foreign key fields in index arrays within these models
-         * - Invalid naming conventions within these specific models
-         * - Type validation errors in fields of these models
-         *
-         * 📝 Model Content Analysis (Targeted Scope):
-         *
-         * - Complete field definitions for each error model only
-         * - Relationships from these models (may reference unchanged models)
-         * - Indexes within these models that need correction
-         * - Business descriptions specific to these models
-         * - Cross-model references that need validation (read-only for targets)
-         *
-         * ⚠️ Processing Notes (Focused Approach):
-         *
-         * - Input contains ONLY models with validation errors
-         * - May reference other models not included in this input
-         * - Cross-model references must be validated but target models won't be
-         *   modified
-         * - Output should return corrected versions of ONLY these input models
-         * - All business logic and descriptions within these models must be preserved
-         * - Corrections must not break references from unchanged models
-         *
-         * 🎯 Correction Scope:
-         *
-         * - Fix validation errors within these specific models
-         * - Update internal model structure (fields, relations, indexes)
-         * - Correct references to external models (without modifying targets)
-         * - Maintain compatibility with unchanged models in the full schema
-         * - Return corrected versions of ONLY these models
-         */
-        models: AutoBePrisma.IModel[];
-    }
-}

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaCorrectApplication.js.map

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

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaReviewApplication.d.ts

@@ -1,105 +0,0 @@
-import { AutoBePrisma } from "@autobe/interface";
-export interface IAutoBePrismaReviewApplication {
-    /**
-     * Reviews and validates Prisma schema modifications to ensure compliance with
-     * database design best practices and business requirements.
-     *
-     * Performs comprehensive validation of proposed schema changes including
-     * normalization compliance, relationship integrity, performance optimization,
-     * and business logic alignment. The review process ensures all modifications
-     * maintain data consistency and follow enterprise-level database standards.
-     */
-    reviewSchemaFile(props: IAutoBePrismaReviewApplication.IProps): void;
-}
-export declare namespace IAutoBePrismaReviewApplication {
-    interface IProps {
-        /**
-         * Comprehensive review analysis of the proposed schema modifications.
-         *
-         * Contains the AI agent's detailed evaluation of the schema changes,
-         * including validation of normalization compliance, relationship integrity,
-         * index optimization, and business requirement alignment. The review
-         * identifies potential issues and confirms adherence to best practices.
-         *
-         * **Review Dimensions:**
-         *
-         * - **Normalization Validation**: Confirms 3NF compliance and proper data
-         *   structure
-         * - **Relationship Integrity**: Validates foreign key references and
-         *   cardinality
-         * - **Performance Optimization**: Reviews indexing strategy and query
-         *   patterns
-         * - **Business Logic Alignment**: Ensures schema supports all use cases
-         * - **Naming Conventions**: Verifies consistent naming patterns
-         * - **Data Type Consistency**: Confirms appropriate field types
-         * - **Temporal Field Handling**: Validates audit trail implementation
-         *
-         * **Example:**
-         *
-         *     "After reviewing the schema modifications:
-         *     1. All tables properly implement UUID primary keys
-         *     2. Foreign key relationships correctly reference existing models
-         *     3. Composite indexes optimize for common query patterns
-         *     4. Snapshot tables include proper temporal fields
-         *     5. Materialized views (mv_) contain appropriate denormalization
-         *     The schema follows all best practices and is ready for implementation."
-         */
-        review: string;
-        /**
-         * Strategic database design plan that guided the schema creation.
-         *
-         * Contains the original planning document that outlines the database
-         * architecture strategy, including table structures, relationships,
-         * normalization approach, and business requirement mapping. This plan
-         * serves as the blueprint for validating the implemented schema.
-         *
-         * **Planning Components:**
-         *
-         * - **Business Requirements**: Mapping of business needs to database
-         *   structures
-         * - **Table Design**: Entity definitions and attribute specifications
-         * - **Relationship Strategy**: Cardinality and referential integrity planning
-         * - **Normalization Approach**: Application of 1NF, 2NF, 3NF principles
-         * - **Performance Considerations**: Index strategy and query optimization
-         * - **Snapshot Architecture**: Temporal data handling and audit requirements
-         * - **Materialized Views**: Denormalization strategy for performance
-         *
-         * **Example:**
-         *
-         *     "Database Design Strategy:
-         *     Component: Sales Domain
-         *     Tables: shopping_sales, shopping_sale_snapshots, shopping_sale_units
-         *
-         *     Design Approach:
-         *     - Normalize product catalog to 3NF for data integrity
-         *     - Implement snapshot pattern for price history tracking
-         *     - Create composite indexes for product search queries
-         *     - Use materialized views for sales analytics dashboards"
-         */
-        plan: string;
-        /**
-         * Array of Prisma models that have been modified based on review feedback.
-         *
-         * Contains ONLY the models that required changes, not the entire schema.
-         * Each model represents a complete table definition with all fields,
-         * relationships, indexes, and documentation. These modifications will be
-         * applied to the models to produce the final implementation.
-         *
-         * **Model Requirements:**
-         *
-         * - **Complete Models**: Each entry must be a complete model definition
-         * - **Targeted Changes**: Only includes models that need modifications
-         * - **AST Compliance**: Follows AutoBePrisma.IModel interface structure
-         * - **Relationship Integrity**: All foreign keys reference valid models
-         * - **Index Optimization**: Strategic indexes without redundancy
-         * - **Documentation**: Comprehensive English descriptions
-         *
-         * **Notes:**
-         *
-         * - Models not included in this array remain unchanged from the models
-         * - The final schema merges these modifications with the original models
-         * - All modifications must resolve issues identified in the review
-         */
-        modifications: AutoBePrisma.IModel[];
-    }
-}

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaReviewApplication.js.map

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

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaSchemaApplication.d.ts

@@ -1,99 +0,0 @@
-import { AutoBePrisma } from "@autobe/interface";
-import { tags } from "typia";
-export interface IAutoBePrismaSchemaApplication {
-    /**
-     * Generates comprehensive Prisma schema files based on detailed requirements
-     * analysis.
-     *
-     * Creates multiple organized schema files following enterprise patterns
-     * including proper domain separation, relationship modeling, snapshot
-     * patterns, inheritance, materialized views, and comprehensive documentation.
-     * The generated schemas implement best practices for scalability,
-     * maintainability, and data integrity.
-     *
-     * @param props Properties containing the file
-     */
-    makePrismaSchemaFile(props: IAutoBePrismaSchemaApplication.IProps): void;
-}
-export declare namespace IAutoBePrismaSchemaApplication {
-    interface IProps {
-        /**
-         * Strategic database design analysis and planning.
-         *
-         * AI analyzes the target component and business requirements to formulate a
-         * comprehensive database design strategy. This planning phase is crucial
-         * for creating well-structured, normalized schemas that align with business
-         * objectives. The AI must define table structures, relationships, indexing
-         * strategies, and data integrity constraints before proceeding to schema
-         * implementation.
-         *
-         * **Key Considerations:**
-         *
-         * - **Assignment Validation**: Extract targetComponent.tables as the complete
-         *   specification
-         * - **Table Count**: Must create exactly targetComponent.tables.length models
-         * - **Other Components**: Identify already-created tables for foreign key
-         *   references only
-         * - **Normalization**: Strict adherence to 1NF, 2NF, 3NF principles
-         * - **Snapshot Architecture**: Design for historical data preservation and
-         *   audit trails
-         * - **Junction Tables**: Plan M:N relationships with proper naming
-         *   ({table1}_{table2})
-         * - **Materialized Views**: Identify needs for mv_ prefixed denormalized
-         *   tables
-         *
-         * Workflow: Component analysis → Strategic planning → Design rationale
-         */
-        plan: string;
-        /**
-         * Production-ready Prisma schema models generated based on the strategic
-         * plan.
-         *
-         * Contains a structured Abstract Syntax Tree (AST) representation of all
-         * database tables for the target component. Each model implements the
-         * planned table structure, relationships, indexes, and constraints using
-         * the AutoBePrisma.IModel interface. These models are designed to be
-         * production-ready from the initial generation, following all best
-         * practices and normalization principles.
-         *
-         * **Implementation Requirements:**
-         *
-         * - **Model Count**: Exactly matches targetComponent.tables.length (plus any
-         *   junction tables)
-         * - **Table Names**: EXACT names from targetComponent.tables - no
-         *   modifications allowed
-         * - **Primary Keys**: Always UUID type with field name "id"
-         * - **Foreign Keys**: Proper IRelation configurations for all relationships
-         * - **Business Fields**: Only raw data fields - no calculated or derived
-         *   values
-         * - **Data Types**: Limited to: uuid, string, int, double, datetime, boolean,
-         *   uri
-         * - **Relationships**: Correct patterns for 1:1, 1:N, and M:N relationships
-         * - **Indexes**:
-         *
-         *   - UniqueIndexes: Business constraints and composite unique keys
-         *   - PlainIndexes: Multi-column query optimization (never single FK indexes)
-         *   - GinIndexes: Full-text search on appropriate string fields
-         * - **Materialized Views**: Tables prefixed with "mv_" have material flag set
-         *   to true
-         * - **Documentation**: Comprehensive English descriptions with business
-         *   context
-         *
-         * **Quality Standards:**
-         *
-         * - **Normalization**: Strict adherence to 3NF (Third Normal Form)
-         * - **No Denormalization**: Except in materialized views (mv_ tables)
-         * - **Referential Integrity**: All foreign keys reference valid existing
-         *   tables
-         * - **Temporal Fields**: Consistent created_at, updated_at, deleted_at
-         *   patterns
-         * - **Snapshot Support**: Proper historical data preservation where needed
-         * - **Performance Ready**: Optimized index strategy for expected query
-         *   patterns
-         *
-         * The generated models will undergo review by a separate specialized agent
-         * to ensure compliance with all requirements and best practices.
-         */
-        models: AutoBePrisma.IModel[] & tags.MinItems<1>;
-    }
-}

package/lib/agent/src/orchestrate/prisma/structures/IAutoBePrismaSchemaApplication.js.map

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

package/lib/agent/src/orchestrate/realize/ProviderCodeComparator.d.ts

@@ -1,5 +0,0 @@
-import { AutoBeOpenApi } from "@autobe/interface";
-export declare namespace ProviderCodeComparator {
-    function hashCode(e: AutoBeOpenApi.IEndpoint): number;
-    function equals(x: AutoBeOpenApi.IEndpoint, y: AutoBeOpenApi.IEndpoint): boolean;
-}

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

@@ -1 +0,0 @@
-{"version":3,"file":"ProviderCodeComparator.js","sourceRoot":"","sources":["../../../../../src/orchestrate/realize/ProviderCodeComparator.ts"],"names":[],"mappings":";;;AACA,+BAA4B;AAE5B,IAAiB,sBAAsB,CAWtC;AAXD,WAAiB,sBAAsB;IACrC,SAAgB,QAAQ,CAAC,CAA0B;QACjD,OAAO,IAAA,WAAI,EAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC;IAChC,CAAC;IAFe,+BAAQ,WAEvB,CAAA;IAED,SAAgB,MAAM,CACpB,CAA0B,EAC1B,CAA0B;QAE1B,OAAO,CAAC,CAAC,IAAI,KAAK,CAAC,CAAC,IAAI,IAAI,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC,MAAM,CAAC;IACpD,CAAC;IALe,6BAAM,SAKrB,CAAA;AACH,CAAC,EAXgB,sBAAsB,sCAAtB,sBAAsB,QAWtC"}

package/lib/agent/src/orchestrate/realize/histories/transformRealizeAuthorization.d.ts

@@ -1,5 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeAnalyzeRole } from "@autobe/interface";
-import { ILlmSchema } from "@samchon/openapi";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-export declare const transformRealizeAuthorizationHistories: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, role: AutoBeAnalyzeRole) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/agent/src/orchestrate/realize/histories/transformRealizeAuthorization.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformRealizeAuthorization.js","sourceRoot":"","sources":["../../../../../../src/orchestrate/realize/histories/transformRealizeAuthorization.ts"],"names":[],"mappings":";;;AAEA,yCAA2C;AAE3C,+BAA0B;AAKnB,MAAM,sCAAsC,GAAG,CAGpD,GAAyB,EACzB,IAAuB,EAGvB,EAAE;;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,ggcAAkD;SACvD;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,EAAE,kBAAU,CAAC,IAAI,CAAA;;;UAGjB,IAAI,CAAC,SAAS,CAAC,IAAI,CAAC;;;;;;UAMpB,IAAI,CAAC,SAAS,CAAC,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,MAAM,0CAAE,OAAO,CAAC;;;;;;;2BAO1B,IAAI,CAAC,IAAI,mBAAmB,IAAI,CAAC,IAAI;4BACpC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,cAAc,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC;0BAC5H,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,iBAAiB,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC;OAChJ;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AAzCW,QAAA,sCAAsC,0CAyCjD"}

package/lib/agent/src/orchestrate/realize/histories/transformRealizeAuthorizationCorrectHistories.d.ts

@@ -1,5 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeRealizeAuthorization, IAutoBeTypeScriptCompileResult } from "@autobe/interface";
-import { ILlmSchema } from "@samchon/openapi";
-import { AutoBeContext } from "../../../context/AutoBeContext";
-export declare const transformRealizeAuthorizationCorrectHistories: <Model extends ILlmSchema.Model>(ctx: AutoBeContext<Model>, auth: AutoBeRealizeAuthorization, templateFiles: Record<string, string>, diagnostics: IAutoBeTypeScriptCompileResult.IDiagnostic[]) => Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;

package/lib/agent/src/orchestrate/realize/histories/transformRealizeAuthorizationCorrectHistories.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformRealizeAuthorizationCorrectHistories.js","sourceRoot":"","sources":["../../../../../../src/orchestrate/realize/histories/transformRealizeAuthorizationCorrectHistories.ts"],"names":[],"mappings":";;;AAKA,yCAA2C;AAE3C,+BAA0B;AAKnB,MAAM,6CAA6C,GAAG,CAG3D,GAAyB,EACzB,IAAgC,EAChC,aAAqC,EACrC,WAAyD,EAGzD,EAAE;;IACF,OAAO;QACL;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,ggcAAkD;SACvD;QACD;YACE,EAAE,EAAE,IAAA,SAAE,GAAE;YACR,UAAU,EAAE,IAAI,IAAI,EAAE,CAAC,WAAW,EAAE;YACpC,IAAI,EAAE,eAAe;YACrB,IAAI,s0MAA0D;SAC/D;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;;;;UAIjB,IAAI,CAAC,SAAS,CAAC;gBACf,QAAQ,EAAE;oBACR,QAAQ,EAAE,IAAI,CAAC,QAAQ,CAAC,QAAQ;oBAChC,IAAI,EAAE,IAAI,CAAC,QAAQ,CAAC,IAAI;oBACxB,OAAO,EAAE,IAAI,CAAC,QAAQ,CAAC,OAAO;iBAC/B;gBACD,SAAS,EAAE;oBACT,QAAQ,EAAE,IAAI,CAAC,SAAS,CAAC,QAAQ;oBACjC,IAAI,EAAE,IAAI,CAAC,SAAS,CAAC,IAAI;oBACzB,OAAO,EAAE,IAAI,CAAC,SAAS,CAAC,OAAO;iBAChC;gBACD,OAAO,EAAE;oBACP,QAAQ,EAAE,IAAI,CAAC,OAAO,CAAC,QAAQ;oBAC/B,IAAI,EAAE,IAAI,CAAC,OAAO,CAAC,IAAI;oBACvB,OAAO,EAAE,IAAI,CAAC,OAAO,CAAC,OAAO;iBAC9B;aACiD,CAAC;;;;;;UAMnD,IAAI,CAAC,SAAS,CAAC,MAAA,GAAG,CAAC,KAAK,EAAE,CAAC,MAAM,0CAAE,OAAO,CAAC;;;;;UAK3C,MAAM,CAAC,IAAI,CAAC,aAAa,CAAC;iBACzB,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,KAAK,IAAI,EAAE,CAAC;iBAC1B,IAAI,CAAC,IAAI,CAAC;;;;;;;UAOX,IAAI,CAAC,SAAS,CAAC,WAAW,CAAC;;;;;;;;;2BASV,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE,mBAAmB,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,WAAW,EAAE;4BAC1E,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,cAAc,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE;0BAC5K,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,iBAAiB,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE,GAAG,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC,WAAW,EAAE;OAChM;SACF;KACF,CAAC;AACJ,CAAC,CAAC;AAlFW,QAAA,6CAA6C,iDAkFxD"}

package/lib/agent/src/orchestrate/realize/histories/transformRealizeCorrectHistories.d.ts

@@ -1,14 +0,0 @@
-import { IAgenticaHistoryJson } from "@agentica/core";
-import { AutoBeRealizeAuthorization } from "@autobe/interface";
-import { AutoBeState } from "../../../context/AutoBeState";
-import { IAutoBeRealizeFunctionFailure } from "../structures/IAutoBeRealizeFunctionFailure";
-import { IAutoBeRealizeScenarioResult } from "../structures/IAutoBeRealizeScenarioResult";
-export declare function transformRealizeCorrectHistories(props: {
-    state: AutoBeState;
-    scenario: IAutoBeRealizeScenarioResult;
-    authorization: AutoBeRealizeAuthorization | null;
-    totalAuthorizations: AutoBeRealizeAuthorization[];
-    code: string;
-    dto: Record<string, string>;
-    failures: IAutoBeRealizeFunctionFailure[];
-}): Array<IAgenticaHistoryJson.IAssistantMessage | IAgenticaHistoryJson.ISystemMessage>;