Feature/mcp cartridge deploy implementation

[patricksullivansf]

Summary

Provides an implementation for the MCP Cartridge Deploy Tool (cartridge_deploy).

• implement using operations SDK findAndDeployCartridges
• add unit tests for MCP Cartridge Deploy Tool, using dependency injection pattern for SDK stubbing.
• add patricksullivansf to CODEOWNERS

Testing

This was tested in cursor within a folder created with the commands (wonky because I don't have b2c cli installed globally):

cd /opt/workspace/dev/b2c-developer-tooling
pnpm --filter @salesforce/b2c-cli run dev scaffold cartridge --name app_custom_test
mkdir ../tmp/cartridge_mcp_test
mv packages/b2c-cli/cartridges ../tmp/cartridge_mcp_test/.

#
# Final Project Folder Layout
#

cartridge_mcp_test/
 ├── dw.json
└── cartridges/
    └── app_custom_test/
        ├── .project      
        └── cartridge/
            ├── app_custom_test.properties
            ├── controllers/
            ├── models/
            ├── scripts/
            └── templates/

# dw.json contents
{
  "client-id": "50f33ebd-20cd-4f08-88bd-4dfefeedbc9e",
  "client-secret": "REDACTED",
   "username": "patricksullivan@salesforce.com",
  "password": "REDACTED",
  "hostname": "zzrf-045.dx.commercecloud.salesforce.com",
  "code-version": "v1"
}

To run the MCP we used the mcp.json below with the prompt: run the cartridge deploy tool to deploy app_custom_test

Note there were several failed attempts (see caveats below)

 "b2c-dx": {
      "command": "node",
      "args": [
        "/opt/workspace/dev/b2c-developer-tooling/packages/b2c-dx-mcp/bin/dev.js",
        "--working-directory",
        "${workspaceFolder}",
        "--toolsets",
        "CARTRIDGES",
        "--allow-non-ga-tools",
        "--debug"
      ]
    }

The cartridge successfully uploaded and can be seen ready to be deployed in https://zzrf-045.dx.commercecloud.salesforce.com/on/demandware.store/Sites-Site/default%3bapp%3d__bm_admin/ViewCodeVersion-Start?VersionID=v1

However, there are caveats worth further investigation

• originally I opened cursor with the root folder /opt/workspace/dev/tmp/cartridge_mcp_test/cartridges and dw.json at this root. I used the simple prompt "run the cartridge deploy tool" and cursor did an excellent job of supplying reasonable default paths to the tool. However, it was unable to find the dw.json file and deployment failed.
• after changing cursors root folder to /opt/workspace/dev/tmp/cartridge_mcp_test and dw.json at this root, cursor found the dw.json file. However, it did a terrible job of supplying default paths. On it's first run it scanned my entire home folder "~/." looking and failing to find the cartridges (note my home folder isn't even in the project path). On the third run it supplied an absolute path as the tool "directory" argument /opt/workspace/dev/tmp/cartridge_mcp_test/cartridges and this run succeeded.
• note the code-version also needed to be explicitly specified in the dw.json or the tool errored out. Mentioning this because I'm not sure if we want to supply a default, or if we want the MCP tool to be able to supply (and hallucinate) a code-version.

---

• Tests pass (pnpm test)
• Code is formatted (pnpm run format)

[clavery]

LGTM

[yhsieh1]

Should we want to allow push only operation?

[yhsieh1]

@patricksullivansf Sorry for not clear on what I mean. A better description helps understand how to use the tool. Can we improve the description so that agent knows how to use this tool properly?
For example add sections for:
When to use this tool:
How to choose operation:
Efficient workflows for agents:
Rules:
Examples:
Requirements:

[clavery]

You can reference the b2c-code skill for some ideas.

[patricksullivansf]

updated tool description and option descriptions using claude opus suggested text based on code and jsdoc of underlying sdk.

[yhsieh1]

We will need better tool name and description if we allow all operations.
We should also ask agent to confirm dangerous operation like delete.

[yhsieh1]

Please also update readme.md with some examples how to prompt agent to use the tool.

[patricksullivansf]

There's already this

[yhsieh1]

It only has description for cartridge deploy but does not contain other operation provided here. Also

b2c-developer-tooling/packages/b2c-dx-mcp/README.md

Line 239 in 87773ad

Cartridge development, deployment, and code version management.

needs update as well.

[patricksullivansf]

removed the delete option.

"cartridge deploy but does not contain other operation provided here" - think this was just a misunderstanding; updated the option descriptions to make it more clear the options affect cartridge deployment and are not unique operations.

[yhsieh1]

LGTM