You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

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.

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

Droid finished @EffortlessSteven's task —— View job

Droid review complete — no actionable findings.

Inspected surfaces:
xtask/src/policy_report.rs — advisory check invocation, area registration, metric priority/universe lists for headline generation

Checks performed:
Diff inspected against codebase patterns for advisory check integration; doc_contracts::check(Mode::Advisory) call follows existing conventions; area registration and metric list updates are structurally correct.

Why no comments:
The diff is purely additive and follows established patterns for including a new advisory check in the policy-report workflow. No correctness, safety, registry, or state-integrity concerns. No publish-state, token-redaction, or events-as-truth surfaces touched.

Residual risk:
None identified — doc-contracts advisory mode is CI-off only per PR description; blocking promotion is deferred to future PRs.

Validation signal:
Observed: Advisory-mode check call, area tuple registration, metric priority and universe list updates.
Reported: PR description states CI wiring kept out of this PR.
Not verified: Actual doc-contracts report output at runtime — advisory mode is non-blocking by design.