v0.13.7

Fixed

• release.sh reads npm's per-version document and retries the MCP Registry
  publish. Every "is x.y.z on npm?" check -- the step-5 skip, the CI hand-off
  poll, the npm propagation wait and the step-8 verify -- now goes through one
  helper that reads the per-version document the MCP Registry's validator
  fetches, not npm view's whole packument, which Cloudflare's edge can serve
  up to 5 minutes stale after a publish. A re-run whose npm publish still
  gets npm's E403 "cannot publish over the previously published versions"
  treats the version as published instead of failing with the token-error
  message. The MCP Registry publish is attempted up to four times, 30/60/90 s
  apart, but only on the answers waiting cures -- the version not found yet,
  "Likely transient, retry later", a failed npm metadata fetch, or the
  registry's own HTTP 429, 502, 503 or 504 -- with a fresh registry login
  before each retry; any other error still fails at once, and a
  duplicate-version answer counts as done.

Documentation

• The README's Add to Yaw MCP button now sits directly under the title, and
  the follow badge links to @YawLabs. The one-click install button and its
  one-line caption moved up from further down the page, so they are the first
  thing under the name on npm and GitHub, and the X badge at the bottom points
  at @YawLabs instead of @TokenLimitNews. npm shows the
  README from the published package, which is why it takes a release to carry
  this there; the package's code is unchanged from 0.13.6.