@ethisyscore/plugin-ui 1.92.1 → 1.93.0

package/dist/components/connectors/index.d.cts

@@ -144,8 +144,24 @@ interface MappingCompletenessBannerProps {
     /**
      * Opens the manual mapping editor for an operation. The consumer owns the editor surface and
      * routing; the banner only raises intent.
+     *
+     * Every known consumer wires this to the request/response translation editor, which is why the
+     * row control is labelled for what it opens rather than for this prop's name. Kept required
+     * because it always was: making it optional would let a consumer render rows with no action.
      */
     onOpenMappingEditor: (operation: MappingCompletenessItem) => void;
+    /**
+     * OPTIONAL, and the preferred wiring. Jumps straight to the operation's REQUEST-FIELD
+     * TRANSLATION editor — the "Configure field translation" surface — rather than to whatever general
+     * mapping surface `onOpenMappingEditor` happens to open.
+     *
+     * @remarks
+     * Optional on purpose. This package is pinned independently by every plugin, so a required prop
+     * would break every consumer that has not been updated. When it is absent the row falls back to
+     * `onOpenMappingEditor` with identical rendering, so an un-updated consumer keeps exactly the
+     * behaviour it had and still gains the corrected copy.
+     */
+    onConfigureTranslation?: (operation: MappingCompletenessItem) => void;
     /**
      * Operation key currently awaiting an AI suggestion, or `null`. Drives the per-row spinner and
      * disabled state so a slow suggestion does not lock the whole banner.
@@ -181,8 +197,22 @@ interface MappingCompletenessBannerProps {
  *
  * A row without the "No tool mapped" chip already HAS a tool and needs its fields mapped. That chip
  * is the only thing distinguishing the two states, which is why the prose points at it.
+ *
+ * **The second wording fix, from a production report.** Saying "fields" was necessary but not
+ * sufficient. An operator read "fields that aren't mapped to this connector's tools", concluded the
+ * TOOL was unmapped (it was not), and had no idea which control closed the gap — the text named an
+ * abstraction, "the mapping editor", and never the affordance on screen. So the copy now names the
+ * thing that is missing (the REQUEST-FIELD TRANSLATION, canonical field name → the tool's own
+ * parameter name) and the control that supplies it ("Configure field translation"), and every
+ * listed operation carries that control inline. Their words: "it doesnt really suggest how to fix
+ * it".
+ *
+ * That label is not invented here: it is the verbatim tooltip and aria-label of the per-row gear in
+ * every consumer's `ConnectorMappingView` (host gogo-ui, self-healing, tech, timesheets, sales). The
+ * prose has to name a string the operator can actually find on the page, so a near-miss paraphrase
+ * would reintroduce the defect in a quieter form.
  */
-declare function MappingCompletenessBanner({ operations, onSuggestWithAi, onOpenMappingEditor, suggestingOperationKey, disableSuggest, }: MappingCompletenessBannerProps): react.JSX.Element | null;
+declare function MappingCompletenessBanner({ operations, onSuggestWithAi, onOpenMappingEditor, onConfigureTranslation, suggestingOperationKey, disableSuggest, }: MappingCompletenessBannerProps): react.JSX.Element | null;
 
 interface ConnectorMappingTranslationEditorProps {
     open: boolean;

package/dist/components/connectors/index.d.ts

@@ -144,8 +144,24 @@ interface MappingCompletenessBannerProps {
     /**
      * Opens the manual mapping editor for an operation. The consumer owns the editor surface and
      * routing; the banner only raises intent.
+     *
+     * Every known consumer wires this to the request/response translation editor, which is why the
+     * row control is labelled for what it opens rather than for this prop's name. Kept required
+     * because it always was: making it optional would let a consumer render rows with no action.
      */
     onOpenMappingEditor: (operation: MappingCompletenessItem) => void;
+    /**
+     * OPTIONAL, and the preferred wiring. Jumps straight to the operation's REQUEST-FIELD
+     * TRANSLATION editor — the "Configure field translation" surface — rather than to whatever general
+     * mapping surface `onOpenMappingEditor` happens to open.
+     *
+     * @remarks
+     * Optional on purpose. This package is pinned independently by every plugin, so a required prop
+     * would break every consumer that has not been updated. When it is absent the row falls back to
+     * `onOpenMappingEditor` with identical rendering, so an un-updated consumer keeps exactly the
+     * behaviour it had and still gains the corrected copy.
+     */
+    onConfigureTranslation?: (operation: MappingCompletenessItem) => void;
     /**
      * Operation key currently awaiting an AI suggestion, or `null`. Drives the per-row spinner and
      * disabled state so a slow suggestion does not lock the whole banner.
@@ -181,8 +197,22 @@ interface MappingCompletenessBannerProps {
  *
  * A row without the "No tool mapped" chip already HAS a tool and needs its fields mapped. That chip
  * is the only thing distinguishing the two states, which is why the prose points at it.
+ *
+ * **The second wording fix, from a production report.** Saying "fields" was necessary but not
+ * sufficient. An operator read "fields that aren't mapped to this connector's tools", concluded the
+ * TOOL was unmapped (it was not), and had no idea which control closed the gap — the text named an
+ * abstraction, "the mapping editor", and never the affordance on screen. So the copy now names the
+ * thing that is missing (the REQUEST-FIELD TRANSLATION, canonical field name → the tool's own
+ * parameter name) and the control that supplies it ("Configure field translation"), and every
+ * listed operation carries that control inline. Their words: "it doesnt really suggest how to fix
+ * it".
+ *
+ * That label is not invented here: it is the verbatim tooltip and aria-label of the per-row gear in
+ * every consumer's `ConnectorMappingView` (host gogo-ui, self-healing, tech, timesheets, sales). The
+ * prose has to name a string the operator can actually find on the page, so a near-miss paraphrase
+ * would reintroduce the defect in a quieter form.
  */
-declare function MappingCompletenessBanner({ operations, onSuggestWithAi, onOpenMappingEditor, suggestingOperationKey, disableSuggest, }: MappingCompletenessBannerProps): react.JSX.Element | null;
+declare function MappingCompletenessBanner({ operations, onSuggestWithAi, onOpenMappingEditor, onConfigureTranslation, suggestingOperationKey, disableSuggest, }: MappingCompletenessBannerProps): react.JSX.Element | null;
 
 interface ConnectorMappingTranslationEditorProps {
     open: boolean;

package/dist/components/connectors/index.js

@@ -850,6 +850,7 @@ function MappingCompletenessBanner({
   operations,
   onSuggestWithAi,
   onOpenMappingEditor,
+  onConfigureTranslation,
   suggestingOperationKey = null,
   disableSuggest = false
 }) {
@@ -875,7 +876,8 @@ function MappingCompletenessBanner({
               !op.isToolMapped && /* @__PURE__ */ jsx(Chip, { label: "No tool mapped", size: "small", color: "warning", variant: "outlined" })
             ] }),
             /* @__PURE__ */ jsxs(Typography, { variant: "caption", color: "text.secondary", children: [
-              "Unmapped required fields: ",
+              "Unmapped required request fields:",
+              " ",
               op.unmappedRequiredCanonicalFields.join(", ")
             ] })
           ] }),
@@ -899,8 +901,8 @@ function MappingCompletenessBanner({
                 size: "small",
                 variant: "text",
                 color: "primary",
-                onClick: () => onOpenMappingEditor(op),
-                children: "Open mapping editor"
+                onClick: () => (onConfigureTranslation ?? onOpenMappingEditor)(op),
+                children: "Configure field translation"
               }
             )
           ] })
