CI / test (push) Failing after 12s

Details

refactor(exploration): absorb settlement.py into ExplorationSessionRepository

将 settlement.py 的 settle_campaign_sessions 函数吸收为
ExplorationSessionRepository.expire_running_sessions 方法。删除浅模块
settlement.py（30 行，接口宽如实现），会话生命周期操作集中在 repository。

- 新增 ExplorationSessionRepository.expire_running_sessions(campaign_id)
- 更新 campaigns.py 和 campaign_runner.py 两个调用点
- 删除 backend/agenteval/exploration/settlement.py
- 所有测试通过，行为不变

2026-08-04 13:28:23 +08:00

1.9 KiB

Raw Blame History

RESOURCES.md Format

RESOURCES.md is the curated set of trusted sources for this topic. Knowledge for explainers should be drawn from here, not from parametric guesses. Wisdom comes from the communities listed here.

Structure

# {Topic} Resources

## Knowledge

- [Book: _The Science and Practice of Strength Training_ — Zatsiorsky & Kraemer](https://example.com)
  Foundational text on programming and adaptation. Use for: anything to do with periodisation, recovery, intensity zones.
- [Article: "How Much Should I Train?" — Greg Nuckols (Stronger By Science)](https://example.com)
  Evidence-based review of volume landmarks. Use for: weekly set targets per muscle group.

## Wisdom (Communities)

- [r/weightroom](https://reddit.com/r/weightroom)
  High-signal subreddit, moderated against bro-science. Use for: programme critique, plateau troubleshooting.
- Local: Tuesday strength class at {gym name}
  Use for: real-time coaching feedback on lifts.

Rules

High-trust only. Prefer primary sources, recognised experts, peer-reviewed work, and communities with strong moderation. If a resource is marketing dressed as education, leave it out.
Annotate every entry. A bare link is useless in three months. Add one line: what it covers and when to reach for it.
Group by Knowledge / Wisdom. Mirrors the philosophy in SKILL.md. It is fine for a resource to appear in only one group.
Surface gaps explicitly. If no good resource exists for an area the mission needs, write a ## Gaps section listing what is missing. This drives future search.
Prune ruthlessly. A resource that turned out to be wrong, shallow, or off-mission should be removed, not buried. Better five sharp sources than thirty mediocre ones.
Record community preferences. If the user has opted out of joining communities, note it here so future sessions don't keep proposing them.

1.9 KiB Raw Blame History

RESOURCES.md Format

Structure

Rules

1.9 KiB

Raw Blame History