GitHub Actions workflows and README fixed to use correct npx invocation
GitHub Actions deployments were silently failing because the CLI binary name didn't match npx's shorthand resolution. A quick syntax update to explicit `--package=` form puts deployments back on track—and prevents anyone reading the docs from hitting the same wall.
The CI/CD pipeline was broken. GitHub Actions workflows that should have been building and deploying gitpulse documentation were instead crashing with "command not found" errors — yet no one noticed until the deploy-vercel workflow started failing on main.
The culprit: npx's shorthand invocation assumes the binary name matches the package suffix. Running npx -y @gitpulse/cli@0 analyze tells npx to look for a binary named cli, find nothing, and fall back to sh -c gitpulse — which fails when PATH isn't set. The actual binary is named gitpulse.
Every invocation across two workflow files and seven README examples was corrected to use the explicit form: npx -y --package=@gitpulse/cli@0 gitpulse analyze. This tells npx exactly which package to fetch and which binary to run, sidestepping the suffix-matching behavior entirely.
The deploy-vercel.yml fix takes effect immediately since it lives on main. The publish-pages.yaml fix requires one more release cycle — a separate self-deploy workflow pins to the @v0 tag, which still points to 0.1.3. Merging this PR triggers release-please to propose 0.1.4; once that ships, the floating tag advances and self-deploy recovers. The README corrections prevent future readers from copying broken commands into their own configurations.