[EgorPPS]

What changed

• adds W3DS schemas for Task, Company, Project, ContributorCapacity, TaskReference, TaskNote, TaskAttachment, Membership, and CompanyProjectLink
• models canonical memberships and user-vault membership references as two forms of the same Membership ontology
• extends the existing CalendarEvent schema with optional provider, ownership, access, presentation, and synchronization fields
• keeps the canonical CalendarEvent fields title, start, and end unchanged and required

Why

80hours stores these MetaEnvelope types in W3DS eVaults, but their schema IDs were not yet published by the Ontology service. CalendarEvent data also needs richer optional metadata without introducing a duplicate calendar ontology.

Compatibility

The CalendarEvent change is additive: existing payloads containing title, start, and end remain valid. No existing schema ID is replaced.

Validation

• parsed every schema as JSON and checked schema ID uniqueness
• compiled all Ontology service schemas with AJV draft-07 in the service-compatible non-strict mode
• validated representative 80hours payloads for all nine new schemas, both Membership variants, and CalendarEvent using AJV with format validation
• started the Ontology service locally; it loaded 27 schemas and returned all nine new IDs through /schemas and /schemas/:id

[coderabbitai]

Warning

Review limit reached

@coodos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 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: a3bde5eb-0c2f-4b1e-9f5b-a54af50a68ed

📥 Commits

Reviewing files that changed from the base of the PR and between 77eb934 and eabd9d1.

📒 Files selected for processing (10)

• services/ontology/schemas/calendarEvent.json
• services/ontology/schemas/company.json
• services/ontology/schemas/companyProjectLink.json
• services/ontology/schemas/contributorCapacity.json
• services/ontology/schemas/membership.json
• services/ontology/schemas/project.json
• services/ontology/schemas/task.json
• services/ontology/schemas/taskAttachment.json
• services/ontology/schemas/taskNote.json
• services/ontology/schemas/taskReference.json

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