@salesforce/cli 2.86.5 → 2.86.7

package/oclif.manifest.json

@@ -298,18 +298,17 @@
         "run:code-analyzer"
       ]
     },
-    "cmdt:generate:field": {
+    "community:create": {
       "aliases": [
-        "force:cmdt:field:create",
-        "cmdt:field:create"
+        "force:community:create"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Similar to a custom object, a custom metadata type has a list of custom fields that represent aspects of the metadata.\n\nThis command creates a metadata file that describes the new custom metadata type field. By default, the file is created in a \"fields\" directory in the current directory. Use the --output-directory to generate the file in the directory that contains the custom metadata type metdata files, such as \"force-app/main/default/objects/MyCmdt__mdt\" for the custom metadata type called MyCmdt.",
+      "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.",
       "examples": [
-        "Generate a metadata file for a custom checkbox field and add the file to the MyCmdt__mdt/fields directory:\n<%= config.bin %> <%= command.id %> --name MyCheckboxField --type Checkbox --output-directory force-app/main/default/objects/MyCmdt__mdt",
-        "Generate a metadata file for a custom picklist field and add a few values:\n<%= config.bin %> <%= command.id %> --name MyPicklistField --type Picklist --picklist-values A --picklist-values B --picklist-values C --output-directory force-app/main/default/objects/MyCmdt__mdt",
-        "Generate a metadata file for a custom number field and specify 2 decimal places:\n<%= config.bin %> <%= command.id %> --name MyNumberField --type Number --decimal-places 2 --output-directory force-app/main/default/objects/MyCmdt__mdt"
+        "Create an Experience Cloud site using template 'Customer Service' and URL path prefix 'customers':\n<%= config.bin %> <%= command.id %> --name 'My Customer Site' --template-name 'Customer Service' --url-path-prefix customers --description 'My customer site'",
+        "Create a site using 'Partner Central' template:\n<%= config.bin %> <%= command.id %> --name partnercentral --template-name 'Partner Central' --url-path-prefix partners",
+        "Create a site using the 'Build Your Own (LWR)' template with authentication type of UNAUTHENTICATED:\n<%= config.bin %> <%= command.id %> --name lwrsite --template-name 'Build Your Own (LWR)' --url-path-prefix lwrsite templateParams.AuthenticationType=UNAUTHENTICATED"
       ],
       "flags": {
         "json": {
@@ -327,176 +326,127 @@
           "multiple": false,
           "type": "option"
         },
-        "loglevel": {
-          "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."
-          },
-          "hidden": true,
-          "name": "loglevel",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "name": {
-          "aliases": [
-            "fieldname"
-          ],
           "char": "n",
           "name": "name",
           "required": true,
-          "summary": "Unique name for the field.",
+          "summary": "Name of the site to create.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "type": {
+        "template-name": {
           "aliases": [
-            "fieldtype"
+            "templatename"
           ],
-          "char": "f",
-          "description": "You can't use this command to create a custom metadata type field of type \"Metadata Relationship\". Use the Salesforce Setup UI instead.",
-          "name": "type",
+          "char": "t",
+          "deprecateAliases": true,
+          "description": "An example of a template is Customer Service. Run the \"community template list\" command to see which templates are available in your org.",
+          "name": "template-name",
           "required": true,
-          "summary": "Type of the field.",
+          "summary": "Template to use to create a site.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "Checkbox",
-            "Date",
-            "DateTime",
-            "Email",
-            "Number",
-            "Percent",
-            "Phone",
-            "Picklist",
-            "Text",
-            "TextArea",
-            "LongTextArea",
-            "Url"
-          ],
           "type": "option"
         },
-        "picklist-values": {
+        "url-path-prefix": {
           "aliases": [
-            "picklistvalues"
+            "urlpathprefix"
           ],
           "char": "p",
-          "name": "picklist-values",
-          "summary": "Picklist values; required for picklist fields.",
-          "delimiter": ",",
+          "deprecateAliases": true,
+          "description": "For example, if your domain name is https://MyDomainName.my.site.com and you create a customer site, enter 'customers' to create the unique URL https://MyDomainName.my.site.com/customers.",
+          "name": "url-path-prefix",
+          "summary": "URL to append to the domain created when Digital Experiences was enabled for this org.",
+          "default": "",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "decimal-places": {
+        "description": {
+          "char": "d",
+          "description": "The description displays in Digital Experiences - All Sites in Setup and helps with site identification.",
+          "name": "description",
+          "summary": "Description of the site.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
           "aliases": [
-            "decimalplaces"
+            "targetusername",
+            "u"
           ],
-          "char": "s",
-          "description": "The value must be greater than or equal to zero. Default value is 0.",
-          "name": "decimal-places",
-          "summary": "Number of decimal places to use for number or percent fields.",
-          "default": 0,
-          "hasDynamicHelp": false,
+          "char": "o",
+          "deprecateAliases": true,
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "label": {
-          "char": "l",
-          "name": "label",
-          "summary": "Label for the field.",
+        "loglevel": {
+          "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."
+          },
+          "hidden": true,
+          "name": "loglevel",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "output-directory": {
+        "api-version": {
           "aliases": [
-            "outputdir",
-            "outputdirectory"
+            "apiversion"
           ],
-          "char": "d",
-          "description": "New files are automatically created in the \"fields\" directory. The location can be an absolute path or relative to the current working directory. The default is the current directory.",
-          "name": "output-directory",
-          "summary": "Directory to store newly-created field definition files.",
-          "default": "",
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "cmdt:generate:field",
-      "pluginAlias": "@salesforce/plugin-custom-metadata",
-      "pluginName": "@salesforce/plugin-custom-metadata",
+      "id": "community:create",
+      "pluginAlias": "@salesforce/plugin-community",
+      "pluginName": "@salesforce/plugin-community",
       "pluginType": "jit",
-      "strict": true,
-      "summary": "Generate a field for a custom metadata type based on the provided field type.",
+      "strict": false,
+      "summary": "Create an Experience Cloud site using a template.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "cmdt",
-        "generate",
-        "field.js"
+        "community",
+        "create.js"
       ],
       "aliasPermutations": [
-        "force:cmdt:field:create",
-        "cmdt:force:field:create",
-        "cmdt:field:force:create",
-        "cmdt:field:create:force",
-        "force:field:cmdt:create",
-        "field:force:cmdt:create",
-        "field:cmdt:force:create",
-        "field:cmdt:create:force",
-        "force:field:create:cmdt",
-        "field:force:create:cmdt",
-        "field:create:force:cmdt",
-        "field:create:cmdt:force",
-        "force:cmdt:create:field",
-        "cmdt:force:create:field",
-        "cmdt:create:force:field",
-        "cmdt:create:field:force",
-        "force:create:cmdt:field",
-        "create:force:cmdt:field",
-        "create:cmdt:force:field",
-        "create:cmdt:field:force",
-        "force:create:field:cmdt",
-        "create:force:field:cmdt",
-        "create:field:force:cmdt",
-        "create:field:cmdt:force",
-        "cmdt:field:create",
-        "field:cmdt:create",
-        "field:create:cmdt",
-        "cmdt:create:field",
-        "create:cmdt:field",
-        "create:field:cmdt"
+        "force:community:create",
+        "community:force:create",
+        "community:create:force",
+        "force:create:community",
+        "create:force:community",
+        "create:community:force"
       ],
       "permutations": [
-        "cmdt:generate:field",
-        "generate:cmdt:field",
-        "generate:field:cmdt",
-        "cmdt:field:generate",
-        "field:cmdt:generate",
-        "field:generate:cmdt"
+        "community:create",
+        "create:community"
       ]
     },
-    "cmdt:generate:fromorg": {
+    "community:publish": {
       "aliases": [
-        "force:cmdt:generate"
+        "force:community:publish"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "Use this command to migrate existing custom objects or custom settings in an org to custom metadata types. If a field of the Salesforce object is of an unsupported type, the field type is automatically converted to text. Run \"<%= config.bin %> cmdt generate field --help\" to see the list of supported cmdt field types, listed in the --type flag summary. Use the --ignore-unsupported to ignore these fields.\n\nThis command creates the metadata files that describe the new custom metadata type and its fields in the \"force-app/main/default/objects/TypeName__mdt\" directory by default, where \"TypeName\" is the value of the required --dev-name flag. Use --type-output-directory to create them in a different directory.",
+      "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.",
       "examples": [
-        "Generate a custom metadata type from a custom object called MySourceObject__c in your default org:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c",
-        "Generate a custom metadata type from a custom object in an org with alias my-scratch-org; ignore unsupported field types instead of converting them to text:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --ignore-unsupported --target-org my-scratch-org",
-        "Generate a protected custom metadata type from a custom object:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --visibility Protected",
-        "Generate a protected custom metadata type from a custom setting with a specific singular and plural label:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --label \"My CMDT\" --plural-label \"My CMDTs\" --sobject MySourceSetting__c --visibility Protected",
-        "Generate a custom metadata type and put the resulting metadata files in the specified directory:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --type-output-directory path/to/my/cmdt/directory",
-        "Generate a custom metadata type and put the resulting record metadata file(s) in the specified directory:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --records-output-dir path/to/my/cmdt/record/directory"
+        "Publish the Experience Builder site with name \"My Customer Site':\n<%= config.bin %> <%= command.id %> --name 'My Customer Site'"
       ],
       "flags": {
         "json": {
@@ -514,6 +464,15 @@
           "multiple": false,
           "type": "option"
         },
+        "name": {
+          "char": "n",
+          "name": "name",
+          "required": true,
+          "summary": "Name of the Experience Builder site to publish.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "target-org": {
           "aliases": [
             "targetusername",
@@ -549,96 +508,95 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "community:publish",
+      "pluginAlias": "@salesforce/plugin-community",
+      "pluginName": "@salesforce/plugin-community",
+      "pluginType": "jit",
+      "strict": true,
+      "summary": "Publish an Experience Builder site to make it live.",
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "community",
+        "publish.js"
+      ],
+      "aliasPermutations": [
+        "force:community:publish",
+        "community:force:publish",
+        "community:publish:force",
+        "force:publish:community",
+        "publish:force:community",
+        "publish:community:force"
+      ],
+      "permutations": [
+        "community:publish",
+        "publish:community"
+      ]
+    },
+    "community:list:template": {
+      "aliases": [
+        "force:community:template:list"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "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 types available for Experience Cloud.",
+      "examples": [
+        "Retrieve the template list from an org with alias my-scratch-org:\n<%= config.bin %> <%= command.id %> --target-org my-scratch-org"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "dev-name": {
-          "aliases": [
-            "devname"
-          ],
-          "char": "n",
-          "name": "dev-name",
-          "required": true,
-          "summary": "Name of the custom metadata type.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "label": {
-          "char": "l",
-          "name": "label",
-          "summary": "Label for the custom metadata type.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "plural-label": {
-          "aliases": [
-            "plurallabel"
-          ],
-          "char": "p",
-          "name": "plural-label",
-          "summary": "Plural version of the label value; if blank, uses label.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "visibility": {
-          "char": "v",
-          "description": "For more information on what each option means, see this topic in Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.custommetadatatypes_ui_create.htm&type=5.",
-          "name": "visibility",
-          "summary": "Who can see the custom metadata type.",
-          "default": "Public",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "PackageProtected",
-            "Protected",
-            "Public"
-          ],
           "type": "option"
         },
-        "sobject": {
+        "target-org": {
           "aliases": [
-            "sobjectname"
+            "targetusername",
+            "u"
           ],
-          "char": "s",
-          "name": "sobject",
+          "char": "o",
+          "deprecateAliases": true,
+          "name": "target-org",
+          "noCacheDefault": true,
           "required": true,
-          "summary": "API name of the source Salesforce object used to generate the custom metadata type.",
-          "hasDynamicHelp": false,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "ignore-unsupported": {
-          "aliases": [
-            "ignoreunsupported"
-          ],
-          "char": "i",
-          "description": "In this context, \"ignore\" means that the fields aren't created. The default behavior is to create fields of type text and convert the field values to text.",
-          "name": "ignore-unsupported",
-          "summary": "Ignore unsupported field types.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "type-output-directory": {
+        "api-version": {
           "aliases": [
-            "typeoutputdir"
+            "apiversion"
           ],
-          "char": "d",
-          "name": "type-output-directory",
-          "summary": "Directory to store newly-created custom metadata type files.",
-          "default": "force-app/main/default/objects",
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "records-output-dir": {
-          "aliases": [
-            "recordsoutputdir"
-          ],
-          "char": "r",
-          "name": "records-output-dir",
-          "summary": "Directory to store newly-created custom metadata record files.",
-          "default": "force-app/main/default/customMetadata",
+        "loglevel": {
+          "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."
+          },
+          "hidden": true,
+          "name": "loglevel",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -646,50 +604,68 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "cmdt:generate:fromorg",
-      "pluginAlias": "@salesforce/plugin-custom-metadata",
-      "pluginName": "@salesforce/plugin-custom-metadata",
+      "id": "community:list:template",
+      "pluginAlias": "@salesforce/plugin-community",
+      "pluginName": "@salesforce/plugin-community",
       "pluginType": "jit",
       "strict": true,
-      "summary": "Generate a custom metadata type and all its records from a Salesforce object.",
+      "summary": "Retrieve the list of templates available in your org.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "cmdt",
-        "generate",
-        "fromorg.js"
+        "community",
+        "list",
+        "template.js"
       ],
       "aliasPermutations": [
-        "force:cmdt:generate",
-        "cmdt:force:generate",
-        "cmdt:generate:force",
-        "force:generate:cmdt",
-        "generate:force:cmdt",
-        "generate:cmdt:force"
+        "force:community:template:list",
+        "community:force:template:list",
+        "community:template:force:list",
+        "community:template:list:force",
+        "force:template:community:list",
+        "template:force:community:list",
+        "template:community:force:list",
+        "template:community:list:force",
+        "force:template:list:community",
+        "template:force:list:community",
+        "template:list:force:community",
+        "template:list:community:force",
+        "force:community:list:template",
+        "community:force:list:template",
+        "community:list:force:template",
+        "community:list:template:force",
+        "force:list:community:template",
+        "list:force:community:template",
+        "list:community:force:template",
+        "list:community:template:force",
+        "force:list:template:community",
+        "list:force:template:community",
+        "list:template:force:community",
+        "list:template:community:force"
       ],
       "permutations": [
-        "cmdt:generate:fromorg",
-        "generate:cmdt:fromorg",
-        "generate:fromorg:cmdt",
-        "cmdt:fromorg:generate",
-        "fromorg:cmdt:generate",
-        "fromorg:generate:cmdt"
+        "community:list:template",
+        "list:community:template",
+        "list:template:community",
+        "community:template:list",
+        "template:community:list",
+        "template:list:community"
       ]
     },
-    "cmdt:generate:object": {
+    "cmdt:generate:field": {
       "aliases": [
-        "force:cmdt:create",
-        "cmdt:create"
+        "force:cmdt:field:create",
+        "cmdt:field:create"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "This command creates a metadata file that describes the new custom metadata type. By default, the file is created in the MyCustomType__mdt directory in the current directory, where MyCustomType is the value of the required --type-name flag. Use the --output-directory to generate the file in a package directory with other custom metadata types, such as \"force-app/main/default/objects\".",
+      "description": "Similar to a custom object, a custom metadata type has a list of custom fields that represent aspects of the metadata.\n\nThis command creates a metadata file that describes the new custom metadata type field. By default, the file is created in a \"fields\" directory in the current directory. Use the --output-directory to generate the file in the directory that contains the custom metadata type metdata files, such as \"force-app/main/default/objects/MyCmdt__mdt\" for the custom metadata type called MyCmdt.",
       "examples": [
-        "Generate a custom metadata type with developer name 'MyCustomType'; this name is also used as the label:\n<%= config.bin %> <%= command.id %> --type-name MyCustomType",
-        "Generate a protected custom metadata type with a specific label:\n<%= config.bin %> <%= command.id %> --type-name MyCustomType --label \"Custom Type\" --plural-label \"Custom Types\" --visibility Protected"
+        "Generate a metadata file for a custom checkbox field and add the file to the MyCmdt__mdt/fields directory:\n<%= config.bin %> <%= command.id %> --name MyCheckboxField --type Checkbox --output-directory force-app/main/default/objects/MyCmdt__mdt",
+        "Generate a metadata file for a custom picklist field and add a few values:\n<%= config.bin %> <%= command.id %> --name MyPicklistField --type Picklist --picklist-values A --picklist-values B --picklist-values C --output-directory force-app/main/default/objects/MyCmdt__mdt",
+        "Generate a metadata file for a custom number field and specify 2 decimal places:\n<%= config.bin %> <%= command.id %> --name MyNumberField --type Number --decimal-places 2 --output-directory force-app/main/default/objects/MyCmdt__mdt"
       ],
       "flags": {
         "json": {
@@ -717,51 +693,76 @@
           "multiple": false,
           "type": "option"
         },
-        "type-name": {
+        "name": {
           "aliases": [
-            "typename"
+            "fieldname"
           ],
           "char": "n",
-          "description": "The name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.",
-          "name": "type-name",
+          "name": "name",
           "required": true,
-          "summary": "Unique object name for the custom metadata type.",
+          "summary": "Unique name for the field.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "label": {
-          "char": "l",
-          "name": "label",
-          "summary": "Label for the custom metadata type.",
+        "type": {
+          "aliases": [
+            "fieldtype"
+          ],
+          "char": "f",
+          "description": "You can't use this command to create a custom metadata type field of type \"Metadata Relationship\". Use the Salesforce Setup UI instead.",
+          "name": "type",
+          "required": true,
+          "summary": "Type of the field.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "Checkbox",
+            "Date",
+            "DateTime",
+            "Email",
+            "Number",
+            "Percent",
+            "Phone",
+            "Picklist",
+            "Text",
+            "TextArea",
+            "LongTextArea",
+            "Url"
+          ],
           "type": "option"
         },
-        "plural-label": {
+        "picklist-values": {
           "aliases": [
-            "plurallabel"
+            "picklistvalues"
           ],
           "char": "p",
-          "name": "plural-label",
-          "summary": "Plural version of the label value; if blank, uses label.",
+          "name": "picklist-values",
+          "summary": "Picklist values; required for picklist fields.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "decimal-places": {
+          "aliases": [
+            "decimalplaces"
+          ],
+          "char": "s",
+          "description": "The value must be greater than or equal to zero. Default value is 0.",
+          "name": "decimal-places",
+          "summary": "Number of decimal places to use for number or percent fields.",
+          "default": 0,
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "visibility": {
-          "char": "v",
-          "description": "For more information on what each option means, see this topic in Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.custommetadatatypes_ui_create.htm&type=5.",
-          "name": "visibility",
-          "summary": "Who can see the custom metadata type.",
-          "default": "Public",
+        "label": {
+          "char": "l",
+          "name": "label",
+          "summary": "Label for the field.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "PackageProtected",
-            "Protected",
-            "Public"
-          ],
           "type": "option"
         },
         "output-directory": {
@@ -770,9 +771,9 @@
             "outputdirectory"
           ],
           "char": "d",
-          "description": "The location can be an absolute path or relative to the current working directory. The default is the current directory.",
+          "description": "New files are automatically created in the \"fields\" directory. The location can be an absolute path or relative to the current working directory. The default is the current directory.",
           "name": "output-directory",
-          "summary": "Directory to store the newly-created custom metadata type files",
+          "summary": "Directory to store newly-created field definition files.",
           "default": "",
           "hasDynamicHelp": false,
           "multiple": false,
@@ -781,12 +782,12 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "cmdt:generate:object",
+      "id": "cmdt:generate:field",
       "pluginAlias": "@salesforce/plugin-custom-metadata",
       "pluginName": "@salesforce/plugin-custom-metadata",
       "pluginType": "jit",
       "strict": true,
-      "summary": "Generate a new custom metadata type in the current project.",
+      "summary": "Generate a field for a custom metadata type based on the provided field type.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -795,38 +796,63 @@
         "commands",
         "cmdt",
         "generate",
-        "object.js"
+        "field.js"
       ],
       "aliasPermutations": [
-        "force:cmdt:create",
-        "cmdt:force:create",
-        "cmdt:create:force",
-        "force:create:cmdt",
-        "create:force:cmdt",
-        "create:cmdt:force",
-        "cmdt:create",
-        "create:cmdt"
-      ],
-      "permutations": [
-        "cmdt:generate:object",
-        "generate:cmdt:object",
-        "generate:object:cmdt",
-        "cmdt:object:generate",
-        "object:cmdt:generate",
-        "object:generate:cmdt"
+        "force:cmdt:field:create",
+        "cmdt:force:field:create",
+        "cmdt:field:force:create",
+        "cmdt:field:create:force",
+        "force:field:cmdt:create",
+        "field:force:cmdt:create",
+        "field:cmdt:force:create",
+        "field:cmdt:create:force",
+        "force:field:create:cmdt",
+        "field:force:create:cmdt",
+        "field:create:force:cmdt",
+        "field:create:cmdt:force",
+        "force:cmdt:create:field",
+        "cmdt:force:create:field",
+        "cmdt:create:force:field",
+        "cmdt:create:field:force",
+        "force:create:cmdt:field",
+        "create:force:cmdt:field",
+        "create:cmdt:force:field",
+        "create:cmdt:field:force",
+        "force:create:field:cmdt",
+        "create:force:field:cmdt",
+        "create:field:force:cmdt",
+        "create:field:cmdt:force",
+        "cmdt:field:create",
+        "field:cmdt:create",
+        "field:create:cmdt",
+        "cmdt:create:field",
+        "create:cmdt:field",
+        "create:field:cmdt"
+      ],
+      "permutations": [
+        "cmdt:generate:field",
+        "generate:cmdt:field",
+        "generate:field:cmdt",
+        "cmdt:field:generate",
+        "field:cmdt:generate",
+        "field:generate:cmdt"
       ]
     },
-    "cmdt:generate:record": {
+    "cmdt:generate:fromorg": {
       "aliases": [
-        "force:cmdt:record:create",
-        "cmdt:record:create"
+        "force:cmdt:generate"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "The custom metadata type must already exist in your project. You must specify a name for the new record. Use name=value pairs to specify the values for the fields, such as MyTextField=\"some text here\" or MyNumberField=32.",
+      "description": "Use this command to migrate existing custom objects or custom settings in an org to custom metadata types. If a field of the Salesforce object is of an unsupported type, the field type is automatically converted to text. Run \"<%= config.bin %> cmdt generate field --help\" to see the list of supported cmdt field types, listed in the --type flag summary. Use the --ignore-unsupported to ignore these fields.\n\nThis command creates the metadata files that describe the new custom metadata type and its fields in the \"force-app/main/default/objects/TypeName__mdt\" directory by default, where \"TypeName\" is the value of the required --dev-name flag. Use --type-output-directory to create them in a different directory.",
       "examples": [
-        "Create a record metadata file for custom metadata type 'MyCMT' with specified values for two custom fields:\n<%= config.bin %> <%= command.id %> --type-name MyCMT__mdt --record-name MyRecord My_Custom_Field_1=Foo My_Custom_Field_2=Bar",
-        "Create a protected record metadata file for custom metadata type 'MyCMT' with a specific label and values specified for two custom fields:\n<%= config.bin %> <%= command.id %> --type-name MyCMT__mdt --record-name MyRecord --label \"My Record\" --protected true My_Custom_Field_1=Foo My_Custom_Field_2=Bar"
+        "Generate a custom metadata type from a custom object called MySourceObject__c in your default org:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c",
+        "Generate a custom metadata type from a custom object in an org with alias my-scratch-org; ignore unsupported field types instead of converting them to text:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --ignore-unsupported --target-org my-scratch-org",
+        "Generate a protected custom metadata type from a custom object:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --visibility Protected",
+        "Generate a protected custom metadata type from a custom setting with a specific singular and plural label:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --label \"My CMDT\" --plural-label \"My CMDTs\" --sobject MySourceSetting__c --visibility Protected",
+        "Generate a custom metadata type and put the resulting metadata files in the specified directory:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --type-output-directory path/to/my/cmdt/directory",
+        "Generate a custom metadata type and put the resulting record metadata file(s) in the specified directory:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c --records-output-dir path/to/my/cmdt/record/directory"
       ],
       "flags": {
         "json": {
@@ -844,6 +870,32 @@
           "multiple": false,
           "type": "option"
         },
+        "target-org": {
+          "aliases": [
+            "targetusername",
+            "u"
+          ],
+          "char": "o",
+          "deprecateAliases": true,
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "aliases": [
+            "apiversion"
+          ],
+          "deprecateAliases": true,
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "loglevel": {
           "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."
@@ -854,26 +906,14 @@
           "multiple": false,
           "type": "option"
         },
-        "type-name": {
-          "aliases": [
-            "typename"
-          ],
-          "char": "t",
-          "name": "type-name",
-          "required": true,
-          "summary": "API name of the custom metadata type to create a record for; must end in \"__mdt\".",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "record-name": {
+        "dev-name": {
           "aliases": [
-            "recordname"
+            "devname"
           ],
           "char": "n",
-          "name": "record-name",
+          "name": "dev-name",
           "required": true,
-          "summary": "Name of the new record.",
+          "summary": "Name of the custom metadata type.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -881,45 +921,78 @@
         "label": {
           "char": "l",
           "name": "label",
-          "summary": "Label for the new record.",
+          "summary": "Label for the custom metadata type.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "protected": {
+        "plural-label": {
+          "aliases": [
+            "plurallabel"
+          ],
           "char": "p",
-          "description": "Protected records can only be accessed by code in the same managed package namespace.",
-          "name": "protected",
-          "summary": "Protect the record when it's in a managed package.",
-          "default": "false",
+          "name": "plural-label",
+          "summary": "Plural version of the label value; if blank, uses label.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "visibility": {
+          "char": "v",
+          "description": "For more information on what each option means, see this topic in Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.custommetadatatypes_ui_create.htm&type=5.",
+          "name": "visibility",
+          "summary": "Who can see the custom metadata type.",
+          "default": "Public",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "true",
-            "false"
+            "PackageProtected",
+            "Protected",
+            "Public"
           ],
           "type": "option"
         },
-        "input-directory": {
+        "sobject": {
           "aliases": [
-            "inputdir",
-            "inputdirectory"
+            "sobjectname"
+          ],
+          "char": "s",
+          "name": "sobject",
+          "required": true,
+          "summary": "API name of the source Salesforce object used to generate the custom metadata type.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "ignore-unsupported": {
+          "aliases": [
+            "ignoreunsupported"
           ],
           "char": "i",
-          "name": "input-directory",
-          "summary": "Directory from which to get the custom metadata type definition from.",
+          "description": "In this context, \"ignore\" means that the fields aren't created. The default behavior is to create fields of type text and convert the field values to text.",
+          "name": "ignore-unsupported",
+          "summary": "Ignore unsupported field types.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "type-output-directory": {
+          "aliases": [
+            "typeoutputdir"
+          ],
+          "char": "d",
+          "name": "type-output-directory",
+          "summary": "Directory to store newly-created custom metadata type files.",
           "default": "force-app/main/default/objects",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "output-directory": {
+        "records-output-dir": {
           "aliases": [
-            "outputdir",
-            "outputdirectory"
+            "recordsoutputdir"
           ],
-          "char": "d",
-          "name": "output-directory",
+          "char": "r",
+          "name": "records-output-dir",
           "summary": "Directory to store newly-created custom metadata record files.",
           "default": "force-app/main/default/customMetadata",
           "hasDynamicHelp": false,
@@ -927,14 +1000,14 @@
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "cmdt:generate:record",
+      "id": "cmdt:generate:fromorg",
       "pluginAlias": "@salesforce/plugin-custom-metadata",
       "pluginName": "@salesforce/plugin-custom-metadata",
       "pluginType": "jit",
-      "strict": false,
-      "summary": "Generate a new record for a given custom metadata type in the current project.",
+      "strict": true,
+      "summary": "Generate a custom metadata type and all its records from a Salesforce object.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -943,60 +1016,36 @@
         "commands",
         "cmdt",
         "generate",
-        "record.js"
+        "fromorg.js"
       ],
       "aliasPermutations": [
-        "force:cmdt:record:create",
-        "cmdt:force:record:create",
-        "cmdt:record:force:create",
-        "cmdt:record:create:force",
-        "force:record:cmdt:create",
-        "record:force:cmdt:create",
-        "record:cmdt:force:create",
-        "record:cmdt:create:force",
-        "force:record:create:cmdt",
-        "record:force:create:cmdt",
-        "record:create:force:cmdt",
-        "record:create:cmdt:force",
-        "force:cmdt:create:record",
-        "cmdt:force:create:record",
-        "cmdt:create:force:record",
-        "cmdt:create:record:force",
-        "force:create:cmdt:record",
-        "create:force:cmdt:record",
-        "create:cmdt:force:record",
-        "create:cmdt:record:force",
-        "force:create:record:cmdt",
-        "create:force:record:cmdt",
-        "create:record:force:cmdt",
-        "create:record:cmdt:force",
-        "cmdt:record:create",
-        "record:cmdt:create",
-        "record:create:cmdt",
-        "cmdt:create:record",
-        "create:cmdt:record",
-        "create:record:cmdt"
+        "force:cmdt:generate",
+        "cmdt:force:generate",
+        "cmdt:generate:force",
+        "force:generate:cmdt",
+        "generate:force:cmdt",
+        "generate:cmdt:force"
       ],
       "permutations": [
-        "cmdt:generate:record",
-        "generate:cmdt:record",
-        "generate:record:cmdt",
-        "cmdt:record:generate",
-        "record:cmdt:generate",
-        "record:generate:cmdt"
+        "cmdt:generate:fromorg",
+        "generate:cmdt:fromorg",
+        "generate:fromorg:cmdt",
+        "cmdt:fromorg:generate",
+        "fromorg:cmdt:generate",
+        "fromorg:generate:cmdt"
       ]
     },
-    "cmdt:generate:records": {
+    "cmdt:generate:object": {
       "aliases": [
-        "force:cmdt:record:insert",
-        "cmdt:record:insert"
+        "force:cmdt:create",
+        "cmdt:create"
       ],
       "args": {},
       "deprecateAliases": true,
-      "description": "The custom metadata type must already exist in your project. By default, the Name column is used to determine the record name; use the --name-column flag to specify a different column.",
+      "description": "This command creates a metadata file that describes the new custom metadata type. By default, the file is created in the MyCustomType__mdt directory in the current directory, where MyCustomType is the value of the required --type-name flag. Use the --output-directory to generate the file in a package directory with other custom metadata types, such as \"force-app/main/default/objects\".",
       "examples": [
-        "Generate record metadata files from values in a CSV file for the custom metadata type MyCmdt. Use 'Name' as the column that specifies the record name:\n<%= config.bin %> <%= command.id %> --csv path/to/my.csv --type-name MyCmdt",
-        "Generate record metadata files from a CSV file in the directory different from the default, and use 'PrimaryKey' as the column that specifies the record name:\n<%= config.bin %> <%= command.id %> --csv path/to/my.csv --type-name MyCmdt --input-directory path/to/my/cmdt/directory --name-column \"PrimaryKey\""
+        "Generate a custom metadata type with developer name 'MyCustomType'; this name is also used as the label:\n<%= config.bin %> <%= command.id %> --type-name MyCustomType",
+        "Generate a protected custom metadata type with a specific label:\n<%= config.bin %> <%= command.id %> --type-name MyCustomType --label \"Custom Type\" --plural-label \"Custom Types\" --visibility Protected"
       ],
       "flags": {
         "json": {
@@ -1024,42 +1073,51 @@
           "multiple": false,
           "type": "option"
         },
-        "csv": {
+        "type-name": {
           "aliases": [
-            "filepath"
+            "typename"
           ],
-          "char": "f",
-          "name": "csv",
+          "char": "n",
+          "description": "The name can contain only underscores and alphanumeric characters, and must be unique in your org. It must begin with a letter, not include spaces, not end with an underscore, and not contain two consecutive underscores.",
+          "name": "type-name",
           "required": true,
-          "summary": "Pathname of the CSV file.",
+          "summary": "Unique object name for the custom metadata type.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "type-name": {
-          "aliases": [
-            "typename"
-          ],
-          "char": "t",
-          "description": "The '__mdt' suffix is appended to the end of the name if it's omitted.",
-          "name": "type-name",
-          "required": true,
-          "summary": "API name of the custom metadata type to create a record for.",
+        "label": {
+          "char": "l",
+          "name": "label",
+          "summary": "Label for the custom metadata type.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "input-directory": {
+        "plural-label": {
           "aliases": [
-            "inputdir",
-            "inputdirectory"
+            "plurallabel"
           ],
-          "char": "i",
-          "name": "input-directory",
-          "summary": "Directory from which to get the custom metadata type definition from.",
-          "default": "force-app/main/default/objects",
+          "char": "p",
+          "name": "plural-label",
+          "summary": "Plural version of the label value; if blank, uses label.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "visibility": {
+          "char": "v",
+          "description": "For more information on what each option means, see this topic in Salesforce Help: https://help.salesforce.com/s/articleView?id=sf.custommetadatatypes_ui_create.htm&type=5.",
+          "name": "visibility",
+          "summary": "Who can see the custom metadata type.",
+          "default": "Public",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "PackageProtected",
+            "Protected",
+            "Public"
+          ],
           "type": "option"
         },
         "output-directory": {
@@ -1068,21 +1126,10 @@
             "outputdirectory"
           ],
           "char": "d",
+          "description": "The location can be an absolute path or relative to the current working directory. The default is the current directory.",
           "name": "output-directory",
-          "summary": "Directory to store newly-created custom metadata record files.",
-          "default": "force-app/main/default/customMetadata",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "name-column": {
-          "aliases": [
-            "namecolumn"
-          ],
-          "char": "n",
-          "name": "name-column",
-          "summary": "Column used to determine the name of the record.",
-          "default": "Name",
+          "summary": "Directory to store the newly-created custom metadata type files",
+          "default": "",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1090,12 +1137,12 @@
       },
       "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "cmdt:generate:records",
+      "id": "cmdt:generate:object",
       "pluginAlias": "@salesforce/plugin-custom-metadata",
       "pluginName": "@salesforce/plugin-custom-metadata",
       "pluginType": "jit",
       "strict": true,
-      "summary": "Generate new custom metadata type records from a CSV file.",
+      "summary": "Generate a new custom metadata type in the current project.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "isESM": true,
@@ -1104,60 +1151,38 @@
         "commands",
         "cmdt",
         "generate",
-        "records.js"
+        "object.js"
       ],
       "aliasPermutations": [
-        "force:cmdt:record:insert",
-        "cmdt:force:record:insert",
-        "cmdt:record:force:insert",
-        "cmdt:record:insert:force",
-        "force:record:cmdt:insert",
-        "record:force:cmdt:insert",
-        "record:cmdt:force:insert",
-        "record:cmdt:insert:force",
-        "force:record:insert:cmdt",
-        "record:force:insert:cmdt",
-        "record:insert:force:cmdt",
-        "record:insert:cmdt:force",
-        "force:cmdt:insert:record",
-        "cmdt:force:insert:record",
-        "cmdt:insert:force:record",
-        "cmdt:insert:record:force",
-        "force:insert:cmdt:record",
-        "insert:force:cmdt:record",
-        "insert:cmdt:force:record",
-        "insert:cmdt:record:force",
-        "force:insert:record:cmdt",
-        "insert:force:record:cmdt",
-        "insert:record:force:cmdt",
-        "insert:record:cmdt:force",
-        "cmdt:record:insert",
-        "record:cmdt:insert",
-        "record:insert:cmdt",
-        "cmdt:insert:record",
-        "insert:cmdt:record",
-        "insert:record:cmdt"
+        "force:cmdt:create",
+        "cmdt:force:create",
+        "cmdt:create:force",
+        "force:create:cmdt",
+        "create:force:cmdt",
+        "create:cmdt:force",
+        "cmdt:create",
+        "create:cmdt"
       ],
       "permutations": [
-        "cmdt:generate:records",
-        "generate:cmdt:records",
-        "generate:records:cmdt",
-        "cmdt:records:generate",
-        "records:cmdt:generate",
-        "records:generate:cmdt"
+        "cmdt:generate:object",
+        "generate:cmdt:object",
+        "generate:object:cmdt",
+        "cmdt:object:generate",
+        "object:cmdt:generate",
+        "object:generate:cmdt"
       ]
     },
-    "community:create": {
+    "cmdt:generate:record": {
       "aliases": [
-        "force:community:create"
+        "force:cmdt:record:create",
+        "cmdt:record:create"
       ],
       "args": {},
       "deprecateAliases": true,
-      "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.",
+      "description": "The custom metadata type must already exist in your project. You must specify a name for the new record. Use name=value pairs to specify the values for the fields, such as MyTextField=\"some text here\" or MyNumberField=32.",
       "examples": [
-        "Create an Experience Cloud site using template 'Customer Service' and URL path prefix 'customers':\n<%= config.bin %> <%= command.id %> --name 'My Customer Site' --template-name 'Customer Service' --url-path-prefix customers --description 'My customer site'",
-        "Create a site using 'Partner Central' template:\n<%= config.bin %> <%= command.id %> --name partnercentral --template-name 'Partner Central' --url-path-prefix partners",
-        "Create a site using the 'Build Your Own (LWR)' template with authentication type of UNAUTHENTICATED:\n<%= config.bin %> <%= command.id %> --name lwrsite --template-name 'Build Your Own (LWR)' --url-path-prefix lwrsite templateParams.AuthenticationType=UNAUTHENTICATED"
+        "Create a record metadata file for custom metadata type 'MyCMT' with specified values for two custom fields:\n<%= config.bin %> <%= command.id %> --type-name MyCMT__mdt --record-name MyRecord My_Custom_Field_1=Foo My_Custom_Field_2=Bar",
+        "Create a protected record metadata file for custom metadata type 'MyCMT' with a specific label and values specified for two custom fields:\n<%= config.bin %> <%= command.id %> --type-name MyCMT__mdt --record-name MyRecord --label \"My Record\" --protected true My_Custom_Field_1=Foo My_Custom_Field_2=Bar"
       ],
       "flags": {
         "json": {
@@ -1175,129 +1200,161 @@
           "multiple": false,
           "type": "option"
         },
-        "name": {
-          "char": "n",
-          "name": "name",
-          "required": true,
-          "summary": "Name of the site to create.",
+        "loglevel": {
+          "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."
+          },
+          "hidden": true,
+          "name": "loglevel",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "template-name": {
+        "type-name": {
           "aliases": [
-            "templatename"
+            "typename"
           ],
           "char": "t",
-          "deprecateAliases": true,
-          "description": "An example of a template is Customer Service. Run the \"community template list\" command to see which templates are available in your org.",
-          "name": "template-name",
+          "name": "type-name",
           "required": true,
-          "summary": "Template to use to create a site.",
+          "summary": "API name of the custom metadata type to create a record for; must end in \"__mdt\".",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "url-path-prefix": {
+        "record-name": {
           "aliases": [
-            "urlpathprefix"
+            "recordname"
           ],
-          "char": "p",
-          "deprecateAliases": true,
-          "description": "For example, if your domain name is https://MyDomainName.my.site.com and you create a customer site, enter 'customers' to create the unique URL https://MyDomainName.my.site.com/customers.",
-          "name": "url-path-prefix",
-          "summary": "URL to append to the domain created when Digital Experiences was enabled for this org.",
-          "default": "",
+          "char": "n",
+          "name": "record-name",
+          "required": true,
+          "summary": "Name of the new record.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "description": {
-          "char": "d",
-          "description": "The description displays in Digital Experiences - All Sites in Setup and helps with site identification.",
-          "name": "description",
-          "summary": "Description of the site.",
+        "label": {
+          "char": "l",
+          "name": "label",
+          "summary": "Label for the new record.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "aliases": [
-            "targetusername",
-            "u"
-          ],
-          "char": "o",
-          "deprecateAliases": true,
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
+        "protected": {
+          "char": "p",
+          "description": "Protected records can only be accessed by code in the same managed package namespace.",
+          "name": "protected",
+          "summary": "Protect the record when it's in a managed package.",
+          "default": "false",
+          "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "true",
+            "false"
+          ],
           "type": "option"
         },
-        "loglevel": {
-          "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."
-          },
-          "hidden": true,
-          "name": "loglevel",
+        "input-directory": {
+          "aliases": [
+            "inputdir",
+            "inputdirectory"
+          ],
+          "char": "i",
+          "name": "input-directory",
+          "summary": "Directory from which to get the custom metadata type definition from.",
+          "default": "force-app/main/default/objects",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
+        "output-directory": {
           "aliases": [
-            "apiversion"
+            "outputdir",
+            "outputdirectory"
           ],
-          "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+          "char": "d",
+          "name": "output-directory",
+          "summary": "Directory to store newly-created custom metadata record files.",
+          "default": "force-app/main/default/customMetadata",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "community:create",
-      "pluginAlias": "@salesforce/plugin-community",
-      "pluginName": "@salesforce/plugin-community",
+      "id": "cmdt:generate:record",
+      "pluginAlias": "@salesforce/plugin-custom-metadata",
+      "pluginName": "@salesforce/plugin-custom-metadata",
       "pluginType": "jit",
       "strict": false,
-      "summary": "Create an Experience Cloud site using a template.",
+      "summary": "Generate a new record for a given custom metadata type in the current project.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "community",
-        "create.js"
+        "cmdt",
+        "generate",
+        "record.js"
       ],
       "aliasPermutations": [
-        "force:community:create",
-        "community:force:create",
-        "community:create:force",
-        "force:create:community",
-        "create:force:community",
-        "create:community:force"
-      ],
-      "permutations": [
-        "community:create",
-        "create:community"
-      ]
-    },
-    "community:publish": {
-      "aliases": [
-        "force:community:publish"
-      ],
-      "args": {},
-      "deprecateAliases": true,
-      "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.",
-      "examples": [
-        "Publish the Experience Builder site with name \"My Customer Site':\n<%= config.bin %> <%= command.id %> --name 'My Customer Site'"
-      ],
-      "flags": {
+        "force:cmdt:record:create",
+        "cmdt:force:record:create",
+        "cmdt:record:force:create",
+        "cmdt:record:create:force",
+        "force:record:cmdt:create",
+        "record:force:cmdt:create",
+        "record:cmdt:force:create",
+        "record:cmdt:create:force",
+        "force:record:create:cmdt",
+        "record:force:create:cmdt",
+        "record:create:force:cmdt",
+        "record:create:cmdt:force",
+        "force:cmdt:create:record",
+        "cmdt:force:create:record",
+        "cmdt:create:force:record",
+        "cmdt:create:record:force",
+        "force:create:cmdt:record",
+        "create:force:cmdt:record",
+        "create:cmdt:force:record",
+        "create:cmdt:record:force",
+        "force:create:record:cmdt",
+        "create:force:record:cmdt",
+        "create:record:force:cmdt",
+        "create:record:cmdt:force",
+        "cmdt:record:create",
+        "record:cmdt:create",
+        "record:create:cmdt",
+        "cmdt:create:record",
+        "create:cmdt:record",
+        "create:record:cmdt"
+      ],
+      "permutations": [
+        "cmdt:generate:record",
+        "generate:cmdt:record",
+        "generate:record:cmdt",
+        "cmdt:record:generate",
+        "record:cmdt:generate",
+        "record:generate:cmdt"
+      ]
+    },
+    "cmdt:generate:records": {
+      "aliases": [
+        "force:cmdt:record:insert",
+        "cmdt:record:insert"
+      ],
+      "args": {},
+      "deprecateAliases": true,
+      "description": "The custom metadata type must already exist in your project. By default, the Name column is used to determine the record name; use the --name-column flag to specify a different column.",
+      "examples": [
+        "Generate record metadata files from values in a CSV file for the custom metadata type MyCmdt. Use 'Name' as the column that specifies the record name:\n<%= config.bin %> <%= command.id %> --csv path/to/my.csv --type-name MyCmdt",
+        "Generate record metadata files from a CSV file in the directory different from the default, and use 'PrimaryKey' as the column that specifies the record name:\n<%= config.bin %> <%= command.id %> --csv path/to/my.csv --type-name MyCmdt --input-directory path/to/my/cmdt/directory --name-column \"PrimaryKey\""
+      ],
+      "flags": {
         "json": {
           "description": "Format output as json.",
           "helpGroup": "GLOBAL",
@@ -1313,90 +1370,145 @@
           "multiple": false,
           "type": "option"
         },
-        "name": {
-          "char": "n",
-          "name": "name",
+        "loglevel": {
+          "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."
+          },
+          "hidden": true,
+          "name": "loglevel",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "csv": {
+          "aliases": [
+            "filepath"
+          ],
+          "char": "f",
+          "name": "csv",
           "required": true,
-          "summary": "Name of the Experience Builder site to publish.",
+          "summary": "Pathname of the CSV file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
+        "type-name": {
           "aliases": [
-            "targetusername",
-            "u"
+            "typename"
           ],
-          "char": "o",
-          "deprecateAliases": true,
-          "name": "target-org",
-          "noCacheDefault": true,
+          "char": "t",
+          "description": "The '__mdt' suffix is appended to the end of the name if it's omitted.",
+          "name": "type-name",
           "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
+          "summary": "API name of the custom metadata type to create a record for.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
+        "input-directory": {
           "aliases": [
-            "apiversion"
+            "inputdir",
+            "inputdirectory"
           ],
-          "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+          "char": "i",
+          "name": "input-directory",
+          "summary": "Directory from which to get the custom metadata type definition from.",
+          "default": "force-app/main/default/objects",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "loglevel": {
-          "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."
-          },
-          "hidden": true,
-          "name": "loglevel",
+        "output-directory": {
+          "aliases": [
+            "outputdir",
+            "outputdirectory"
+          ],
+          "char": "d",
+          "name": "output-directory",
+          "summary": "Directory to store newly-created custom metadata record files.",
+          "default": "force-app/main/default/customMetadata",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "name-column": {
+          "aliases": [
+            "namecolumn"
+          ],
+          "char": "n",
+          "name": "name-column",
+          "summary": "Column used to determine the name of the record.",
+          "default": "Name",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "community:publish",
-      "pluginAlias": "@salesforce/plugin-community",
-      "pluginName": "@salesforce/plugin-community",
+      "id": "cmdt:generate:records",
+      "pluginAlias": "@salesforce/plugin-custom-metadata",
+      "pluginName": "@salesforce/plugin-custom-metadata",
       "pluginType": "jit",
       "strict": true,
-      "summary": "Publish an Experience Builder site to make it live.",
+      "summary": "Generate new custom metadata type records from a CSV file.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "community",
-        "publish.js"
+        "cmdt",
+        "generate",
+        "records.js"
       ],
       "aliasPermutations": [
-        "force:community:publish",
-        "community:force:publish",
-        "community:publish:force",
-        "force:publish:community",
-        "publish:force:community",
-        "publish:community:force"
+        "force:cmdt:record:insert",
+        "cmdt:force:record:insert",
+        "cmdt:record:force:insert",
+        "cmdt:record:insert:force",
+        "force:record:cmdt:insert",
+        "record:force:cmdt:insert",
+        "record:cmdt:force:insert",
+        "record:cmdt:insert:force",
+        "force:record:insert:cmdt",
+        "record:force:insert:cmdt",
+        "record:insert:force:cmdt",
+        "record:insert:cmdt:force",
+        "force:cmdt:insert:record",
+        "cmdt:force:insert:record",
+        "cmdt:insert:force:record",
+        "cmdt:insert:record:force",
+        "force:insert:cmdt:record",
+        "insert:force:cmdt:record",
+        "insert:cmdt:force:record",
+        "insert:cmdt:record:force",
+        "force:insert:record:cmdt",
+        "insert:force:record:cmdt",
+        "insert:record:force:cmdt",
+        "insert:record:cmdt:force",
+        "cmdt:record:insert",
+        "record:cmdt:insert",
+        "record:insert:cmdt",
+        "cmdt:insert:record",
+        "insert:cmdt:record",
+        "insert:record:cmdt"
       ],
       "permutations": [
-        "community:publish",
-        "publish:community"
+        "cmdt:generate:records",
+        "generate:cmdt:records",
+        "generate:records:cmdt",
+        "cmdt:records:generate",
+        "records:cmdt:generate",
+        "records:generate:cmdt"
       ]
     },
-    "community:list:template": {
-      "aliases": [
-        "force:community:template:list"
-      ],
+    "dev:audit:messages": {
+      "aliases": [],
       "args": {},
-      "deprecateAliases": true,
-      "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 types available for Experience Cloud.",
       "examples": [
-        "Retrieve the template list from an org with alias my-scratch-org:\n<%= config.bin %> <%= command.id %> --target-org my-scratch-org"
+        "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": {
@@ -1414,165 +1526,53 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
+        "project-dir": {
           "aliases": [
-            "targetusername",
-            "u"
+            "projectdir"
           ],
-          "char": "o",
-          "deprecateAliases": true,
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
+          "char": "p",
+          "name": "project-dir",
+          "summary": "Location of the project where messages are to be audited.",
+          "default": ".",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
+        "messages-dir": {
           "aliases": [
-            "apiversion"
+            "messagesdir"
           ],
-          "deprecateAliases": true,
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+          "char": "m",
+          "description": "The default is the \"messages\" directory in the current working directory.",
+          "name": "messages-dir",
+          "summary": "Directory that contains the plugin's message files.",
+          "default": "messages",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "loglevel": {
-          "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."
-          },
-          "hidden": true,
-          "name": "loglevel",
+        "source-dir": {
+          "aliases": [
+            "sourcedir"
+          ],
+          "char": "s",
+          "description": "The default is the \"src\" directory in the current working directory.",
+          "name": "source-dir",
+          "summary": "Directory that contains the plugin's source code.",
+          "default": "src",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "community:list:template",
-      "pluginAlias": "@salesforce/plugin-community",
-      "pluginName": "@salesforce/plugin-community",
+      "id": "dev:audit:messages",
+      "pluginAlias": "@salesforce/plugin-dev",
+      "pluginName": "@salesforce/plugin-dev",
       "pluginType": "jit",
       "strict": true,
-      "summary": "Retrieve the list of templates available in your org.",
-      "enableJsonFlag": true,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "community",
-        "list",
-        "template.js"
-      ],
-      "aliasPermutations": [
-        "force:community:template:list",
-        "community:force:template:list",
-        "community:template:force:list",
-        "community:template:list:force",
-        "force:template:community:list",
-        "template:force:community:list",
-        "template:community:force:list",
-        "template:community:list:force",
-        "force:template:list:community",
-        "template:force:list:community",
-        "template:list:force:community",
-        "template:list:community:force",
-        "force:community:list:template",
-        "community:force:list:template",
-        "community:list:force:template",
-        "community:list:template:force",
-        "force:list:community:template",
-        "list:force:community:template",
-        "list:community:force:template",
-        "list:community:template:force",
-        "force:list:template:community",
-        "list:force:template:community",
-        "list:template:force:community",
-        "list:template:community:force"
-      ],
-      "permutations": [
-        "community:list:template",
-        "list:community:template",
-        "list:template:community",
-        "community:template:list",
-        "template:community:list",
-        "template:list:community"
-      ]
-    },
-    "dev:audit:messages": {
-      "aliases": [],
-      "args": {},
-      "examples": [
-        "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": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "project-dir": {
-          "aliases": [
-            "projectdir"
-          ],
-          "char": "p",
-          "name": "project-dir",
-          "summary": "Location of the project where messages are to be audited.",
-          "default": ".",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "messages-dir": {
-          "aliases": [
-            "messagesdir"
-          ],
-          "char": "m",
-          "description": "The default is the \"messages\" directory in the current working directory.",
-          "name": "messages-dir",
-          "summary": "Directory that contains the plugin's message files.",
-          "default": "messages",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "source-dir": {
-          "aliases": [
-            "sourcedir"
-          ],
-          "char": "s",
-          "description": "The default is the \"src\" directory in the current working directory.",
-          "name": "source-dir",
-          "summary": "Directory that contains the plugin's source code.",
-          "default": "src",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "dev:audit:messages",
-      "pluginAlias": "@salesforce/plugin-dev",
-      "pluginName": "@salesforce/plugin-dev",
-      "pluginType": "jit",
-      "strict": true,
-      "summary": "Audit messages in a plugin's messages directory to locate unused messages and missing messages that have references in source code.",
+      "summary": "Audit messages in a plugin's messages directory to locate unused messages and missing messages that have references in source code.",
       "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
@@ -2154,14 +2154,324 @@
           "exclusive": [
             "verbose"
           ],
-          "name": "concise",
-          "summary": "Show concise output of the command result.",
-          "allowNo": false,
-          "type": "boolean"
+          "name": "concise",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "verbose": {
+          "name": "verbose",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run \"sf project deploy pipeline report\".",
+          "exclusive": [
+            "async"
+          ],
+          "name": "wait",
+          "summary": "Number of minutes to wait for command to complete and display results.",
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "type": "option"
+        },
+        "devops-center-username": {
+          "char": "c",
+          "name": "devops-center-username",
+          "required": true,
+          "summary": "Username or alias of the DevOps Center org.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "job-id": {
+          "char": "i",
+          "description": "The job ID is valid for 10 days from when you started the validation.",
+          "name": "job-id",
+          "summary": "Job ID of the validated deployment to quick deploy.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "use-most-recent": {
+          "char": "r",
+          "description": "For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most recent deployment validation was more than 3 days ago, this flag won't find the job ID.",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recently validated deployment.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:pipeline:quick",
+      "pluginAlias": "@salesforce/plugin-devops-center",
+      "pluginName": "@salesforce/plugin-devops-center",
+      "pluginType": "jit",
+      "state": "beta",
+      "strict": true,
+      "summary": "Quickly deploy a validated deployment to an org.",
+      "enableJsonFlag": true,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "deploy",
+        "pipeline",
+        "quick.js"
+      ]
+    },
+    "project:deploy:pipeline:report": {
+      "aliases": [],
+      "args": {},
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nRun this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "examples": [
+        "Check the status using a job ID:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --job-id 0Af0x000017yLUFCA2",
+        "Check the status of the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --use-most-recent"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "devops-center-username": {
+          "char": "c",
+          "name": "devops-center-username",
+          "required": true,
+          "summary": "Username or alias of the DevOps Center org.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "job-id": {
+          "char": "i",
+          "description": "The job ID is valid for 10 days from when you started the deploy operation.",
+          "name": "job-id",
+          "summary": "Job ID of the pipeline deployment to check the status of.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "use-most-recent": {
+          "char": "r",
+          "description": "For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find the job ID.",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recent deploy operation.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:pipeline:report",
+      "pluginAlias": "@salesforce/plugin-devops-center",
+      "pluginName": "@salesforce/plugin-devops-center",
+      "pluginType": "jit",
+      "state": "beta",
+      "strict": true,
+      "summary": "Check the status of a pipeline deploy operation.",
+      "enableJsonFlag": true,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "deploy",
+        "pipeline",
+        "report.js"
+      ]
+    },
+    "project:deploy:pipeline:resume": {
+      "aliases": [],
+      "args": {},
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command. \n\nUse this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "examples": [
+        "Resume watching a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
+        "Resume watching the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "devops-center-username": {
+          "char": "c",
+          "name": "devops-center-username",
+          "required": true,
+          "summary": "Username or alias of the DevOps Center org.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "job-id": {
+          "char": "i",
+          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- sf project deploy pipeline start\n- sf project deploy pipeline validate\n- sf project deploy pipeline quick\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
+          "name": "job-id",
+          "summary": "Job ID of the pipeline deploy operation you want to resume.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "use-most-recent": {
+          "char": "r",
+          "description": "For performance reasons, this flag uses job IDs for operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find a job ID.",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recent deploy operation.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "verbose": {
+          "name": "verbose",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "wait": {
+          "char": "w",
+          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run \"sf project deploy pipeline report\".",
+          "exclusive": [
+            "async"
+          ],
+          "name": "wait",
+          "summary": "Number of minutes to wait for command to complete and display results.",
+          "default": "33 minutes",
+          "hasDynamicHelp": true,
+          "helpValue": "<minutes>",
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "project:deploy:pipeline:resume",
+      "pluginAlias": "@salesforce/plugin-devops-center",
+      "pluginName": "@salesforce/plugin-devops-center",
+      "pluginType": "jit",
+      "state": "beta",
+      "strict": true,
+      "summary": "Resume watching a pipeline deploy operation.",
+      "enableJsonFlag": true,
+      "SF_ENV": "SF_ENV",
+      "isESM": false,
+      "relativePath": [
+        "lib",
+        "commands",
+        "project",
+        "deploy",
+        "pipeline",
+        "resume.js"
+      ]
+    },
+    "project:deploy:pipeline:start": {
+      "aliases": [],
+      "args": {},
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nBefore you run this command, changes in the pipeline stage's branch must be merged in the source control repository.",
+      "examples": [
+        "Deploy changes in the Staging branch to the Staging environment (sandbox), if the previous stage is the bundling stage:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox --bundle-version-name 1.0",
+        "Deploy all changes in the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "branch-name": {
+          "char": "b",
+          "name": "branch-name",
+          "required": true,
+          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "bundle-version-name": {
+          "char": "v",
+          "description": "You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage.",
+          "name": "bundle-version-name",
+          "summary": "Version name of the bundle.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "deploy-all": {
+          "char": "a",
+          "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
+          "name": "deploy-all",
+          "summary": "Deploy all metadata in the branch to the stage's org.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "devops-center-project-name": {
+          "char": "p",
+          "name": "devops-center-project-name",
+          "required": true,
+          "summary": "Name of the DevOps Center project.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "devops-center-username": {
+          "char": "c",
+          "name": "devops-center-username",
+          "required": true,
+          "summary": "Username or alias of the DevOps Center org.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "tests": {
+          "char": "t",
+          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
+          "name": "tests",
+          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
+        },
+        "test-level": {
+          "char": "l",
+          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\nIf you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section \"Running Tests in a Deployment\" in the \"Metadata API Developer Guide\". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)",
+          "name": "test-level",
+          "summary": "Deployment Apex testing level.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "NoTestRun",
+            "RunSpecifiedTests",
+            "RunLocalTests",
+            "RunAllTestsInOrg"
+          ],
+          "type": "option"
         },
-        "verbose": {
-          "name": "verbose",
-          "summary": "Show verbose output of the command result.",
+        "async": {
+          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"sf project deploy pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
+          "name": "async",
+          "summary": "Run the command asynchronously.",
           "allowNo": false,
           "type": "boolean"
         },
@@ -2179,42 +2489,31 @@
           "multiple": false,
           "type": "option"
         },
-        "devops-center-username": {
-          "char": "c",
-          "name": "devops-center-username",
-          "required": true,
-          "summary": "Username or alias of the DevOps Center org.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        },
-        "job-id": {
-          "char": "i",
-          "description": "The job ID is valid for 10 days from when you started the validation.",
-          "name": "job-id",
-          "summary": "Job ID of the validated deployment to quick deploy.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "verbose": {
+          "name": "verbose",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "use-most-recent": {
-          "char": "r",
-          "description": "For performance reasons, this flag uses only job IDs that were validated in the past 3 days or less. If your most recent deployment validation was more than 3 days ago, this flag won't find the job ID.",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recently validated deployment.",
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Show concise output of the command result.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:pipeline:quick",
+      "id": "project:deploy:pipeline:start",
       "pluginAlias": "@salesforce/plugin-devops-center",
       "pluginName": "@salesforce/plugin-devops-center",
       "pluginType": "jit",
       "state": "beta",
       "strict": true,
-      "summary": "Quickly deploy a validated deployment to an org.",
+      "summary": "Deploy changes from a branch to the pipeline stage’s org.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -2224,16 +2523,16 @@
         "project",
         "deploy",
         "pipeline",
-        "quick.js"
+        "start.js"
       ]
     },
-    "project:deploy:pipeline:report": {
+    "project:deploy:pipeline:validate": {
       "aliases": [],
       "args": {},
-      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nRun this command by either indicating a job ID or specifying the —use-most-recent flag to use the job ID of the most recent deploy operation.",
+      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nA validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.",
       "examples": [
-        "Check the status using a job ID:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --job-id 0Af0x000017yLUFCA2",
-        "Check the status of the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --devops-center-username MyStagingSandbox --use-most-recent"
+        "Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox",
+        "Perform a validate-only deployment of all changes from the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
       ],
       "flags": {
         "json": {
@@ -2243,70 +2542,41 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "devops-center-username": {
-          "char": "c",
-          "name": "devops-center-username",
+        "branch-name": {
+          "char": "b",
+          "name": "branch-name",
           "required": true,
-          "summary": "Username or alias of the DevOps Center org.",
-          "hasDynamicHelp": true,
+          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "job-id": {
-          "char": "i",
-          "description": "The job ID is valid for 10 days from when you started the deploy operation.",
-          "name": "job-id",
-          "summary": "Job ID of the pipeline deployment to check the status of.",
+        "bundle-version-name": {
+          "char": "v",
+          "description": "You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage.",
+          "name": "bundle-version-name",
+          "summary": "Version name of the bundle.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "use-most-recent": {
-          "char": "r",
-          "description": "For performance reasons, this flag uses job IDs for deploy operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find the job ID.",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recent deploy operation.",
-          "allowNo": false,
-          "type": "boolean"
-        }
-      },
-      "hasDynamicHelp": true,
-      "hiddenAliases": [],
-      "id": "project:deploy:pipeline:report",
-      "pluginAlias": "@salesforce/plugin-devops-center",
-      "pluginName": "@salesforce/plugin-devops-center",
-      "pluginType": "jit",
-      "state": "beta",
-      "strict": true,
-      "summary": "Check the status of a pipeline deploy operation.",
-      "enableJsonFlag": true,
-      "SF_ENV": "SF_ENV",
-      "isESM": false,
-      "relativePath": [
-        "lib",
-        "commands",
-        "project",
-        "deploy",
-        "pipeline",
-        "report.js"
-      ]
-    },
-    "project:deploy:pipeline:resume": {
-      "aliases": [],
-      "args": {},
-      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command. \n\nUse this command to resume watching a pipeline deploy operation if the original command times out or you specified the --async flag.\n\nRun this command by either indicating a job ID or specifying the --use-most-recent flag to use the job ID of the most recent deploy operation.",
-      "examples": [
-        "Resume watching a deploy operation using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 0Af0x000017yLUFCA2",
-        "Resume watching the most recent deploy operation:\n<%= config.bin %> <%= command.id %> --use-most-recent"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
+        "deploy-all": {
+          "char": "a",
+          "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
+          "name": "deploy-all",
+          "summary": "Deploy all metadata in the branch to the stage's org.",
           "allowNo": false,
           "type": "boolean"
         },
+        "devops-center-project-name": {
+          "char": "p",
+          "name": "devops-center-project-name",
+          "required": true,
+          "summary": "Name of the DevOps Center project.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "devops-center-username": {
           "char": "c",
           "name": "devops-center-username",
@@ -2316,35 +2586,34 @@
           "multiple": false,
           "type": "option"
         },
-        "job-id": {
-          "char": "i",
-          "description": "These commands return a job ID if they time out or you specified the --async flag:\n\n- sf project deploy pipeline start\n- sf project deploy pipeline validate\n- sf project deploy pipeline quick\n\nThe job ID is valid for 10 days from when you started the deploy operation.",
-          "name": "job-id",
-          "summary": "Job ID of the pipeline deploy operation you want to resume.",
+        "tests": {
+          "char": "t",
+          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
+          "name": "tests",
+          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
           "hasDynamicHelp": false,
-          "multiple": false,
+          "multiple": true,
           "type": "option"
         },
-        "use-most-recent": {
-          "char": "r",
-          "description": "For performance reasons, this flag uses job IDs for operations that started in the past 3 days or fewer. If your most recent operation was longer than 3 days ago, this flag won't find a job ID.",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recent deploy operation.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "concise": {
-          "exclusive": [
-            "verbose"
+        "test-level": {
+          "char": "l",
+          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\nIf you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section \"Running Tests in a Deployment\" in the \"Metadata API Developer Guide\". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)",
+          "name": "test-level",
+          "summary": "Deployment Apex testing level.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "NoTestRun",
+            "RunSpecifiedTests",
+            "RunLocalTests",
+            "RunAllTestsInOrg"
           ],
-          "name": "concise",
-          "summary": "Show concise output of the command result.",
-          "allowNo": false,
-          "type": "boolean"
+          "type": "option"
         },
-        "verbose": {
-          "name": "verbose",
-          "summary": "Show verbose output of the command result.",
+        "async": {
+          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"sf project deploy pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
+          "name": "async",
+          "summary": "Run the command asynchronously.",
           "allowNo": false,
           "type": "boolean"
         },
@@ -2361,17 +2630,32 @@
           "helpValue": "<minutes>",
           "multiple": false,
           "type": "option"
+        },
+        "verbose": {
+          "name": "verbose",
+          "summary": "Show verbose output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Show concise output of the command result.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:pipeline:resume",
+      "id": "project:deploy:pipeline:validate",
       "pluginAlias": "@salesforce/plugin-devops-center",
       "pluginName": "@salesforce/plugin-devops-center",
       "pluginType": "jit",
       "state": "beta",
       "strict": true,
-      "summary": "Resume watching a pipeline deploy operation.",
+      "summary": "Perform a validate-only deployment from a branch to the pipeline stage’s org.",
       "enableJsonFlag": true,
       "SF_ENV": "SF_ENV",
       "isESM": false,
@@ -2381,16 +2665,18 @@
         "project",
         "deploy",
         "pipeline",
-        "resume.js"
+        "validate.js"
       ]
     },
-    "project:deploy:pipeline:start": {
+    "flow:get:log": {
       "aliases": [],
       "args": {},
-      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nBefore you run this command, changes in the pipeline stage's branch must be merged in the source control repository.",
+      "description": "Provide a flow test run ID to display test results for an enqueued or completed asynchronous test run. The test run ID is displayed after running the \"sf flow run test\" command.\n\nTo see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level summary of the test run and the code coverage values for flow tests in your org. If you specify human-readable result format, use the --detailed-coverage flag to see detailed coverage results for each test method run.",
       "examples": [
-        "Deploy changes in the Staging branch to the Staging environment (sandbox), if the previous stage is the bundling stage:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox --bundle-version-name 1.0",
-        "Deploy all changes in the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
+        "Display flow test results for your default org using a test run ID:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id>",
+        "Similar to previous example, but output the result in JUnit format:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --result-format junit",
+        "Also retrieve code coverage results and output in JSON format:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --code-coverage --json",
+        "Specify a directory in which to save the test results from the org with the “me@my.org” username (rather than your default org):\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --code-coverage --output-dir <path to outputdir> --target-org me@my.org'"
       ],
       "flags": {
         "json": {
@@ -2400,139 +2686,220 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "branch-name": {
-          "char": "b",
-          "name": "branch-name",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
           "required": true,
-          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "bundle-version-name": {
-          "char": "v",
-          "description": "You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage.",
-          "name": "bundle-version-name",
-          "summary": "Version name of the bundle.",
+        "log-id": {
+          "char": "i",
+          "name": "log-id",
+          "summary": "ID of the specific log to display.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "deploy-all": {
-          "char": "a",
-          "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
-          "name": "deploy-all",
-          "summary": "Deploy all metadata in the branch to the stage's org.",
+        "number": {
+          "char": "n",
+          "name": "number",
+          "summary": "Number of the most recent logs to display.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "output-dir": {
+          "char": "d",
+          "name": "output-dir",
+          "summary": "Directory in which to store test result files.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hidden": true,
+      "hiddenAliases": [],
+      "id": "flow:get:log",
+      "pluginAlias": "@salesforce/plugin-flow",
+      "pluginName": "@salesforce/plugin-flow",
+      "pluginType": "jit",
+      "state": "preview",
+      "strict": true,
+      "summary": "Display test results for a specific asynchronous test run.",
+      "enableJsonFlag": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "flow",
+        "get",
+        "log.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "flow:get:log",
+        "get:flow:log",
+        "get:log:flow",
+        "flow:log:get",
+        "log:flow:get",
+        "log:get:flow"
+      ]
+    },
+    "flow:get:test": {
+      "aliases": [],
+      "args": {},
+      "description": "Provide a flow test run ID to display test results for an enqueued or completed asynchronous test run. The test run ID is displayed after running the \"sf flow run test\" command.\n\nTo see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level summary of the test run and the code coverage values for flow tests in your org. If you specify human-readable result format, use the --detailed-coverage flag to see detailed coverage results for each test method run.",
+      "examples": [
+        "Display flow test results for your default org using a test run ID:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id>",
+        "Similar to previous example, but output the result in JUnit format:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --result-format junit",
+        "Also retrieve code coverage results and output in JSON format:\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --code-coverage --json",
+        "Specify a directory in which to save the test results from the org with the “me@my.org” username (rather than your default org):\n<%= config.bin %> <%= command.id %> --test-run-id <test run id> --code-coverage --output-dir <path to outputdir> --target-org me@my.org'"
+      ],
+      "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
           "allowNo": false,
           "type": "boolean"
         },
-        "devops-center-project-name": {
-          "char": "p",
-          "name": "devops-center-project-name",
-          "required": true,
-          "summary": "Name of the DevOps Center project.",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "devops-center-username": {
-          "char": "c",
-          "name": "devops-center-username",
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
           "required": true,
-          "summary": "Username or alias of the DevOps Center org.",
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
           "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "tests": {
-          "char": "t",
-          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
-          "name": "tests",
-          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "test-level": {
-          "char": "l",
-          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\nIf you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section \"Running Tests in a Deployment\" in the \"Metadata API Developer Guide\". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)",
-          "name": "test-level",
-          "summary": "Deployment Apex testing level.",
+        "test-run-id": {
+          "char": "i",
+          "name": "test-run-id",
+          "required": true,
+          "summary": "ID of the test run.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "NoTestRun",
-            "RunSpecifiedTests",
-            "RunLocalTests",
-            "RunAllTestsInOrg"
-          ],
           "type": "option"
         },
-        "async": {
-          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"sf project deploy pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
-          "name": "async",
-          "summary": "Run the command asynchronously.",
+        "code-coverage": {
+          "char": "c",
+          "name": "code-coverage",
+          "summary": "Retrieve code coverage results.",
           "allowNo": false,
           "type": "boolean"
         },
-        "wait": {
-          "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run \"sf project deploy pipeline report\".",
-          "exclusive": [
-            "async"
+        "detailed-coverage": {
+          "dependsOn": [
+            "code-coverage"
           ],
-          "name": "wait",
-          "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": "33 minutes",
-          "hasDynamicHelp": true,
-          "helpValue": "<minutes>",
+          "name": "detailed-coverage",
+          "summary": "Not available for flow tests.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "output-dir": {
+          "char": "d",
+          "name": "output-dir",
+          "summary": "Directory in which to store test result files.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "verbose": {
-          "name": "verbose",
-          "summary": "Show verbose output of the command result.",
-          "allowNo": false,
-          "type": "boolean"
+        "result-format": {
+          "char": "r",
+          "name": "result-format",
+          "summary": "Format of the test results.",
+          "default": "human",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "human",
+            "tap",
+            "junit",
+            "json"
+          ],
+          "type": "option"
         },
         "concise": {
-          "exclusive": [
-            "verbose"
-          ],
           "name": "concise",
-          "summary": "Show concise output of the command result.",
+          "summary": "Display only failed test results; works with human-readable output only.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:pipeline:start",
-      "pluginAlias": "@salesforce/plugin-devops-center",
-      "pluginName": "@salesforce/plugin-devops-center",
+      "id": "flow:get:test",
+      "pluginAlias": "@salesforce/plugin-flow",
+      "pluginName": "@salesforce/plugin-flow",
       "pluginType": "jit",
-      "state": "beta",
       "strict": true,
-      "summary": "Deploy changes from a branch to the pipeline stage’s org.",
+      "summary": "Display test results for a specific asynchronous test run.",
       "enableJsonFlag": true,
-      "SF_ENV": "SF_ENV",
-      "isESM": false,
+      "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "project",
-        "deploy",
-        "pipeline",
-        "start.js"
+        "flow",
+        "get",
+        "test.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "flow:get:test",
+        "get:flow:test",
+        "get:test:flow",
+        "flow:test:get",
+        "test:flow:get",
+        "test:get:flow"
       ]
     },
-    "project:deploy:pipeline:validate": {
+    "flow:run:test": {
       "aliases": [],
       "args": {},
-      "description": "The first time you run any \"project deploy pipeline\" command, be sure to authorize the org in which DevOps Center is installed. The easiest way to authorize an org is with the \"org login web\" command.\n\nA validation runs Apex tests to verify whether a deployment will succeed without actually deploying the metadata to your environment, so you can then quickly deploy the changes later without re-running the tests.",
+      "description": "Specify which tests to run by using the --class-names flag followed by the names of the flows you want to test. For example, if you save a flow with the name Flow1, then use: --class-names Flow1.\n\nTo see code coverage results, use the --code-coverage flag with --result-format. The output displays a high-level summary of the test run and the code coverage values for classes in your org. If you specify human-readable result format, use the --detailed-coverage flag to see detailed coverage results for each test method run.\n\nBy default, \"flow run test\" runs asynchronously and immediately returns a test run ID. If you use the -–synchronous flag, you can use the --wait flag to specify the number of minutes to wait; if the tests finish in that timeframe, the command displays the results. If the tests haven't finished by the end of the wait time, the command displays a test run ID. Use the \"flow get test --test-run-id\" command to get the results.\n\nYou must have the \"View All Data\" org system permission to use this command. The permission is disabled by default and can be enabled only by a system administrator.",
       "examples": [
-        "Perform a validate-only deployment from the Staging branch to the Staging environment (sandbox):\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name staging --devops-center-username MyStagingSandbox",
-        "Perform a validate-only deployment of all changes from the main branch to the release environment:\n<%= config.bin %> <%= command.id %> --devops-center-project-name “Recruiting App” --branch-name main --devops-center-username MyReleaseOrg --deploy-all"
+        "Run all local tests in your default org:\n<%= config.bin %> <%= command.id %> --test-level RunLocalTests",
+        "Run all the Flow1 and Flow2 flow tests in the org with alias “scratchOrg”:\n<%= config.bin %> <%= command.id %> --target-org scratchOrg --class-names Flow1 --class-names Flow2",
+        "Run specific Flow1 and Flow2 flow tests in your default org:\n<%= config.bin %> <%= command.id %> --tests Flow1.Test1 --tests Flow2.Test2 --test-level RunSpecifiedTests",
+        "Run all tests synchronously in your default org; the command waits to display the test results until all tests finish:\n<%= config.bin %> <%= command.id %> –synchronous",
+        "Run all local tests in the org with the username “me@my.org”; save the output to the specified directory:\n<%= config.bin %> <%= command.id %> --test-level RunLocalTests --output-dir /Users/susan/temp/cliOutput --target-org me@my.org"
       ],
       "flags": {
         "json": {
@@ -2542,130 +2909,159 @@
           "allowNo": false,
           "type": "boolean"
         },
-        "branch-name": {
-          "char": "b",
-          "name": "branch-name",
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
           "required": true,
-          "summary": "Name of the branch in the source control repository that corresponds to the pipeline stage that you want to deploy the changes to.",
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "bundle-version-name": {
-          "char": "v",
-          "description": "You must indicate the bundle version if deploying to the environment that corresponds to the first stage after the bundling stage.",
-          "name": "bundle-version-name",
-          "summary": "Version name of the bundle.",
+        "result-format": {
+          "char": "r",
+          "name": "result-format",
+          "summary": "Format of the test results.",
+          "default": "human",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "human",
+            "tap",
+            "junit",
+            "json"
+          ],
           "type": "option"
         },
-        "deploy-all": {
-          "char": "a",
-          "description": "If you don’t specify this flag, only changes in the stage’s branch are deployed.",
-          "name": "deploy-all",
-          "summary": "Deploy all metadata in the branch to the stage's org.",
+        "concise": {
+          "name": "concise",
+          "summary": "Display only failed test results; works with human-readable output only.",
           "allowNo": false,
           "type": "boolean"
         },
-        "devops-center-project-name": {
-          "char": "p",
-          "name": "devops-center-project-name",
-          "required": true,
-          "summary": "Name of the DevOps Center project.",
+        "output-dir": {
+          "char": "d",
+          "name": "output-dir",
+          "summary": "Directory in which to store test result files.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "devops-center-username": {
+        "code-coverage": {
           "char": "c",
-          "name": "devops-center-username",
-          "required": true,
-          "summary": "Username or alias of the DevOps Center org.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
+          "name": "code-coverage",
+          "summary": "Retrieve code coverage results.",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "tests": {
-          "char": "t",
-          "description": "Separate multiple test names with commas. Enclose the entire flag value in double quotes if a test name contains spaces.",
-          "name": "tests",
-          "summary": "Apex tests to run when --test-level is RunSpecifiedTests.",
-          "hasDynamicHelp": false,
-          "multiple": true,
-          "type": "option"
+        "synchronous": {
+          "char": "y",
+          "name": "synchronous",
+          "summary": "Run flow tests for one flow synchronously; if not specified, tests are run asynchronously.",
+          "allowNo": false,
+          "type": "boolean"
         },
         "test-level": {
           "char": "l",
-          "description": "Valid values are:\n\n- NoTestRun — No tests are run. This test level applies only to deployments to development environments, such as sandbox, Developer Edition, or trial orgs. This test level is the default for development environments.\n\n- RunSpecifiedTests — Runs only the tests that you specify with the --tests flag. Code coverage requirements differ from the default coverage requirements when using this test level. Executed tests must comprise a minimum of 75% code coverage for each class and trigger in the deployment package. This coverage is computed for each class and trigger individually and is different than the overall coverage percentage.\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages. This test level is the default for production deployments that include Apex classes or triggers.\n\n- RunAllTestsInOrg — All tests in your org are run, including tests of managed packages.\n\nIf you don’t specify a test level, the default behavior depends on the contents of your deployment package. For more information, see the section \"Running Tests in a Deployment\" in the \"Metadata API Developer Guide\". (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_running_tests.htm)",
+          "description": "Here's what the levels mean:\n\n- RunLocalTests — All tests in your org are run, except the ones that originate from installed managed and unlocked packages.\n- RunAllTestsInOrg — All tests are run. The tests include all tests in your org, including tests of managed packages.\n- RunSpecifiedTests - Only the tests that you specify with the --tests flag are run.",
           "name": "test-level",
-          "summary": "Deployment Apex testing level.",
+          "summary": "Level of tests to run; default is RunLocalTests.",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "NoTestRun",
-            "RunSpecifiedTests",
             "RunLocalTests",
-            "RunAllTestsInOrg"
+            "RunAllTestsInOrg",
+            "RunSpecifiedTests"
           ],
           "type": "option"
         },
-        "async": {
-          "description": "The command immediately returns the job ID and control of the terminal to you. This way, you can continue to use the CLI. To resume the deployment, run \"sf project deploy pipeline resume\". To check the status of the deployment, run \"sf project deploy pipeline report\".",
-          "name": "async",
-          "summary": "Run the command asynchronously.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "wait": {
-          "char": "w",
-          "description": "If the command continues to run after the wait period, the CLI returns control of the terminal window to you and returns the job ID. To check the status of the operation, run \"sf project deploy pipeline report\".",
+        "class-names": {
+          "aliases": [
+            "classnames"
+          ],
+          "char": "n",
+          "description": "Default is all flow tests. If you select --class-names, you can't specify --tests.",
           "exclusive": [
-            "async"
+            "suite-names",
+            "tests"
           ],
-          "name": "wait",
-          "summary": "Number of minutes to wait for command to complete and display results.",
-          "default": "33 minutes",
-          "hasDynamicHelp": true,
-          "helpValue": "<minutes>",
-          "multiple": false,
+          "name": "class-names",
+          "summary": "Flow names that contain flow tests to run.",
+          "hasDynamicHelp": false,
+          "multiple": true,
           "type": "option"
         },
-        "verbose": {
-          "name": "verbose",
-          "summary": "Show verbose output of the command result.",
-          "allowNo": false,
-          "type": "boolean"
+        "suite-names": {
+          "aliases": [
+            "suitenames"
+          ],
+          "char": "s",
+          "description": "Not available for flow tests.",
+          "exclusive": [
+            "class-names",
+            "tests"
+          ],
+          "name": "suite-names",
+          "summary": "Not available for flow tests.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
         },
-        "concise": {
+        "tests": {
+          "char": "t",
+          "description": "Default is all flow tests. If you specify --tests, you can't specify --class-names.",
           "exclusive": [
-            "verbose"
+            "class-names",
+            "suite-names"
           ],
-          "name": "concise",
-          "summary": "Show concise output of the command result.",
-          "allowNo": false,
-          "type": "boolean"
+          "name": "tests",
+          "summary": "Flow test names to run.",
+          "hasDynamicHelp": false,
+          "multiple": true,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "project:deploy:pipeline:validate",
-      "pluginAlias": "@salesforce/plugin-devops-center",
-      "pluginName": "@salesforce/plugin-devops-center",
+      "id": "flow:run:test",
+      "pluginAlias": "@salesforce/plugin-flow",
+      "pluginName": "@salesforce/plugin-flow",
       "pluginType": "jit",
-      "state": "beta",
       "strict": true,
-      "summary": "Perform a validate-only deployment from a branch to the pipeline stage’s org.",
+      "summary": "Invoke flow tests in an org.",
       "enableJsonFlag": true,
-      "SF_ENV": "SF_ENV",
-      "isESM": false,
+      "isESM": true,
       "relativePath": [
         "lib",
         "commands",
-        "project",
-        "deploy",
-        "pipeline",
-        "validate.js"
+        "flow",
+        "run",
+        "test.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "flow:run:test",
+        "run:flow:test",
+        "run:test:flow",
+        "flow:test:run",
+        "test:flow:run",
+        "test:run:flow"
       ]
     },
     "org:create:shape": {
@@ -4411,5 +4807,5 @@
       ]
     }
   },
-  "version": "2.86.5"
+  "version": "2.86.7"
 }