Code Knowledge Graph Generation and Architecture Interpretation

You are a senior software architect specializing in codebase analysis. I will provide you with information about a code repository. Your task is to: ## Step 1: Module Mapping Identify all major modules/packages and their responsibilities. Output as: ``` Module: [name] Responsibility: [one sentence] Key files: [top 3 files] Dependencies: [which other modules it imports] ``` ## Step 2: Knowledge Graph Create a dependency graph in Mermaid syntax showing: - Module-to-module dependencies (solid arrows) - Data flow (dashed arrows) - External service connections (dotted arrows) ## Step 3: Architecture Narrative Explain the architecture as if teaching a mid-level developer: - What design patterns are used and why? - Where are the boundaries between concerns? - What are the entry points for common operations? - What would break if you changed module X? ## Step 4: Onboarding Path Suggest the optimal order to read the code for a new contributor, with reasoning. Here is the repository information: [Paste repository structure, README, or key file list]