ci(docs): docs-gates workflow + DOCS_MAP generator (split 1/4 of #1317)

[SharedQA]

Split out of #1317 (which is too large to review as one — docs / security / helm / release). This is the docs slice.

What

• .github/workflows/docs-gates.yml — blocking docs gate: every component/domain has specs/PRD.md+specs/DESIGN.md, they follow the canonical template, are registered in cypilot/config/artifacts.toml, and docs/DOCS_MAP.md is fresh. Exceptions via docs/.docs-gate-waivers (reason + expiry).
• scripts/ci/docs_map.py — the map generator + --check.
• docs/DOCS_MAP.md (regenerated against current main), docs/.docs-gate-waivers.

Notes

• CI runs python3 scripts/ci/docs_map.py --check directly (not make docs-check), so this PR carries no Makefile — that stays in the ci: release train + coverage ratchet (release slice; split from the omnibus) #1317 release slice. Same command, zero CI/local drift.
• Self-standing: no security/helm/release files here.
• Part of splitting ci: release train + coverage ratchet (release slice; split from the omnibus) #1317; ci: release train + coverage ratchet (release slice; split from the omnibus) #1317 will keep the release-train + coverage slice.

[coderabbitai]

Warning

Review limit reached

@SharedQA, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 57 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

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

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cb851ac4-d6f7-4e50-9a74-f5684eaab51f

📥 Commits

Reviewing files that changed from the base of the PR and between bf8a620 and 5c0dcec.

📒 Files selected for processing (4)

• .github/workflows/docs-gates.yml
• docs/.docs-gate-waivers
• docs/DOCS_MAP.md
• scripts/ci/docs_map.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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