Repository navigation
README version badge says 0.1.0 (plugin is 0.5.3); README never mentions the marketplace install route; CHANGELOG lacks 0.5.x headings #73
Description
Found by the 2026-10-12 clownware.org copy audit. Evidence on main @ 6fd2f1a.
README.md:5version badge reads0.1.0;plugin/.claude-plugin/plugin.jsonis0.5.3.README.md:39documents onlyclaude plugin install --plugin-dir ./plugin. The marketing site and clownware/plugins README install it with/plugin marketplace add clownware/plugins+/plugin install product-dev@clownware; the README should show that route too.CHANGELOG.mdhas "Plugin 0.5.1/0.5.2/0.5.3" lines under Unreleased but no[0.5.x]release headings; the clownware/plugins marketplace description still headlines v0.5.0 (filed there separately).- No GitHub releases exist (only tag
pre-contract-2025-11-16), so the website's "Latest release" fact strip cannot render for this product (ADR-063 pull model). A tagged release would light it up.
Everything else on the product page checked out: six commands, five skills, two subagents, 20 validation checks in validate_spec.py, Apache-2.0, tea-tracker example.
Activity
chrispezza commentedon Oct 13, 2026
Addressed in #75 and release v0.5.4. Each claim was checked against the repo first.
plugin.jsonagain./plugin marketplace add clownware/pluginsand/plugin install product-dev@clownware, plus the terminal form. The previous command,claude plugin install --plugin-dir ./plugin, used a flag thatclaude plugin installdoes not have; development use is nowclaude --plugin-dir ./plugin.plugin.jsonhistory and the ADRs and are marked as such. The same test requires a heading for the current version.v0.5.4is tagged onmainand marked latest, so the website's fact strip has something to pull./optimizeto the README command table.Not done here: the marketplace description in
clownware/pluginsstill headlines v0.5.0, which the issue says is filed there. The marketplace entry installs frommainof this repo, so users already receive 0.5.4.