Skip to content

lean-forge 2.0.2

Choose a tag to compare

View all tags
@beyondworks beyondworks released this 22 Sep 07:38
· 7 commits to main since this release
v2.0.2
f830f12

Fix: a turn that only explained something no longer opens the gate for the next request.

Before 2.0.2, any turn that ended without edits counted as "the agent asked", so the next message was treated as an answer and file edits opened without triage. After a plain question ("what does total do?"), a new, vague feature request could slip through.

Now the message that follows such a turn is judged by Jev: is it a reply to that turn, or a new request? A reply opens the gate as before; a new request is triaged from scratch. Calibrated on 10 exchanges (replies ≥ 0.79, new requests ≤ 0.24; threshold 0.5). If Jev is unavailable, the message counts as a reply (2.0.1 behavior).

  • hooks/test_forge.py gains the case; it fails on 2.0.1 and passes on 2.0.2.
  • README state diagrams show the new transition.
Assets 2
Loading