You are an AI assistant helping me understand and improve a codebase.
Use the attached/generated files as the authoritative context.
Your goal is to refactor the project based on these files, not just summarize it.

we are in project path: .

Files for analysis:

Note: project/validation.toon.yaml and project/duplication.toon.yaml are generated by external tools (vallm and redup)
- project/analysis.toon.yaml  (Health diagnostics - complexity metrics, god modules, coupling issues, refactoring priorities) [22KB]
- project/map.toon.yaml  (Structural map - files, sizes, imports, exports, signatures, project header) [127KB]
- project/evolution.toon.yaml  (Refactoring queue - ranked actions by impact/effort, risks, metrics targets, history) [2KB]
- project/project.toon.yaml  (Compact project overview - generated from project.yaml data) [2KB]
- project/context.md  (LLM narrative - architecture summary and project context) [40KB]
- project/README.md  (Generated documentation - overview and usage guide) [9KB]

Task:
- Treat this prompt as a refactoring brief: identify the highest-priority changes and prepare concrete edits.
- Use the file set to decide whether the first pass should focus on correctness, duplication, complexity reduction, or architecture cleanup.
- If you can safely implement the refactor, do it; otherwise give an exact file-by-file change plan and test plan.
- Use analysis.toon.yaml to locate high-CC functions and god modules that should be split first.
- Keep module boundaries intact and update imports/exports according to map.toon.yaml.
- Use evolution.toon.yaml as the execution backlog and work from the top-ranked items.
- Keep project.toon.yaml aligned with the refactored architecture.

Priority Order:
P1 — Split or simplify the highest-CC / god modules identified in analysis.toon.yaml.
P1 — Preserve module boundaries and update imports/exports according to map.toon.yaml.
P2 — Keep the compact project overview in project.toon.yaml aligned with the refactor.
P2 — Execute the highest-impact items from evolution.toon.yaml in order of benefit/risk.

Focus Areas for Analysis:
1. **Code Health Analysis** - Review complexity metrics, god modules, coupling issues from analysis.toon.yaml
2. **Structural Map** - Use map.toon.yaml to inspect imports, exports, signatures, and the project header
3. **Refactoring Priorities** - Examine ranked refactoring actions and risk assessment from evolution.toon.yaml
4. **Project Overview** - Review the compact project overview from project.toon.yaml

Analysis Strategy:
- Start with analysis.toon.yaml for health metrics, then map.toon.yaml for structure and signatures
- Review evolution.toon.yaml for action priorities and next steps
- Compare the compact project overview in project.toon.yaml with the main analysis files

Constraints:
- Prefer minimal, incremental changes.
- Maintain full backward compatibility.
- Base recommendations on concrete metrics from the provided files.
- If uncertain, ask clarifying questions.
