Deployment workflows fixed with correct npx syntax
GitHub Actions workflows and documentation examples now use the correct explicit npx invocation, fixing deployments that were silently failing with "command not found" errors.
Both the Vercel deploy workflow and GitHub Pages publish workflow were failing on main with "sh: gitpulse: command not found". The culprit: npx's shorthand resolution (npx -y @gitpulse/cli@0 analyze) tries to find a binary matching the package suffix "cli", but the actual binary is named "gitpulse". When that lookup fails, npx falls back to running sh -c gitpulse against an empty PATH — guaranteeing the command won't be found. The fix switches all occurrences to the explicit --package=<spec> <bin> <args> form: npx -y --package=@gitpulse/cli@0 gitpulse analyze. This change was applied to two workflow files (2 commands each) and seven README examples across Vercel, Netlify, Cloudflare Pages, and generic GitHub Actions sections. The Vercel workflow picks up the fix immediately; the Pages workflow requires a release-please bump to v0.1.4 before self-deploy will work.