Add CI, drop private-repo install instructions

[johnnyrobot]

Why

Two things blocked this repo from being usable publicly: there was no build/test workflow (only a release workflow), and all install instructions required GOPRIVATE plus Git auth for a private module.

Includes both commits from ci/add-build-test-workflow, which this branch is stacked on — that branch needs no separate PR.

What changed

• Added ci.yml — build, vet, test, govulncheck on push to main and PRs.
• Aligned release.yml — pinned to Go 1.26.5 (matching CI) and added a build/vet/test gate before goreleaser publishes. Dropped the unused Homebrew tap token; this repo's goreleaser config has no brews section.
• Removed GOPRIVATE and private-repo instructions from README.md, SKILL.md, AGENTS.md and CLAUDE.md. go install now works plainly.
• Added pre-built-binary and from-source install sections to README, matching canvas-pp-cli.
• Ignore /bin/.

Verification

make build-all                    both binaries build
go vet ./... / go test ./...      clean
./bin/programmapper-cli doctor    OK config, OK auth, OK API reachable

goreleaser ldflags were already correct here (this repo always had the right module path) — verified by building with a fake version: programmapper-cli 9.9.9-ldflagtest.

Ordering note

Tagging v1.0.0 while the repo is still private produces a private release. Flip visibility to public first, then tag.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@johnnyrobot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 03ae0a34-13fd-47b4-a645-a872124d6f31

📥 Commits

Reviewing files that changed from the base of the PR and between 4b0196f and 97e7776.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (8)

• .github/workflows/ci.yml
• .github/workflows/release.yml
• .gitignore
• AGENTS.md
• CLAUDE.md
• README.md
• SKILL.md
• go.mod

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}