chore: disable CodeRabbit docstring coverage

[M4n5ter]

Summary

Disable CodeRabbit's built-in docstring coverage pre-merge check.

The check applies a generic 80% documentation threshold to changed code elements. That threshold does not match this TypeScript and mixed-language repository's documentation conventions and has produced low-signal warnings, including 0% coverage on otherwise normal changes. Disabling it removes that noise without changing the title, description, issue-assessment, or custom AI-use checks.

Verification

• Parsed .coderabbit.yaml successfully with Ruby/Psych.
• git diff --check passes.
• No application tests were run because this change only affects CodeRabbit configuration.

AI use

Select exactly one:

• No generative tool made a substantive contribution
• Generative tooling made a substantive contribution

Tool(s) and scope: Codex investigated the built-in pre-merge checks, edited the CodeRabbit configuration, validated the YAML, and prepared this PR.

Checklist

• Tests cover the change and fail without it
• Lint, format, typecheck and the affected suites pass locally

Does this PR entail a change in behavior?

• Yes — described under Summary above
• No

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 26a1777f-ca08-4686-abe8-db3eeafbc092

📥 Commits

Reviewing files that changed from the base of the PR and between a75640f and 60dd451.

📒 Files selected for processing (1)

• .coderabbit.yaml

---

📝 Walkthrough

Summary

• Disables CodeRabbit’s generic 80% docstrings pre-merge check.
• Preserves the existing title, description, issue-assessment, and custom AI-use checks.
• Updates the existing CodeRabbit configuration. It does not create a parallel documentation path.
• The two-line change is the smallest coherent solution. It adds no application complexity.
• No source code, tests, or regression coverage can be removed or simplified.

Validation and risks

• The YAML parsed successfully.
• git diff --check passed.
• Application tests were not run because the change only affects CodeRabbit configuration.
• The required-check status remains unverified without direct CI evidence.

Review-relevant risks

No protected-area effect was identified in the current diff. The person performing the merge reviews the final diff, and a maintainer makes the final determination.

Walkthrough

The repository configuration adds the docstrings pre-merge check and sets its mode to off.

Changes

Pre-merge check configuration

Layer / File(s)	Summary
Configure docstrings check .coderabbit.yaml	The configuration adds pre_merge_checks.docstrings and disables the check.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: astro-han

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/disable-coderabbit-docstrings

---

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

[M4n5ter]

Fast-path assessment for final revision 60dd451d7:

• The diff is limited to two lines in .coderabbit.yaml, disabling only CodeRabbit's built-in docstring coverage warning.
• It is low impact and easy to reverse.
• It does not affect user-visible behavior, public contracts, security, licensing, releases, or governance. In particular, it does not change required checks or the repository's human-review policy.
• The YAML parses successfully and git diff --check passes. The application CI jobs do not exercise this CodeRabbit-only configuration and cannot be affected by the change.

This revision is eligible for the fast path once the required checks complete. Any later commit requires a fresh assessment and comment; a maintainer makes the final determination.