npm - @salesforce/b2c-dx-mcp - Versions diffs - 2.1.2 → 3.0.1 - Mend

@salesforce/b2c-dx-mcp 2.1.2 → 3.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1439) hide show

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/assets/logo.svg ADDED Viewed

@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 92 64">
+  <defs>
+    <style>
+      .cls-1, .cls-2 {
+        fill: #fff;
+      }
+      .cls-3 {
+        fill: #0d9dda;
+      }
+      .cls-2 {
+        fill-rule: evenodd;
+      }
+    </style>
+  </defs>
+  <path class="cls-3" d="m38.33,6.98c2.95-3.07,7.05-4.98,11.59-4.98,6.04,0,11.3,3.37,14.11,8.36,2.44-1.09,5.14-1.7,7.97-1.7,10.89,0,19.71,8.9,19.71,19.89s-8.83,19.89-19.71,19.89c-1.33,0-2.63-.13-3.88-.39-2.47,4.4-7.18,7.38-12.58,7.38-2.26,0-4.4-.52-6.3-1.45-2.5,5.89-8.34,10.02-15.13,10.02s-13.11-4.48-15.43-10.76c-1.01.21-2.06.33-3.14.33-8.43,0-15.26-6.9-15.26-15.42,0-5.71,3.07-10.69,7.63-13.36-.94-2.16-1.46-4.55-1.46-7.05C6.45,7.94,14.4,0,24.21,0,29.97,0,35.09,2.74,38.33,6.98Z"/>
+  <g>
+    <path class="cls-1" d="m13.53,33.19c-.06.15.02.18.04.21.17.12.35.21.52.32.93.49,1.81.64,2.73.64,1.88,0,3.04-1,3.04-2.6v-.03c0-1.48-1.32-2.02-2.55-2.41l-.16-.05c-.93-.3-1.73-.56-1.73-1.18v-.03c0-.52.47-.91,1.2-.91.81,0,1.77.27,2.38.61,0,0,.18.12.25-.06.04-.1.35-.94.38-1.03.04-.1-.03-.17-.09-.21-.71-.43-1.68-.72-2.69-.72h-.19c-1.72,0-2.92,1.04-2.92,2.52v.03c0,1.57,1.32,2.07,2.56,2.43l.2.06c.9.28,1.68.52,1.68,1.15v.03c0,.58-.51,1.01-1.32,1.01-.32,0-1.33,0-2.42-.7-.13-.08-.21-.13-.31-.19-.05-.03-.19-.09-.25.08l-.37,1.03Z"/>
+    <path class="cls-1" d="m40.98,33.19c-.06.15.02.18.04.21.17.12.35.21.52.32.93.49,1.81.64,2.73.64,1.88,0,3.04-1,3.04-2.6v-.03c0-1.48-1.31-2.02-2.55-2.41l-.16-.05c-.93-.3-1.73-.56-1.73-1.18v-.03c0-.52.47-.91,1.2-.91.81,0,1.77.27,2.38.61,0,0,.18.12.25-.06.04-.1.35-.94.38-1.03.04-.1-.03-.17-.09-.21-.71-.43-1.68-.72-2.69-.72h-.19c-1.72,0-2.92,1.04-2.92,2.52v.03c0,1.57,1.32,2.07,2.56,2.43l.2.06c.9.28,1.68.52,1.68,1.15v.03c0,.58-.51,1.01-1.32,1.01-.32,0-1.33,0-2.42-.7-.13-.08-.21-.13-.31-.19-.03-.02-.19-.08-.25.08l-.37,1.03Z"/>
+    <path class="cls-1" d="m61.29,28.36c-.15-.52-.39-.98-.71-1.36-.32-.38-.72-.69-1.2-.91-.48-.22-1.04-.34-1.68-.34s-1.2.11-1.68.34c-.48.22-.88.53-1.2.91-.32.38-.56.84-.71,1.36-.15.52-.23,1.08-.23,1.68s.08,1.17.23,1.68c.15.52.39.98.71,1.36.32.38.73.69,1.2.91.48.22,1.04.33,1.68.33s1.2-.11,1.68-.33c.48-.22.88-.52,1.2-.91.32-.38.56-.84.71-1.36.15-.52.23-1.08.23-1.68s-.08-1.17-.23-1.68m-1.57,1.68c0,.91-.17,1.62-.5,2.13-.33.5-.83.74-1.52.74s-1.19-.24-1.52-.74c-.33-.51-.5-1.22-.5-2.13s.17-1.62.49-2.12c.33-.5.82-.74,1.52-.74s1.19.24,1.52.74c.33.5.5,1.21.5,2.12"/>
+    <path class="cls-2" d="m74.15,32.67c-.05-.15-.2-.09-.2-.09-.23.09-.47.17-.73.21-.26.04-.55.06-.86.06-.76,0-1.36-.23-1.79-.67-.43-.45-.68-1.17-.67-2.14,0-.89.22-1.55.6-2.06.38-.51.96-.76,1.74-.76.65,0,1.14.07,1.66.24,0,0,.12.05.18-.11.14-.38.24-.65.39-1.07.04-.12-.06-.17-.1-.18-.2-.08-.68-.21-1.04-.26-.34-.05-.73-.08-1.17-.08-.66,0-1.24.11-1.75.34-.5.22-.92.53-1.26.91-.34.38-.59.84-.76,1.36-.17.52-.26,1.08-.26,1.69,0,1.3.35,2.35,1.04,3.12.69.77,1.73,1.16,3.09,1.16.8,0,1.62-.16,2.22-.4,0,0,.11-.05.06-.19l-.38-1.06Z"/>
+    <path class="cls-2" d="m82.16,28.07c-.13-.5-.46-1.01-.68-1.24-.34-.37-.67-.62-1.01-.77-.43-.19-.95-.31-1.52-.31-.66,0-1.26.11-1.75.34-.49.23-.9.54-1.22.93-.32.39-.56.85-.72,1.38-.15.52-.23,1.09-.23,1.69s.08,1.18.24,1.69c.16.52.42.97.77,1.35.35.38.8.68,1.33.88.53.21,1.18.31,1.92.31,1.53,0,2.34-.35,2.67-.53.06-.03.11-.09.05-.25l-.35-.97c-.05-.14-.2-.09-.2-.09-.38.14-.92.39-2.18.39-.82,0-1.43-.24-1.81-.62-.39-.39-.58-.96-.62-1.76h5.3s.14,0,.15-.13c0-.06.18-1.09-.16-2.28Zm-5.27,1.11c.07-.5.21-.92.43-1.25.32-.5.82-.77,1.52-.77s1.15.27,1.48.77c.22.33.31.76.35,1.25h-3.78Z"/>
+    <path class="cls-2" d="m39.72,28.07c-.13-.5-.46-1.01-.68-1.24-.34-.37-.67-.62-1.01-.77-.43-.19-.95-.31-1.52-.31-.66,0-1.26.11-1.75.34-.49.23-.9.54-1.22.93-.32.39-.56.85-.72,1.38-.15.52-.23,1.09-.23,1.69s.08,1.18.24,1.69c.16.52.42.97.77,1.35.35.38.8.68,1.33.88.53.21,1.18.31,1.92.31,1.53,0,2.34-.35,2.67-.53.06-.03.11-.09.04-.25l-.35-.97c-.05-.14-.2-.09-.2-.09-.38.14-.92.39-2.18.39-.82,0-1.43-.24-1.81-.62-.39-.39-.58-.96-.62-1.76h5.3s.14,0,.15-.13c0-.06.18-1.09-.16-2.28Zm-5.27,1.11c.07-.5.21-.92.43-1.25.33-.5.82-.77,1.52-.77s1.15.27,1.49.77c.22.33.31.76.35,1.25h-3.78Z"/>
+    <path class="cls-1" d="m25.1,28.92c-.22-.02-.49-.02-.83-.02-.45,0-.89.06-1.31.17-.41.11-.79.28-1.11.51-.32.23-.58.52-.77.87-.19.35-.28.76-.28,1.22s.08.88.24,1.21c.16.33.39.61.69.83.29.21.66.37,1.08.47.42.09.89.14,1.4.14.54,0,1.09-.05,1.61-.13.52-.09,1.16-.22,1.33-.26.18-.04.37-.09.37-.09.13-.03.12-.17.12-.17v-4.85c0-1.06-.29-1.85-.85-2.34-.56-.49-1.37-.73-2.43-.73-.4,0-1.04.05-1.42.13,0,0-1.16.22-1.63.6,0,0-.1.06-.05.21l.38,1.01c.05.13.17.09.17.09,0,0,.04-.02.09-.04,1.02-.55,2.31-.54,2.31-.54.57,0,1.01.12,1.31.34.29.22.44.56.44,1.26v.22c-.45-.07-.87-.1-.87-.1Zm-2.11,3.72c-.21-.17-.24-.21-.31-.31-.1-.16-.16-.39-.16-.69,0-.47.15-.8.47-1.03,0,0,.46-.4,1.54-.38.76,0,1.44.12,1.44.12v2.41h0s-.67.14-1.43.19c-1.08.06-1.56-.31-1.55-.31Z"/>
+    <path class="cls-2" d="m67.84,26.19c.04-.12-.04-.18-.08-.19-.09-.03-.54-.13-.89-.15-.67-.04-1.04.07-1.37.22-.33.15-.69.39-.9.66v-.65c0-.09-.06-.16-.15-.16h-1.36c-.09,0-.15.07-.15.16v7.91c0,.09.07.16.16.16h1.39c.09,0,.16-.07.16-.16v-3.95c0-.53.06-1.06.18-1.39.11-.33.27-.59.46-.78.19-.19.41-.32.65-.39.25-.08.52-.1.71-.1.28,0,.58.07.58.07.1.01.16-.05.19-.14.09-.24.35-.97.4-1.11Z"/>
+    <path class="cls-2" d="m54.77,22.53c-.17-.05-.32-.09-.52-.12-.2-.04-.45-.06-.72-.06-.96,0-1.71.27-2.24.81-.53.53-.89,1.34-1.06,2.4l-.06.36h-1.2s-.15,0-.18.15l-.2,1.1c-.01.11.03.17.17.17h1.17l-1.19,6.63c-.09.53-.2.97-.32,1.31-.12.33-.23.57-.37.75-.14.17-.26.3-.48.37-.18.06-.39.09-.62.09-.13,0-.3-.02-.43-.05-.13-.02-.19-.05-.29-.09,0,0-.14-.05-.19.09-.04.11-.36.97-.39,1.08-.04.1.02.19.08.21.16.06.27.09.48.14.29.07.54.07.78.07.49,0,.93-.07,1.3-.2.37-.13.69-.37.98-.68.31-.34.5-.7.69-1.19.18-.48.34-1.08.47-1.78l1.19-6.76h1.75s.15,0,.18-.15l.2-1.1c.01-.11-.03-.17-.17-.17h-1.69s.09-.63.28-1.2c.08-.24.24-.43.37-.57.13-.13.28-.22.44-.28.17-.05.36-.08.57-.08.16,0,.32.02.44.04.16.03.23.05.27.07.17.05.2,0,.23-.08l.41-1.11c.04-.12-.06-.17-.1-.18Z"/>
+    <path class="cls-2" d="m31.1,33.99c0,.09-.06.16-.15.16h-1.41c-.09,0-.15-.07-.15-.16v-11.31c0-.09.06-.16.15-.16h1.41c.09,0,.15.07.15.16v11.31Z"/>
+  </g>
+</svg>

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/plugin.json ADDED Viewed

