refactor(b2c-dx-mcp): migrate page-designer-decorator tests from custom runner to Mocha

Remove custom test runner (index.test.mjs) and consolidate all test cases
into the standard Mocha test suite (index.test.ts) for consistency with
the monorepo's test framework.

Author: sf-cboscenco

packages/b2c-dx-mcp/src/tools/page-designer-decorator/README.md

@@ -227,20 +227,22 @@ pnpm test
 
 Comprehensive test suite covers all workflow modes, component discovery, and error handling.
 
-### Manual Test Runner
+### Running Tests
 
-For quick manual verification, use the test runner script:
+Run the comprehensive Mocha test suite:
 
 ```bash
 cd packages/b2c-dx-mcp
-pnpm build
-node test/tools/page-designer-decorator/index.test.mjs all
+pnpm run test:agent -- test/tools/page-designer-decorator/index.test.ts
 ```
 
-Run a specific test case:
-```bash
-node test/tools/page-designer-decorator/index.test.mjs TC-1.1
-```
+The test suite covers:
+- Component discovery (name-based, kebab-case, nested, path-based, custom paths, name collisions)
+- Auto mode (basic, type inference, complex props exclusion, UI-only props exclusion, edge cases)
+- Interactive mode (all steps: analyze, select_props, configure_attrs, configure_regions, confirm_generation)
+- Error handling (invalid input, invalid step name, missing parameters)
+- Edge cases (no props, only complex props, optional props, union types, already decorated components)
+- Environment variables (SFCC_WORKING_DIRECTORY)
 
 See [`test/tools/page-designer-decorator/README.md`](../../../test/tools/page-designer-decorator/README.md) for detailed testing instructions.
 

packages/b2c-dx-mcp/test/tools/page-designer-decorator/README.md

@@ -5,10 +5,15 @@
 The page-designer-decorator tool has comprehensive unit tests covering:
 - ✅ Tool metadata (name, description, toolsets, isGA)
 - ✅ Mode selection flow
-- ✅ Error handling
+- ✅ Auto mode (basic, type inference, complex/UI props exclusion, edge cases)
+- ✅ Interactive mode (all steps: analyze, select_props, configure_attrs, configure_regions, confirm_generation)
+- ✅ Component resolution (name-based, kebab-case, nested, path-based, custom searchPaths, name collisions)
+- ✅ Error handling (invalid input, invalid step name, missing parameters)
 - ✅ Input validation
+- ✅ Edge cases (no props, only complex props, optional props, union types, already decorated components)
+- ✅ Environment variables (SFCC_WORKING_DIRECTORY)
 
-Some integration tests may require actual component files in a real workspace to fully validate component resolution.
+All tests use the standard Mocha test framework and run with `pnpm test`.
 
 ## Testing Approaches
 
@@ -50,68 +55,28 @@ npx mcp-inspector --cli node bin/dev.js --toolsets STOREFRONTNEXT --allow-non-ga
   --args '{"component": "MyComponent"}'
 ```
 
-### 4. Automated Manual Test Runner
+### 4. Running Tests Against a Local Storefront Next Installation
 
-A test runner script is available to quickly verify the tool with various test scenarios:
+The Mocha test suite supports testing against a real Storefront Next installation by setting `SFCC_WORKING_DIRECTORY`:
 
 ```bash
 cd packages/b2c-dx-mcp
-pnpm build  # Build the package first
-node test/tools/page-designer-decorator/index.test.mjs all
-```
-
-Run a specific test case:
-```bash
-node test/tools/page-designer-decorator/index.test.mjs TC-1.1
-```
-
-The script covers 24 automated test cases including:
-- Component discovery (name-based, path-based, nested, custom paths)
-- Auto mode (basic, type inference, complex props exclusion)
-- Interactive mode (mode selection, analyze step)
-- Error handling (invalid input, missing parameters)
-- Edge cases (no props, optional props, union types, collisions)
-- Environment variables (SFCC_WORKING_DIRECTORY)
-
-See the script's JSDoc header for a complete list of available test cases.
-
-#### Running Tests Against a Local Storefront Next Installation
-
-The test runner script supports two modes:
-
-**1. Temporary Directory Mode (Default)**
-Creates isolated test environments with temporary directories. Ideal for CI/CD and regression testing.
-
-```bash
-cd packages/b2c-dx-mcp
-pnpm build
-node test/tools/page-designer-decorator/index.test.mjs all
-```
-
-**2. Real Storefront Next Project Mode**
-Test against an existing Storefront Next installation by setting `SFCC_WORKING_DIRECTORY`:
-
-```bash
-cd packages/b2c-dx-mcp
-pnpm build
 SFCC_WORKING_DIRECTORY=/path/to/storefront-next \
-  node test/tools/page-designer-decorator/index.test.mjs all
+  pnpm run test:agent -- test/tools/page-designer-decorator/index.test.ts
 ```
 
 Or set it as an environment variable:
 ```bash
 export SFCC_WORKING_DIRECTORY=/path/to/storefront-next
 cd packages/b2c-dx-mcp
-pnpm build
-node test/tools/page-designer-decorator/index.test.mjs TC-1.1
+pnpm run test:agent -- test/tools/page-designer-decorator/index.test.ts
 ```
 
 **Important Notes for Real Project Mode**:
 - Component discovery searches in your real Storefront Next project (`SFCC_WORKING_DIRECTORY`)
-- Test components created by the script are placed in a temporary directory (not in your real project)
-- The script will **not** modify your real project files (read-only)
+- Tests create temporary directories for test components (not in your real project)
+- Tests will **not** modify your real project files (read-only)
 - Tests will use existing components from your real project if they exist
-- If a test component doesn't exist in your real project, the test will show a "component not found" result (this is expected)
 - The real project directory is preserved after testing
 - To test with specific components, ensure they exist in your real project's `src/components/` directory