@salesforce/cli 2.0.0-qa.7 → 2.0.1

package/oclif.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.0.0-qa.7",
+  "version": "2.0.1",
   "commands": {
     "cmdt:generate:field": {
       "id": "cmdt:generate:field",
@@ -561,7 +561,7 @@
     "community:create": {
       "id": "community:create",
       "summary": "Create an Experience Cloud site using a template.",
-      "description": "See 'Which Experience Cloud Template Should I Use?' (https://help.salesforce.com/s/articleView?id=sf.siteforce_commtemp_intro.htm&type=5) in Salesforce Help for more information about the different template\ntypes available for Experience Cloud.\n\nWhen creating a site with the Build Your Own (LWR) template, you must also specify the AuthenticationType value using the format templateParams.AuthenticationType=value, where value is AUTHENTICATED, UNAUTHENTICATED, or AUTHENTICATED_WITH_PUBLIC_ACCESS. Name and values are case-sensitive. See 'ExperienceBundle' in the Metadata API Developer Guide for more information. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_experiencebundle.htm)\n\nWhen you execute this command, it creates the site in preview status, which means that it isn't yet live. After you finish building your site, you can make it live.\n\nIf you have an Experience Builder site, publish the site using the \"community publish\" command to make it live.\n\nIf you have a Salesforce Tabs + Visualforce site, activate the site to make it live by updating the status field of the Network type in the Metadata API. Alternatively, in Experience Workspaces, go to Administration | Settings, and click Activate.\n\nFor Experience Builder sites, activating the site just sends out a welcome email to site members.",
+      "description": "Run the \"community list template\" command to see the templates available in your org. See 'Which Experience Cloud Template Should I Use?' in Salesforce Help for more information about the different template types available. (https://help.salesforce.com/s/articleView?id=sf.siteforce_commtemp_intro.htm&type=5)\n\nWhen you create a site with the Build Your Own (LWR) template, you must also specify the AuthenticationType value using the format templateParams.AuthenticationType=value, where value is AUTHENTICATED or AUTHENTICATED_WITH_PUBLIC_ACCESS_ENABLED. Name and values are case-sensitive. See 'DigitalExperienceBundle' in the Metadata API Developer Guide for more information. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperiencebundle.htm)\n\nThe site creation process is an async job that generates a jobId. To check the site creation status, query the BackgroundOperation object and enter the jobId as the Id. See ‘BackgroundOperation’ in the Object Reference for the Salesforce Platform for more information. (https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_backgroundoperation.htm)\n\nIf the job doesn’t complete within 10 minutes, it times out. You receive an error message and must restart the site creation process. Completed jobs expire after 24 hours and are removed from the database.\n\nWhen you run this command, it creates the site in preview status, which means that the site isn't yet live. After you finish building your site, you can make it live.\n\nIf you have an Experience Builder site, publish the site using the \"community publish\" command to make it live.\n\nIf you have a Salesforce Tabs + Visualforce site, to activate the site and make it live, update the status field of the Network type in Metadata API. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_network.htm) Alternatively, in Experience Workspaces, go to Administration | Settings, and click Activate.\n\nFor Experience Builder sites, activating the site sends a welcome email to site members.",
       "strict": false,
       "pluginName": "@salesforce/plugin-community",
       "pluginAlias": "@salesforce/plugin-community",
@@ -663,19 +663,12 @@
         }
       },
       "args": {},
-      "validationPatterns": [
-        "name",
-        "urlPathPrefix",
-        "templateName",
-        "description",
-        "templateParams(\\.\\w+)+"
-      ],
       "hasDynamicHelp": true
     },
     "community:publish": {
       "id": "community:publish",
       "summary": "Publish an Experience Builder site to make it live.",
-      "description": "Each time you publish it, you update the live site with the most recent updates. When you publish an Experience Builder site for the first time, you make the site's URL live and enable login access for site members.\n\nAdditionally, to send a welcome email to all site members, you must activate the site. (Activation is also required to successfully set up SEO for Experience Builder sites.) To activate a site, update the status field of the Network type in the Metadata API. Alternatively, in Experience Workspaces, go to Administration | Settings, and click Activate.\n\nSubsequently, each time you publish the site, you update the live site with all changes made to the site since it was last published.\n\nAn email notification informs you when your changes are live.",
+      "description": "Each time you publish a site, you update the live site with the most recent updates. When you publish an Experience Builder site for the first time, you make the site's URL live and enable login access for site members.\n\nIn addition to publishing, you must activate a site to send a welcome email to all site members. Activation is also required to set up SEO for Experience Builder sites. To activate a site, update the status field of the Network type in Metadata API. (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_network.htm)Alternatively, in Experience Workspaces, go to Administration | Settings, and click Activate.\n\nAn email notification informs you when your changes are live on the published site. The site publish process is an async job that generates a jobId. To check the site publish status manually, query the BackgroundOperation object and enter the jobId as the Id. See ‘BackgroundOperation’ in the Object Reference for the Salesforce Platform for more information. (https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_backgroundoperation.htm)\n\nIf the job doesn’t complete within 15 minutes, it times out. You receive an error message and must restart the site publish process. Completed jobs expire after 24 hours and are removed from the database.",
       "strict": true,
       "pluginName": "@salesforce/plugin-community",
       "pluginAlias": "@salesforce/plugin-community",
@@ -848,14 +841,14 @@
     "dev:audit:messages": {
       "id": "dev:audit:messages",
       "summary": "Audit messages in a plugin's messages directory to locate unused messages and missing messages that have references in source code.",
-      "description": "Audit messages in a plugin's messages directory to locate unused messages and missing messages that have references in source code.",
       "strict": true,
       "pluginName": "@salesforce/plugin-dev",
       "pluginAlias": "@salesforce/plugin-dev",
       "pluginType": "jit",
       "aliases": [],
       "examples": [
-        "sf dev audit messages\nsf dev audit messages --json\nsf dev audit messages --messages-dir ./messages --source-dir ./src"
+        "Audit messages using default directories:\n<%= config.bin %> <%= command.id %>",
+        "Audit messages in the \"messages\" directory in the current working directory; the plugin's source directory is in \"src\":\n<%= config.bin %> <%= command.id %> --messages-dir ./messages --source-dir ./src"
       ],
       "flags": {
         "json": {
@@ -869,8 +862,7 @@
           "name": "project-dir",
           "type": "option",
           "char": "p",
-          "summary": "Location project where messages are to be audited.",
-          "description": "The project directory.",
+          "summary": "Location of the project where messages are to be audited.",
           "multiple": false,
           "default": ".",
           "aliases": [
@@ -881,8 +873,8 @@
           "name": "messages-dir",
           "type": "option",
           "char": "m",
-          "summary": "Location of the message bundle directory.",
-          "description": "The directory that holds the message bundle files. The default is the messages directory in the current working directory.",
+          "summary": "Directory that contains the plugin's message files.",
+          "description": "The default is the \"messages\" directory in the current working directory.",
           "multiple": false,
           "default": "messages",
           "aliases": [
@@ -893,8 +885,8 @@
           "name": "source-dir",
           "type": "option",
           "char": "s",
-          "summary": "Location of the plugin's source code.",
-          "description": "The directory that holds the plugin's source code. The default is the src directory in the current working directory.",
+          "summary": "Directory that contains the plugin's source code.",
+          "description": "The default is the \"src\" directory in the current working directory.",
           "multiple": false,
           "default": "src",
           "aliases": [
@@ -906,15 +898,15 @@
     },
     "dev:configure:repo": {
       "id": "dev:configure:repo",
-      "summary": "Configure github repo for Actions pipeline.",
-      "description": "Sets up labels and exempts the CLI bot for branch protection and PR rules",
+      "summary": "Configure a GitHub repo for the GitHub Actions pipeline.",
+      "description": "Sets up labels and exempts the CLI bot for branch protection and PR rules.",
       "strict": true,
       "pluginName": "@salesforce/plugin-dev",
       "pluginAlias": "@salesforce/plugin-dev",
       "pluginType": "jit",
       "aliases": [],
       "examples": [
-        "<%= config.bin %> <%= command.id %> -r salesforcecli/testPackageRelease"
+        "Configure the repo \"testPackageRelease\", with owner \"salesforcecli\", for GitHub Actions.\n<%= config.bin %> <%= command.id %> --repository salesforcecli/testPackageRelease"
       ],
       "flags": {
         "json": {
@@ -928,7 +920,7 @@
           "name": "repository",
           "type": "option",
           "char": "r",
-          "summary": "The github owner/repo",
+          "summary": "GitHub owner/repo for which you want to configure GitHub Actions.",
           "required": true,
           "multiple": false
         },
@@ -936,7 +928,7 @@
           "name": "dry-run",
           "type": "boolean",
           "char": "d",
-          "summary": "Make no changes",
+          "summary": "Make no changes.",
           "allowNo": false,
           "aliases": [
             "dryrun"
@@ -946,7 +938,7 @@
           "name": "bot",
           "type": "option",
           "char": "b",
-          "summary": "The github login/username for the bot.",
+          "summary": "GitHub login/username for the bot.",
           "multiple": false,
           "default": "SF-CLI-BOT"
         }
@@ -955,15 +947,16 @@
     },
     "dev:configure:secrets": {
       "id": "dev:configure:secrets",
-      "summary": "Ensures a repo has correct access to secrets based on its workflows",
-      "description": "Inspects a repo's yaml files and verifies that secrets required are available for the repo (either set at the repo level or shared via organization-level secrets).\n\nThis command requires scope:admin permissions to inspect the org secrets and admin access to the repo to inspect the repo secrets",
+      "summary": "Ensures a GitHub repo has correct access to secrets based on its workflows.",
+      "description": "Inspects a repo's yaml files and verifies that secrets required are available for the repo (either set at the repo level or shared via organization-level secrets).\n\nThis command requires scope:admin permissions to inspect the org secrets and admin access to the repo to inspect the repo secrets.",
       "strict": true,
       "pluginName": "@salesforce/plugin-dev",
       "pluginAlias": "@salesforce/plugin-dev",
       "pluginType": "jit",
       "aliases": [],
       "examples": [
-        "<%= config.bin %> <%= command.id %> -r salesforcecli/testPackageRelease"
+        "Ensure secrets access for the repo \"testPackageRelease\", with owner \"salesforcecli\":",
+        "<%= config.bin %> <%= command.id %> --repository salesforcecli/testPackageRelease"
       ],
       "flags": {
         "json": {
@@ -977,7 +970,7 @@
           "name": "repository",
           "type": "option",
           "char": "r",
-          "summary": "The github owner/repo",
+          "summary": "Github owner/repo.",
           "required": true,
           "multiple": false
         },
@@ -985,7 +978,7 @@
           "name": "dry-run",
           "type": "boolean",
           "char": "d",
-          "summary": "Make no changes",
+          "summary": "Make no changes.",
           "allowNo": false,
           "aliases": [
             "dryrun"
@@ -996,15 +989,16 @@
     },
     "dev:convert:messages": {
       "id": "dev:convert:messages",
-      "summary": "Convert a .json messages file",
+      "summary": "Convert a .json messages file into Markdown.",
       "strict": true,
       "pluginName": "@salesforce/plugin-dev",
       "pluginAlias": "@salesforce/plugin-dev",
       "pluginType": "jit",
       "aliases": [],
       "examples": [
-        "<%= config.bin %> <%= command.id %> --filename something.json",
-        "<%= config.bin %> <%= command.id %> --project-dir ./path/to/plugin --filename something.json"
+        "Convert the my-command.json message file into my-command.md with the standard messages headers:\n<%= config.bin %> <%= command.id %> --filename my-command.json",
+        "Similar to previous example, but specify the plugin project directory:",
+        "<%= config.bin %> <%= command.id %> --project-dir ./path/to/plugin --filename my-command.json"
       ],
       "flags": {
         "json": {
@@ -1018,8 +1012,7 @@
           "name": "project-dir",
           "type": "option",
           "char": "p",
-          "summary": "Location of the project whose messages are to be audited.",
-          "description": "Location of the project whose messages are to be audited.",
+          "summary": "Location of the project whose messages are to be converted.",
           "multiple": false,
           "default": ".",
           "aliases": [
@@ -1030,7 +1023,7 @@
           "name": "file-name",
           "type": "option",
           "char": "f",
-          "summary": "Filename to convert",
+          "summary": "Filename to convert.",
           "required": true,
           "multiple": true,
           "aliases": [
@@ -1040,6 +1033,44 @@
       },
       "args": {}
     },
+    "dev:convert:script": {
+      "id": "dev:convert:script",
+      "summary": "Convert a script file that contains deprecated sfdx-style commands to use the new sf-style commands instead.",
+      "description": "Important: Use this command only to get started on the sfdx->sf script migration. We don't guarantee that the new sf-style command replacements work correctly or as you expect. You must test, and probably update, the new script before putting it into production. We also don't guarantee that the JSON results are the same as before. \n\nThis command can convert a large part of your script, but possibly not all. There are some sfdx-style commands that don't have an obvious sf-style equivalent. In this case, this command doesn't replace the sfdx-style command but instead adds a comment to remind you that you must convert it manually. See the Salesforce CLI Command Reference for migration information about each deprecated sfdx-style command: https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference.htm.\n\nThis command is interactive; as it scans your script, it prompts you when it finds an sfdx-style command or flag and asks if you want to convert it to the displayed suggestion. The command doesn't update the script file directly; rather, it creates a new file whose name is the original name but with \"-converted\" appended to it. The script replaces all instances of \"sfdx\" with \"sf\". For each prompt you answer \"y\" to, the command replaces the sfdx-style names with their equivalent sf-style ones. For example, \"sfdx force:apex:execute --targetusername myscratch\" is replaced with \"sf apex run --target-org myscratch\".",
+      "strict": true,
+      "pluginName": "@salesforce/plugin-dev",
+      "pluginAlias": "@salesforce/plugin-dev",
+      "pluginType": "jit",
+      "aliases": [],
+      "examples": [
+        "Convert the YAML file called \"myScript.yml\" located in the current directory; the new file that contains the replacements is called \"myScript-converted.yml\":\n<%= config.bin %> <%= command.id %> --script ./myScript.yml"
+      ],
+      "flags": {
+        "json": {
+          "name": "json",
+          "type": "boolean",
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "allowNo": false
+        },
+        "script": {
+          "name": "script",
+          "type": "option",
+          "char": "s",
+          "summary": "Filepath to the script you want to convert.",
+          "required": true,
+          "multiple": false
+        },
+        "no-prompt": {
+          "name": "no-prompt",
+          "type": "boolean",
+          "summary": "Don't prompt for suggested replacements.",
+          "hidden": true,
+          "allowNo": false
+        }
+      },
+      "args": {}
+    },
     "dev:generate:command": {
       "id": "dev:generate:command",
       "summary": "Generate a new sf command.",
@@ -2390,7 +2421,6 @@
       "pluginType": "jit",
       "hidden": true,
       "aliases": [
-        "force:package:beta:convert",
         "force:package:convert"
       ],
       "examples": [
@@ -2531,7 +2561,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:create",
         "force:package:create"
       ],
       "examples": [
@@ -2673,7 +2702,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:delete",
         "force:package:delete"
       ],
       "examples": [
@@ -2765,7 +2793,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:install",
         "force:package:install"
       ],
       "examples": [
@@ -2953,7 +2980,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:list",
         "force:package:list"
       ],
       "examples": [
@@ -3024,7 +3050,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:uninstall",
         "force:package:uninstall"
       ],
       "examples": [
@@ -3109,7 +3134,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:update",
         "force:package:update"
       ],
       "examples": [
@@ -3195,6 +3219,14 @@
           "aliases": [
             "errornotificationusername"
           ]
+        },
+        "enable-app-analytics": {
+          "name": "enable-app-analytics",
+          "type": "boolean",
+          "summary": "Enable AppExchange App Analytics usage data collection on this managed package and its components.",
+          "hidden": true,
+          "allowNo": true,
+          "deprecateAliases": true
         }
       },
       "args": {},
@@ -3209,7 +3241,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:install:report",
         "force:package:install:report"
       ],
       "examples": [
@@ -3283,7 +3314,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:installed:list",
         "force:package:installed:list"
       ],
       "examples": [
@@ -3346,7 +3376,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:uninstall:report",
         "force:package:uninstall:report"
       ],
       "examples": [
@@ -3421,7 +3450,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:create",
         "force:package:version:create"
       ],
       "examples": [
@@ -3730,7 +3758,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:delete",
         "force:package:version:delete"
       ],
       "examples": [
@@ -3821,7 +3848,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:displayancestry",
         "force:package:version:displayancestry"
       ],
       "examples": [
@@ -3915,7 +3941,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:list",
         "force:package:version:list"
       ],
       "examples": [
@@ -4045,7 +4070,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:promote",
         "force:package:version:promote"
       ],
       "examples": [
@@ -4130,7 +4154,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:report",
         "force:package:version:report"
       ],
       "examples": [
@@ -4201,6 +4224,78 @@
       "requiresProject": true,
       "hasDynamicHelp": true
     },
+    "package:version:retrieve": {
+      "id": "package:version:retrieve",
+      "summary": "Retrieve package metadata for a specified package version.",
+      "description": "Retrieving a package version downloads the metadata into the directory you specify.\n\nYou can retrieve metadata for a second- or first-generation managed package, or an unlocked package.\n\nSpecify the subscriber package version ID (starts with 04t) and the path to an empty directory when you run this command.",
+      "strict": true,
+      "pluginName": "@salesforce/plugin-packaging",
+      "pluginAlias": "@salesforce/plugin-packaging",
+      "pluginType": "jit",
+      "hidden": true,
+      "aliases": [],
+      "examples": [
+        "Retrieve package metadata for a subscriber package version ID (starts with 04t) into my-folder/ within your Salesforce DX project directory:\n<%= config.bin %> <%= command.id %> --package 04t... --output-dir my-folder –-target-org my-scratch\nIf you omit --target-org, this command runs against your default org."
+      ],
+      "flags": {
+        "json": {
+          "name": "json",
+          "type": "boolean",
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "allowNo": false
+        },
+        "loglevel": {
+          "name": "loglevel",
+          "type": "option",
+          "hidden": true,
+          "multiple": false,
+          "deprecated": {
+            "message": "The loglevel flag is no longer in use on this command. You may use it without error, but it will be ignored.\nSet the log level using the `SFDX_LOG_LEVEL` environment variable."
+          }
+        },
+        "api-version": {
+          "name": "api-version",
+          "type": "option",
+          "description": "Override the api version used for api requests made by this command",
+          "multiple": false,
+          "aliases": [
+            "apiversion"
+          ]
+        },
+        "target-org": {
+          "name": "target-org",
+          "type": "option",
+          "char": "o",
+          "summary": "Username or alias of the target org.",
+          "required": true,
+          "multiple": false,
+          "aliases": [
+            "targetusername",
+            "u"
+          ]
+        },
+        "package": {
+          "name": "package",
+          "type": "option",
+          "char": "p",
+          "summary": "Subscriber package version ID (starts with 04t).",
+          "required": true,
+          "multiple": false
+        },
+        "output-dir": {
+          "name": "output-dir",
+          "type": "option",
+          "char": "d",
+          "summary": "Path within your Salesforce DX project directory in which to download the metadata. This directory must be empty.",
+          "multiple": false,
+          "default": "force-app"
+        }
+      },
+      "args": {},
+      "requiresProject": true,
+      "hasDynamicHelp": true
+    },
     "package:version:update": {
       "id": "package:version:update",
       "summary": "Update a package version.",
@@ -4210,7 +4305,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:update",
         "force:package:version:update"
       ],
       "examples": [
@@ -4333,7 +4427,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package1:beta:version:create",
         "force:package1:version:create"
       ],
       "examples": [
@@ -4488,7 +4581,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package1:beta:version:display",
         "force:package1:version:display"
       ],
       "examples": [
@@ -4562,7 +4654,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package1:beta:version:list",
         "force:package1:version:list"
       ],
       "examples": [
@@ -4637,7 +4728,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:create:list",
         "force:package:version:create:list"
       ],
       "examples": [
@@ -4728,7 +4818,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package:beta:version:create:report",
         "force:package:version:create:report"
       ],
       "examples": [
@@ -4802,7 +4891,6 @@
       "pluginAlias": "@salesforce/plugin-packaging",
       "pluginType": "jit",
       "aliases": [
-        "force:package1:beta:version:create:get",
         "force:package1:version:create:get"
       ],
       "examples": [
@@ -6272,13 +6360,13 @@
       "id": "scanner:run:dfa",
       "description": "scan codebase with all DFA rules",
       "strict": true,
-      "usage": "<%= command.id %> -t <array> [-c <array>] [-f csv|html|json|junit|sarif|table|xml] [-o <string>] [-s <integer> | --json] [--normalize-severity] [-p <array>] [--rule-thread-count <integer>] [--rule-thread-timeout <integer>] [--rule-disable-warning-violation] [--sfgejvmargs <string>] [--pathexplimit <integer>] [--verbose] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]",
+      "usage": "<%= command.id %> -t <array> [-c <array>] [-f csv|html|json|junit|sarif|table|xml] [-o <string>] [-s <integer> | --json] [--normalize-severity] [-p <array>] [--with-pilot] [--rule-thread-count <integer>] [--rule-thread-timeout <integer>] [--rule-disable-warning-violation] [--sfgejvmargs <string>] [--pathexplimit <integer>] [--verbose] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]",
       "pluginName": "@salesforce/sfdx-scanner",
       "pluginAlias": "@salesforce/sfdx-scanner",
       "pluginType": "jit",
       "aliases": [],
       "examples": [
-        "The paths specified for --projectdir must contain all files specified through --target cumulatively.\n\t$ sfdx scanner:run:dfa --target \"./myproject/main/default/classes/*.cls\" --projectdir \"./myproject/\"\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls\" --projectdir \"./\"\n\t$ sfdx scanner:run:dfa --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\nThis example fails because the set of files included in --target is larger than that contained in --projectdir:\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls\" --projectdir \"./myproject/\"\nGlobs must be wrapped in quotes, as in these Windows and Unix examples, which evaluate rules against all .cls files in the current directory and subdirectories except for IgnoreMe.cls:\nUnix example:\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls,!./**/IgnoreMe.cls\" ...\nWindows example:\n\t$ sfdx scanner:run:dfa --target \".\\**\\*.cls,!.\\**\\IgnoreMe.cls\" ...\nYou can target individual methods within a file with a suffix hash (#) on the file's path, and with a semi-colon-delimited list of method names. This syntax is incompatible with globs and directories. This example evaluates rules against all methods named Method1 or Method2 in File1.cls, and all methods named Method3 in File2.cls:\n\t$ sfdx scanner:run:dfa --target \"./File1.cls#Method1;Method2,./File2.cls#Method3\" ...\nUse --normalize-severity to output a normalized severity across all engines, in addition to the engine-specific severity. Normalized severity is 1 (high), 2 (moderate), and 3 (low):\n\t$ sfdx scanner:run:dfa --target \"./some-project/\" --projectdir \"./some-project/\" --format csv --normalize-severity\nUse --severity-threshold to throw a non-zero exit code when rule violations of a specific normalized severity or greater are found. If there are any rule violations with a severity of 2 or 1, the exit code is equal to the severity of the most severe violation:\n\t$ sfdx scanner:run:dfa --target \"./some-project/\" --projectdir \"./some-project/\" --severity-threshold 2\nuse --rule-thread-count to allow more (or fewer) entrypoints to be evaluated concurrently:\n\t$ sfdx scanner:run:dfa --rule-thread-count 6 ...\nUse --rule-thread-timeout to increase or decrease the maximum runtime for a single entrypoint evaluation. This increases the timeout from the 15-minute default to 150 minutes:\n\t$ sfdx scanner:run:dfa --rule-thread-timeout 9000000 ...\nUse --sfgejvmargs to pass Java Virtual Machine args to override system defaults while executing Salesforce Graph Engine's rules.\nThe example overrides the system's default heap space allocation to 8 GB and decreases chances of encountering OutOfMemory error.\n\t$ sfdx scanner:run:dfa --sfgejvmargs \"-Xmx8g\" ...\n"
+        "The paths specified for --projectdir must contain all files specified through --target cumulatively.\n\t$ sfdx scanner:run:dfa --target \"./myproject/main/default/classes/*.cls\" --projectdir \"./myproject/\"\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls\" --projectdir \"./\"\n\t$ sfdx scanner:run:dfa --target \"./dir1/file1.cls,./dir2/file2.cls\" --projectdir \"./dir1/,./dir2/\"\nThis example fails because the set of files included in --target is larger than that contained in --projectdir:\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls\" --projectdir \"./myproject/\"\nGlobs must be wrapped in quotes, as in these Windows and Unix examples, which evaluate rules against all .cls files in the current directory and subdirectories except for IgnoreMe.cls:\nUnix example:\n\t$ sfdx scanner:run:dfa --target \"./**/*.cls,!./**/IgnoreMe.cls\" ...\nWindows example:\n\t$ sfdx scanner:run:dfa --target \".\\**\\*.cls,!.\\**\\IgnoreMe.cls\" ...\nYou can target individual methods within a file with a suffix hash (#) on the file's path, and with a semi-colon-delimited list of method names. This syntax is incompatible with globs and directories. This example evaluates rules against all methods named Method1 or Method2 in File1.cls, and all methods named Method3 in File2.cls:\n\t$ sfdx scanner:run:dfa --target \"./File1.cls#Method1;Method2,./File2.cls#Method3\" ...\nUse --normalize-severity to output a normalized severity across all engines, in addition to the engine-specific severity. Normalized severity is 1 (high), 2 (moderate), and 3 (low):\n\t$ sfdx scanner:run:dfa --target \"./some-project/\" --projectdir \"./some-project/\" --format csv --normalize-severity\nUse --severity-threshold to throw a non-zero exit code when rule violations of a specific normalized severity or greater are found. If there are any rule violations with a severity of 2 or 1, the exit code is equal to the severity of the most severe violation:\n\t$ sfdx scanner:run:dfa --target \"./some-project/\" --projectdir \"./some-project/\" --severity-threshold 2\nuse --rule-thread-count to allow more (or fewer) entrypoints to be evaluated concurrently:\n\t$ sfdx scanner:run:dfa --rule-thread-count 6 ...\nUse --rule-thread-timeout to increase or decrease the maximum runtime for a single entrypoint evaluation. This increases the timeout from the 15-minute default to 150 minutes:\n\t$ sfdx scanner:run:dfa --rule-thread-timeout 9000000 ...\nUse --sfgejvmargs to pass Java Virtual Machine args to override system defaults while executing Salesforce Graph Engine's rules.\nThe example overrides the system's default heap space allocation to 8 GB and decreases chances of encountering OutOfMemory error.\n\t$ sfdx scanner:run:dfa --sfgejvmargs \"-Xmx8g\" ...\nUse --with-pilot to allow execution of pilot rules:\nThis example allows pilot rules in the \"Performance\" category to execute.\n\t$ sfdx scanner:run:dfa --category 'Performance' --with-pilot ...\n"
       ],
       "flags": {
         "json": {
@@ -6370,6 +6458,12 @@
           "description": "provide root directory of project",
           "multiple": false
         },
+        "with-pilot": {
+          "name": "with-pilot",
+          "type": "boolean",
+          "description": "allow pilot rules to execute",
+          "allowNo": false
+        },
         "target": {
           "name": "target",
           "type": "option",
@@ -6490,6 +6584,13 @@
           "multiple": false,
           "type": "option"
         },
+        "with-pilot": {
+          "kind": "boolean",
+          "description": "allow pilot rules to execute",
+          "longDescription": "Allows pilot rules to execute.",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "target": {
           "kind": "array",
           "char": "t",