docs: add capabilities, notes, SSO

[pratyush618]

Final slice of the docs SDK-parity work: getting-started capability coverage and two missing per-SDK guides. Every feature verified against SDK source. 4 commits.

Getting-started capabilities

• Python: surface pub/sub, distributed locks, mesh, predicates, interception (all ship; the page under-listed them).
• Java: add the Circuit Breakers row (feature ships; only Node advertised it).

New guides

• Java notes: structured-notes guide (EnqueueOptions.builder().notes(...), 15-field/64-key/500-value/depth-3/4 KiB limits, Job.notesMap(), dashboard rendering) — the feature shipped undocumented for Java.
• Node SSO: dashboard OAuth/OIDC guide (Google/GitHub/generic OIDC, allowlists, OAuth-only mode, security model, env-var reference) — mirrors the Java SSO page, Node-accurate (built-in node:crypto, no JOSE dependency; serveDashboard({ authEnabled }) wiring).

Parity gate, typecheck, and static build all pass.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Run ID: 9ae2e574-b3d9-4602-9d45-33c8fd6a2192

📥 Commits

Reviewing files that changed from the base of the PR and between fe0c249 and 577b197.

📒 Files selected for processing (6)

• docs/content/docs/java/getting-started/capabilities.mdx
• docs/content/docs/java/guides/observability/meta.json
• docs/content/docs/java/guides/observability/notes.mdx
• docs/content/docs/node/guides/operations/meta.json
• docs/content/docs/node/guides/operations/sso.mdx
• docs/content/docs/python/getting-started/capabilities.mdx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/parity-onboarding

---

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