With v2 becoming the stable release, v1.x moves from the site root to
/v1/ and stops deploying the site itself: the combined site is built and
deployed from main, which builds this branch's docs into /v1/ via the
new scripts/docs/build.sh. A `docs` CI job runs that same script, so a
change that breaks the v1 docs fails on this branch rather than at
main's next deploy. site_url and the package's Documentation URL move to
/v1/ so canonical links, the sitemap, and llms.txt point at where these
pages are actually served.
The README and landing page now describe v1.x as the maintenance line
and send new users to the v2 docs, and every install line pins `mcp<2`
so a reader following these docs stays on the 1.x line now that an
unpinned install selects 2.x.
Max Isbey