feat(identity): add tenant-scoped data-rights status lookup

[seonghobae]

Intent

Advance #55 with the tenant-scoped persistence primitive required by the authenticated data-rights status resource. This is the clean current-main successor to #143 after calendar trusted-context hardening moved protected main.

TDD evidence carried forward

The predecessor RED contract proved PostgresDataRightsRequestLedger.getRequest was missing. This successor contains the same bounded implementation and regression tests directly on protected main eb4ff993a6c8f948377d68d186130c149f370154.

Implemented

• validated UUIDv4 request/workspace/requesting-user status lookup
• one fixed parameterized PostgreSQL query scoped simultaneously by request ID, workspace ID and requesting user ID
• inaccessible/cross-tenant lookup returns undefined without disclosing existence
• malformed identifiers fail before SQL
• duplicate persisted rows fail closed as persistence corruption
• existing immutable request/terminal-receipt behavior remains unchanged

Scope

This is a persistence primitive only. It does not yet expose the authenticated public status endpoint or complete whole-product export/erasure orchestration under #55.

Verification

The equivalent predecessor exact head passed CI, AppGuardrail, Semgrep, Security Scan and Commercial Readiness before its base became stale. Those results are historical only. This clean successor must pass its own exact-head checks/review before merge.

Refs #55 and supersedes #143.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 1 minute

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: 6d133bc8-f919-489c-81d4-3927eb9cc295

📥 Commits

Reviewing files that changed from the base of the PR and between eb4ff99 and 0132e4c.

📒 Files selected for processing (2)

• apps/identity-service/src/data-rights-request-ledger.test.ts
• apps/identity-service/src/data-rights-request-ledger.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.}