Release pipeline unblocked with plugin removal
Dropped a deadlock-causing release plugin and fixed workflow gating so the CLI package finally reaches npm when only root gets released.
The monorepo's release pipeline had frozen. When only one package (root) had new commits since the prior release, the linked-versions release-please plugin reported "0 candidates" and prevented any release from being created. The v0.1.2 release was never published to GitHub or npm — the fix was merged but nothing shipped.
The plugin has been removed so root and cli packages release independently. They still share the v<X.Y.Z> tag namespace via include-component-in-tag: false, and they move together in practice because most commits touch both. Now a one-sided release no longer deadlocks the pipeline.
Additionally, the workflow was updated to gate downstream jobs on cli_release_created rather than the bare release_created output. This prevents publish-cli from firing on root-only releases and hitting an npm 403 error when trying to republish the CLI at its already-published version.
In the CLI itself, the --help text for GITPULSE_BASE_PATH was corrected to reference "none" instead of "" for Vercel/Netlify deployments, aligning with the actual resolver logic in next.config.js.