Merge pull request #280 from salesforcecli/jshackell-sfdc-patch-1

W-20424458: edit messages

Author: shetzel

messages/agent.generate.authoring-bundle.md

@@ -18,6 +18,10 @@ This command requires an org because it uses it to access an LLM for generating
 
 Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.
 
+# flags.spec.prompt
+
+Path to the agent spec YAML file
+
 # flags.output-dir.summary
 
 Directory where the authoring bundle files are generated.
@@ -26,6 +30,10 @@ Directory where the authoring bundle files are generated.
 
 Name (label) of the authoring bundle; if not specified, you're prompted for the name.
 
+# flags.name.prompt
+
+Name (label) of the authoring bundle
+
 # flags.api-name.summary
 
 API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name can't exist in the org.

messages/agent.publish.authoring-bundle.md

@@ -6,7 +6,7 @@ Publish an authoring bundle to your org, which results in a new agent or a new v
 
 An authoring bundle is a metadata type (named aiAuthoringBundle) that provides the blueprint for an agent. The metadata type contains two files: the standard metatada XML file and an Agent Script file (extension ".agent") that fully describes the agent using the Agent Script language.
 
-When you publish an authoring bundle to your org, a number of things happen. First, this command validates that the Agent Script file successfully compiles. If there are compilation errors, the command exits and you must fix the Agent Script file to continue. Once the Agent Script file compiles, then the authoring bundle metadata component is deployed to the org. All associated agent metadata components, such as the Bot, BotVersion, and GenAiXXX components, are either created or updated in the org. Finally, all the new or changed metadata components associated with the new agent are retrieved back to your local DX project.
+When you publish an authoring bundle to your org, a number of things happen. First, this command validates that the Agent Script file successfully compiles. If there are compilation errors, the command exits and you must fix the Agent Script file to continue. Once the Agent Script file compiles, then it's published to the org, which in turn creates new associated metadata (Bot, BotVersion, GenAiX), or new versions of the metadata if the agent already exists. The new or updated metadata is retrieved back to your DX project, and then the authoring bundle metadata (AiAuthoringBundle) is deployed to your org. 
 
 This command uses the API name of the authoring bundle.
 

src/commands/agent/generate/authoring-bundle.ts

@@ -64,6 +64,7 @@ export default class AgentGenerateAuthoringBundle extends SfCommand<AgentGenerat
   private static readonly FLAGGABLE_PROMPTS = {
     name: {
       message: messages.getMessage('flags.name.summary'),
+      promptMessage: messages.getMessage('flags.name.prompt'),
       validate: (d: string): boolean | string =>
         d.trim().length > 0 || 'Name cannot be empty or contain only whitespace',
       required: true,
@@ -87,6 +88,7 @@ export default class AgentGenerateAuthoringBundle extends SfCommand<AgentGenerat
     },
     spec: {
       message: messages.getMessage('flags.spec.summary'),
+      promptMessage: messages.getMessage('flags.spec.prompt'),
       validate: (d: string): boolean | string => {
         const specPath = resolve(d);
         if (!existsSync(specPath)) {