Fixed
-
v0.11.0 published to npm but was REFUSED by the MCP Registry. The registry
capsserver.jsondescription at 100 characters and returns a 422; the
0.11.0 description was 121. npm and GitHub took it, the registry did not, so
the listing stayed on 0.10.0 while npm moved to 0.11.0.The publish step is
continue-on-error— a registry outage must not fail a
release that already published — so it still showed a green tick. The only
evidence was in the step log. That is the second time a "✓" on that step has
meant nothing; the first was reading its summary line instead of its log.npm run check:countsnow asserts the length locally, so this fails before a
tag rather than after one.