[High] 架构问题：巨型单体文件难以维护

[Colin4k1024]

问题描述

核心模块文件过大（1700+ 行），导致代码难以维护和理解。

问题文件

文件	行数	职责
evolve.js	~1704	整个进化运行逻辑
solidify.js	~1681	状态管理、Git操作、验证、发布、回滚
prompt.js	~566	提示词构建

影响

• 任何修改都需要理解整个文件
• 代码审查困难
• 重构风险高
• 新开发者学习曲线陡峭

建议

1. 拆分大型模块为独立职责的文件
2. 引入依赖注入
3. 按功能划分目录结构

---

严重程度: High
分类: Architecture

[autogame-17]

Thank you @Colin4k1024 for this observation. The file sizes are indeed large, and we agree this affects maintainability.

Context:

These files have been progressively decomposed over time. Earlier versions were significantly larger -- modules like narrativeMemory.js, reflection.js, hubSearch.js, hubReview.js, taskReceiver.js, skillDistiller.js, and skillPublisher.js were all extracted from the original monolithic evolve.js and solidify.js in recent releases.

The current sizes (~1200 lines each) still contain multiple responsibilities, and further decomposition is planned:

Planned extractions:

1. solidify.js -> extract git operations into src/gep/gitOps.js (reset, commit, diff, rollback)
2. solidify.js -> extract validation logic into src/gep/validation.js (constraint checking, policy evaluation)
3. evolve.js -> extract signal processing and candidate evaluation into dedicated modules

Why we're cautious:

Large refactors of these files carry high risk because they contain the core evolution loop -- any regression could cause data loss or incorrect solidification. We prefer incremental extraction with comprehensive testing at each step over a single large restructuring pass.

We appreciate the suggestion about dependency injection -- it's something we'll consider as we extract modules. However, a full architectural overhaul is not planned for the near term.