✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Greptile Summary

This PR migrates the organization membership page from v2 components (FontAwesome icons, v2 Table/Input/Select/Dropdown/Pagination/EmptyState) to their v3 counterparts (Lucide icons, UnstableTable, InputGroup, v3 Select, UnstableDropdownMenu, UnstablePagination, UnstableEmpty). It also wraps the section in v3 UnstableCard components for structural consistency.

• Component migration: All v2 UI components in OrgMembersTable and OrgMembersSection are replaced with v3 equivalents while preserving existing business logic (permissions, SCIM checks, role changes, invite resend, bulk delete)
• Icon migration: FontAwesome icons replaced with Lucide equivalents across OrgMembersTable, OrgMembersSection, and LastLoginSection
• v3 shared component tweaks: Minor global styling adjustments to SelectTrigger (truncation behavior), InputGroupAddon (SVG accent color), UnstableTableHead (user-select none), and DocumentationLinkBadge (optional className prop)
• Theme tokens: Hardcoded mineshaft-* color classes largely replaced with semantic tokens (bg-container, text-label, border-border, etc.), though a few remain in the delete confirmation modal

Confidence Score: 4/5

• This PR is a safe UI migration with no logic changes; the main risk is visual regressions.
• Score of 4 reflects that this is a pure frontend component migration with no business logic changes. All permission checks, SCIM guards, and data flows are preserved 1:1. The shared v3 component styling tweaks (Select, InputGroup, Table) are minimal and affect only a small number of consumers. The only risk is visual inconsistency from the few remaining hardcoded color classes.
• Pay close attention to OrgMembersTable.tsx as it has the most extensive changes, and Select.tsx since the display model change from flex to block could affect other consumers (though current usage appears safe).

Important Files Changed

_{Last reviewed commit: dc6c6e3}