Release plugin removed, pipeline unblocked
Monorepo releases should flow freely again after removing a plugin that was blocking version bumps when only one package had changes.
The release pipeline had become stuck. After a prior PR merged, the v0.1.2 release was never actually created on GitHub or npm—only the root package had new commits, while the CLI had none. The linked-versions plugin requires all linked packages to change simultaneously; when one is idle, the whole group deadlocks with a "0 candidates" error.
This fix removes the linked-versions plugin from the release configuration. Root and CLI will now release independently, which resolves the deadlock. They still share the same version tag namespace, so in practice they move together since most commits touch both packages.
The release workflow was also updated to handle the new reality: without linked-versions, release-please-action emits per-package outputs again. The publish and tag-move jobs now gate on the CLI-specific release output rather than the bare top-level output. This prevents publish-cli from attempting to republish the CLI at its already-published version during root-only releases, which would cause npm 403 errors and noisy CI failures.
A minor documentation fix was also applied: the CLI help text now correctly references the "none" sentinel for Vercel/Netlify deployments, matching the resolver in the Next.js config and README.