review-loop 0.11.0

• Windows. review-loop runs on Windows: checks find their program through PATH and PATHEXT, npm and other .cmd programs run through cmd.exe with safe quoting, Gradle and Maven use gradlew.bat and mvnw.cmd, and the commit gate reads Git Bash paths such as /c/repo. Programs, including git, are started from PATH only, never from the repository folder. A Windows job in CI runs every test. (#112)

claude plugin marketplace update lim
claude plugin update review-loop@lim

• Unattended reviews fix things. Whole headless sessions showed that an unattended review deferred every finding and fixed nothing. Now the reviewer's touchesTests flag no longer counts the regression test every fix gets, a finding whose only question is which fix to use gets the smallest one (logged), deferred findings go to the next reviewer, and a failing check that waits stays one finding. In the same session as before, an unattended review now reproduces the bug with verify, fixes it, proves it with a regression test, reruns the verify check, and resolves it as measured. (#114)

• No silent no-op rounds. loop next refuses when nothing changed since the review. When nothing should change, such as a finding you chose to keep or a check that fails only because of the environment, loop next --unchanged "<why>" continues and logs the reason. (#114)

• Measured. 215 behaviors in evals/review-loop/behaviors.csv, 204 checked by unit tests in CI on Linux and Windows. On the detection benchmark the reviewer still found 36 of 36 and 30 of 30 seeded bugs, and set touchesTests on 0 of 100 P1 or P2 findings, against 29 of 50 before.