Skip to content

LoopX v0.2.0

Choose a tag to compare

View all tags
@huangruiteng huangruiteng released this 11 Jul 05:04
v0.2.0
af005ae
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

LoopX v0.2.0

This is the v0.2 control-plane release. It promotes the peer-agent runtime cutover and prepares LoopX for longer-lived issue-fix and PR lifecycle workflows.

中文 Highlights

  • Peer Agent 控制面落地：Agent 之间不再依赖主从层级分配权限；claim 回归为“谁优先接手、谁负责写回”的软路由信号，真正的执行边界继续由 quota、gate、capability 和 write scope 共同决定。
  • PR Issue Fix 从“会写 patch”走向“能照看完整周期”：补齐 feasibility、分支准备、acceptance evidence、reviewer fallback、PR 状态观察和 domain-state 写回等公共契约，为长期跟进 CI、review 与 merge 奠定底座。
  • 长程运行更可验证：Explore 和 issue-fix 的长链路不只看一个汇总分数，而是分别验证 writeback、quota spend、控制面开销和 git-heavy acceptance，更容易看出卡在哪一层。
  • 重构以降低后续复杂度：将膨胀的 registry-admin 和 todo CLI 逻辑拆回边界清晰的 helper，不新增一套并行状态机，让后续的 claim、handoff 和 todo 演进更容易定位与回滚。

Highlights

  • Peer-agent runtime v1: task claims are soft routing/writeback signals, independent handoff uses continuation_policy=independent_handoff plus excluded_agents, and legacy reviewer-continuation assumptions are migrated or rejected by focused smokes.
  • Issue-fix capability: public maintainer-loop surfaces now cover feasibility, caller-repo branch preparation, acceptance artifacts, reviewer request fallback, PR lifecycle observation, and domain-state writeback.
  • Explore/long-run validation: full-public smokes now cover the v0.2 control-plane contracts more reliably, including serial handling for git-heavy issue-fix acceptance checks and component-level long-run control-plane assertions.
  • CLI maintainability: registry-admin and todo command modules were trimmed into bounded helpers so module ownership budgets stay green for the release cut.
  • Release readiness: package version, release-readiness docs, full-public shards, release smokes, and premerge canary were validated for this tag.

Compatibility Notes

  • Agent hierarchy terms are no longer runtime authority. Use peer-agent task claims, excluded_agents, capability gates, quota, and write scope to decide execution.
  • Legacy review continuation should be represented as independent_handoff with explicit successor/exclusion metadata rather than a special reviewer lane.
  • Existing installs should update through loopx update --check and loopx update --execute after stable advances.

Validation

  • GitHub Full Public Smokes workflow dispatch passed on PR #1852: all six shards passed.
  • Local full-public sweep passed: 539/539.
  • loopx canary premerge --from-git-diff passed after rebase: selected 17, failures 0.
  • Release/version/update smokes passed locally, with dashboard browser readiness skipped because dashboard npm dependencies were not installed and dashboard code was not changed.
Assets 2
Loading