Merge branch 'master' into lendritibrahimi/feat/NEX-981-node-diff-content-cli-command

# Conflicts:
#	DOCUMENTATION.md
#	src/commands/configuration-management/module.ts

Author: LendritIbrahimi

DOCUMENTATION.md

@@ -113,9 +113,7 @@ on your behalf.
 
 With Client Credentials, you need to provide the credentials (Client ID, Client Secret) configured for your OAuth client. 
 You can create and configure an OAuth clients in the `Admin & Settings` section of your Celonis account, under `Applications`. 
-The OAuth client needs to have scopes configured based on the area of commands they're using, e.g.: 
-- For Studio commands: studio, 
-- Data Pipeline/Data Pool commands: integration.data-pools,
+The client needs to have all four scopes configured: "studio", "integration.data-pools", "action-engine.projects" and "package-manager".
 After creating an OAuth client, you should assign it the permissions necessary for the respective commands. More 
 information on registering OAuth clients can be found [here](https://docs.celonis.com/en/registering-oauth-client.html).
 
@@ -643,11 +641,11 @@ This mapping should be saved and then used during import.
 Since the format of the variables.json file on import is the same JSON structure as the list variables result, you can either map the values to the variables.json file for each variable, or replace the variables.json file with the result of the listing & mapping altogether.
 If the mapping of variables is skipped, you should delete the variables.json file before importing.
 
-#### Finding staging nodes
+#### Finding nodes
 
-The **config nodes find** command allows you to retrieve information about a specific node within a package in the staging environment.
+The **config nodes find** command allows you to retrieve information about a specific node within a package.
 
-##### Find a node
+##### Find a staging node
 To find a specific node in a package, use the following command:
 ```
 content-cli config nodes find --packageKey <packageKey> --nodeKey <nodeKey>
@@ -668,7 +666,7 @@ info:    Change Date: 2025-10-22T15:45:00.000Z
 info:    Flavor: STUDIO
 ```
 
-##### Find a node with configuration
+##### Find a staging node with configuration
 By default, the node configuration is not included in the response. To include the node's configuration, use the `--withConfiguration` flag:
 ```
 content-cli config nodes find --packageKey <packageKey> --nodeKey <nodeKey> --withConfiguration
@@ -679,7 +677,7 @@ When configuration is included, it will be displayed as a JSON string in the out
 info:    Configuration: {"key":"value","nested":{"field":"data"}}
 ```
 
-##### Export node as JSON
+##### Export staging node as JSON
 To export the node information as a JSON file instead of displaying it in the console, use the `--json` option:
 ```
 content-cli config nodes find --packageKey <packageKey> --nodeKey <nodeKey> --json
@@ -696,7 +694,6 @@ You can combine options to export a node with its configuration:
 ```
 content-cli config nodes find --packageKey <packageKey> --nodeKey <nodeKey> --withConfiguration --json
 ```
-
 #### Diffing node configurations
 
 The **config nodes diff** command allows you to compare two versions of a node's configuration within a package.

src/core/profile/profile.service.ts

@@ -14,7 +14,7 @@ const homedir = os.homedir();
 // use 5 seconds buffer to avoid rare cases when accessToken is just about to expire before the command is sent
 const expiryBuffer = 5000;
 const deviceCodeScopes = ["studio", "package-manager", "integration.data-pools", "action-engine.projects"];
-const clientCredentialsScopes = ["studio", "integration.data-pools", "action-engine.projects"];
+const clientCredentialsScopes = ["studio", "integration.data-pools", "action-engine.projects", "package-manager"];
 
 export interface Config {
     defaultProfile: string;