From f146dbdddbee989acca1e18a22f1f2bb3dfff7ed Mon Sep 17 00:00:00 2001 From: Michael Dailey Date: Fri, 15 May 2026 11:17:03 -0500 Subject: [PATCH] PDX-0: docs(mcp): remove internal ticket references from customer docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit RCA: The published customer-facing MCP guides (docs/mcp.md and docs/mcp-pilot-guide.md) leaked internal Jira identifiers — "PDX-464", "PDX-479" — and a corresponding internal-only version reference ("1.5.0 (PDX-479)"). These ticket IDs are only meaningful inside the Provar engineering org and should not appear in docs that ship to pilots and customers. Fix: Rewrite the three offending passages without losing technical meaning. (1) docs/mcp.md catalog-source note replaces "(dev build or pre-PDX-464 release)" with "(dev build or an older release that predates this metadata)". (2) docs/mcp-pilot-guide.md Scenario 12 Background drops "in 1.5.0 (PDX-479)" and describes the regression as "previously observed". (3) docs/mcp-pilot-guide.md Scenario 12 FAIL action replaces "file against PDX-479 (or its successor)" with "report it to the Provar team". No tool, schema, or behaviour changes — docs only. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/mcp-pilot-guide.md | 4 ++-- docs/mcp.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/mcp-pilot-guide.md b/docs/mcp-pilot-guide.md index 9fbaa55b..c771ee78 100644 --- a/docs/mcp-pilot-guide.md +++ b/docs/mcp-pilot-guide.md @@ -443,7 +443,7 @@ NitroX is Provar's Hybrid Model for locators — it maps Salesforce component-ba **Goal:** Confirm the AI authors a multi-scenario test case by passing the full step tree to `provar_testcase_generate` in **one** call — not by generating an empty skeleton and looping `provar_testcase_step_edit` per step. -**Background:** A regression in 1.5.0 (PDX-479) traced to authoring guidance that steered LLMs toward a per-step construction pattern. Multi-call construction drops scenario numbers (e.g. Scenario 1 → Scenario 3, no Scenario 2), flattens asserts that should be nested inside `UiWithScreen` clauses, and produces inconsistent assert API IDs across the case. This scenario exists so the regression class is exercised in pilot evaluation and cannot recur silently. +**Background:** A previously observed regression traced to authoring guidance that steered LLMs toward a per-step construction pattern. Multi-call construction drops scenario numbers (e.g. Scenario 1 → Scenario 3, no Scenario 2), flattens asserts that should be nested inside `UiWithScreen` clauses, and produces inconsistent assert API IDs across the case. This scenario exists so the regression class is exercised in pilot evaluation and cannot recur silently. **Prompt:** @@ -469,7 +469,7 @@ NitroX is Provar's Hybrid Model for locators — it maps Salesforce component-ba - A call to `provar_testcase_generate` with `steps: []` followed by `provar_testcase_step_edit` calls - The generated case skips a scenario number, mixes assert API IDs for similar assertions, or emits asserts as flat siblings rather than nested inside the screen wrapper -If any FAIL indicator appears, file against PDX-479 (or its successor) with the prompt and the generated XML attached. +If any FAIL indicator appears, report it to the Provar team with the prompt and the generated XML attached. --- diff --git a/docs/mcp.md b/docs/mcp.md index 7a08fed2..805e6d56 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -2102,7 +2102,7 @@ Version metadata for the bundled NitroX component catalog and JSON schemas. Retu } ``` -`commitSha` and `fetchedAt` are `null` when the release build could not reach the internal source (fallback catalog in use). `schemasUpdated` is `true` when both `FactComponent.schema` and `FactPackage.schema` were successfully fetched from the same internal revision and bundled into this release; `false` when the schema fetch failed and the previously committed schemas are in use; `null` when the catalog source was not generated (dev build or pre-PDX-464 release). +`commitSha` and `fetchedAt` are `null` when the release build could not reach the internal source (fallback catalog in use). `schemasUpdated` is `true` when both `FactComponent.schema` and `FactPackage.schema` were successfully fetched from the same internal revision and bundled into this release; `false` when the schema fetch failed and the previously committed schemas are in use; `null` when the catalog source was not generated (dev build or an older release that predates this metadata). ---