test: align send-budget default assertion with shipped 20x/200 cap

[jithin23-kv]

Problem

runners/cli/tests/fork.test.ts fails on master, so the CLI test suite is red (28/29). CI does not surface this because the test job runs only the core and sdk workspaces — the CLI suite is never executed.

Root cause

The test asserted BudgetGuard send-budget defaults of 300 (50× budgetUsd) and 400 (no budget), but the shipped code in core/src/autonomous/lib/budget.ts:64 uses 20× budgetUsd (else 200):

this.maxTotalSends =
  opts.maxTotalSends ?? (opts.budgetUsd ? Math.ceil(opts.budgetUsd * 20) : 200);

So budgetUsd: 6 → 120 (not 300) and no-budget → 200 (not 400).

Change

Test-only. Assertions + test name updated to match the shipped 20×/200 behaviour (the lower, intended spend ceiling). No production code touched.

How verified

• npm test --workspace=@keyvaluesystems/agent-opfor-cli → green (was failing)
• npm run typecheck · npm run lint · npm run format:check → pass
• Committed with the full pre-commit hook (typecheck/lint/format/catalog/validate-skills/gitleaks), no --no-verify.

Follow-ups (separate PRs)

• Run the CLI + MCP workspaces in CI so this class of regression is caught.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 53 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cc41998b-d90d-45fd-8258-1c2f41b8361d

📥 Commits

Reviewing files that changed from the base of the PR and between 55596b3 and 3b10aac.

📒 Files selected for processing (1)

• runners/cli/tests/fork.test.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch test/align-send-budget-default

---

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.}