Version 1.0.26

Highlights

• run_audit no longer claims an SEO audit. There is no SEO module. The scores.seo field was always a proxy built from seven crawlability and markup signals, and the description now names them: robots.txt, AI crawler access, sitemap, structured data, meta description and Open Graph tags. The field keeps its name, so existing clients are unaffected.
• Every other surface says the same. The prompts, server instructions, README, manifest, and the Codex and Cursor plugins and their skills were all updated. Their seo keyword is now aeo. A new test fails if any of them, or anything served over the MCP handshake, claims SEO again.
• get_recommendations answers any key. The API now decides what a key without Pro receives, and the tool passes through the evidence behind each fix.
• The release script finishes what it starts.
  • It waits for npm to serve the new version, then retries the MCP registry with a fresh token minted from your gh login.
  • It packs the .mcpb before publishing anything.
  • If a release does stop halfway, running the script again completes it. 1.0.25 stopped at the registry step.

What's Changed

• The release script finishes what it starts by @SpikeyCoder in #86
• get_recommendations: answer any key, pass through the evidence (card 227) by @SpikeyCoder in #87
• No surface claims an SEO audit: run_audit names what scores.seo measures by @SpikeyCoder in #88
• Bump to 1.0.26 by @SpikeyCoder in #89

Full Changelog: v1.0.25...v1.0.26