@@ -0,0 +1,43 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "b2c-ops",
+  "version": "1.9.0",
+  "description": "B2C Commerce operator and administrator runbooks for job health, checkout and failed orders, and incident triage.",
+  "author": {
+    "name": "Salesforce"
+  },
+  "homepage": "https://salesforcecommercecloud.github.io/b2c-developer-tooling/",
+  "repository": "https://github.com/SalesforceCommerceCloud/b2c-developer-tooling",
+  "license": "Apache-2.0",
+  "keywords": [
+    "salesforce",
+    "b2c-commerce",
+    "operations",
+    "administration",
+    "runbooks",
+    "incident-triage"
+  ],
+  "extensions": {
+    "com.openai": {
+      "interface": {
+        "displayName": "B2C Operations",
+        "shortDescription": "Job health and incident investigation runbooks.",
+        "longDescription": "Review scheduled work, investigate checkout and failed orders, and prepare evidence-backed handoffs using B2C Commerce tools.",
+        "developerName": "Salesforce",
+        "category": "Productivity",
+        "capabilities": [
+          "Read"
+        ],
+        "logo": "./assets/logo.svg",
+        "composerIcon": "./assets/logo.svg",
+        "brandColor": "#0D9DDA",
+        "websiteURL": "https://salesforcecommercecloud.github.io/b2c-developer-tooling/",
+        "defaultPrompt": [
+          "Review scheduled jobs and flag incomplete updates",
+          "Investigate checkout failures without changing the instance",
+          "Prepare a developer handoff for this incident"
+        ]
+      }
+    }
+  }
+}

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-checkout-triage/SKILL.md ADDED Viewed

