Skip to content

Releases: HoMuChen/loop-engineering

Release list

v0.2.0

Choose a tag to compare

@HoMuChen HoMuChen released this 09 Jul 04:20

First tagged release of the Loop Engineering plugin (Claude Code + Codex).

Highlights

Product OS ↔ GitHub Milestones

  • Milestones now map one-to-one to Product OS features (milestone title = feature id). loop-split-feature groups a feature's work-item issues under its milestone; loop-product-review reads milestone completion as a fact; loop-close flags a feature as release-ready when its milestone is 100% closed.

Pipeline reliability

  • Label bootstrap: loop_labels.py ensure idempotently upserts the full loop label set, so a fresh repository no longer fails its first labeling call.
  • Blocked recovery: loop-recover sweeps loop:blocked issues and returns them to loop:ready once a human has answered and no protected label remains — closing the only permanent dead end.
  • Repairing hand-off: loop-engineer-issue prioritizes resuming loop:repairing issues (reusing the existing worktree) over new work, so review fixes no longer wait a full stale window.
  • Repair budget survives hand-off: repair counts live in the run comment and are enforced against local_repair_limit / pr_repair_limit across stale-and-reassign.
  • Heartbeat contract: long healthy runs refresh their run comment so they are not misjudged stale and reassigned mid-flight.
  • Verification vacuum: when required_verification is empty, the loop infers repo checks and otherwise states "no verification" explicitly instead of implying success.
  • Same-issue double-claim: run-comment tiebreak prevents two agents building one issue.

Product OS write-back

  • loop_product_os.py work-item records execution facts (status, issue/PR links) back into .product/, so the product layer stops drifting from GitHub state.

Portability

  • All skills reference bundled scripts, references, and templates via ${CLAUDE_PLUGIN_ROOT}, so the loop resolves helper paths correctly when run against a target repo. Codex handling documented explicitly.

All changes are backward compatible. See the commit history for details.