Sync user archive across all interfaces

Align user-removal UX and API surface semantics with the new archive\nbehavior for manually managed users.\n\nFrontend copy and actions now use archive wording, and list rows are\nrefetched after the mutation so archived users reappear as inactive.\n\nMCP removeUser now documents and returns archived_user_id, n8n labels\nand response mapping now use archive semantics, and the CLI gains a\nuser archive command backed by the same mutation.

Signed-off-by: Cursor Agent <cursoragent@cursor.com>

packages/n8n-node/nodes/Probo/actions/user/index.ts

@@ -58,10 +58,10 @@ export const description: INodeProperties[] = [
 				action: 'List users',
 			},
 			{
-				name: 'Remove',
+				name: 'Archive',
 				value: 'removeUser',
-				description: 'Remove a user from the organization',
-				action: 'Remove a user',
+				description: 'Archive a user in the organization',
+				action: 'Archive a user',
 			},
 			{
 				name: 'Update',

packages/n8n-node/nodes/Probo/actions/user/removeUser.operation.ts

@@ -41,7 +41,7 @@ export const description: INodeProperties[] = [
 			},
 		},
 		default: '',
-		description: 'The ID of the user (profile) to remove from the organization',
+		description: 'The ID of the user (profile) to archive in the organization',
 		required: true,
 	},
 ];
@@ -56,7 +56,7 @@ export async function execute(
 	const query = `
 		mutation RemoveUser($input: RemoveUserInput!) {
 			removeUser(input: $input) {
-				deletedProfileId
+				archivedProfileId: deletedProfileId
 			}
 		}
 	`;