Release v2.0.0

[wanng-ide]

Summary

• bump evolver to 2.0.0
• persist structured exploration context from the evolver prompt into run state and exploration_status.json
• align repository references and release docs with the new EvoMap/evolver / autogame-17/evolver 2.0 release line

Why

This PR makes evolver the canonical upstream producer of exploration context such as role, persona, target profile, and objective. Downstream wrappers and reports can then render the same context without semantic drift or hand-maintained display-only patches.

Scope

• add prompt-context extraction and persistence in src/evolve.js
• merge exploration context into the current run state for downstream consumers
• write structured fields into exploration_status.json
• update issue reporter default repo and upstream links
• add CHANGELOG.md and refresh release-facing README text for 2.0.0

Coordination

• companion wrapper PR: EvoMap/feishu-evolver-wrapper-private#1
• intended release pairing: evolver v2.0.0 + feishu-evolver-wrapper v2.0.0
• wrapper-side reporting changes depend on the structured exploration context emitted here

Test plan

• node --check index.js
• node --check src/evolve.js
• node --check src/gep/issueReporter.js
• inspect release diff scope in clean worktree
• run one end-to-end cycle in a real workspace before tagging
• verify exploration_status.json contains role / persona / target / objective fields
• verify wrapper / unified report surfaces the same exploration role and target

Release checklist

• merge after companion wrapper PR is approved or ready to merge in lockstep
• tag v2.0.0
• publish release notes mentioning canonical reporting convergence and structured exploration context
• smoke test downstream reporting after merge

Notes

• this PR intentionally keeps the upstream responsibility in evolver: emit structured exploration context once, let wrappers consume it
• no runtime release tag is created by this PR; tagging should happen after final smoke validation

[wanng-ide]

更新说明：

• 这个 PR 现在代表 evolver v2.0.0 的 upstream 侧改动，重点是把 exploration role / persona / target / objective 以结构化字段写入运行态与 exploration_status.json。
• companion PR 是 EvoMap/feishu-evolver-wrapper-private#1；wrapper 侧会消费这里产出的结构化 context，并负责 canonical summary / Feishu 展示层收口。
• 目前 clean release worktree 已完成 commit、push、PR 和基础语法检查；剩余主要是 merge 前的真实 workspace smoke test。
• merge 时建议和 wrapper PR 近邻合并，并在联动验证通过后再统一打 v2.0.0 tag。

[wanng-ide]

补充说明（版本升级视角）：

这次 evolver v2.0.0 的意义，不只是版本号提升，而是把 exploration 从“prompt 中的隐含信息”正式提升为“结构化运行态上下文”。

具体来说，这个 PR 让 evolver 开始稳定产出并持久化以下字段：

• role
• persona
• agent
• target_profile_id
• target_profile_title
• exploration_objective
• direction

这些字段会进入当前 run state，并写入 exploration_status.json，从而为 wrapper、Unified Evolution Report 以及其他下游展示层提供统一数据源。这样做的核心价值是：

• 避免 exploration 角色/目标只存在于 prompt 文本里，导致下游展示不稳定
• 减少 display-only patch 带来的语义漂移
• 明确 evolver 在 2.x 版本线中的职责：负责产出结构化 context，而不是把展示逻辑散落到各处

从 2.0 的整体方向看，这个 PR 对应的是三件大事中的 upstream 部分：

1. structured exploration context 上游化
2. canonical reporting 开始向统一语义收敛
3. core evolver 与 wrapper/reporting 层的边界更清晰

参数/默认配置口径方面，这个 PR 中明确落地并更新文档的变化主要是：

• EVOLVER_ISSUE_REPO: autogame-17/capability-evolver -> autogame-17/evolver

除此之外，本 PR 更偏向“数据语义与架构边界升级”，而不是一次集中修改大量默认参数。像报告频率、loop 间隔、某些运行环境默认值，更适合放在运行环境或 companion wrapper 侧口径中说明，而不是误写成 core evolver 的统一默认值变化。

如果把这次 2.0 用一句话概括，我会写成：
evolver 2.0.0 开始成为 exploration context 的 canonical upstream source，为后续 wrapper、summary artifact 和 Unified Report 的一致展示打基础。

[autogame-17]

Closing this PR. The changes from PR #260 have already been reviewed, merged into the upstream codebase, and released as v1.32.0 (not 2.0.0 -- the changes are backward-compatible additions, not breaking changes).

Deleting the release/2.0.0-clean branch as well to avoid confusion.