From d15461d6679a72971033b855dd557782bf33aaa7 Mon Sep 17 00:00:00 2001
From: svc-cli-bot <Svc_cli_bot@salesforce.com>
Date: Tue, 3 Jun 2025 18:06:38 +0000
Subject: [PATCH] chore(release): bump to 2.92.6

---
 README.md    | 784 +++++++++++++++++++++++++++++++++++++++++++++++++--
 package.json |   6 +-
 yarn.lock    |  47 ++-
 3 files changed, 800 insertions(+), 37 deletions(-)

diff --git a/README.md b/README.md
index bc6dfecfa..31d74a218 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ $ npm install -g @salesforce/cli
 $ sf COMMAND
 running command...
 $ sf (--version|-v)
-@salesforce/cli/2.92.5 linux-x64 node-v22.16.0
+@salesforce/cli/2.92.6 linux-x64 node-v22.16.0
 $ sf --help [COMMAND]
 USAGE
   $ sf COMMAND
@@ -42,6 +42,16 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 
 <!-- commands -->
 
+- [`sf agent create`](#sf-agent-create)
+- [`sf agent generate agent-spec`](#sf-agent-generate-agent-spec)
+- [`sf agent generate template`](#sf-agent-generate-template)
+- [`sf agent generate test-spec`](#sf-agent-generate-test-spec)
+- [`sf agent preview`](#sf-agent-preview)
+- [`sf agent test create`](#sf-agent-test-create)
+- [`sf agent test list`](#sf-agent-test-list)
+- [`sf agent test results`](#sf-agent-test-results)
+- [`sf agent test resume`](#sf-agent-test-resume)
+- [`sf agent test run`](#sf-agent-test-run)
 - [`sf alias list`](#sf-alias-list)
 - [`sf alias set`](#sf-alias-set)
 - [`sf alias unset`](#sf-alias-unset)
@@ -124,6 +134,7 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf org refresh sandbox`](#sf-org-refresh-sandbox)
 - [`sf org resume sandbox`](#sf-org-resume-sandbox)
 - [`sf org resume scratch`](#sf-org-resume-scratch)
+- [`sf package convert`](#sf-package-convert)
 - [`sf package create`](#sf-package-create)
 - [`sf package delete`](#sf-package-delete)
 - [`sf package install`](#sf-package-install)
@@ -187,6 +198,646 @@ See [architecture page](ARCHITECTURE.md) for diagrams of the Salesforce CLI.
 - [`sf visualforce generate page`](#sf-visualforce-generate-page)
 - [`sf which`](#sf-which)
 
+## `sf agent create`
+
+Create an agent in your org using a local agent spec file.
+
+```
+USAGE
+  $ sf agent create -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [--name <value>] [--api-name
+    <value>] [--spec <value>] [--preview]
+
+FLAGS
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
+      --api-name=<value>     API name of the new agent; if not specified, the API name is derived from the agent name
+                             (label); the API name must not exist in the org.
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --name=<value>         Name (label) of the new agent.
+      --preview              Preview the agent without saving it in your org.
+      --spec=<value>         Path to an agent spec file.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Create an agent in your org using a local agent spec file.
+
+  To run this command, you must have an agent spec file, which is a YAML file that define the agent properties and
+  contains a list of AI-generated topics. Topics define the range of jobs the agent can handle. Use the "agent generate
+  agent-spec" CLI command to generate an agent spec file. Then specify the file to this command using the --spec flag,
+  along with the name (label) of the new agent with the --name flag. If you don't specify any of the required flags, the
+  command prompts you.
+
+  When this command completes, your org contains the new agent, which you can then edit and customize in the Agent
+  Builder UI. The new agent's topics are the same as the ones listed in the agent spec file. The agent might also have
+  some AI-generated actions, or you can add them. This command also retrieves all the metadata files associated with the
+  new agent to your local Salesforce DX project.
+
+  Use the --preview flag to review what the agent looks like without actually saving it in your org. When previewing,
+  the command creates a JSON file in the current directory with all the agent details. The name of the JSON file is the
+  agent's API name and a timestamp.
+
+  To open the new agent in your org's Agent Builder UI, run this command: "sf org open agent --api-name <api-name>".
+
+EXAMPLES
+  Create an agent by being prompted for the required information, such as the agent spec file and agent name, and then
+  create it in your default org:
+
+    $ sf agent create
+
+  Create an agent by specifying the agent name, API name, and spec file with flags; use the org with alias "my-org";
+  the command fails if the API name is already being used in your org:
+
+    $ sf agent create --name "Resort Manager" --api-name Resort_Manager --spec specs/resortManagerAgent.yaml \
+      --target-org my-org
+
+  Preview the creation of an agent named "Resort Manager" and use your default org:
+
+    $ sf agent create --name "Resort Manager" --spec specs/resortManagerAgent.yaml --preview
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/create.ts)_
+
+## `sf agent generate agent-spec`
+
+Generate an agent spec, which is a YAML file that captures what an agent can do.
+
+```
+USAGE
+  $ sf agent generate agent-spec -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [--type customer|internal]
+    [--role <value>] [--company-name <value>] [--company-description <value>] [--company-website <value>] [--max-topics
+    <value>] [--agent-user <value>] [--enrich-logs true|false] [--tone formal|casual|neutral] [--spec <value>]
+    [--output-file <value>] [--full-interview] [--grounding-context <value> --prompt-template <value>]
+    [--force-overwrite]
+
+FLAGS
+  -o, --target-org=<value>           (required) Username or alias of the target org. Not required if the `target-org`
+                                     configuration variable is already set.
+      --agent-user=<value>           Username of a user in your org to assign to your agent; determines what your agent
+                                     can access and do.
+      --api-version=<value>          Override the api version used for api requests made by this command
+      --company-description=<value>  Description of your company.
+      --company-name=<value>         Name of your company.
+      --company-website=<value>      Website URL of your company.
+      --enrich-logs=<option>         Adds agent conversation data to event logs so you can view all agent session
+                                     activity in one place.
+                                     <options: true|false>
+      --force-overwrite              Don't prompt the user to confirm that an existing spec file will be overwritten.
+      --full-interview               Prompt for both required and optional flags.
+      --grounding-context=<value>    Context information and personalization that's added to your prompts when using a
+                                     custom prompt template.
+      --max-topics=<value>           Maximum number of topics to generate in the agent spec; default is 5.
+      --output-file=<value>          [default: specs/agentSpec.yaml] Path for the generated YAML agent spec file; can be
+                                     an absolute or relative path.
+      --prompt-template=<value>      API name of a customized prompt template to use instead of the default prompt
+                                     template.
+      --role=<value>                 Role of the agent.
+      --spec=<value>                 Agent spec file, in YAML format, to use as input to the command.
+      --tone=<option>                Conversational style of the agent, such as how it expresses your brand personality
+                                     in its messages through word choice, punctuation, and sentence structure.
+                                     <options: formal|casual|neutral>
+      --type=<option>                Type of agent to create. Internal types are copilots used internally by your
+                                     company and customer types are the agents you create for your customers.
+                                     <options: customer|internal>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate an agent spec, which is a YAML file that captures what an agent can do.
+
+  The first step in creating an agent in your org with Salesforce CLI is to generate an agent spec using this command.
+  An agent spec is a YAML-formatted file that contains information about the agent, such as its role and company
+  description, and then an AI-generated list of topics based on this information. Topics define the range of jobs your
+  agent can handle.
+
+  Use flags, such as --role and --company-description, to provide details about your company and the role that the agent
+  plays in your company. If you prefer, you can also be prompted for the basic information; use --full-interview to be
+  prompted for all required and optional properties. Upon command execution, the large language model (LLM) associated
+  with your org uses the provided information to generate a list of topics for the agent. Because the LLM uses the
+  company and role information to generate the topics, we recommend that you provide accurate, complete, and specific
+  details so the LLM generates the best and most relevant topics. Once generated, you can edit the spec file; for
+  example, you can remove topics that don't apply or change a topic's description.
+
+  You can also iterate the spec generation process by using the --spec flag to pass an existing agent spec file to this
+  command, and then using the --role, --company-description, etc, flags to refine your agent properties. Iteratively
+  improving the description of your agent allows the LLM to generate progressively better topics.
+
+  You can also specify other agent properties, such as a custom prompt template, how to ground the prompt template to
+  add context to the agent's prompts, the tone of the prompts, and the username of a user in the org to assign to the
+  agent.
+
+  When your agent spec is ready, you then create the agent in your org by running the "agent create" CLI command and
+  specifying the spec with the --spec flag.
+
+EXAMPLES
+  Generate an agent spec in the default location and use flags to specify the agent properties, such as its role and
+  your company details; use your default org:
+
+    $ sf agent generate agent-spec --type customer --role "Field customer complaints and manage employee schedules." \
+      --company-name "Coral Cloud Resorts" --company-description "Provide customers with exceptional destination \
+      activities, unforgettable experiences, and reservation services."
+
+  Generate an agent spec by being prompted for the required agent properties and generate a maxiumum of 5 topics;
+  write the generated file to the "specs/resortManagerSpec.yaml" file and use the org with alias "my-org":
+
+    $ sf agent generate agent-spec --max-topics 5 --output-file specs/resortManagerAgent.yaml --target-org my-org
+
+  Be prompted for all required and optional agent properties; use your default org:
+
+    $ sf agent generate agent-spec --full-interview
+
+  Specify an existing agent spec file called "specs/resortManagerAgent.yaml", and then overwrite it with a new version
+  that contains newly AI-generated topics based on the updated role information passed in with the --role flag:
+
+    $ sf agent generate agent-spec --spec specs/resortManagerAgent.yaml --output-file specs/resortManagerAgent.yaml \
+      --role "Field customer complaints, manage employee schedules, and ensure all resort operations are running \
+      smoothly"
+
+  Specify that the conversational tone of the agent is formal and to attach the "resortmanager@myorg.com" username to
+  it; be prompted for the required properties and use your default org:
+
+    $ sf agent generate agent-spec --tone formal --agent-user resortmanager@myorg.com
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/generate/agent-spec.ts)_
+
+## `sf agent generate template`
+
+Generate an agent template from an existing agent in your DX project so you can then package the template in a managed package.
+
+```
+USAGE
+  $ sf agent generate template --agent-version <value> -f <value> [--json] [--flags-dir <value>] [--api-version <value>]
+
+FLAGS
+  -f, --agent-file=<value>     (required) Path to an agent (Bot) metadata file.
+      --agent-version=<value>  (required) Version of the agent (BotVersion).
+      --api-version=<value>    Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Generate an agent template from an existing agent in your DX project so you can then package the template in a managed
+  package.
+
+  At a high-level, agents are defined by the Bot, BotVersion, and GenAiPlannerBundle metadata types. The
+  GenAiPlannerBundle type in turn defines the agent's topics and actions. This command uses the metadata files for these
+  three types, located in your local DX project, to generate a BotTemplate file for a specific agent (Bot). You then use
+  the BotTemplate file, along with the GenAiPlannerBundle file that references the BotTemplate, to package the template
+  in a managed package that you can share between orgs or on AppExchange.
+
+  Use the --agent-file flag to specify the relative or full pathname of the Bot metadata file, such as
+  force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml. A single Bot can have multiple
+  BotVersions, so use the --agent-version flag to specify the version. The corresponding BotVersion file must exist
+  locally. For example, if you specify "--agent-version 4", then the file
+  force-app/main/default/bots/My_Awesome_Agent/v4.botVersion-meta.xml must exist.
+
+  The new BotTemplate file is generated in the "botTemplates" directory in your local package directory, and has the
+  name <Agent_API_name>_v<Version>_Template.botTemplate-meta.xml, such as
+  force-app/main/default/botTemplates/My_Awesome_Agent_v4_Template.botTemplate-meta.xml. The command displays the full
+  pathname of the generated files when it completes.
+
+EXAMPLES
+  Generate an agent template from a Bot metadata file in your DX project that corresponds to the My_Awesome_Agent
+  agent; use version 1 of the agent.
+
+    $ sf agent generate template --agent-file \
+      force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/generate/template.ts)_
+
+## `sf agent generate test-spec`
+
+Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.
+
+```
+USAGE
+  $ sf agent generate test-spec [--flags-dir <value>] [-d <value>] [--force-overwrite] [-f <value>]
+
+FLAGS
+  -d, --from-definition=<value>  Filepath to the AIEvaluationDefinition metadata XML file in your DX project that you
+                                 want to convert to a test spec YAML file.
+  -f, --output-file=<value>      Name of the generated test spec YAML file. Default value is
+                                 "specs/<AGENT_API_NAME>-testSpec.yaml".
+      --force-overwrite          Don't prompt for confirmation when overwriting an existing test spec YAML file.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+
+DESCRIPTION
+  Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.
+
+  The first step when using Salesforce CLI to create an agent test in your org is to use this interactive command to
+  generate a local YAML-formatted test spec file. The test spec YAML file contains information about the agent being
+  tested, such as its API name, and then one or more test cases. This command uses the metadata components in your DX
+  project when prompting for information, such as the agent API name; it doesn't look in your org.
+
+  To generate a specific agent test case, this command prompts you for this information; when possible, the command
+  provides a list of options for you to choose from:
+
+  - Utterance: Natural language statement, question, or command used to test the agent.
+  - Expected topic: API name of the topic you expect the agent to use when responding to the utterance.
+  - Expected actions: One or more API names of the expection actions the agent takes.
+  - Expected outcome: Natural language description of the outcome you expect.
+
+  When your test spec is ready, you then run the "agent test create" command to actually create the test in your org and
+  synchronize the metadata with your DX project. The metadata type for an agent test is AiEvaluationDefinition.
+
+  If you have an existing AiEvaluationDefinition metadata XML file in your DX project, you can generate its equivalent
+  YAML test spec file with the --from-definition flag.
+
+EXAMPLES
+  Generate an agent test spec YAML file interactively:
+
+    $ sf agent generate test-spec
+
+  Generate an agent test spec YAML file and specify a name for the new file; if the file exists, overwrite it without
+  confirmation:
+
+    $ sf agent generate test-spec --output-file specs/Resort_Manager-new-version-testSpec.yaml --force-overwrite
+
+  Generate an agent test spec YAML file from an existing AiEvaluationDefinition metadata XML file in your DX project:
+
+    $ sf agent generate test-spec --from-definition \
+      force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/generate/test-spec.ts)_
+
+## `sf agent preview`
+
+Interact with an active agent to preview how the agent responds to your statements, questions, and commands (utterances).
+
+```
+USAGE
+  $ sf agent preview -o <value> -a <value> [--flags-dir <value>] [--api-version <value>] [-n <value>] [-d <value>]
+    [-x]
+
+FLAGS
+  -a, --connected-app-user=<value>  (required) Username or alias of the connected app user that's configured with
+                                    web-based access tokens to the agent.
+  -d, --output-dir=<value>          Directory where conversation transcripts are saved.
+  -n, --api-name=<value>            API name of the agent you want to interact with.
+  -o, --target-org=<value>          (required) Username or alias of the target org. Not required if the `target-org`
+                                    configuration variable is already set.
+  -x, --apex-debug                  Enable Apex debug logging during the agent preview conversation.
+      --api-version=<value>         Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+
+DESCRIPTION
+  Interact with an active agent to preview how the agent responds to your statements, questions, and commands
+  (utterances).
+
+  Use this command to have a natural language conversation with an active agent in your org, as if you were an actual
+  user. The interface is simple: in the "Start typing..." prompt, enter a statement, question, or command; when you're
+  done, enter Return. Your utterance is posted on the right along with a timestamp. The agent then responds on the left.
+  To exit the conversation, hit ESC or Control+C.
+
+  This command is useful to test if the agent responds to your utterances as you expect. For example, you can test that
+  the agent uses a particular topic when asked a question, and then whether it invokes the correct action associated
+  with that topic. This command is the CLI-equivalent of the Conversation Preview panel in your org's Agent Builder UI.
+
+  When the session concludes, the command asks if you want to save the API responses and chat transcripts. By default,
+  the files are saved to the "./temp/agent-preview" directory. Specify a new default directory by setting the
+  environment variable "SF_AGENT_PREVIEW_OUTPUT_DIR" to the directory. Or you can pass the directory to the --output-dir
+  flag.
+
+  Find the agent's API name in its main details page in your org's Agent page in Setup.
+
+  Before you use this command, you must complete these steps:
+
+  1. Create a connected app in your org as described in the "Create a Connected App" section here:
+  https://developer.salesforce.com/docs/einstein/genai/guide/agent-api-get-started.html#create-a-connected-app. Do these
+  four additional steps:
+
+  a. When specifying the connected app's Callback URL, add this second callback URL on a new line:
+  "http://localhost:1717/OauthRedirect".
+
+  b. When adding the scopes to the connected app, add "Manage user data via Web browsers (web)".
+
+  c. Ensure that the "Require Secret for Web Server Flow" option is not selected.
+
+  d. Make note of the user that you specified as the "Run As" user when updating the Client Credentials Flow section.
+
+  2. Add the connected app to your agent as described in the "Add Connected App to Agent" section here:
+  https://developer.salesforce.com/docs/einstein/genai/guide/agent-api-get-started.html#add-connected-app-to-agent.
+
+  3. Copy the consumer key from your connected app as described in the "Obtain Credentials" section here:
+  https://developer.salesforce.com/docs/einstein/genai/guide/agent-api-get-started.html#obtain-credentials.
+
+  4. Set the "SFDX_AUTH_SCOPES" environment variable to "refresh_token sfap_api chatbot_api web api". This step ensures
+  that you get the specific OAuth scopes required by this command.
+
+  5. Using the username of the user you specified as the "Run As" user above, authorize your org using the web server
+  flow, as described in this document:
+  https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_web_flow.htm.
+
+  IMPORTANT: You must use the "--client-id <CONNECTED-APP-CONSUMER-KEY>" flag of "org login web", where
+  CONNECTED-APP-CONSUMER-KEY is the consumer key you previously copied. This step ensures that the "org login web"
+  command uses your custom connected app, and not the default CLI connected app.
+
+  Press Enter to skip sharing the client secret.
+
+  6. When you run this command to interact with an agent, specify the username you authorized in the preceding step with
+  the --connected-app-user (-a) flag.
+
+EXAMPLES
+  Interact with an agent with API name "Resort_Manager" in the org with alias "my-org". Connect to your agent using
+  the alias "my-agent-user"; this alias must point to the username who is authorized using the Web server flow:
+
+    $ sf agent preview --api-name "Resort_Manager" --target-org my-org --connected-app-user my-agent-user
+
+  Same as the preceding example, but this time save the conversation transcripts to the "./transcripts/my-preview"
+  directory rather than the default "./temp/agent-preview":
+
+    $ sf agent preview --api-name "Resort_Manager" --target-org my-org --connected-app-user my-agent-user \
+      --output-dir "transcripts/my-preview"
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/preview.ts)_
+
+## `sf agent test create`
+
+Create an agent test in your org using a local test spec YAML file.
+
+```
+USAGE
+  $ sf agent test create -o <value> [--json] [--flags-dir <value>] [--api-name <value>] [--spec <value>] [--api-version
+    <value>] [--preview] [--force-overwrite]
+
+FLAGS
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
+      --api-name=<value>     API name of the new test; the API name must not exist in the org.
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --force-overwrite      Don't prompt for confirmation when overwriting an existing test (based on API name) in your
+                             org.
+      --preview              Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.
+      --spec=<value>         Path to the test spec YAML file.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Create an agent test in your org using a local test spec YAML file.
+
+  To run this command, you must have an agent test spec file, which is a YAML file that lists the test cases for testing
+  a specific agent. Use the "agent generate test-spec" CLI command to generate a test spec file. Then specify the file
+  to this command with the --spec flag, or run this command with no flags to be prompted.
+
+  When this command completes, your org contains the new agent test, which you can view and edit using the Testing
+  Center UI. This command also retrieves the metadata component (AiEvaluationDefinition) associated with the new test to
+  your local Salesforce DX project and displays its filename.
+
+  After you've created the test in the org, use the "agent test run" command to run it.
+
+EXAMPLES
+  Create an agent test interactively and be prompted for the test spec and API name of the test in the org; use the
+  default org:
+
+    $ sf agent test create
+
+  Create an agent test and use flags to specify all required information; if a test with same API name already exists
+  in the org, overwrite it without confirmation. Use the org with alias "my-org":
+
+    $ sf agent test create --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test \
+      --force-overwrite --target-org my-org
+
+  Preview what the agent test metadata (AiEvaluationDefinition) looks like without deploying it to your default org:
+
+    $ sf agent test create --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/test/create.ts)_
+
+## `sf agent test list`
+
+List the available agent tests in your org.
+
+```
+USAGE
+  $ sf agent test list -o <value> [--json] [--flags-dir <value>] [--api-version <value>]
+
+FLAGS
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
+      --api-version=<value>  Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  List the available agent tests in your org.
+
+  The command outputs a table with the name (API name) of each test along with its unique ID and the date it was created
+  in the org.
+
+EXAMPLES
+  List the agent tests in your default org:
+
+    $ sf agent test list
+
+  List the agent tests in an org with alias "my-org""
+
+    $ sf agent test list --target-org my-org
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/test/list.ts)_
+
+## `sf agent test results`
+
+Get the results of a completed agent test run.
+
+```
+USAGE
+  $ sf agent test results -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--result-format
+    json|human|junit|tap] [-d <value>]
+
+FLAGS
+  -d, --output-dir=<value>      Directory to write the agent test results into.
+  -i, --job-id=<value>          (required) Job ID of the completed agent test run.
+  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
+                                configuration variable is already set.
+      --api-version=<value>     Override the api version used for api requests made by this command
+      --result-format=<option>  [default: human] Format of the agent test run results.
+                                <options: json|human|junit|tap>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Get the results of a completed agent test run.
+
+  This command requires a job ID, which the original "agent test run" command displays when it completes. You can also
+  use the --use-most-recent flag to see results for the most recently run agent test.
+
+  By default, this command outputs test results in human-readable tables for each test case. The tables show whether the
+  test case passed, the expected and actual values, the test score, how long the test took, and more. Use the
+  --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to
+  a file rather than to the terminal.
+
+EXAMPLES
+  Get the results of an agent test run in your default org using its job ID:
+
+    $ sf agent test results --job-id 4KBfake0000003F4AQ
+
+  Get the results of the most recently run agent test in an org with alias "my-org":
+
+    $ sf agent test results --use-most-recent --target-org my-org
+
+  Get the results of the most recently run agent test in your default org, and write the JSON-formatted results into a
+  directory called "test-results":
+
+    $ sf agent test results --use-most-recent --output-dir ./test-results --result-format json
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory to write the agent test results into.
+
+    If the agent test run completes, write the results to the specified directory. If the test is still running, the
+    test results aren't written.
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/test/results.ts)_
+
+## `sf agent test resume`
+
+Resume an agent test that you previously started in your org so you can view the test results.
+
+```
+USAGE
+  $ sf agent test resume -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-i <value>] [-r] [-w
+    <value>] [--result-format json|human|junit|tap] [-d <value>]
+
+FLAGS
+  -d, --output-dir=<value>      Directory to write the agent test results into.
+  -i, --job-id=<value>          Job ID of the original agent test run.
+  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
+                                configuration variable is already set.
+  -r, --use-most-recent         Use the job ID of the most recent agent test run.
+  -w, --wait=<value>            [default: 5 minutes] Number of minutes to wait for the command to complete and display
+                                results to the terminal window.
+      --api-version=<value>     Override the api version used for api requests made by this command
+      --result-format=<option>  [default: human] Format of the agent test run results.
+                                <options: json|human|junit|tap>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Resume an agent test that you previously started in your org so you can view the test results.
+
+  This command requires a job ID, which the original "agent test run" command displays when it completes. You can also
+  use the --use-most-recent flag to see results for the most recently run agent test.
+
+  Use the --wait flag to specify the number of minutes for this command to wait for the agent test to complete; if the
+  test completes by the end of the wait time, the command displays the test results. If not, the CLI returns control of
+  the terminal to you, and you must run "agent test resume" again.
+
+  By default, this command outputs test results in human-readable tables for each test case. The tables show whether the
+  test case passed, the expected and actual values, the test score, how long the test took, and more. Use the
+  --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to
+  a file rather than to the terminal.
+
+EXAMPLES
+  Resume an agent test in your default org using a job ID:
+
+    $ sf agent test resume --job-id 4KBfake0000003F4AQ
+
+  Resume the most recently-run agent test in an org with alias "my-org" org; wait 10 minutes for the tests to finish:
+
+    $ sf agent test resume --use-most-recent --wait 10 --target-org my-org
+
+  Resume the most recent agent test in your default org, and write the JSON-formatted results into a directory called
+  "test-results":
+
+    $ sf agent test resume --use-most-recent --output-dir ./test-results --result-format json
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory to write the agent test results into.
+
+    If the agent test run completes, write the results to the specified directory. If the test is still running, the
+    test results aren't written.
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/test/resume.ts)_
+
+## `sf agent test run`
+
+Start an agent test in your org.
+
+```
+USAGE
+  $ sf agent test run -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>] [-w <value>]
+    [--result-format json|human|junit|tap] [-d <value>]
+
+FLAGS
+  -d, --output-dir=<value>      Directory to write the agent test results into.
+  -n, --api-name=<value>        API name of the agent test to run; corresponds to the name of the AiEvaluationDefinition
+                                metadata component that implements the agent test.
+  -o, --target-org=<value>      (required) Username or alias of the target org. Not required if the `target-org`
+                                configuration variable is already set.
+  -w, --wait=<value>            Number of minutes to wait for the command to complete and display results to the
+                                terminal window.
+      --api-version=<value>     Override the api version used for api requests made by this command
+      --result-format=<option>  [default: human] Format of the agent test run results.
+                                <options: json|human|junit|tap>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Start an agent test in your org.
+
+  Use the --api-name flag to specify the name of the agent test you want to run. Use the output of the "agent test list"
+  command to get the names of all the available agent tests in your org.
+
+  By default, this command starts the agent test in your org, but it doesn't wait for the test to finish. Instead, it
+  displays the "agent test resume" command, with a job ID, that you execute to see the results of the test run, and then
+  returns control of the terminal window to you. Use the --wait flag to specify the number of minutes for the command to
+  wait for the agent test to complete; if the test completes by the end of the wait time, the command displays the test
+  results. If not, run "agent test resume".
+
+  By default, this command outputs test results in human-readable tables for each test case, if the test completes in
+  time. The tables show whether the test case passed, the expected and actual values, the test score, how long the test
+  took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag
+  to write the results to a file rather than to the terminal.
+
+EXAMPLES
+  Start an agent test called Resort_Manager_Test for an agent in your default org, don't wait for the test to finish:
+
+    $ sf agent test run --api-name Resort_Manager_Test
+
+  Start an agent test for an agent in an org with alias "my-org" and wait for 10 minutes for the test to finish:
+
+    $ sf agent test run --api-name Resort_Manager_Test --wait 10 --target-org my-org
+
+  Start an agent test and write the JSON-formatted results into a directory called "test-results":
+
+    $ sf agent test run --api-name Resort_Manager_Test --wait 10 --output-dir ./test-results --result-format json
+
+FLAG DESCRIPTIONS
+  -d, --output-dir=<value>  Directory to write the agent test results into.
+
+    If the agent test run completes, write the results to the specified directory. If the test is still running, the
+    test results aren't written.
+```
+
+_See code: [@salesforce/plugin-agent](https://github.com/salesforcecli/plugin-agent/blob/1.22.7/src/commands/agent/test/run.ts)_
+
 ## `sf alias list`
 
 List all aliases currently set on your local computer.
@@ -4849,6 +5500,93 @@ FLAG DESCRIPTIONS
 
 _See code: [@salesforce/plugin-org](https://github.com/salesforcecli/plugin-org/blob/5.7.13/src/commands/org/resume/scratch.ts)_
 
+## `sf package convert`
+
+Create a second-generation package version from a first-generation package.
+
+```
+USAGE
+  $ sf package convert -v <value> -p <value> [--json] [--flags-dir <value>] [--api-version <value>] [-k <value>] [-f
+    <value>] [-x] [-w <value>] [-m <value>] [--verbose] [-a <value>]
+
+FLAGS
+  -a, --patch-version=<value>     Specific released patch version to convert
+  -f, --definition-file=<value>   Path to a definition file that contains features and org preferences that the metadata
+                                  of the package version depends on.
+  -k, --installation-key=<value>  Installation key for key-protected package.
+  -m, --seed-metadata=<value>     Directory containing metadata to be deployed prior to conversion.
+  -p, --package=<value>           (required) ID (starts with 033) of the first-generation package to convert.
+  -v, --target-dev-hub=<value>    (required) Username or alias of the Dev Hub org. Not required if the `target-dev-hub`
+                                  configuration variable is already set.
+  -w, --wait=<value>              Minutes to wait for the package version to be created.
+  -x, --installation-key-bypass   Bypass the installation key requirement.
+      --api-version=<value>       Override the api version used for api requests made by this command
+      --verbose                   Display verbose command output.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Create a second-generation package version from a first-generation package.
+
+  The package convert creates a new package in the Dev Hub if one does not already exist for the specified
+  first-generation package.
+
+  It then creates a new package version in the Dev Hub with contents based on the specified first-generation package.
+
+  By default, the latest released non-patch version from the specified first-generation package will be converted. Use
+  --patch-version to override the default. Read more about --patch-version option in help
+
+  To retrieve details about a package version create request, including status and package version ID (04t), run "sf
+  package version create report -i 08c...".
+
+  We recommend specifying the --installation-key to protect the contents of your package and to prevent unauthorized
+  installation of your package.
+
+  To list package version creation requests in the org, run "sf package version create list".
+
+ALIASES
+  $ sf force package convert
+
+EXAMPLES
+  Create a second-generation package version from the first-generation package with the specified ID and give it the
+  installation key "password123"; uses your default Dev Hub org:
+
+    $ sf package convert --package 033... --installation-key password123
+
+  Similar to previous example, but uses the specified Dev Hub org:
+
+    $ sf package convert --package 033... --installation-key password123 --target-dev-hub devhuborg@example.com
+
+FLAG DESCRIPTIONS
+  -a, --patch-version=<value>  Specific released patch version to convert
+
+    Specify a released patch version as major.minor.patch.build to convert to second generation package version
+
+  -f, --definition-file=<value>
+
+    Path to a definition file that contains features and org preferences that the metadata of the package version
+    depends on.
+
+    This definition file is similar to the scratch org definition file.
+
+  -k, --installation-key=<value>  Installation key for key-protected package.
+
+    Either an --installation-key value or the --installation-key-bypass flag is required.
+
+  -m, --seed-metadata=<value>  Directory containing metadata to be deployed prior to conversion.
+
+    The directory containing metadata that will be deployed on the build org prior to attempting conversion.
+
+  -x, --installation-key-bypass  Bypass the installation key requirement.
+
+    If you bypass this requirement, anyone can install your package. Either an --installation-key value or the
+    --installation-key-bypass flag is required.
+```
+
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/convert.ts)_
+
 ## `sf package create`
 
 Create a package.
@@ -4926,7 +5664,7 @@ FLAG DESCRIPTIONS
     Org-Dependent Unlocked Packages" in the Salesforce DX Developer Guide.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/create.ts)_
 
 ## `sf package delete`
 
@@ -4968,7 +5706,7 @@ EXAMPLES
     $ sf package delete --package 0Ho... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/delete.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/delete.ts)_
 
 ## `sf package install`
 
@@ -5067,7 +5805,7 @@ FLAG DESCRIPTIONS
     - Delete: Delete all removed components that can be safely deleted, and deprecate the other components.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/install.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/install.ts)_
 
 ## `sf package install report`
 
@@ -5100,7 +5838,7 @@ EXAMPLES
     $ sf package install report --request-id 0Hf... --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/install/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/install/report.ts)_
 
 ## `sf package installed list`
 
@@ -5132,7 +5870,7 @@ EXAMPLES
     $ sf package installed list --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/installed/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/installed/list.ts)_
 
 ## `sf package list`
 
@@ -5170,7 +5908,7 @@ EXAMPLES
     $ sf package list --target-dev-hub devhub@example.com --verbose
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/list.ts)_
 
 ## `sf package uninstall`
 
@@ -5218,7 +5956,7 @@ EXAMPLES
     $ sf package uninstall --package "Undesirable Package Alias"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/uninstall.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/uninstall.ts)_
 
 ## `sf package uninstall report`
 
@@ -5251,7 +5989,7 @@ EXAMPLES
     $ sf package uninstall report --request-id 06y... --target-org me@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/uninstall/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/uninstall/report.ts)_
 
 ## `sf package update`
 
@@ -5306,7 +6044,7 @@ FLAG DESCRIPTIONS
     associated with your package.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/update.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/update.ts)_
 
 ## `sf package version create`
 
