docs(agents): note CODEOWNERS gates are off until the org has multiple maintainers

[seonghobae]

Documentation-only. Replaces #747, addressing every objection raised there.

What changed vs #747

• Scope narrowed to CODEOWNERS gates only. The note now states explicitly that all other review requirements — independent write-capable approval, required status checks, exact-head evidence — remain in force. It is not, and does not read as, an instruction to keep review protections disabled.
• Non-authoritative by construction. ContextualWisdomLab/.github is named as the authoritative source for the policy and its re-enable criteria; the note says central governance wins on any disagreement. It exists so agents working in this repo do not re-introduce an unsatisfiable gate.
• Policy-only diff. This branch touches AGENTS.md and nothing else — no dependency, lockfile, or Semgrep changes rode along this time.

Why keep a per-repo line at all: agents read this repo's AGENTS.md, not the org's, before proposing branch-protection or CODEOWNERS changes. A one-paragraph pointer prevents re-adding a gate that a single-maintainer org can never satisfy, while leaving enforcement entirely to central governance.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 23 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 Plus

Run ID: 16afb827-bc3e-45a1-a2ad-ea9da9a1ef79

📥 Commits

Reviewing files that changed from the base of the PR and between acdbea6 and eed0ee1.

📒 Files selected for processing (1)

• AGENTS.md

---

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

[seonghobae]

Closing this repository-local policy PR to keep CODEOWNERS policy centralized in ContextualWisdomLab/.github#740 and avoid a second documentation authority that can drift. BandScope’s product and merge protections remain unchanged; the central policy explicitly preserves independent current-head approval, required checks, and unresolved-thread gates.