Require the CLA gate status check on world-at-ruin

[devantler]

🤖 Generated by the Daily AI Engineer

Evidence: world-at-ruin#35 delivered a first-party CLA gate (CLA gate check from .github/workflows/cla.yaml) that blocks external PRs until their author signs CLA.md (world-at-ruin#2). The check currently fails red on unsigned external PRs but is not required by the repo's ruleset, so a merge is technically possible while it is red.
Audience/problem: the maintainer and agents relying on the CLA legal gate being unbypassable; today it depends on reviewer discipline (agents never merge external PRs per the trust gate, but the ruleset should encode it).
Proposed: add CLA gate to world-at-ruin's required status checks in the declarative org config (note: required_status_checks rulesets have historically been UI-created + Observe-imported — follow that established path).
Acceptance: an external (non-allowlisted) PR with a red CLA gate check cannot be merged; trusted-author PRs are unaffected (the check passes instantly via the allowlist).
Size: small.

[coderabbitai]

🔗 Related PRs

#74 - feat(rulesets): require the CodeRabbit review status check org-wide [merged]
#75 - revert(rulesets): drop the provider-uncreatable CodeRabbit required-check ruleset [merged]
#92 - docs: complete agent and deploy contributor guidance [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!