SDK regression: views-new member role-change still uses raw policy CRUD

[whoAbhishekSah]

Where

web/sdk/react/views-new/members/components/update-role-dialog.tsx

Problem

The new members page dialog still changes an org member's role by:

1. listPolicies({ orgId, userId })
2. deletePolicy per existing policy
3. createPolicy against app/organization: with the new role

The dedicated RPC SetOrganizationMemberRole should be used instead — same pattern as the legacy view migration in #1477.

How it happened

• feat(sdk): use SetOrganizationMemberRole RPC for member role changes #1477 (Mar 25) migrated the legacy views/members/member-columns.tsx to setOrganizationMemberRole.
• feat: members page revamp #1488 (Apr 6, "members page revamp") landed the new dialog and reintroduced the policy-CRUD pattern — likely because the revamp branched off pre-feat(sdk): use SetOrganizationMemberRole RPC for member role changes #1477 and copied the older pattern from a neighboring file.

Same flavor of drift fixed for groups in #1608 / #1609.

Suggested fix

Replace useQuery(listPolicies) + useMutation(deletePolicy) + useMutation(createPolicy) with a single useMutation(setOrganizationMemberRole). Drop the unused schemas/types.

const { mutateAsync: setOrgMemberRole } = useMutation(
  FrontierServiceQueries.setOrganizationMemberRole
);

await setOrgMemberRole(create(SetOrganizationMemberRoleRequestSchema, {
  orgId: organizationId,
  userId: payload.memberId,
  roleId: payload.role.id,
}));

Related

• feat(sdk): use SetOrganizationMemberRole RPC for member role changes #1477 — legacy view migration
• feat: members page revamp #1488 — introduced the regression
• refactor(group): migrate AddGroupUsers handler to membership #1608 / refactor(sdk): migrate group add-member flows to setGroupMemberRole #1609 — group-side equivalent fixes