feat(identity): expose authenticated data-rights status API

[seonghobae]

Intent

Advance issue #55 from the protected-main tenant-scoped request lookup in #144 to a real authenticated public status resource without claiming complete export/erasure orchestration.

Test-first evidence

The PR began with focused application/controller regressions that failed because the production status application and HTTP controller did not exist. A later runtime-composition regression also exposed the missing production wiring. After implementation, the exact current head 0a1ae988a0975e6ed51bf7d180cd111c2a6556f1 passes CI, AppGuardrail, SAST Semgrep, Security Scan and Commercial Readiness.

Implementation

• derives workspace/requesting-user scope only from the validated opaque server session
• calls the durable request ledger with request ID + session workspace + session user
• returns only schemaVersion, request ID, request kind, lifecycle status and timestamps
• does not expose workspace/user IDs, idempotency keys, request digests or receipt digests
• publishes GET /v1/data-rights/requests/:requestId
• applies Cache-Control: no-store
• maps malformed request ID to bounded 400
• maps invalid/expired session to bounded 401
• maps absent and cross-tenant requests to the same bounded 404
• maps unexpected persistence/dependency failure to sanitized 503
• composes the status application into the production identity runtime and Nest controller graph

Scope

This completes one authenticated status surface only. Whole-product contributor orchestration, protected export delivery, erasure reconciliation, retention/legal-hold/backup-expiry semantics and final whole-right completion remain issue #55.

Refs #55 and follows #144.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 46 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: 3e24f148-9bee-4d14-8ce1-0775732f974c

📥 Commits

Reviewing files that changed from the base of the PR and between dcc787f and 0a1ae98.

📒 Files selected for processing (7)

• apps/identity-service/src/data-rights-http-controller.test.ts
• apps/identity-service/src/data-rights-http-controller.ts
• apps/identity-service/src/data-rights-status-application.test.ts
• apps/identity-service/src/data-rights-status-application.ts
• apps/identity-service/src/identity-runtime.test.ts
• apps/identity-service/src/identity-runtime.ts
• apps/identity-service/src/main.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.}