chore(gates): rebuild agent-device.dev after each stable release
Summary
agent-device.dev builds /.well-known/mcp.json with the npm latest version read at build time. A stable release is a tag push, which builds nothing on Vercel, so the manifest stayed one version behind until the next site change on main.
A redeploy-site job in release.yml now calls the site's Vercel deploy hook after publish, for stable releases only. The hook ("release", production build of main) and the repository secret VERCEL_SITE_DEPLOY_HOOK already exist. The mcp.json route's comment now says how the version follows releases.
2 files: release.yml and the mcp.json route comment.
Validation
At 07a27b9, pnpm check:affected --run --head HEAD passed every runnable check (fail-open full set). The workflow tests (15/15), the release-plan and release-version tests (16/16) and the gate manifest pass. The hook was triggered once by hand: Vercel built a production deployment of main labelled "release" (READY), and agent-device.dev then served mcp.json with 0.21.33, the current npm latest. The job itself first runs on the next stable release.
š¤ Generated with Claude Code