open-git

Summary

Add a repo .coderabbit.yaml so reviews follow AGENTS.md instead of the org ASSERTIVE / 80% docstring defaults. That mismatch is what produced the docstring warning on #398.

This branch starts from main and does not include #398.

Changes

Turn off docstring coverage and docstring / unit-test finishing touches.
Use chill reviews. Do not enable request-changes or inheritance.
Point reviews at AGENTS.md, engineering/domain notes, product standards, and the verify/ci-notes skills, with explicit applyTo so docs guidelines apply to source.
Warn on IPC contract drift, TypeScript type escapes, missing acceptance evidence, and hand-edited CHANGELOG.md.
Ignore lockfiles, generated assets, model cache, and icons.
Disable Biome, ESLint, and markdownlint (this repo uses oxlint / oxfmt).
Classify .coderabbit.yaml as frontend_tooling so it does not trip full CI.

Quote mode: "off". Unquoted YAML 1.1 parses off as boolean false, which fails the CodeRabbit schema and leaves the docstring check on.

Acceptance criteria

CodeRabbit no longer requires JSDoc or 80% docstring coverage.
Review instructions match AGENTS.md: no type escapes, IPC contracts stay in sync, Conventional Commits, no hand-edited CHANGELOG.
Changing only .coderabbit.yaml classifies as frontend_tooling.

Test plan

.coderabbit.yaml validates against coderabbit.ai/integrations/schema.v2.json (mode is the string off, not boolean false)
pnpm exec vitest run tests/ci/classify-changes.test.ts — 59 passed
pre-push: standards-route, lint, format-check, cargo-fmt-check, patch-coverage
Rust / i18n / IPC — skipped; no app or contract change
Product standards — no product surface change

Related issues

None. Follow-up to the #398 CodeRabbit pre-merge checks.

Review limit reached

[@thedavidweng](/thedavidweng), you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 seconds

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](/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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: d99cec62-c2de-4e5b-b7b9-a14cb55afb58

📥 Commits

Reviewing files that changed from the base of the PR and between 7abeba25f160c51ba3ef447f99cb07d6e306795f and ea64e8c89c6238e5169187f95a545c6cfd95f798.

📒 Files selected for processing (3)

.coderabbit.yaml
scripts/ci/classify-changes.mjs
tests/ci/classify-changes.test.ts

Status	Category	Percentage	Covered / Total
🟢	Lines	83.68% (🎯 65%)	7013 / 8380
🟢	Statements	82.85% (🎯 65%)	7430 / 8968
🟢	Functions	78.74% (🎯 60%)	1767 / 2244
🟢	Branches	76.14% (🎯 60%)	3939 / 5173

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
scripts/ci/classify-changes.mjs	53.1%	75.59%	90%	53.14%	48-49, 444-552, 570

dev / openkara

chore: add a CodeRabbit config that matches repo review rules