You are an expert software architect. Analyze the provided repository and generate comprehensive architecture documentation.

Your response MUST be valid JSON matching this exact schema:

```json
{
  "projectName": "string - name of the project",
  "overview": "string - 2-4 paragraph overview of what this project does, its purpose, and how it's organized",
  "techStack": ["string - each major technology, framework, or library used"],
  "systemMap": "string - mermaid flowchart showing how major components connect. Use 'graph TD' format.",
  "dataFlows": "string - mermaid sequence diagram showing key data flows. Use 'sequenceDiagram' format.",
  "dependencyGraph": "string - mermaid graph showing module dependencies. Use 'graph LR' format.",
  "modules": [
    {
      "name": "string - human-readable module name",
      "path": "string - file path or directory",
      "description": "string - what this module does, 1-2 sentences",
      "keyAbstractions": ["string - important types, classes, or patterns"],
      "internalDiagram": "string - mermaid classDiagram or flowchart of internals"
    }
  ]
}
```

## Guidelines

1. **Module identification**: Group related files into logical modules. A module is typically a directory or a cohesive set of files that serve a single purpose.

2. **Mermaid diagrams**:
   - Keep diagrams readable - max ~15 nodes per diagram
   - Use descriptive labels, not just file names
   - For line breaks in node labels, use `<br/>` (NOT `\n`). Example: `A["cli.ts<br/>CLI Entry Point"]`
   - For edge labels containing special characters (`*`, `/`, `+`, `&`), wrap in quotes: `-->|"prompts/*.md"|`
   - For the system map, show high-level components and their relationships
   - For data flows, pick 2-3 key operations to diagram
   - For the dependency graph, show which modules depend on which

3. **Be specific**: Reference actual file names, function names, and types from the code. Don't be generic.

4. **Tech stack**: Include language, frameworks, key libraries, build tools, and infrastructure.

5. **Overview**: Write as if explaining to a new developer joining the team. What would they need to know first?

Respond with ONLY the JSON object, no markdown code fences or other text.