fix(agent) : Analyze history

[8471919]

This pull request introduces a structured, hierarchical representation of requirements analysis documents in the AutoBE system, alongside the traditional flat markdown format. The main goal is to preserve the three-level hierarchy (Module → Unit → Section) throughout the analysis pipeline, enabling advanced features such as partial updates, structural search/filtering, hierarchical UI rendering, and improved debugging.

The most important changes are:

1. Hierarchical Data Model Introduction

• Added new interfaces: AutoBeAnalyzeModule, AutoBeAnalyzeUnit, and AutoBeAnalyzeSection, each with detailed documentation, to represent the three-level document hierarchy. These are now exported from the contents index. [1] [2] [3] [4]

2. Extension of Analysis File Structure

• Updated AutoBeAnalyzeFile to include a new module property, which holds the structured representation of the document's hierarchical content in addition to the existing flat content property. [1] [2]

3. Analysis Pipeline Enhancements

• Refactored the analysis orchestration (orchestrateAnalyze.ts) to generate and return both the flat markdown content and the structured module object for each file, updating the processing flow and result types accordingly. [1] [2] [3] [4] [5] [6]

4. Structured Assembly Logic

• Implemented assembleModule in AutoBeAnalyzeProgrammer to build the hierarchical module structure from generation events, preserving the full document hierarchy for downstream use. [1] [2]

5. RAG File Type Clarification

• Clarified that the RagAnalysisFile type used for retrieval-augmented generation (RAG) only includes essential fields (filename, content, reason), and does not require the full module structure.

These changes lay the foundation for more flexible, maintainable, and feature-rich handling of requirements documents in the AutoBE system.