@autobe/agent 0.25.7 → 0.27.0

package/src/orchestrate/interface/structures/IAutobeInterfaceSchemasReviewApplication.ts

@@ -1,96 +0,0 @@
-import { AutoBeOpenApi } from "@autobe/interface";
-
-export interface IAutoBeInterfaceSchemasReviewApplication {
-  /**
-   * Analyzes and improves OpenAPI schema definitions.
-   *
-   * This function receives schema definitions and performs comprehensive review
-   * and enhancement. It identifies issues, creates an improvement plan, and
-   * produces refined schemas that meet quality standards.
-   *
-   * The function populates three key outputs:
-   *
-   * - A detailed review of findings organized by severity
-   * - An actionable plan for improvements
-   * - Enhanced schemas with all issues resolved
-   *
-   * @param props Contains review findings, improvement plan, and enhanced
-   *   schemas
-   */
-  review: (props: IAutoBeInterfaceSchemasReviewApplication.IProps) => void;
-}
-
-export namespace IAutoBeInterfaceSchemasReviewApplication {
-  /**
-   * Schema review and enhancement parameters for the review function.
-   *
-   * When the review function is called, these properties must be populated to
-   * complete the schema validation and improvement process. The LLM uses this
-   * interface to understand what outputs are required.
-   */
-  export interface IProps {
-    think: IThink;
-
-    /**
-     * Final validated and enhanced schemas ready for production use.
-     *
-     * DO:
-     *
-     * - Include valid OpenAPI schema definitions
-     * - Include all entities that were in the original input
-     * - Provide fixed versions if original schemas have issues
-     * - Rename entities correctly if names are wrong
-     * - Include created variants if schemas are missing them
-     *
-     * DO NOT:
-     *
-     * - Return an empty object {} (this will delete all schemas)
-     * - Return undefined or null
-     * - Include explanations or excuses in schema descriptions
-     * - Leave broken schemas unfixed
-     *
-     * When original schemas are beyond repair, recreate them properly based on
-     * entity names and context. This field becomes the final schemas used by
-     * the system, so it must always contain complete, valid schemas.
-     */
-    content: Record<string, AutoBeOpenApi.IJsonSchemaDescriptive>;
-  }
-
-  export interface IThink {
-    /**
-     * Issues and problems found during schema analysis.
-     *
-     * DO: Document only problems that need fixing. DO NOT: Include positive
-     * feedback, compliments, or confirmations
-     *
-     * Focus exclusively on issues organized by severity:
-     *
-     * Severity levels:
-     *
-     * - Security vulnerabilities (exposed passwords, missing auth boundaries)
-     * - Missing required variants, incorrect type mappings
-     * - Missing format specifications, incomplete relationships
-     * - Documentation improvements, style consistency
-     *
-     * Each issue must include the specific schema name and what needs to be
-     * fixed. If there are no issues at all, simply state: "No issues found."
-     */
-    review: string;
-
-    /**
-     * Action plan for addressing identified issues.
-     *
-     * Must specify concrete fixes categorized by priority:
-     *
-     * - For perfect schemas: "No improvements required. All schemas meet AutoBE
-     *   standards."
-     * - For fixable issues: List each fix with operation path and exact change
-     * - For critical problems: Describe how schemas were recreated or corrected
-     *
-     * Never leave this empty. Always provide a clear plan even if no changes
-     * are needed. The plan documents what was done to produce the content
-     * field.
-     */
-    plan: string;
-  }
-}