@@ -5481,7 +6219,7 @@ FLAG DESCRIPTIONS
     periods of no output from commands.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/create.ts)_
 
 ## `sf package version create list`
 
@@ -5542,7 +6280,7 @@ EXAMPLES
     $ sf package version create list --created-last-days 0 --status Success
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/create/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/create/list.ts)_
 
 ## `sf package version create report`
 
@@ -5585,7 +6323,7 @@ EXAMPLES
     $ sf package version create report --package-create-request-id 08c... --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/create/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/create/report.ts)_
 
 ## `sf package version delete`
 
@@ -5626,7 +6364,7 @@ EXAMPLES
     $ sf package version delete --package 04t... --target-org devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/delete.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/delete.ts)_
 
 ## `sf package version displayancestry`
 
@@ -5686,7 +6424,7 @@ FLAG DESCRIPTIONS
     You can use the DOT code output in graph visualization software to create tree visualizations.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/displayancestry.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/displayancestry.ts)_
 
 ## `sf package version list`
 
@@ -5762,7 +6500,7 @@ EXAMPLES
     $ sf package version list --packages exp-mgr,exp-mgr-util --released --modified-last-days 0
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/list.ts)_
 
 ## `sf package version promote`
 
@@ -5806,7 +6544,7 @@ EXAMPLES
     $ sf package version promote --package "Awesome Package Alias"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/promote.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/promote.ts)_
 
 ## `sf package version report`
 
