deps: repoint lance-graph-ontology ogar-vocab to OGAR main

[AdaWorldAPI]

What

Post-merge cleanup after OGAR #91 landed the HealthcarePort + 0x09XX Health codebook on OGAR main.

crates/lance-graph-ontology/Cargo.toml was the lone holdout still pinning ogar-vocab to the OGAR claude/medcare-bridge-lance-graph-wmx76z branch, while its siblings (lance-graph-ogar, cognitive-stack, symbiont) already track main. That split risked two ogar-vocab versions in one graph — the duplicate-crate / "patch not used" hazard the P0 dep policy warns about. This repoints the ontology crate to main so all four resolve to one OGAR source.

Also sweeps up ffd6883 (a test-only temp-dir cleanup that the #582 merge missed — it was pushed to the branch after the merge captured the head).

Commits

• ffd6883 — fix(medcare_bridge): drop the test temp dir instead of mem::forget (CodeRabbit, orphaned after MedcareBridge = UnifiedBridge<HealthcarePort> + FieldMask role projection + Fisher-z clamp fix #582 merged).
• 15f4031 — deps: lance-graph-ontology ogar-vocab branch → main; Cargo.lock re-resolved to OGAR main (rev 19a6886e).

Tests

cargo build -p lance-graph-ontology clean · 31 bridges:: tests green against ogar-vocab@main.

Coordinated with

• medcare-rs# — repoints its root ogar-vocab dep to main next (must land after this, since medcare CI builds against lance-graph main).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EYvNjD8M8LMNYbRy3gq2FP

---

Generated by Claude Code

[chatgpt-codex-connector]

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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Warning

Review limit reached

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

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

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ 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 refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 528a563c-6144-4e2e-9e27-32d109b5ec87

📥 Commits

Reviewing files that changed from the base of the PR and between 52edeb0 and 15f4031.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• crates/lance-graph-ontology/Cargo.toml
• crates/lance-graph-ontology/src/bridges/medcare_bridge.rs

---

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 and usage tips.}