docs: add Cursor Cloud setup notes to AGENTS.md

[bschellenberger2600]

Summary

Sets up and verifies the development environment for git-rain and records durable, non-obvious caveats for future Cloud Agents in AGENTS.md under ## Cursor Cloud specific instructions. No application code changed.

Why this change?

Future agents start in a VM with the update script (go mod download) already run. The notes capture environment gotchas that are not obvious from README/Makefile: make lint is only go vet (CI also runs golangci-lint + shellcheck), make test-race is slow because internal/git shells out to real git, and running the CLI persists registry/config state (so use --path <sandbox> for isolated runs).

Bug Reproducibility (if this fixes a bug)

N/A — environment setup only.

Tests

• I added or updated tests for all code changes in this PR.
• For bug fixes, I added regression coverage.
• I ran go test -race -count=1 ./....
• I ran go vet ./....

Verified in this environment:

• make build — built ./git-rain
• make lint (go vet ./...) — clean
• golangci-lint run --timeout=5m (v2.11.4) — 0 issues
• shellcheck scripts/install.sh — clean
• make test-race — all packages pass
• End-to-end: git-rain --sync fast-forwarded a local clone to an upstream commit

git_rain_hello_world.log

Risk / Rollback Notes (optional)

Docs-only change; revert the commit to roll back.

  

[coderabbitai]

Warning

Review limit reached

@bschellenberger2600, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 48 minutes and 25 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d9b7a060-9818-4a43-8fa9-fcc68cb273f9

📥 Commits

Reviewing files that changed from the base of the PR and between 3af70fd and 851fd9a.

📒 Files selected for processing (1)

• AGENTS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/setup-dev-environment-0d13

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cursor]

Cursor Bugbot completed successfully, but no corresponding Cursor[bot] review comment was found — withholding approval until that signal is present. Human review is still required; no reviewers were assigned because the only repo collaborator is the PR author.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}