Add read-only DSR policy detail page

[gilluminate]

Ticket ENG-2716

Description Of Changes

Add a read-only policy detail page with Rules and Conditions tabs. This lays the groundwork for future policy editing capabilities.

Code Changes

• Add policies list page at /privacy-requests/policies/ with search by name/key, action type tags, and empty states
• Add policy detail page at /privacy-requests/policies/[key] with PolicyBox header, RulesTab, and PolicyConditionsTab components
• Extend policy.slice.ts with getPolicy
• Add and update related type definitions
• Update LinkCell so that href is correctly using the with Next.js Url type
• Add Cypress E2E tests for the policy detail page

Steps to Confirm

1. Navigate to Privacy Requests > Policies and click a policy name to navigate to the detail page
2. Verify the detail page shows the policy name/key and has working Rules and Conditions tabs
   (Tabs are pretty basic right now but the next PR will populate those more)

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
• UX feedback:
  • All UX related changes have been reviewed by a designer
• Followup issues:
  • Followup issues created
• Database migrations:
  • No migrations
• Documentation:
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 19, 2026 5:52pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 19, 2026 5:52pm

[greptile-apps]

Greptile Summary

This PR adds a read-only DSR policy detail page at /privacy-requests/policies/[key], including a PolicyBox header component, stub RulesTab and PolicyConditionsTab tabs, a new getPolicy RTK Query endpoint, and Cypress E2E tests. It also updates LinkCell to accept Next.js Url objects and adds navigation links from the policy list to detail pages.

• The Cypress test visits a URL with key default_consent_policy but the stub always returns default_erasure_policy data — the test passes due to the wildcard intercept but is semantically misleading
• The policies list page uses useState for search instead of the existing useSearch hook, which would provide URL state synchronization consistent with other pages
• conditions?: any added to PolicyResponse bypasses type safety; a more specific type (e.g., ConditionGroup) would be preferable
• New components (PolicyBox, RulesTab, PolicyConditionsTab) are clean and well-structured placeholder implementations

Confidence Score: 4/5

• This PR is safe to merge with minor issues around test data consistency and type safety.
• The core implementation is clean and follows existing patterns well. The issues found are a test data mismatch (misleading but not broken), a style suggestion to use the existing useSearch hook, and an untyped any field. None of these are blocking.
• Pay attention to clients/admin-ui/cypress/e2e/policies/policy-detail.cy.ts (test key mismatch with stub data) and clients/admin-ui/src/types/api/models/PolicyResponse.ts (untyped any field).

Important Files Changed

Filename	Overview
clients/admin-ui/cypress/e2e/policies/policy-detail.cy.ts	New Cypress E2E tests for policy detail page. Test visits default_consent_policy but stub returns default_erasure_policy data — a mismatch that's masked by the wildcard intercept.
clients/admin-ui/src/features/common/table/cells/LinkCell.tsx	Updates href prop to accept Next.js Url type (supporting object-based hrefs). Import is from next/dist/ internal path, which is pre-existing in the codebase.
clients/admin-ui/src/features/policy/policy.slice.ts	Adds getPolicy RTK Query endpoint with proper providesTags for cache management. Clean implementation.
clients/admin-ui/src/pages/privacy-requests/policies/[key].tsx	New policy detail page with loading, error, and success states. Uses useURLHashedTabs for tab navigation and proper skip on the query hook when key is undefined.
clients/admin-ui/src/pages/privacy-requests/policies/index.tsx	Adds LinkCell navigation to policy detail pages. Uses local useState for search instead of the existing useSearch hook.
clients/admin-ui/src/types/api/models/PolicyResponse.ts	Adds conditions?: any — an untyped field to an auto-generated type file. Should use a more specific type.

_{Last reviewed commit: 33f18df}

[greptile-apps]

_{13 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

clients/admin-ui/src/pages/privacy-requests/policies/index.tsx
Consider using useSearch hook

The codebase has an existing useSearch hook (~/features/common/hooks/useSearch) that provides URL state synchronization via NuQS. Using useState here means search state is lost when navigating away and back. Consider using useSearch for consistency with the rest of the codebase.

Context Used: Rule from dashboard - Use the existing useSearch hook for search functionality to maintain URL state synchronization ins... (source)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}