@autobe/agent 0.30.0-dev.20260315 → 0.30.1

package/src/orchestrate/analyze/structures/IAutoBeAnalyzeScenarioApplication.ts

@@ -1,141 +1,141 @@
-import {
-  AutoBeAnalyze,
-  AutoBeAnalyzeScenarioEntity,
-  CamelCasePattern,
-} from "@autobe/interface";
-
-import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
-import { FixedAnalyzeTemplateFeature } from "./FixedAnalyzeTemplate";
-
-export interface IAutoBeAnalyzeScenarioApplication {
-  /**
-   * Process scenario composition task or preliminary data requests.
-   *
-   * Composes project structure with actors and entities based on requirements.
-   * File structure is fixed (6-file SRS template); the LLM only determines
-   * actors, entities, prefix, and language.
-   *
-   * @param props Request containing either preliminary data request or complete
-   *   task
-   */
-  process(props: IAutoBeAnalyzeScenarioApplication.IProps): void;
-}
-
-export namespace IAutoBeAnalyzeScenarioApplication {
-  export interface IProps {
-    /**
-     * Think before you act.
-     *
-     * Before requesting preliminary data or completing your task, reflect on
-     * your current state and explain your reasoning:
-     *
-     * For preliminary requests (getPreviousAnalysisSections):
-     *
-     * - What critical information is missing that you don't already have?
-     * - Why do you need it specifically right now?
-     * - Be brief - state the gap, don't list everything you have.
-     *
-     * For completion (complete):
-     *
-     * - What key assets did you acquire?
-     * - What did you accomplished?
-     * - Why is it sufficient to complete?
-     * - Summarize - don't enumerate every single item.
-     *
-     * This reflection helps you avoid duplicate requests and premature
-     * completion.
-     */
-    thinking?: string | null;
-
-    /**
-     * Type discriminator for the request.
-     *
-     * Determines which action to perform: preliminary data retrieval
-     * (getPreviousAnalysisSections) or final scenario composition (complete).
-     * When preliminary returns empty array, that type is removed from the
-     * union, physically preventing repeated calls.
-     */
-    request: IComplete | IAutoBePreliminaryGetPreviousAnalysisSections;
-  }
-
-  /**
-   * Request to compose project structure with actors and entities.
-   *
-   * The document file structure is fixed as 6-file SRS template. LLM only
-   * determines actors, entities, prefix, and language. Files are generated
-   * programmatically from FixedAnalyzeTemplate.
-   */
-  export interface IComplete {
-    /**
-     * Type discriminator for the request.
-     *
-     * Determines which action to perform: preliminary data retrieval or actual
-     * task execution. Value "complete" indicates this is the final task
-     * execution request.
-     */
-    type: "complete";
-
-    /** Reason for the analysis and composition of the project structure. */
-    reason: string;
-
-    /**
-     * Prefix for file names and variable names. This will be used for
-     * organizing documentation files.
-     *
-     * DO: Use camelCase naming convention.
-     */
-    prefix: string & CamelCasePattern;
-
-    /**
-     * Actors to be assigned for the project.
-     *
-     * Each actor has:
-     *
-     * - `name`: Actor identifier (camelCase)
-     * - `kind`: "guest" | "member" | "admin"
-     * - `description`: Actor's permissions and capabilities
-     */
-    actors: AutoBeAnalyze.IActor[];
-
-    /**
-     * Language for document content. When specified by the user, this takes
-     * precedence over the locale setting for determining document language. Set
-     * to `null` if not specified.
-     */
-    language: string | null;
-
-    /**
-     * Core domain entities with their key attributes and relationships.
-     *
-     * These serve as the AUTHORITATIVE entity list — all downstream document
-     * writers (module, unit, section) MUST reference only these entities. This
-     * prevents hallucination and ensures cross-file consistency.
-     *
-     * Each entity should include:
-     *
-     * - `name`: PascalCase entity name (e.g., "Todo", "User", "Comment")
-     * - `attributes`: Key attributes with type hints (e.g., "title: text(1-500),
-     *   required")
-     * - `relationships`: How this entity relates to others (e.g., "belongsTo User
-     *   via userId")
-     *
-     * Include ALL domain entities that will appear in the requirements
-     * documents. Do NOT include meta-entities (InterpretationLog,
-     * ScopeDecisionLog, etc.) that describe the requirements process rather
-     * than the production system.
-     */
-    entities: AutoBeAnalyzeScenarioEntity[];
-
-    /**
-     * High-level project features that activate conditional modules.
-     *
-     * Selected from a FIXED catalog — the LLM must NOT invent features outside
-     * the predefined list. Each feature activates additional modules in the
-     * appropriate SRS files.
-     *
-     * If the project has no special features beyond REST CRUD, return an empty
-     * array.
-     */
-    features: FixedAnalyzeTemplateFeature[];
-  }
-}
+import {
+  AutoBeAnalyze,
+  AutoBeAnalyzeScenarioEntity,
+  CamelCasePattern,
+} from "@autobe/interface";
+
+import { IAutoBePreliminaryGetPreviousAnalysisSections } from "../../common/structures/IAutoBePreliminaryGetPreviousAnalysisSections";
+import { FixedAnalyzeTemplateFeature } from "./FixedAnalyzeTemplate";
+
+export interface IAutoBeAnalyzeScenarioApplication {
+  /**
+   * Process scenario composition task or preliminary data requests.
+   *
+   * Composes project structure with actors and entities based on requirements.
+   * File structure is fixed (6-file SRS template); the LLM only determines
+   * actors, entities, prefix, and language.
+   *
+   * @param props Request containing either preliminary data request or complete
+   *   task
+   */
+  process(props: IAutoBeAnalyzeScenarioApplication.IProps): void;
+}
+
+export namespace IAutoBeAnalyzeScenarioApplication {
+  export interface IProps {
+    /**
+     * Think before you act.
+     *
+     * Before requesting preliminary data or completing your task, reflect on
+     * your current state and explain your reasoning:
+     *
+     * For preliminary requests (getPreviousAnalysisSections):
+     *
+     * - What critical information is missing that you don't already have?
+     * - Why do you need it specifically right now?
+     * - Be brief - state the gap, don't list everything you have.
+     *
+     * For completion (complete):
+     *
+     * - What key assets did you acquire?
+     * - What did you accomplished?
+     * - Why is it sufficient to complete?
+     * - Summarize - don't enumerate every single item.
+     *
+     * This reflection helps you avoid duplicate requests and premature
+     * completion.
+     */
+    thinking?: string | null;
+
+    /**
+     * Type discriminator for the request.
+     *
+     * Determines which action to perform: preliminary data retrieval
+     * (getPreviousAnalysisSections) or final scenario composition (complete).
+     * When preliminary returns empty array, that type is removed from the
+     * union, physically preventing repeated calls.
+     */
+    request: IComplete | IAutoBePreliminaryGetPreviousAnalysisSections;
+  }
+
+  /**
+   * Request to compose project structure with actors and entities.
+   *
+   * The document file structure is fixed as 6-file SRS template. LLM only
+   * determines actors, entities, prefix, and language. Files are generated
+   * programmatically from FixedAnalyzeTemplate.
+   */
+  export interface IComplete {
+    /**
+     * Type discriminator for the request.
+     *
+     * Determines which action to perform: preliminary data retrieval or actual
+     * task execution. Value "complete" indicates this is the final task
+     * execution request.
+     */
+    type: "complete";
+
+    /** Reason for the analysis and composition of the project structure. */
+    reason: string;
+
+    /**
+     * Prefix for file names and variable names. This will be used for
+     * organizing documentation files.
+     *
+     * DO: Use camelCase naming convention.
+     */
+    prefix: string & CamelCasePattern;
+
+    /**
+     * Actors to be assigned for the project.
+     *
+     * Each actor has:
+     *
+     * - `name`: Actor identifier (camelCase)
+     * - `kind`: "guest" | "member" | "admin"
+     * - `description`: Actor's permissions and capabilities
+     */
+    actors: AutoBeAnalyze.IActor[];
+
+    /**
+     * Language for document content. When specified by the user, this takes
+     * precedence over the locale setting for determining document language. Set
+     * to `null` if not specified.
+     */
+    language: string | null;
+
+    /**
+     * Core domain entities with their key attributes and relationships.
+     *
+     * These serve as the AUTHORITATIVE entity list — all downstream document
+     * writers (module, unit, section) MUST reference only these entities. This
+     * prevents hallucination and ensures cross-file consistency.
+     *
+     * Each entity should include:
+     *
+     * - `name`: PascalCase entity name (e.g., "Todo", "User", "Comment")
+     * - `attributes`: Key attributes with type hints (e.g., "title: text(1-500),
+     *   required")
+     * - `relationships`: How this entity relates to others (e.g., "belongsTo User
+     *   via userId")
+     *
+     * Include ALL domain entities that will appear in the requirements
+     * documents. Do NOT include meta-entities (InterpretationLog,
+     * ScopeDecisionLog, etc.) that describe the requirements process rather
+     * than the production system.
+     */
+    entities: AutoBeAnalyzeScenarioEntity[];
+
+    /**
+     * High-level project features that activate conditional modules.
+     *
+     * Selected from a FIXED catalog — the LLM must NOT invent features outside
+     * the predefined list. Each feature activates additional modules in the
+     * appropriate SRS files.
+     *
+     * If the project has no special features beyond REST CRUD, return an empty
+     * array.
+     */
+    features: FixedAnalyzeTemplateFeature[];
+  }
+}

