docs: document incompatibleWith authoring rules in AUTHORING.md (fixes #119)

[emberb170d]

Adds 5 detailed authoring rules for incompatibleWith declarations with checklist for new entries

[coderabbitai]

Warning

Review limit reached

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

Next review available in:59 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7166860b-459f-40fd-9436-8f4750703082

📥 Commits

Reviewing files that changed from the base of the PR and between 62aacc3 and 79055f7.

📒 Files selected for processing (1)

• docs/AUTHORING.md

---

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

[ulises-jeremias]

Thanks — rules 1–4 and the checklist are what we needed for #119.

One blocker before merge: templates.json is strict JSON (templates.schema.json), so rule 5 cannot ask for inline comments next to incompatibleWith. Please reword that rule to put the colliding paths in the PR description, AUTHORING, or AI_ML_AUTHORING.md. After that this can squash-merge as-is.

I would have pushed the wording myself; the fork did not accept a maintainer push.