Verify scout checkout origins before reading

[s-hiraoku]

Summary

• require the organization scout to validate each checkout's normalized GitHub origin before fetching or reading it
• document fallback to authoritative GitHub default-branch content on mismatch
• lock the origin-verification boundary into the automation contract checks

Verification

• bash scripts/check-automation-prompt-contract.sh
• bash scripts/test-automation-prompt-contract.sh
• git diff --check

Review context

• Source issue: [scout] Verify scout checkout remotes before reading #213
• Self-review: prompt, source documentation, and executable contract assertions are aligned
• Residual risk: URL normalization is an execution instruction; this change does not introduce a new URL parser

Closes #213

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 31 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Repository: kaizen-agents-org/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f7c093ae-9350-473c-ac29-9ea2daf406cd

📥 Commits

Reviewing files that changed from the base of the PR and between 376afb0 and 15a4d9a.

📒 Files selected for processing (3)

• automations/kaizen-agents-repo-improvement-scout.prompt.md
• docs/repo-improvement-scout.md
• scripts/check-automation-prompt-contract.sh

---

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

[s-hiraoku]

Guardian final state for HEAD 59d5b54:

• GitHub reports MERGEABLE / CLEAN; PR is ready for review (not draft).
• Watched Pull Request Contracts run 31309324612; Verify organization contracts passed.
• Local verification passed: check-automation-prompt-contract.sh, test-automation-prompt-contract.sh, and git diff --check.
• Paginated feedback audit found 0 review threads and no actionable review comments.
• The Node 20 Actions annotation is pre-existing workflow maintenance outside this diff.
• Codex and CodeRabbit both reported external review-usage limits; CodeRabbit still posted a successful status but did not perform a substantive review. No code fix was required.
• Two same-head passing snapshots more than 30 seconds apart remained unchanged.

No unresolved merge blocker remains.