miqdadbadjuber/anti-slop v3.2.23

v3.2.23: the plugin-door probes report the newest copy

on GitHub

The installer could name a plugin copy's update command, but the version it printed was whichever copy the filesystem listed first. On a machine that kept an old copy beside a new one, that could be 3.2.9 while 3.2.22 was installed. Folder order decides this, not the operating system, so the same report appeared on macOS and Windows.

The newest copy wins

The Kimi Code, Cline, and Oh My Pi probes now read every copy in their store and report the highest version, the rule Oh My Pi's cache path already used. Two more bugs came out of the same run:

• Codex compared versions as text, so 3.2.9 ranked above 3.2.22. It now compares them as numbers.
• --update run from the home folder treated home as a project. Every global folder was updated twice, and ~/CLAUDE.md, ~/AGENTS.md, and ~/GEMINI.md were created with a pointer that every agent then loads in every project. It now updates each global folder once and writes no pointer there.

What is verified

New smoke checks cover all three: a store with an old copy that sorts first, Codex's text-versus-number order, and --update from a home directory. All three fail against v3.2.22 and pass on this release. CI runs them on Linux, Windows, and macOS, and the contributor ran the suite on macOS 26.6.2 with Node 22.22.3.

Updating is unchanged:

npx antislop-ai --update

A plugin keeps its own copy, so update it through the agent that installed it. Skills load when a session starts, so start a new one afterwards. Full detail is in the ROADMAP. Thanks to @fajarhide for finding all three and for the fix in #47.