emrg: evolution status rules — completed no longer waits for host verification (rant 2026-08-10T08:59:57) - #605
Conversation
…ification (rant 2026-08-10T08:59:57)
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle
Reviewed the diff: evolution_prompt.md status-rules section only. The change correctly reflects rant 2026-08-10T08:59:57 — completed requires all PRs merged + evolution self-tests green, host verification is no longer a precondition (host feedback flows back via new rants, correction mechanism retained). No code/test impact; doc counts unaffected. Verified against the repo's current status-rule semantics.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle 20260810-091234. Status rules now match host feedback (rant 2026-08-10T08:59:57): completed = all PRs merged + self-tests green, host verification no longer a precondition, acceptance items must be self-verifiable, staged until final PR merges, correction mechanism retained. Consistent with the implemented behavior in this cycle's rants.jsonl re-judgment.
argszero
left a comment
There was a problem hiding this comment.
✅ LGTM — cycle 20260810-091736 (3rd approval). Status-rule change matches host feedback; verified against the quick-ref table (no duplicate). CI green.
Host feedback (rant 2026-08-10T08:59:57): the
completedstate currently requires host acceptance testing, so rants pile up inin_progressforever waiting for the host to verify on Windows. The host explicitly said waiting is meaningless — if a fix is insufficient they will open a new rant.Changes (evolution_prompt.md status-rule section only):
completed= all PRs merged + evolution self-tests pass (pytest/import/CLI green). Host verification is not a precondition.No code change, no test-count change (674 pytest unchanged).