@@ -5846,7 +6584,7 @@ EXAMPLES
     $ sf package version report --package "Your Package Alias" --target-dev-hub devhub@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/report.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/report.ts)_
 
 ## `sf package version update`
 
@@ -5899,7 +6637,7 @@ EXAMPLES
     $ sf package version update --package 04t... --version-description "New Package Version Description"
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package/version/update.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package/version/update.ts)_
 
 ## `sf package1 version create`
 
@@ -5966,7 +6704,7 @@ FLAG DESCRIPTIONS
     subscribers.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package1/version/create.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package1/version/create.ts)_
 
 ## `sf package1 version create get`
 
@@ -5999,7 +6737,7 @@ EXAMPLES
     $ sf package1 version create get --request-id 0HD... --target-org myorg@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package1/version/create/get.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package1/version/create/get.ts)_
 
 ## `sf package1 version display`
 
@@ -6033,7 +6771,7 @@ EXAMPLES
     $ sf package1 version display --package-version-id 04t... --target-org myorg@example.com
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package1/version/display.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package1/version/display.ts)_
 
 ## `sf package1 version list`
 
@@ -6071,7 +6809,7 @@ FLAG DESCRIPTIONS
     If not specified, shows all versions for all packages (managed and unmanaged) in the org.
 ```
 
-_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.13.6/src/commands/package1/version/list.ts)_
+_See code: [@salesforce/plugin-packaging](https://github.com/salesforcecli/plugin-packaging/blob/2.14.0/src/commands/package1/version/list.ts)_
 
 ## `sf plugins`
 
diff --git a/package.json b/package.json
index e042710ba..a34faf8b7 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@salesforce/cli",
   "description": "The Salesforce CLI",
-  "version": "2.92.5",
+  "version": "2.92.6",
   "author": "Salesforce",
   "bin": {
     "sf": "./bin/run.js",
@@ -158,7 +158,7 @@
     "@oclif/plugin-which": "3.2.35",
     "@salesforce/core": "^8.9.1",
     "@salesforce/kit": "^3.1.6",
-    "@salesforce/plugin-agent": "1.22.6",
+    "@salesforce/plugin-agent": "1.22.7",
     "@salesforce/plugin-apex": "3.6.19",
     "@salesforce/plugin-api": "1.3.3",
     "@salesforce/plugin-auth": "3.6.126",
@@ -168,7 +168,7 @@
     "@salesforce/plugin-limits": "3.3.56",
     "@salesforce/plugin-marketplace": "1.3.8",
     "@salesforce/plugin-org": "5.7.13",
-    "@salesforce/plugin-packaging": "2.13.6",
+    "@salesforce/plugin-packaging": "2.14.0",
     "@salesforce/plugin-schema": "3.3.65",
     "@salesforce/plugin-settings": "2.4.29",
     "@salesforce/plugin-sobject": "1.4.59",
diff --git a/yarn.lock b/yarn.lock
index 56fee0efc..69c2c6ffb 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -2069,10 +2069,10 @@
     jszip "^3.10.1"
     object-treeify "^2"
 
-"@salesforce/plugin-agent@1.22.6":
-  version "1.22.6"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-agent/-/plugin-agent-1.22.6.tgz#3276ef5b62ea2b8f90d98da9980ef38d9567aab9"
-  integrity sha512-6UVUUqONdNjOkZFXFRU4pq4CCG/B+R420ABGZTxs4XtmXEceHc3DzZzlEI41KwE2tjJxjf4hiGpz9nUrW8I+uw==
+"@salesforce/plugin-agent@1.22.7":
+  version "1.22.7"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-agent/-/plugin-agent-1.22.7.tgz#e30c874fedfa7c50ff68113311e5be6fdbf2cce4"
+  integrity sha512-WxanBYmK67kSAD3yeo1HjkgrXzuGTOuVXzJmdgxyMtHJ58HSm+/udmvGUub9SajfjBi6RQeEY4XI7qDFAB+fMg==
   dependencies:
     "@inquirer/core" "^10.1.6"
     "@inquirer/prompts" "^7.2.0"
@@ -2239,10 +2239,10 @@
     open "^10.1.2"
     terminal-link "^3.0.0"
 
-"@salesforce/plugin-packaging@2.13.6":
-  version "2.13.6"
-  resolved "https://registry.yarnpkg.com/@salesforce/plugin-packaging/-/plugin-packaging-2.13.6.tgz#644d13637b0e9f8a401dfd888b68e88d405a4e66"
-  integrity sha512-BbSXWRjvptf1T5lhWPkYPcvWBbLlsq4w8FxXV88rwkjEJ/aYgJRrzurzEryOziS8MMElN8bovIIBgWsxeeJRSw==
+"@salesforce/plugin-packaging@2.14.0":
+  version "2.14.0"
+  resolved "https://registry.yarnpkg.com/@salesforce/plugin-packaging/-/plugin-packaging-2.14.0.tgz#b90c79d4972254ab301f04b09f07904c0ea87655"
+  integrity sha512-a0AzxLYPeJ80FjblZOLMRvyHQ1HMbkJEx2B6jjZN5bG1LN8BwkkdaaSiqT53PtftMTJhgtrOmlZ8Zs5zfvLO9g==
   dependencies:
     "@oclif/core" "^4"
     "@salesforce/core" "^8.11.1"
@@ -10421,7 +10421,16 @@ static-eval@2.0.2:
   dependencies:
     escodegen "^1.8.1"
 
-"string-width-cjs@npm:string-width@^4.2.0", string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
+"string-width-cjs@npm:string-width@^4.2.0":
+  version "4.2.3"
+  resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz"
+  integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
+  dependencies:
+    emoji-regex "^8.0.0"
+    is-fullwidth-code-point "^3.0.0"
+    strip-ansi "^6.0.1"
+
+string-width@^4.0.0, string-width@^4.1.0, string-width@^4.2.0, string-width@^4.2.3:
   version "4.2.3"
   resolved "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz"
   integrity sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==
@@ -10503,7 +10512,14 @@ stringify-package@^1.0.1:
   resolved "https://registry.npmjs.org/stringify-package/-/stringify-package-1.0.1.tgz"
   integrity sha512-sa4DUQsYciMP1xhKWGuFM04fB0LG/9DlluZoSVywUMRNvzid6XucHK0/90xGxRoHrAaROrcHK1aPKaijCtSrhg==
 
-"strip-ansi-cjs@npm:strip-ansi@^6.0.1", strip-ansi@6.0.1, strip-ansi@^6, strip-ansi@^6.0.0, strip-ansi@^6.0.1:
+"strip-ansi-cjs@npm:strip-ansi@^6.0.1":
+  version "6.0.1"
+  resolved "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz"
+  integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
+  dependencies:
+    ansi-regex "^5.0.1"
+
+strip-ansi@6.0.1, strip-ansi@^6, strip-ansi@^6.0.0, strip-ansi@^6.0.1:
   version "6.0.1"
   resolved "https://registry.npmjs.org/strip-ansi/-/strip-ansi-6.0.1.tgz"
   integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
@@ -11324,7 +11340,7 @@ workerpool@^6.5.1:
   resolved "https://registry.yarnpkg.com/workerpool/-/workerpool-6.5.1.tgz#060f73b39d0caf97c6db64da004cd01b4c099544"
   integrity sha512-Fs4dNYcsdpYSAfVxhnl1L5zTksjvOJxtC5hzMNl+1t9B8hTJTdKDyZ5ju7ztgPy+ft9tBFXoOlDNiOT9WUXZlA==
 
-"wrap-ansi-cjs@npm:wrap-ansi@^7.0.0", wrap-ansi@^7.0.0:
+"wrap-ansi-cjs@npm:wrap-ansi@^7.0.0":
   version "7.0.0"
   resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz"
   integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
@@ -11342,6 +11358,15 @@ wrap-ansi@^6.2.0:
     string-width "^4.1.0"
     strip-ansi "^6.0.0"
 
+wrap-ansi@^7.0.0:
+  version "7.0.0"
+  resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-7.0.0.tgz"
+  integrity sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==
+  dependencies:
+    ansi-styles "^4.0.0"
+    string-width "^4.1.0"
+    strip-ansi "^6.0.0"
+
 wrap-ansi@^8.1.0:
   version "8.1.0"
   resolved "https://registry.npmjs.org/wrap-ansi/-/wrap-ansi-8.1.0.tgz"