Your install now says which version it is
Nothing inside an antislop folder recorded which release it came from. That made
"compare the current version against what you have" a sentence with nothing to compare
against, and it left the installer asking you to choose without naming either side.
Every install route now copies a VERSION file inside the antislop folder, written
from cli/package.json by sync-skills. That reaches the installer, the skills
directory, the plugin doors, and a manual copy alike, because they all copy the same
folder. The installer reads it back and prints both versions before it asks:
▲ Already here: antislop 3.2.10. This installer carries 3.2.13.
A folder with no VERSION file predates the stamp, and the prompt says that rather
than inventing a number. --version reads the same source, which let cli/index.mjs
drop the version string it used to carry by hand.
One consequence is deliberate: skills/antislop/VERSION is generated, so a version
bump now needs node cli/scripts/sync-skills.mjs before the commit, or check-repo
fails. That is the point of putting a generated file in the version check.
Fenced examples in your entry file survive an install
Reported by @CBOSSX. scanMarkers accepted any line starting with three backticks as a
closing fence, including one carrying an info string, three backticks followed by js.
That line closed the block it sat inside, so the marker comments below it were read as
real ones. Installing antislop into a project whose entry file documents antislop with a
fenced example replaced the example with the pointer block.
A closing fence may be followed only by spaces or tabs, which is CommonMark's rule and
not a heuristic. The regression covers backtick and tilde fences and reinstall
stability, and it fails on the old code.
The README has an Update section
It was the one question the README never answered. There is now one row per route,
sitting next to the install commands it mirrors, and antislop.md carries the same
answer, so an agent asked in a session can reply without sending you to a comment
threads.
Kimi Code was run for real
v3.2.12 shipped that door on the vendor's documentation and moved the live check into
this slot. It was run after release by @fajarhide, who runs Kimi Code and opened the
issue the door came from, and it works. That is a report from a real install rather
than a probe a maintainer logged, so it is recorded as the weaker of the two kinds of
evidence.
Full detail is in the ROADMAP.