feat(contracts): version data-rights contributor lifecycle

[seonghobae]

Outcome

Advance #55 with the first bounded cross-service contract slice: independently deployable LifeOS services can implement one versioned data-rights contributor lifecycle without granting identity-service direct database authority.

Test-first sequence

The first branch commit added a compile-time contract consumer before the contributor module existed, making @life-os/contracts typecheck fail on the missing version, request, erase and export response types. The production commits then add and export the v1 contract.

Contract

life-os.data-rights-contributor.v1 separates four operations:

• export — deterministic bounded service-owned JSON section with schema version, record count and SHA-256 evidence;
• erase_preflight — non-mutating readiness and bounded blocker evidence;
• erase — explicit opaque idempotency key plus owning-service erased-record and receipt-digest evidence;
• verify_erased — post-erasure owning-service verification evidence.

Every request carries opaque workspace, requesting-user and request UUIDs. Every response binds contributor and request identity. The shared package defines transport-neutral JSON/type contracts only; it does not create cross-service SQL, persistence, authentication, or false whole-product completion.

Scope / next slices

This PR intentionally does not implement Planning/Habit HTTP adapters, contributor authentication, erasure SQL, retry/reconciliation, artifact delivery, or final whole-product completion. After this contract is accepted, #55 can implement the first planning/habit service adapter tranche against it with real PostgreSQL multi-tenant evidence.

Acceptance

Require exact-head typecheck/build/test plus repository CI, AppGuardrail, SAST Semgrep, Security Scan, Commercial Readiness, current review findings and live-base mergeability. Active-PR behavior is not protected-main truth until integration.

Refs #55.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 56 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 99bc7e80-e838-42a9-bedd-5b90a98dfb3b

📥 Commits

Reviewing files that changed from the base of the PR and between 2c272a4 and fc717ed.

📒 Files selected for processing (3)

• packages/contracts/src/data-rights-contract.typecheck.ts
• packages/contracts/src/data-rights.ts
• packages/contracts/src/index.ts

---

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