verify 0.5.0

• A check can no longer pass by repeating its own input. An equals or matches rule that one argument in run already satisfies is refused, as includes already was, so a program that only echoes its argument cannot pass. A map that relied on this now asks Claude for a different input. (#140)

claude plugin marketplace update lim
claude plugin update verify@lim

• No binaries through node. A compiled .node addon or a file with NUL bytes is refused as the script node runs, as python3 scripts already were. (#140)

• Programs come from PATH only, on every system. On macOS and Linux, node, python3, and git are looked up only in absolute PATH folders, and the check's PATH loses relative entries, so a node in the repository never runs in place of the installed one. Windows already worked this way. (#140)

• "Changed after it failed" sticks. A check edited after it failed stays marked on every later run until its new definition fails once or it passes unchanged, also after removing and adding it back or running another map. review-loop no longer sees a clean run as the only evidence. (#140)

• One unreadable file no longer stops the run. A script, a file named in run, or a stdin file that cannot be read makes only that check not verified. When git cannot record the working tree, the run keeps its results and the report says review-loop cannot use it as evidence. (#140)