package/src/orchestrate/analyze/structures/IAutoBeAnalyzeScenarioReviewApplication.ts

@@ -1,96 +1,96 @@
-/**
- * Application interface for the Scenario Review agent.
- *
- * This agent reviews the scenario output against the user's original
- * requirements, checking entity coverage, hallucination, actor classification,
- * relationship completeness, and feature identification accuracy.
- */
-export interface IAutoBeAnalyzeScenarioReviewApplication {
-  /**
-   * Process scenario review task.
-   *
-   * Reviews the scenario output and provides an approved/rejected verdict with
-   * structured feedback.
-   *
-   * @param props Request containing the review result
-   */
-  process(props: IAutoBeAnalyzeScenarioReviewApplicationProps): void;
-}
-
-export interface IAutoBeAnalyzeScenarioReviewApplicationProps {
-  /**
-   * Think before you act.
-   *
-   * Before completing the review, reflect on your analysis:
-   *
-   * - Does every user-mentioned concept have a corresponding entity?
-   * - Are there entities the user never mentioned or implied?
-   * - Are actors correctly classified by identity boundary?
-   * - Are all entity relationships complete and bidirectional?
-   * - Are features correctly identified from user requirements?
-   */
-  thinking?: string | null;
-
-  /** Review result. */
-  request: IAutoBeAnalyzeScenarioReviewApplicationComplete;
-}
-
-/** Request to complete the scenario review. */
-export interface IAutoBeAnalyzeScenarioReviewApplicationComplete {
-  /** Type discriminator for the request. */
-  type: "complete";
-
-  /**
-   * Whether the scenario passed review.
-   *
-   * Set to true if all review criteria pass. Set to false if any criterion
-   * fails.
-   */
-  approved: boolean;
-
-  /**
-   * Detailed review feedback.
-   *
-   * When rejecting: describe each issue clearly so the scenario generator can
-   * fix them on the next attempt.
-   *
-   * When approving: may include minor observations.
-   */
-  feedback: string;
-
-  /**
-   * Structured issues for targeted scenario regeneration.
-   *
-   * Each issue identifies a specific category and provides a concrete
-   * suggestion for fixing the scenario.
-   */
-  issues: IAutoBeAnalyzeScenarioReviewApplicationScenarioReviewIssue[];
-}
-
-export interface IAutoBeAnalyzeScenarioReviewApplicationScenarioReviewIssue {
-  /**
-   * Issue category.
-   *
-   * - "missing_entity": User mentioned a concept but no entity exists for it
-   * - "hallucinated_entity": Entity exists but user never mentioned or implied it
-   * - "actor_misclassification": Actor's kind doesn't match identity boundary
-   *   test
-   * - "incomplete_relationship": Entity relationships are missing or
-   *   one-directional
-   * - "missing_feature": User mentioned a capability but feature is not activated
-   * - "hallucinated_feature": Feature is activated but user never requested it
-   */
-  category:
-    | "missing_entity"
-    | "hallucinated_entity"
-    | "actor_misclassification"
-    | "incomplete_relationship"
-    | "missing_feature"
-    | "hallucinated_feature";
-
-  /** Human-readable description of the issue. */
-  description: string;
-
-  /** Concrete suggestion for fixing the issue. */
-  suggestion: string;
-}
+/**
+ * Application interface for the Scenario Review agent.
+ *
+ * This agent reviews the scenario output against the user's original
+ * requirements, checking entity coverage, hallucination, actor classification,
+ * relationship completeness, and feature identification accuracy.
+ */
+export interface IAutoBeAnalyzeScenarioReviewApplication {
+  /**
+   * Process scenario review task.
+   *
+   * Reviews the scenario output and provides an approved/rejected verdict with
+   * structured feedback.
+   *
+   * @param props Request containing the review result
+   */
+  process(props: IAutoBeAnalyzeScenarioReviewApplicationProps): void;
+}
+
+export interface IAutoBeAnalyzeScenarioReviewApplicationProps {
+  /**
+   * Think before you act.
+   *
+   * Before completing the review, reflect on your analysis:
+   *
+   * - Does every user-mentioned concept have a corresponding entity?
+   * - Are there entities the user never mentioned or implied?
+   * - Are actors correctly classified by identity boundary?
+   * - Are all entity relationships complete and bidirectional?
+   * - Are features correctly identified from user requirements?
+   */
+  thinking?: string | null;
+
+  /** Review result. */
+  request: IAutoBeAnalyzeScenarioReviewApplicationComplete;
+}
+
+/** Request to complete the scenario review. */
+export interface IAutoBeAnalyzeScenarioReviewApplicationComplete {
+  /** Type discriminator for the request. */
+  type: "complete";
+
+  /**
+   * Whether the scenario passed review.
+   *
+   * Set to true if all review criteria pass. Set to false if any criterion
+   * fails.
+   */
+  approved: boolean;
+
+  /**
+   * Detailed review feedback.
+   *
+   * When rejecting: describe each issue clearly so the scenario generator can
+   * fix them on the next attempt.
+   *
+   * When approving: may include minor observations.
+   */
+  feedback: string;
+
+  /**
+   * Structured issues for targeted scenario regeneration.
+   *
+   * Each issue identifies a specific category and provides a concrete
+   * suggestion for fixing the scenario.
+   */
+  issues: IAutoBeAnalyzeScenarioReviewApplicationScenarioReviewIssue[];
+}
+
+export interface IAutoBeAnalyzeScenarioReviewApplicationScenarioReviewIssue {
+  /**
+   * Issue category.
+   *
+   * - "missing_entity": User mentioned a concept but no entity exists for it
+   * - "hallucinated_entity": Entity exists but user never mentioned or implied it
+   * - "actor_misclassification": Actor's kind doesn't match identity boundary
+   *   test
+   * - "incomplete_relationship": Entity relationships are missing or
+   *   one-directional
+   * - "missing_feature": User mentioned a capability but feature is not activated
+   * - "hallucinated_feature": Feature is activated but user never requested it
+   */
+  category:
+    | "missing_entity"
+    | "hallucinated_entity"
+    | "actor_misclassification"
+    | "incomplete_relationship"
+    | "missing_feature"
+    | "hallucinated_feature";
+
+  /** Human-readable description of the issue. */
+  description: string;
+
+  /** Concrete suggestion for fixing the issue. */
+  suggestion: string;
+}