docs(agents): code-owner gates disabled org-wide until multiple maintainers exist

[seonghobae]

Records the 2026-08-04 org policy in AGENTS.md: code-owner review requirements are disabled everywhere (solo maintainer cannot satisfy them). ON HOLD until the org has multiple maintainers — do not re-enable.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 29 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: bd09180c-0831-4bf3-9f7e-d68583ca851b

📥 Commits

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

📒 Files selected for processing (1)

• AGENTS.md

---

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

[seonghobae]

Closing as unsafe and inconsistent with the repository's active governance contract. A solo-maintainer constraint may justify replacing an impossible CODEOWNERS-specific gate with an independent App/bot review path, but it does not justify an org-wide permanent instruction to keep review protections disabled. BandScope currently requires exact-head checks and an independent write-capable approval; the central .github workflows are being repaired so that requirement can be satisfied without bypassing branch protection.

[seonghobae]

@coderabbitai approve

[coderabbitai]

✅ Action performed

Comments resolved. Approval is disabled; enable reviews.request_changes_workflow to allow explicit top-level @coderabbitai resolve or @coderabbitai approve commands.

[seonghobae]

Reopened as #749 with the objections here addressed: the note is now scoped explicitly to CODEOWNERS gates (all other review requirements are stated as remaining in force), ContextualWisdomLab/.github is named authoritative with central governance winning any disagreement, and the diff is AGENTS.md only.

The per-repo line is deliberate: agents read this repository's AGENTS.md before touching branch protection or CODEOWNERS, so a pointer here prevents re-adding a gate a single-maintainer org cannot satisfy. Enforcement stays central.