revert(skills): remove offline validation scripts

Drop the metadata XML and dw.json validation scripts plus the optional
SKILL.md sections that referenced them. Use case needs more evaluation.

Author: clavery

.changeset/skills-plugin-install-improvements.md

@@ -8,6 +8,5 @@ Broaden skills-plugin install support and improve the installation docs.
 - Add a Codex plugin marketplace so the three plugins (`b2c-cli`, `b2c`, `b2c-dx-mcp`) can be installed directly from Codex CLI's plugin directory.
 - Add a new `b2c-onboarding` skill (in the `b2c` plugin) that walks new developers through CLI verify, `dw.json` setup, sandbox connect, and first cartridge deploy, then hands off to the topic-specific skill for the user's goal.
 - Add per-plugin READMEs with install instructions for each supported client.
-- Add optional offline validation scripts for generated metadata XML (`b2c-metadata`) and `dw.json` (`b2c-config`).
 - Document Copilot CLI + VS Code Copilot install paths and the Codex marketplace install path.
 - Remove the `b2c-experimental` plugin from the public marketplace.

skills/b2c-cli/skills/b2c-config/SKILL.md

@@ -7,16 +7,6 @@ description: Inspect and debug CLI configuration, instance connections, and auth
 
 The B2C CLI (`@salesforce/b2c-cli`) is a command-line tool for Salesforce B2C Commerce development. It provides commands organized by topic: `auth`, `code`, `webdav`, `sandbox`, `mrt`, `scapi`, `slas`, `ecdn`, `job`, `logs`, `sites`, `content`, `cip`, `setup`, and more. Use `b2c --help` or `b2c <topic> --help` for a full list.
 
-## Optional: validate a generated dw.json
-
-After writing or editing a `dw.json`, you can lint it structurally with the bundled script. The check is offline and requires no credentials — it validates JSON shape, recognized keys, and that at least one complete auth method is present.
-
-```bash
-node scripts/validate.mjs ./dw.json
-```
-
-Exit 0 = valid. Exit 1 = validation errors (e.g., no auth credentials). Exit 2 = file/parse error. Unknown keys are warnings, not errors.
-
 > **Tip:** If `b2c` is not installed globally, use `npx @salesforce/b2c-cli` instead (e.g., `npx @salesforce/b2c-cli setup inspect`).
 
 ## Authentication

skills/b2c-cli/skills/b2c-config/scripts/validate.mjs

@@ -7,21 +7,6 @@ description: Define custom attributes, custom object types, and site preferences
 
 This skill guides you through working with site metadata XML for Salesforce B2C Commerce, including custom attributes, custom objects, and site preferences.
 
-## Optional: validate before returning
-
-Before returning generated metadata XML to the user, you can validate it against the authoritative XSD (shipped with the `b2c` CLI) using the bundled script. This is optional but catches structural mistakes early (missing required attributes, wrong element nesting, invalid enum values).
-
-```bash
-node scripts/validate.mjs --file <your-file.xml> --schema <schema-name>
-
-# Common schemas
-node scripts/validate.mjs --file system-objecttype-extensions.xml --schema metadata
-node scripts/validate.mjs --file catalog.xml --schema catalog
-node scripts/validate.mjs --file preferences.xml --schema preferences
-```
-
-Requires `b2c` on PATH (or `B2C_CMD="npx @salesforce/b2c-cli"` env var) and system `xmllint`. Exit 0 = valid. Non-zero = validation errors printed to stderr. List all schemas: `b2c docs schema --list`.
-
 
 ## Overview