YawLabs/tailscale-mcp v0.20.0 on GitHub

Documentation and release tooling only; no change to the published package's behavior.

README: the X follow badge moved from the top of the page to the bottom, so the description leads on npm and GitHub (#57).
release.sh waits for npm to serve the new version before the MCP Registry step. npm publish returns as soon as the registry accepts the tarball, but the version is not yet readable from npm's CDN-backed read path, and the MCP Registry validates a version by reading it -- so a registry publish straight after npm publish could fail with version '<x.y.z>' was not found (status: 404) and need a re-run (ssh-mcp 0.15.3 did; aws-mcp did on three consecutive releases). The gate polls the exact URL the registry's npm validator fetches, with curl rather than npm view, whose metadata cache could outlast the wait; it warns rather than fails on timeout so mcp-publisher still reports its own precise error; SKIP_NPM_WAIT=1 bypasses it and NPM_WAIT_TIMEOUT_S retunes the 300s default (#56).