@@ -910,20 +912,29 @@ function MappingCompletenessBanner({
   };
   return /* @__PURE__ */ jsxs(Box, { sx: { mb: 2 }, children: [
     required.length > 0 && /* @__PURE__ */ jsxs(Alert, { severity: "warning", sx: { mb: optional.length > 0 ? 2 : 0 }, children: [
-      /* @__PURE__ */ jsx(AlertTitle, { children: "Required operations aren't fully mapped" }),
+      /* @__PURE__ */ jsx(AlertTitle, { children: "Required operations are missing request-field mappings" }),
+      /* @__PURE__ */ jsxs(Typography, { variant: "body2", children: [
+        required.length === 1 ? "1 required operation declares" : `${required.length} required operations declare`,
+        " ",
+        `canonical request fields that aren't mapped to any parameter the tool accepts. The missing piece is the REQUEST-FIELD TRANSLATION: the per-operation map from the operation's canonical field names to the tool's own parameter names. It is not the tool binding, which a row without a "No tool mapped" chip already has. Ethisys Core can't run these reliably until every listed field is translated, and auto-match picks the TOOL, not its fields, so it won't clear them on its own.`
+      ] }),
       /* @__PURE__ */ jsxs(Typography, { variant: "body2", sx: { mb: 1.5 }, children: [
-        required.length === 1 ? "1 required operation has" : `${required.length} required operations have`,
+        'Fix each operation below with "Configure field translation": for every field listed, enter the parameter name the tool actually expects, for example a canonical',
+        " ",
+        /* @__PURE__ */ jsx(Box, { component: "code", children: "startDate" }),
+        " the tool calls",
         " ",
-        `fields that aren't mapped to this connector's tools yet. Ethisys Core can't run these reliably until every required field is mapped. Auto-match picks the TOOL, not its fields, so it won't clear these on its own: use "Suggest with AI" or the mapping editor per operation.`
+        /* @__PURE__ */ jsx(Box, { component: "code", children: "start_date" }),
+        '. "Suggest with AI" proposes the same translation for you to review in that editor before saving.'
       ] }),
       /* @__PURE__ */ jsx(Stack, { spacing: 1.5, children: required.map(renderRow) })
     ] }),
     optional.length > 0 && /* @__PURE__ */ jsxs(Alert, { severity: "info", children: [
-      /* @__PURE__ */ jsx(AlertTitle, { children: "Optional operations aren't fully mapped" }),
+      /* @__PURE__ */ jsx(AlertTitle, { children: "Optional operations are missing request-field mappings" }),
       /* @__PURE__ */ jsxs(Typography, { variant: "body2", sx: { mb: 1.5 }, children: [
-        optional.length === 1 ? "1 optional operation has fields that aren't" : `${optional.length} optional operations have fields that aren't`,
+        optional.length === 1 ? "1 optional operation declares request fields that aren't" : `${optional.length} optional operations declare request fields that aren't`,
         " ",
-        `mapped to this connector's tools. These power extra capabilities (e.g. pull-request quality and check-run insights) and stay off until their fields are mapped \u2014 safe to leave if you don't need them, or if this connector doesn't provide a matching tool. Each row below lists exactly which fields are missing; a row without a "No tool mapped" chip already HAS a tool and needs its fields mapped, which auto-match does not do.`
+        `mapped to the tool's own parameter names. These power extra capabilities and stay off until that request-field translation is supplied, so they are safe to leave if you don't need them, or if this connector exposes no matching tool. Each row below lists exactly which fields are missing; a row without a "No tool mapped" chip already HAS a tool and needs only its fields translated, which auto-match does not do. Use "Configure field translation" on the row to supply it.`
       ] }),
       /* @__PURE__ */ jsx(Stack, { spacing: 1.5, children: optional.map(renderRow) })
     ] })