Merge branch 'main' into feature-W-20893693-add-am-topic

Author: amit-kumar8-sf

.changeset/mrt-command-reorganization.md

@@ -0,0 +1,5 @@
+---
+'@salesforce/b2c-cli': minor
+---
+
+Reorganizes MRT commands by scope: project-level commands under `mrt project`, environment-level under `mrt env`, and deployment commands under `mrt bundle`. The `mrt bundle download` command now downloads files by default instead of just printing the URL.

.changeset/mrt-complete-coverage.md

@@ -0,0 +1,6 @@
+---
+'@salesforce/b2c-cli': minor
+'@salesforce/b2c-tooling-sdk': minor
+---
+
+Adds complete MRT CLI coverage organized by scope: `mrt project` (CRUD, members, notifications), `mrt env` (CRUD, variables, redirects, access-control, cache invalidation, B2C connections), `mrt bundle` (deploy, list, history, download), `mrt org` (list, B2C instances), and `mrt user` (profile, API key, email preferences).

.changeset/mrt-push-to-bundle.md

@@ -0,0 +1,5 @@
+---
+'@salesforce/b2c-cli': minor
+---
+
+Replaces `mrt push` with `mrt bundle deploy`. The new command supports both pushing local builds and deploying existing bundles by ID.

.changeset/sour-months-post.md

@@ -3,4 +3,4 @@
 '@salesforce/b2c-tooling-sdk': minor
 ---
 
-adds package.json config source for project level shared config
+Add `b2c ecdn` commands for managing eCDN zones, certificates, WAF, caching, security settings, and related configurations.

.github/workflows/changesets.yml

@@ -4,6 +4,8 @@ on:
   push:
     branches:
       - main
+    paths:
+      - '.changeset/**'
 
 concurrency: ${{ github.workflow }}-${{ github.ref }}
 

AGENTS.md

@@ -110,12 +110,12 @@ Changeset guidelines:
 - Create a changeset for any user-facing changes (features, bug fixes); typically in new pull requests; 
 - a pull request can have multiple changesets
 - Select the appropriate semver bump: `patch` (bug fixes) or `minor` (new features)
-- This is a pre-1.0 preview release, so there are no `major` breaking change bumps
+- This is a pre-1.0 preview release, so there are no `major` breaking change bumps yet
 - Good changesets explain:
   - WHAT the change is
   - WHY the change was made
   - HOW a consumer should update their code
-- Good changesets are brief and user-focused (not contributor); they are generally 1 line or a short paragraph for detailed changes
+- Good changesets are brief and user-focused (not contributor); they are generally 1 line or a short paragraph for detailed changes; The content of the changeset is used in CHANGELOG and release notes.
 
 create a changeset file directly in `.changeset/` with a unique filename (e.g., `descriptive-change-name.md`):
 
@@ -129,4 +129,3 @@ Description of the change explaining WHAT, WHY, and HOW to update
 ```
 
 - Include only the packages that were modified
-- Use `patch` for bug fixes, `minor` for new features

docs/.vitepress/config.mts

@@ -35,6 +35,7 @@ const guideSidebar = [
       { text: 'WebDAV Commands', link: '/cli/webdav' },
       { text: 'ODS Commands', link: '/cli/ods' },
       { text: 'MRT Commands', link: '/cli/mrt' },
+      { text: 'eCDN Commands', link: '/cli/ecdn' },
       { text: 'SLAS Commands', link: '/cli/slas' },
       { text: 'Custom APIs', link: '/cli/custom-apis' },
       { text: 'SCAPI Schemas', link: '/cli/scapi-schemas' },