@@ -0,0 +1,68 @@
+---
+name: b2c-checkout-triage
+description: Investigate B2C Commerce checkout or payment failures, increased failed orders, or falling order volume. Compare bounded order evidence, integration logs and affected data; separate payment failures from traffic and reporting gaps.
+---
+# Checkout and payment triage
+Outcome: quantify the observed symptom, localize a likely subsystem, and produce
+an actionable handoff. Do not create test orders, charge/refund payments, change
+order status, or modify production data as part of inspection.
+## Scope and impact
+Use `config_inspect` (CLI: `b2c setup inspect`) and confirm site, UTC time window,
+reported symptom, and comparison period. Ask for missing values. Preserve the
+same target/window in all calls. No cartridge source is required.
+"Orders down" can mean less traffic, checkout errors, abandoned baskets, payment
+declines, or delayed reporting. Failed order records alone do not measure all
+checkout attempts or conversion. Do not force every incident into a payment cause.
+Record breadth, duration, workaround, and owner. Follow the team's severity and
+update process for live customer impact; do not wait for exact counts to escalate.
+## Access and tools
+| Signal                       | Preferred path                                                   | Limit / fallback                                                                                                                                                               |
+| ---------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Payment/custom logs          | `logs_list_files`, then `logs_get_recent` on discovered prefixes | Start with 20 relevant entries; samples are not full-window counts. CLI: `b2c logs list` / `b2c logs get`.                                                                     |
+| Order records                | Discover Admin Orders contracts via code mode                    | A response enum does not establish supported status filters. See [failed-order triage](skill://b2c-ops/b2c-order-failure-triage/SKILL.md) for the demonstrated OCAPI fallback. |
+| Affected products/attributes | SCAPI Admin product reads; live schemas for tenant custom fields | Compare known IDs and selected fields. Shopper contracts are reference-only in this runtime.                                                                                   |
+| Suspected import/integration | [b2c-job-health](skill://b2c-ops/b2c-job-health/SKILL.md)        | Read the chosen job's log and check its actual data effects.                                                                                                                   |
+| Traffic/latency context      | Code mode Metrics where enabled; CLI `b2c metrics`               | Feature access and scopes vary. CIP/CCAC trends: `cip_discover` / `cip_query` after [CIP guidance](skill://mcp/cip/SKILL.md), with freshness/coverage limits. CLI fallback: `b2c cip`.                                                          |
+Read `skill://mcp/scapi/SKILL.md` before code mode; prefer dedicated tools when
+available. Discover operations/required fields before requests, compose bounded
+reads, and return selected evidence with errors and continuation. Read only the
+conditional reference needed; native assistants can use installed skill names.
+## Checks and decisions
+1. Quantify with comparable windows and explicit denominators. Label unavailable
+   counts unknown, a zero-denominator ratio undefined, and sampled products as
+   sample frequencies. Preserve query errors; never convert them to zero failures.
+2. Find recurring integration errors, timestamps, and safe correlation IDs. Avoid
+   customer/payment data in output. A gateway response may point to upstream data,
+   configuration, provider availability, or input validation; test the alternatives.
+3. Compare a failing and healthy input. Discover relevant custom attributes if
+   needed; do not dump whole product/order payloads into context.
+4. Identify the writer of a suspect field, if evidence warrants it. Review job
+   execution/logs and real change records. Coincident modification timestamps
+   alone do not identify a regressing deployment.
+## Mitigation and recovery
+Reproduction, reruns, deployments, or data changes require explicit authorization
+and a suitable environment. After an intervention, compare the same signals over
+a fresh equivalent interval; verify business behavior and distinguish observation
+delay from confirmed recovery. Operator handoff can be complete without a code fix.
+## Escalation and handoff
+Report impact/site/window, counts and sample limits, safe correlation IDs, log
+excerpts, affected input, hypotheses, access gaps, and next owner/update. Continue
+with logs if order access is blocked. Route provider evidence to the integration
+owner, custom defects to the developer, and suspected platform failures to
+Salesforce Support. Use native `b2c-production-triage` or the MCP
+[case template](skill://b2c-ops/b2c-production-triage/references/escalation.md).
+Prepare a draft; submitting a case/message requires authorization.

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-job-health/SKILL.md ADDED Viewed

@@ -0,0 +1,75 @@
+---
+name: b2c-job-health
+description: Review B2C Commerce scheduled jobs during routine operations or investigate failed jobs, missing runs, stale imports, and green executions with incomplete results. Check logs and business data before proposing a rerun.
+---
+# Job health
+Outcome: identify which scheduled work completed its business purpose, what is
+late/failed/partial, and whether intervention or a developer handoff is needed.
+## Scope and impact
+Resolve instance/site and a fixed UTC interval with `config_inspect` (CLI:
+`b2c setup inspect`). Obtain the expected jobs, schedule/timezone, and intended
+updates from the user or available configuration. No matching execution is
+"missing" only when a run was actually expected.
+Record the business deadline, affected data/sites, and owner. For material impact,
+use the team's incident severity/update process; a routine review need not declare
+an incident. Do not invent impact from a red status alone.
+## Access and tools
+| Evidence                     | Preferred MCP path                                               | CLI fallback                                                 |
+| ---------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------ |
+| Execution history and steps  | `builtin/job-execution-review` / `builtin/job-execution-inspect` in code mode                                     | `b2c job search`; check `--help` for filters                 |
+| Known execution log          | `webdav_get` with the returned `logFilePath` | `b2c job log JOB_ID EXECUTION_ID`                            |
+| Expected product/data change | Discover the relevant Admin operation and select affected fields | Relevant CLI/data workflow if supported                      |
+| Code-version clues           | `builtin/code-version-inspect` in code mode                  | `b2c code list`; modification time is not activation history |
+Read `skill://mcp/scapi/SKILL.md` before code mode. Use its search/discovery
+contract; project/instance context belongs on tool calls. Authentication is
+managed. Do not export tokens or use ambient fetch inside code mode.
+## Checks and decisions
+1. Describe/run `builtin/job-execution-review` for a small page in the interval. For routine review, include
+   successful and unfinished runs, not only failures. Compare against the expected
+   schedule; inspect relevant steps/duration and time zone before calling a run late.
+2. For failure-only review, reuse `builtin/failed-job-triage`: inspect with
+   `codemode.describe`, then `codemode.run` with fixed `from`, `to`, and `limit`
+   (maximum 3). Continue using its returned offset/window only as needed. Keep
+   errors and partial results. The snippet returns selected execution fields,
+   not `stepExecutions`; use `builtin/job-execution-inspect` if steps matter.
+   A POST search can be blocked by Safety Mode;
+   explain the denied read operation rather than weakening policy.
+3. Read the selected execution's `logFilePath` with `webdav_get`; it accepts
+   `/Sites/LOGS/...` paths. Inspect size via `webdav_list`; read a bounded range
+   and continue via byte `nextOffset` only as needed. Download to `outputPath`
+   for local analysis. Use recent-log tools for filtering and watches, not an
+   exact raw-file read. [Job-log details](references/job-logs.md).
+4. Identify the first relevant fault, processed/skipped records, and which steps
+   actually ran. Job transitions can continue after errors; do not assume every
+   later step was skipped. Green status can also hide skipped or incomplete work.
+5. Verify a small sample of the expected data and one healthy comparison. Correlate
+   changes without claiming causation from matching timestamps alone.
+## Mitigation and recovery
+Before an authorized rerun, check for an active execution, partial writes,
+idempotency, duplicate exports/messages, and rollback limits. Inspect uncertain
+outcomes before retrying; never replay a whole code-mode program after writes.
+Verify business data as well as terminal job status after intervention.
+## Escalation and handoff
+Summarize job/execution/step IDs, impact/window, status, affected inputs, log
+evidence, observed data, unknowns, and next owner/action. Use the administrator
+for custom schedule/access issues, developer for custom-step defects, and
+Salesforce Support for suspected platform/system-job problems. Native skill:
+`b2c-production-triage`; MCP [case template](skill://b2c-ops/b2c-production-triage/references/escalation.md).
+No source access is required; case submission needs authorization.
+CLI-specific detail when needed: native `b2c-job`, MCP
+`skill://b2c-cli/b2c-job/SKILL.md`, or the
+[Jobs reference](https://salesforcecommercecloud.github.io/b2c-developer-tooling/cli/jobs).

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-job-health/references/job-logs.md ADDED Viewed

@@ -0,0 +1,21 @@
+# Job execution logs
+Use `logFilePath` from the selected execution, not a guessed file or only its
+status. `builtin/job-execution-inspect` returns the exact path and step details.
+`webdav_get` accepts Sites-relative paths and returned `/Sites/LOGS/...` paths.
+Use `webdav_list` on the parent directory for sizes when needed.
+Read a bounded byte range; reuse `nextOffset` to preserve UTF-8 boundaries.
+`size` is total bytes, not characters. Null continuation means end; a few pages
+do not establish whole-file or interval coverage. Files may grow/rotate between
+reads. Download to a new `outputPath` for local analysis of a large file.
+For recent parsed entries or ongoing watches, use `logs_get_recent` / `logs_watch`.
+These tools parse and filter; an empty result does not prove an empty raw log.
+Use `webdav_get` when parsing loses useful context. CLI alternative when needed:
+`b2c job log JOB_ID EXECUTION_ID`, preserving the selected instance.
+Never run the job just to obtain its previous log. A deleted/expired log, missing
+path, permission failure, and no matching recent parsed entries are different
+outcomes. Preserve the error and suggest the smallest next check. If no file is
+available, request the selected execution's log from Business Manager.

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-order-failure-triage/SKILL.md ADDED Viewed

@@ -0,0 +1,66 @@
+---
+name: b2c-order-failure-triage
+description: Find and investigate FAILED B2C Commerce orders, quantify their share of indexed orders, and correlate failed inputs with logs and jobs. Covers SCAPI status-filter limitations and the OCAPI Shop order_search fallback.
+---
+# Failed-order triage
+Use when the user needs failed order records, counts, affected products, or an
+explanation of why a group of orders failed. Broader "checkout is down" symptoms
+start with `b2c-checkout-triage`; some checkout failures create no order at all.
+## Scope and impact
+Resolve instance/site with `config_inspect` (CLI: `b2c setup inspect`). Fix UTC
+`from`/`to` boundaries and a comparison period. Ask for missing site/window;
+do not use a demo default. Record impact and owner under the team's incident
+process. Counts describe indexed orders, not all checkout attempts or conversion.
+## Access and tools
+| Need                             | Toolkit path                                                                                                   | Important limit                                                                                                                              |
+| -------------------------------- | -------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| Enumerate FAILED orders          | Check Admin Orders query support with `scapi_search`; external OCAPI Shop `POST /order_search` is the fallback | SCAPI `status=failed` has returned HTTP 400; a response enum does not prove query support. CIP/CCAC is not a substitute for this population. |
+| External request authentication  | CLI `b2c auth token --json` or MCP's documented AM token-export helper                                         | Use only for the external client. SCAPI code mode has no OCAPI request helper, and its safety policy does not cover external HTTP.           |
+| Failure reason and correlation   | `logs_list_files` -> discovered integration prefix -> bounded `logs_get_recent`                                | Discover `custom-*` categories; error/customerror defaults can miss the payment integration.                                                 |
+| Suspect product/custom attribute | Code-mode Admin reads; live schema expansion when the field is unknown                                         | Compare selected fields on known failed/healthy IDs; Shopper execution is unsupported.                                                       |
+| Suspected data writer            | [b2c-job-health](skill://b2c-ops/b2c-job-health/SKILL.md)                                                      | Inspect the execution log and actual data effects, not just job status.                                                                      |
+Read [order-search recipe](references/order-evidence.md) before counting: it
+defines the site grant/index prerequisites, bounded request bodies, auth handling,
+and fault interpretation. For code mode, first read `skill://mcp/scapi/SKILL.md`.
+If external requests are unavailable, report that evidence gap and continue with
+logs; do not deploy an OrderMgr endpoint to obtain access.
+## Checks and decisions
+1. Query FAILED and all indexed order totals for the **same site/window**. Validate
+   every response. Report `failed / all indexed orders`; if either query fails,
+   the ratio is unknown. Zero denominator means undefined, not zero failures.
+2. Select at most 10 recent failed orders: order number, creation time, status,
+   and product IDs. Omit customer/payment fields. Label product frequencies as a
+   sample and deduplicate each product per order. The earliest indexed failure
+   in the window is not necessarily incident onset.
+3. Correlate safe order/request IDs and timestamps with integration logs. Test
+   whether failures cluster by input, provider response, region, or change window.
+   Do not infer a payment decline solely from the order's FAILED status.
+4. Compare one healthy input before blaming an attribute. If a job writes the
+   suspect field, inspect its log and persisted data. Keep failed stages,
+   sampling/index delays, alternative causes, and missing access explicit.
+## Mitigation and recovery
+Investigation does not authorize changing order status, reprocessing orders,
+retrying charges, refunding, rerunning integrations, or changing access/indexes.
+Before authorized intervention, establish duplicate-charge/message risks and
+partial effects. Verify new outcomes over an equivalent interval; old FAILED
+records need not disappear for recovery to be real.
+## Escalation and handoff
+Provide site/window, totals/denominator, sample size and safe IDs, recurring error,
+affected input, suspected writer/component, limitations, and the next owner.
+Route to the administrator, developer, integration provider, or Salesforce Support
+using the [case template](skill://b2c-ops/b2c-production-triage/references/escalation.md).
+Missing Shop access is a targeted administrator request, not evidence of no
+failures. Case submission and other external communication require authorization.

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-order-failure-triage/references/order-evidence.md ADDED Viewed

@@ -0,0 +1,87 @@
+# Failed-order search recipe
+## Choose a supported surface
+Admin Orders has rejected `status=failed` while its
+response schema still contained `failed`. Verify current query support before
+relying on it; do not infer a filter from response values or repeat a rejected
+request unchanged. CIP/CCAC is not evidence of the complete failed-order population.
+Its reporting model, ingestion delay, and coverage differ from order search.
+The demonstrated fallback is OCAPI **Shop** `POST /order_search`, backed by the
+site's order search index. There is no managed OCAPI request helper in SCAPI code
+mode. Use an authorized external HTTP client/terminal if available; otherwise
+report the gap and continue with logs. Do not deploy an OrderMgr controller or
+Custom API just to gain inspection access.
+## Access and execution
+Use configured hostname, site ID, and client ID from `config_inspect` or
+`b2c setup inspect`. Obtain an AM token through the CLI's `b2c auth token --json`
+for an external request, keeping it in memory and out of output/files. If using
+the MCP token helper, read `skill://mcp/scapi/references/tokens.md`; token export
+is only for the external client, never required for managed SCAPI calls.
+MCP Safety Mode does not protect an independently executed HTTP request.
+The OAuth client needs the site's OCAPI Shop resource grant for `POST /order_search`
+and a usable order search index. Use the
+[authentication guide](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/authentication)
+and `docs_search` for current OCAPI Settings/order indexing instructions. Have
+the user authorize any grant or index maintenance; do not perform it to satisfy
+a read request.
+POST `https://{hostname}/s/{siteId}/dw/shop/{version}/order_search?client_id={clientId}`
+with a Bearer token and JSON content type. Select a supported OCAPI version from
+configuration/docs; do not assume a version from an unrelated example.
+## Bounded query recipe
+Count FAILED orders for fixed UTC boundaries (replace `FROM` and `TO`):
+```json
+{
+  "query": {
+    "filtered_query": {
+      "query": {"term_query": {"fields": ["status"], "operator": "is", "values": ["failed"]}},
+      "filter": {"range_filter": {"field": "creation_date", "from": "FROM", "to": "TO"}}
+    }
+  },
+  "select": "(total)",
+  "count": 1
+}
+```
+For all indexed orders, replace only the inner query with `{"match_all_query":{}}`.
+Use the same site and bounds. `count: 0` is rejected; read `total` from a valid
+response. Report `failed / all indexed orders`, not failed/success or conversion.
+The denominator includes other statuses and cannot see attempts without orders.
+Separate requests are not an atomic snapshot; retain capture times/index caveats.
+For a maximum 10-order sample, keep the failed query and set:
+```json
+{
+  "select": "(hits.(data.(order_no,status,creation_date,product_items.(product_id))),total)",
+  "sorts": [{"field": "creation_date", "sort_order": "desc"}],
+  "count": 10
+}
+```
+Do not select email, addresses, or payment instruments. Count a product once per
+sampled order; label the sample size and total. For the earliest indexed failure
+inside this window, use ascending sort with `count: 1`; this is not necessarily
+incident onset. Do not crawl all historical orders by default.
+## Errors and interpretation
+Check HTTP success and expected response fields for **every** count/sample call.
+Report failed stages and preserve available results. Missing `total` or a failed
+query is unknown, never zero. Suppress the ratio if either count is unavailable.
+- 401: inspect the actual auth fault/expiry; do not print tokens.
+- 403 `ClientAccessForbiddenException`: check the site-specific Shop resource grant.
+  Other 403s need their own fault interpretation.
+- 500 mentioning Order Incremental Indexing: index prerequisite is unmet. Other
+  500s are server errors, not proof of an index problem.
+- Successful zero matches: distinguish no indexed matches in this window from
+  no checkout failures, ingestion/index lag, and incorrect target/window.

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-production-triage/SKILL.md ADDED Viewed

@@ -0,0 +1,87 @@
+---
+name: b2c-production-triage
+description: Investigate B2C Commerce incidents using B2C MCP logs, SCAPI code-mode job/data reads, and CLI fallbacks. Route error spikes, stale data, or checkout failures to focused runbooks and produce a team or Support handoff.
+---
+# Production triage
+Connect the toolkit's logs, job executions, business data, and configuration
+into an evidence-backed assessment and next action. Investigation does not
+authorize remediation. Use the symptom routes below rather than collecting
+every available signal.
+## Scope and impact
+- Resolve the task's project/instance with `config_inspect`; CLI: `b2c setup inspect`.
+  Preserve the resolved target across calls. Ask for missing site, time window,
+  timezone, symptom, or expected behavior; never invent IDs or silently switch tenants.
+- Start with the reported interval; if unspecified, propose the last two hours
+  and label that assumption. Use fixed UTC boundaries for comparisons and paging.
+- Record current impact (sites, checkout availability, order/data integrity,
+  workaround) and the incident owner. Apply the team's severity policy; do not
+  invent a priority or support SLA. Escalate active material impact early without
+  waiting for root cause; agree who communicates and the next update time.
+## Access and tools
+- Establish access: MCP, terminal/CLI, logs, data, source. Operator work does not
+  require a cartridge checkout. Credentials/setup issues: MCP `mcp/b2c-config`
+  section `setup-and-access`; native `b2c-config`/`b2c-auth`, or the
+  [authentication guide](https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/authentication).
+Prefer dedicated MCP tools; discover available names once. Read
+`skill://mcp/scapi/SKILL.md` before using `scapi_search`/`scapi_execute`, as those
+tools require. Read only the matching runbook/reference, not every linked skill.
+Native assistants use the installed skill name; MCP can read these URIs or use
+`skills_read` with `collection: "b2c-ops"` and a task query.
+| Symptom                                                   | Toolkit path                                                                                                                                | Decision / detail                                                                                                                                                            |
+| --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Error spike or integration errors                         | `logs_list_files` -> returned `prefix` -> `logs_get_recent` with `count: 20`, `since`, and a relevant `search`                              | Defaults cover error/customerror, not every `custom-*` integration log. CLI: `b2c logs list` / `b2c logs get`.                                                               |
+| Failed job or stale data                                  | Code mode `codemode.describe("builtin/failed-job-triage")`, then run with fixed `from`/`to` -> execution IDs and `logFilePath` -> log tools | [Job health](skill://b2c-ops/b2c-job-health/SKILL.md) covers continuation, step details, exact WebDAV logs, and green-but-incomplete runs.                                        |
+| Checkout failures or orders down                          | Custom logs -> determine whether failures produce order records -> relevant data/traffic evidence                                           | [Checkout triage](skill://b2c-ops/b2c-checkout-triage/SKILL.md) distinguishes checkout symptoms from failed-order records.                                                   |
+| Find/count FAILED orders or investigate affected products | Verify Admin filter support; otherwise external OCAPI Shop order search -> safe IDs -> logs and selected Admin product reads                | [Failed-order triage](skill://b2c-ops/b2c-order-failure-triage/SKILL.md) owns enumeration, count/sample limits, and the workaround. No OCAPI helper exists inside code mode. |
+| Suspected code change                                     | Code mode `builtin/code-version-inspect`: active/rollback versions and activation/modification timestamps                                                                             | Current metadata is not a complete activation history. Corroborate with release records.                                                             |
+| Runtime-only defect                                       | [MCP debugger](skill://mcp/debugger/SKILL.md) on an authorized reproduction target                                                          | Operator handoff is valid without source access. Do not halt production requests for routine triage.                                                                         |
+## Checks and decisions
+1. Carry the returned configuration `resolution` into the evidence record.
+   `config_inspect` stays masked; do not read `dw.json` or request tokens merely
+   to make managed MCP calls. Pass the same project/instance context to CLI fallbacks.
+2. Join signals using execution IDs, log timestamps, and affected record IDs.
+   For exact job logs, pass the returned `logFilePath` to `webdav_get`; use byte
+   continuation or download locally. Recent-log tools remain preferred for
+   filtered samples/watches. A bounded result is not full-interval coverage.
+3. Reuse code-mode snippet totals/window/`nextOffset`; do not return entire
+   schemas or records. The failed-job snippet omits step details and healthy
+   runs: use `builtin/job-execution-inspect` / `builtin/job-execution-review` selectively. Compare expected business data
+   with a healthy input before calling a green job healthy.
+4. Preserve failed stages: HTTP `ok`/`status` and diagnostics, or thrown
+   auth/transport/safety errors. An OCAPI fallback error may mask an earlier
+   SCAPI rejection; CLI `--api-backend scapi` isolates it. POST searches can
+   be blocked by Safety Mode despite being reads. Do not infer missing scopes
+   from every 403 or treat unavailable counts as zero.
+## Mitigation and recovery
+Recommend the smallest supported mitigation, its blast radius and rollback limit.
+The authorized owner decides; inspecting an incident is not permission to change
+it. Restore service when justified without waiting for a full causal explanation.
+After intervention, recheck business behavior and comparable signals over an
+agreed observation interval. Report recovered, partial, pending, or unknown;
+record follow-up prevention separately from immediate recovery.
+## Escalation and handoff
+Report: target/site; UTC window; observed impact and denominator; evidence
+locations (execution IDs, log path/timestamps, minimal excerpts); suspected
+component/input/change; alternative explanations; access gaps; next owner/action.
+Exclude tokens, payment details, and unnecessary customer data.
+Route custom-code evidence to the developer/implementation partner, grant or
+schedule issues to the administrator, provider failures to the integration owner,
+and suspected platform failures to Salesforce Support. Read
+[escalation and case template](references/escalation.md) when preparing a handoff.
+Do not submit a case/message without authorization or claim a confirmed cause
+when evidence establishes only a lead.

package/node_modules/@salesforce/b2c-agent-plugins/b2c-ops/skills/b2c-production-triage/references/escalation.md ADDED Viewed

@@ -0,0 +1,57 @@
+# Escalation and support cases
+Use the team's incident process and severity definitions. Record an owner and
+next update time; keep a short UTC timeline of observations/actions. Escalation
+does not require a proven root cause, and a customer-impacting incident should
+not wait for complete diagnostics. Say what remains unknown.
+## Select the owner
+| Evidence or constraint                                                                                                              | Next owner/action                                                                                                                                                                                                             |
+| ----------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Custom cartridge defect or regression                                                                                               | Developer/implementation partner; minimal input, stack/context, change evidence, safe reproduction target                                                                                                                     |
+| Missing grant, local setup, business configuration, custom job schedule                                                             | Instance/account administrator; exact denied operation or configuration discrepancy; no blanket privilege request                                                                                                             |
+| Gateway/provider timeout or documented provider rejection                                                                           | Integration owner/provider; sanitized correlation IDs, UTC window, matching error and healthy comparison                                                                                                                      |
+| Platform/system errors, suspected platform regression, inaccessible infrastructure, system-job contention requiring platform action | Contact Salesforce Support through a support case; attach evidence and impact, not an unproven diagnosis                                                                                                                      |
+| Broad availability/performance incident                                                                                             | Check [B2C Commerce Trust status](https://status.salesforce.com/products/B2C_Commerce_Cloud), correlate instance/window, and engage the incident owner/Support as appropriate; green status does not rule out a local problem |
+| Unknown owner or insufficient access                                                                                                | Give a bounded handoff to the incident owner with the missing evidence and next check; do not keep collecting unrelated data                                                                                                  |
+Salesforce Platform Support covers the product; custom solutions normally go to
+the implementation partner unless the customer's Solution Support agreement
+applies. Follow the customer's support entitlement and current official guidance.
+## Case or handoff draft
+```text
+Title: [B2C Commerce] symptom and affected instance/site
+Impact / urgency: affected users or business function, scope, workaround;
+  severity per the customer's policy (or unassigned)
+Target: realm/instance, hostname, site, environment, platform version if known
+Window: first observed / last observed UTC; ongoing or intermittent
+Expected / observed: business behavior, counts and denominator, sample limits
+Reproduction: simplest safe steps; reference-app comparison if feasible
+Evidence: execution/request IDs, exact log files/timestamps, short redacted excerpts
+Changes checked: code/data/configuration changes and actual evidence
+Actions taken: time, owner, operation, result; partial effects and rollback state
+Assessment: confirmed observations, hypotheses, alternatives, missing access/data
+Request: specific investigation/help needed; current owner and next update
+```
+For suspected product issues, use a minimal reproduction, preferably on the
+Reference Application when safe and available. Do not deploy a reference app
+or reproduce production writes merely to complete a case. Redact credentials,
+customer/payment data, session cookies, and sensitive HAR content before sharing.
+Keep unredacted evidence in the customer's approved store; do not put it in a
+public repository. A draft is not a submitted case.
+## Official platform guidance
+- `docs_read` ID `b2c-commerce/b2c-reporting-to-support`, or
+  [Reporting to B2C Commerce Support](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-reporting-to-support.html):
+  select Platform/Solution Support, gather reproduction and logs, open a case in
+  [Salesforce Help](https://help.salesforce.com/s/).
+- `docs_read` ID `b2c-commerce/b2c-troubleshooting-platform-performance`, or
+  [Troubleshooting B2C Commerce Performance](https://developer.salesforce.com/docs/commerce/b2c-commerce/guide/b2c-troubleshooting-platform-performance.html):
+  distinguish custom code, system errors, provider timeouts, and resource locks.
+Read the applicable guidance on demand; it is not a prerequisite for routine checks.