nucleus-core-ts 0.10.147 → 0.10.151

package/dist/fe/components/IntegrationsPage/components/ConnectionOauthFields.js

@@ -6,12 +6,12 @@ import { clientAuthOptions, grantTypeOptions, toClientAuth, toGrantType } from '
 import { usesOauth } from './connectionDraft';
 import { describedBy } from './formSupport';
 import { Field } from './Primitives';
-/**
- * The OAuth 2 half of the auth section.
- *
- * It renders nothing at all for the other auth types, so the caller can place it
- * unconditionally and the question "is this connection OAuth" is answered in one
- * place instead of at every field.
+/**
+ * The OAuth 2 half of the auth section.
+ *
+ * It renders nothing at all for the other auth types, so the caller can place it
+ * unconditionally and the question "is this connection OAuth" is answered in one
+ * place instead of at every field.
  */ const theme = integrationsPageTheme;
 export function ConnectionOauthFields({ draft, errors, disabled, onChange }) {
     const labels = useLabels();

package/dist/fe/components/IntegrationsPage/components/ConnectionSettingsTab.js

@@ -7,33 +7,33 @@ import { ConnectionExport } from './ConnectionExport';
 import { ConnectionForm } from './ConnectionForm';
 import { ConnectionTest } from './ConnectionTest';
 import { CredentialFields } from './CredentialFields';
-/**
- * Everything about the connection itself: its address and authentication, its
- * credentials, and whether it answers.
- *
- * These three were written and then never reachable — the shell mounted the
- * connection list and the three child tabs and nothing else, so the panel could
- * show you connections but gave you no way to create or edit one. That is the
- * first screen an operator needs and it was the one screen missing.
- *
- * Credentials sit between the form and the test on purpose: an operator fills in
- * the address, enters the secret, then presses test. Putting the test above the
- * credential boxes invites pressing it before there is anything to authenticate
- * with, and reading the failure as "the address is wrong".
+/**
+ * Everything about the connection itself: its address and authentication, its
+ * credentials, and whether it answers.
+ *
+ * These three were written and then never reachable — the shell mounted the
+ * connection list and the three child tabs and nothing else, so the panel could
+ * show you connections but gave you no way to create or edit one. That is the
+ * first screen an operator needs and it was the one screen missing.
+ *
+ * Credentials sit between the form and the test on purpose: an operator fills in
+ * the address, enters the secret, then presses test. Putting the test above the
+ * credential boxes invites pressing it before there is anything to authenticate
+ * with, and reading the failure as "the address is wrong".
  */ export function ConnectionSettingsTab({ actions, onSaved, onDeleted }) {
     const store = useIntegrationsStore();
     const source = store.sources.find((candidate)=>candidate.id === store.selectedSourceId) ?? null;
-    /**
-   * Waiting for THIS record, and nothing else.
-   *
-   * It used to be `store.sourcesLoading || missingFromPage`, and sourcesLoading
-   * is true whenever the rail is fetching ANY page — including a page fetched
-   * because somebody typed a letter into the search box. With no connection
-   * chosen this tab is the blank "new connection" form, and every keystroke in
-   * the rail beside it replaced that form with skeletons.
-   *
-   * A form that is not editing a record is never loading: there is nothing to
-   * wait for. A form that IS editing one waits only until that record is here.
+    /**
+   * Waiting for THIS record, and nothing else.
+   *
+   * It used to be `store.sourcesLoading || missingFromPage`, and sourcesLoading
+   * is true whenever the rail is fetching ANY page — including a page fetched
+   * because somebody typed a letter into the search box. With no connection
+   * chosen this tab is the blank "new connection" form, and every keystroke in
+   * the rail beside it replaced that form with skeletons.
+   *
+   * A form that is not editing a record is never loading: there is nothing to
+   * wait for. A form that IS editing one waits only until that record is here.
    */ const waitingForRecord = store.selectedSourceId !== null && source === null;
     return /*#__PURE__*/ _jsxs("div", {
         className: theme.layout.main,

package/dist/fe/components/IntegrationsPage/components/ConnectionSwitcher.js

@@ -4,28 +4,28 @@ import { cn } from '../../../utils/cn';
 import { useIntegrationsStore } from '../store';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme as theme } from '../theme';
-/**
- * The chosen connection, as one line instead of a column.
- *
- * The panel used to keep the connection list as a permanent rail, so the work
- * happened in what was left — and the work is itself a list beside an editor.
- * Three columns inside an admin page that already has a nav is how a form ends
- * up past the right edge of the screen with the page scrolling sideways.
- *
- * A connection is CHOSEN once and then worked in. Once it is chosen the rail
- * has nothing left to say that this line does not, so the rail goes and the
- * whole width goes to the step.
+/**
+ * The chosen connection, as one line instead of a column.
+ *
+ * The panel used to keep the connection list as a permanent rail, so the work
+ * happened in what was left — and the work is itself a list beside an editor.
+ * Three columns inside an admin page that already has a nav is how a form ends
+ * up past the right edge of the screen with the page scrolling sideways.
+ *
+ * A connection is CHOSEN once and then worked in. Once it is chosen the rail
+ * has nothing left to say that this line does not, so the rail goes and the
+ * whole width goes to the step.
  */ export function ConnectionSwitcher() {
     const store = useIntegrationsStore();
     const labels = useLabels();
-    /**
-   * The way back does not depend on finding anything.
-   *
-   * `store.sources` is the rail's CURRENT PAGE, and the rail is unmounted the
-   * moment a connection is chosen — so a selected connection that is not on
-   * that page rendered nothing at all here: no name, and no way back to the
-   * list short of reloading the page. The name is what needs looking up; the
-   * button is not.
+    /**
+   * The way back does not depend on finding anything.
+   *
+   * `store.sources` is the rail's CURRENT PAGE, and the rail is unmounted the
+   * moment a connection is chosen — so a selected connection that is not on
+   * that page rendered nothing at all here: no name, and no way back to the
+   * list short of reloading the page. The name is what needs looking up; the
+   * button is not.
    */ if (!store.selectedSourceId) return null;
     const source = store.sources.find((candidate)=>candidate.id === store.selectedSourceId);
     return /*#__PURE__*/ _jsxs("div", {

package/dist/fe/components/IntegrationsPage/components/ConnectionTabs.js

@@ -4,21 +4,21 @@ import { useRef } from 'react';
 import { cn } from '../../../utils/cn';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
-/**
- * The four phases of an import, in the order they happen.
- *
- * These were four flat tabs — Connection, Endpoints, Mappings, Runs — sitting
- * side by side with nothing to say that they are a SEQUENCE, that a mapping is
- * meaningless before a call has been tried, or which of them the operator had
- * already finished. People opened the middle one first and met a dead end.
- *
- * So each is a step: a number, its name, one sentence saying what it is for, and
- * a line of evidence once it is done. What is on screen now answers "where am I,
- * what is this for, and what have I already got".
- *
- * It remains a real ARIA tablist — one stop in the tab order, arrow keys between
- * the steps. A row of separately tabbable cards would make a keyboard user press
- * Tab four times to leave a strip they were never inside.
+/**
+ * The four phases of an import, in the order they happen.
+ *
+ * These were four flat tabs — Connection, Endpoints, Mappings, Runs — sitting
+ * side by side with nothing to say that they are a SEQUENCE, that a mapping is
+ * meaningless before a call has been tried, or which of them the operator had
+ * already finished. People opened the middle one first and met a dead end.
+ *
+ * So each is a step: a number, its name, one sentence saying what it is for, and
+ * a line of evidence once it is done. What is on screen now answers "where am I,
+ * what is this for, and what have I already got".
+ *
+ * It remains a real ARIA tablist — one stop in the tab order, arrow keys between
+ * the steps. A row of separately tabbable cards would make a keyboard user press
+ * Tab four times to leave a strip they were never inside.
  */ const theme = integrationsPageTheme;
 const ORDER = [
     'connection',

package/dist/fe/components/IntegrationsPage/components/ConnectionTest.js

@@ -7,13 +7,13 @@ import { integrationsPageTheme } from '../theme';
 import { errorText } from './formSupport';
 import { Badge, Notice } from './Primitives';
 import { CardSkeleton } from './Skeletons';
-/**
- * One real call to the service, reported exactly as it came back.
- *
- * The failure text is printed whole. The server already names the setting that
- * has to change — a timeout, a certificate it would not accept, a 401 from the
- * token endpoint — and every word of that is worth more than a tidy summary that
- * sends the operator back to guessing.
+/**
+ * One real call to the service, reported exactly as it came back.
+ *
+ * The failure text is printed whole. The server already names the setting that
+ * has to change — a timeout, a certificate it would not accept, a 401 from the
+ * token endpoint — and every word of that is worth more than a tidy summary that
+ * sends the operator back to guessing.
  */ const theme = integrationsPageTheme;
 export function ConnectionTest({ actions, source, loading = false }) {
     const t = useLabels().errors;
@@ -26,20 +26,20 @@ export function ConnectionTest({ actions, source, loading = false }) {
         setResult(null);
         setTesting(false);
     });
-    /**
-   * A verdict describes the settings it was given, not the connection's name.
-   *
-   * Keyed on the id alone, "Reachable" survived editing the base URL and saving:
-   * the record object is replaced but its id is not, so this never re-ran and a
-   * green badge sat under an address that had never been called. Everything the
-   * test actually depends on is in the key.
-   *
-   * A stored CREDENTIAL is such a setting, and it was the one left out. Clearing
-   * a token left the green verdict standing for a connection that would now be
-   * refused; the mirror image costs more of an afternoon — a red "Not reachable"
-   * from a 401 stayed up after the right password was saved, reading as "the
-   * password did not help". The masked hints are what move when a credential
-   * does, so they are what this watches.
+    /**
+   * A verdict describes the settings it was given, not the connection's name.
+   *
+   * Keyed on the id alone, "Reachable" survived editing the base URL and saving:
+   * the record object is replaced but its id is not, so this never re-ran and a
+   * green badge sat under an address that had never been called. Everything the
+   * test actually depends on is in the key.
+   *
+   * A stored CREDENTIAL is such a setting, and it was the one left out. Clearing
+   * a token left the green verdict standing for a connection that would now be
+   * refused; the mirror image costs more of an afternoon — a red "Not reachable"
+   * from a 401 stayed up after the right password was saved, reading as "the
+   * password did not help". The masked hints are what move when a credential
+   * does, so they are what this watches.
    */ useEffect(()=>{
         clear();
     }, [

package/dist/fe/components/IntegrationsPage/components/ConnectionTransfer.js

@@ -6,24 +6,24 @@ import { useIntegrationsStore } from '../store';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { Notice } from './Primitives';
-/**
- * Bringing a whole integration in from another installation.
- *
- * A connection is the connection, the calls it makes, the parameters those calls
- * take from each other, and the mappings that turn the answers into rows.
- * Rebuilding that by hand in a second environment is hours of work and a fresh
- * chance to get one field wrong in a way nobody notices until an import writes
- * it. So it travels as one file.
- *
- * The file carries NO credentials — deliberately, and it says so on both sides,
- * because a connection that arrives looking configured and cannot authenticate
- * is a confusing half hour otherwise.
- *
- * Export used to sit beside this button and could never be pressed: it needs a
- * connection to be CHOSEN, and choosing one replaces this rail with that
- * connection's own screens. It now lives there, on the thing being exported —
- * see ConnectionExport. Importing is the one that belongs here, because
- * importing is what you do when you have nothing chosen yet.
+/**
+ * Bringing a whole integration in from another installation.
+ *
+ * A connection is the connection, the calls it makes, the parameters those calls
+ * take from each other, and the mappings that turn the answers into rows.
+ * Rebuilding that by hand in a second environment is hours of work and a fresh
+ * chance to get one field wrong in a way nobody notices until an import writes
+ * it. So it travels as one file.
+ *
+ * The file carries NO credentials — deliberately, and it says so on both sides,
+ * because a connection that arrives looking configured and cannot authenticate
+ * is a confusing half hour otherwise.
+ *
+ * Export used to sit beside this button and could never be pressed: it needs a
+ * connection to be CHOSEN, and choosing one replaces this rail with that
+ * connection's own screens. It now lives there, on the thing being exported —
+ * see ConnectionExport. Importing is the one that belongs here, because
+ * importing is what you do when you have nothing chosen yet.
  */ const theme = integrationsPageTheme;
 const messageOf = (error, fallback)=>error instanceof Error ? error.message : fallback;
 export function ConnectionTransfer({ actions, onImported }) {

package/dist/fe/components/IntegrationsPage/components/CredentialFields.js

@@ -9,14 +9,14 @@ import { hintColumnsFor, hintFromResult, patchFor, slotsForSource, storedHint }
 import { errorText } from './formSupport';
 import { Notice } from './Primitives';
 import { CardSkeleton } from './Skeletons';
-/**
- * The secrets, written and never read.
- *
- * Nothing on this screen has ever seen a stored value and nothing here asks for
- * one: the record carries a masked hint, a save returns a new masked hint, and
- * that is the whole conversation. An empty box therefore cannot mean "make it
- * empty" — it means "leave it alone" — which is why clearing is a separate
- * button per field.
+/**
+ * The secrets, written and never read.
+ *
+ * Nothing on this screen has ever seen a stored value and nothing here asks for
+ * one: the record carries a masked hint, a save returns a new masked hint, and
+ * that is the whole conversation. An empty box therefore cannot mean "make it
+ * empty" — it means "leave it alone" — which is why clearing is a separate
+ * button per field.
  */ const theme = integrationsPageTheme;
 export function CredentialFields({ actions, source, loading = false }) {
     const t = useLabels().errors;
@@ -52,17 +52,17 @@ export function CredentialFields({ actions, source, loading = false }) {
     const sourceRecord = source;
     const slots = slotsForSource(sourceRecord);
     const hintOf = (slot)=>slot in hints ? hints[slot] ?? null : storedHint(sourceRecord, slot);
-    /**
-   * The new masks, into local state AND into the record everything else reads.
-   *
-   * Local state alone is not enough, and the way it failed is worth keeping:
-   * `hintOf` falls back to `storedHint(sourceRecord, …)` for any slot local
-   * state has nothing for, and local state is cleared whenever the chosen
-   * connection changes. So a token could be saved, show its green "Stored"
-   * badge, and revert to "Not set" the moment the operator visited another tab
-   * and came back — because the store's copy of the connection still carried
-   * the pre-save hints. The value was in the database throughout; only the
-   * record in memory was old.
+    /**
+   * The new masks, into local state AND into the record everything else reads.
+   *
+   * Local state alone is not enough, and the way it failed is worth keeping:
+   * `hintOf` falls back to `storedHint(sourceRecord, …)` for any slot local
+   * state has nothing for, and local state is cleared whenever the chosen
+   * connection changes. So a token could be saved, show its green "Stored"
+   * badge, and revert to "Not set" the moment the operator visited another tab
+   * and came back — because the store's copy of the connection still carried
+   * the pre-save hints. The value was in the database throughout; only the
+   * record in memory was old.
    */ const remember = (changed)=>{
         if (Object.keys(changed).length === 0) return;
         setHints((current)=>({

package/dist/fe/components/IntegrationsPage/components/CredentialSlotRow.js

@@ -6,14 +6,14 @@ import { integrationsPageTheme } from '../theme';
 import { slotHint, slotLabel } from './credentialSlots';
 import { describedBy } from './formSupport';
 import { Badge, Field } from './Primitives';
-/**
- * One secret: a box to type a new value into, the masked preview of whatever is
- * already stored, and the only way to remove it.
- *
- * Clearing is its own button rather than "save an empty box", because an empty
- * box is what an operator leaves behind when they came to change something else.
- * Making that mean "delete the credential" would break a working connection by
- * accident, roughly once.
+/**
+ * One secret: a box to type a new value into, the masked preview of whatever is
+ * already stored, and the only way to remove it.
+ *
+ * Clearing is its own button rather than "save an empty box", because an empty
+ * box is what an operator leaves behind when they came to change something else.
+ * Making that mean "delete the credential" would break a working connection by
+ * accident, roughly once.
  */ const theme = integrationsPageTheme;
 export function CredentialSlotRow({ slot, source, value, maskedHint, disabled, onChange, onClear }) {
     const t = useLabels().errors;

package/dist/fe/components/IntegrationsPage/components/EndpointForm.js

@@ -10,13 +10,13 @@ import { formatJsonObject, parseJsonObject } from './jsonObjectField';
 import { PaginationFields } from './PaginationFields';
 import { ParamBindingRows } from './ParamBindingRows';
 import { pathParamNames } from './pathParams';
-/**
- * One call against a connection: what to ask for, and where the records sit in
- * the answer.
- *
- * The draft is seeded once. The parent remounts this form when the selection
- * changes, so a half-typed path is never pulled out from under the operator by
- * a list page arriving in the background.
+/**
+ * One call against a connection: what to ask for, and where the records sit in
+ * the answer.
+ *
+ * The draft is seeded once. The parent remounts this form when the selection
+ * changes, so a half-typed path is never pulled out from under the operator by
+ * a list page arriving in the background.
  */ const theme = integrationsPageTheme;
 export function EndpointForm({ sourceId, endpoint, actions, onSaved, onDeleted, onCancel }) {
     const t = useLabels().errors;

package/dist/fe/components/IntegrationsPage/components/EndpointFormFields.js

@@ -6,11 +6,11 @@ import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { describedBy } from './formSupport';
 import { Field } from './Primitives';
-/**
- * The plain fields of an endpoint.
- *
- * Split out of the form because the form's job is saving and deleting, and this
- * one's is asking. The draft type lives here, next to the controls that fill it.
+/**
+ * The plain fields of an endpoint.
+ *
+ * Split out of the form because the form's job is saving and deleting, and this
+ * one's is asking. The draft type lives here, next to the controls that fill it.
  */ const theme = integrationsPageTheme;
 const METHODS = [
     'GET',
@@ -21,13 +21,13 @@ const METHODS = [
 ];
 export function EndpointFormFields({ draft, disabled, errors, onChange }) {
     const labels = useLabels();
-    /**
-   * Unique per instance.
-   *
-   * These ids were literals — `endpoint-tag`, `endpoint-name` — which is fine
-   * for one form on a page and wrong the moment there are two: every `<label
-   * htmlFor>` binds to whichever rendered first, so clicking a label focuses the
-   * OTHER record's field. `useId` makes that structurally impossible.
+    /**
+   * Unique per instance.
+   *
+   * These ids were literals — `endpoint-tag`, `endpoint-name` — which is fine
+   * for one form on a page and wrong the moment there are two: every `<label
+   * htmlFor>` binds to whichever rendered first, so clicking a label focuses the
+   * OTHER record's field. `useId` makes that structurally impossible.
    */ const uid = useId();
     return /*#__PURE__*/ _jsxs(_Fragment, {
         children: [

package/dist/fe/components/IntegrationsPage/components/EndpointList.js

@@ -8,13 +8,13 @@ import { integrationsPageTheme } from '../theme';
 import { Badge, Field, Notice } from './Primitives';
 import { ListSkeleton } from './Skeletons';
 import { useInfiniteList } from './useInfiniteList';
-/**
- * The calls one connection knows how to make.
- *
- * The server owns the list: the search term goes back out on the next request
- * and the next page arrives when the sentinel scrolls into view. Nothing here
- * narrows rows already fetched, so a connection with six endpoints and one with
- * six hundred behave identically.
+/**
+ * The calls one connection knows how to make.
+ *
+ * The server owns the list: the search term goes back out on the next request
+ * and the next page arrives when the sentinel scrolls into view. Nothing here
+ * narrows rows already fetched, so a connection with six endpoints and one with
+ * six hundred behave identically.
  */ const theme = integrationsPageTheme;
 const PAGE_SIZE = 20;
 const SEARCH_DEBOUNCE_MS = 300;

package/dist/fe/components/IntegrationsPage/components/EndpointSample.js

@@ -8,13 +8,13 @@ import { Badge, CodeBlock, Field, Notice, Stat } from './Primitives';
 import { pathParamNames } from './pathParams';
 import { CardSkeleton, StatGridSkeleton } from './Skeletons';
 import { settlementOf } from './settleOwnership';
-/**
- * One real request, shown in full.
- *
- * The interesting case is zero records, because that is when a configuration
- * looks finished and imports nothing. The server already answers it — it returns
- * the top-level keys of the body it actually received — so those keys are given
- * their own block here rather than being folded into a generic "no data".
+/**
+ * One real request, shown in full.
+ *
+ * The interesting case is zero records, because that is when a configuration
+ * looks finished and imports nothing. The server already answers it — it returns
+ * the top-level keys of the body it actually received — so those keys are given
+ * their own block here rather than being folded into a generic "no data".
  */ const theme = integrationsPageTheme;
 export function EndpointSample({ endpoint, actions }) {
     const t = useLabels().errors;
@@ -27,27 +27,27 @@ export function EndpointSample({ endpoint, actions }) {
     const selectedRef = useRef(store.selectedEndpointId);
     selectedRef.current = store.selectedEndpointId;
     const params = pathParamNames(endpoint.path);
-    /**
-   * Only a sample taken of THIS call.
-   *
-   * The card is keyed per selection, so switching calls removes it and a request
-   * still in flight settles with nowhere to report to — except the shared slot,
-   * which it writes to regardless. Before the tag, that answer appeared under
-   * whichever call was open when it landed, and the mapping built next took its
-   * field list from a call that had never returned those fields.
+    /**
+   * Only a sample taken of THIS call.
+   *
+   * The card is keyed per selection, so switching calls removes it and a request
+   * still in flight settles with nowhere to report to — except the shared slot,
+   * which it writes to regardless. Before the tag, that answer appeared under
+   * whichever call was open when it landed, and the mapping built next took its
+   * field list from a call that had never returned those fields.
    */ const sample = store.sampleEndpointId === endpoint.id ? store.sample : null;
     let unfilled = 0;
     for (const name of params){
         if (!(values[name] ?? '').trim()) unfilled += 1;
     }
-    /**
-   * Discard a late answer, but hand the busy flag back on the way out.
-   *
-   * The discard itself is right — the operator has moved on and the field list
-   * must describe the endpoint they are looking at. It used to be a bare
-   * `return`, which skipped the clearing too: `sampling` stayed set with nobody
-   * left to unset it, and the sample card showed a skeleton until the page was
-   * reloaded. See settleOwnership.ts for who owns the flag.
+    /**
+   * Discard a late answer, but hand the busy flag back on the way out.
+   *
+   * The discard itself is right — the operator has moved on and the field list
+   * must describe the endpoint they are looking at. It used to be a bare
+   * `return`, which skipped the clearing too: `sampling` stayed set with nobody
+   * left to unset it, and the sample card showed a skeleton until the page was
+   * reloaded. See settleOwnership.ts for who owns the flag.
    */ const settleElsewhere = (mine, requestedFor)=>{
         const { discard, releaseFlag } = settlementOf({
             mine,
@@ -70,19 +70,19 @@ export function EndpointSample({ endpoint, actions }) {
         actions.sampleEndpoint(requestedFor, params.length > 0 ? values : undefined).then((result)=>{
             if (settleElsewhere(mine, requestedFor)) return;
             store.setSample(result, requestedFor);
-            /**
-         * The ROW learns it has been tried, not just this card.
-         *
-         * The step strip counts "tried" off `endpoints[].sampleResponse`,
-         * because whether a call has ever been run is a fact about the call and
-         * not about whichever screen is open. The server stores it there. This
-         * panel never did, so a connection whose calls had all been sampled
-         * went on announcing "7 call(s), 0 tried" — seen exactly that way on a
-         * customer's live connection, where it read as "nobody has ever tried
-         * these", which was not true.
-         *
-         * Only a sample that actually returned records counts, which is the
-         * same rule the strip applies.
+            /**
+         * The ROW learns it has been tried, not just this card.
+         *
+         * The step strip counts "tried" off `endpoints[].sampleResponse`,
+         * because whether a call has ever been run is a fact about the call and
+         * not about whichever screen is open. The server stores it there. This
+         * panel never did, so a connection whose calls had all been sampled
+         * went on announcing "7 call(s), 0 tried" — seen exactly that way on a
+         * customer's live connection, where it read as "nobody has ever tried
+         * these", which was not true.
+         *
+         * Only a sample that actually returned records counts, which is the
+         * same rule the strip applies.
          */ if (result.ok && result.recordCount > 0) {
                 const row = store.endpoints.find((candidate)=>candidate.id === requestedFor);
                 if (row) {

package/dist/fe/components/IntegrationsPage/components/EndpointsTab.js

@@ -7,12 +7,12 @@ import { integrationsPageTheme } from '../theme';
 import { EndpointForm } from './EndpointForm';
 import { EndpointList } from './EndpointList';
 import { EndpointSample } from './EndpointSample';
-/**
- * The endpoints section: the list on one side, the selected call on the other.
- *
- * The record the list hands over is the record the form edits, so opening an
- * endpoint costs no extra request. The form is keyed by that record's id, which
- * is what makes switching selection a fresh form rather than a merged one.
+/**
+ * The endpoints section: the list on one side, the selected call on the other.
+ *
+ * The record the list hands over is the record the form edits, so opening an
+ * endpoint costs no extra request. The form is keyed by that record's id, which
+ * is what makes switching selection a fresh form rather than a merged one.
  */ const theme = integrationsPageTheme;
 export function EndpointsTab({ actions }) {
     const labels = useLabels();
@@ -20,15 +20,15 @@ export function EndpointsTab({ actions }) {
     const sourceId = store.selectedSourceId;
     const [creating, setCreating] = useState(false);
     const [reloadToken, setReloadToken] = useState(0);
-    /**
-   * The selection is the STORE's, and only the store's.
-   *
-   * It used to be kept here as well, and the two were reconciled by comparing
-   * them on every render. Clicking a second call then left the first form on
-   * screen and added the new one under it — two live editors of two different
-   * records, both writing to the same hard-coded field ids, growing by one card
-   * per click. One source of truth, and one keyed container below, is what makes
-   * that impossible rather than unlikely.
+    /**
+   * The selection is the STORE's, and only the store's.
+   *
+   * It used to be kept here as well, and the two were reconciled by comparing
+   * them on every render. Clicking a second call then left the first form on
+   * screen and added the new one under it — two live editors of two different
+   * records, both writing to the same hard-coded field ids, growing by one card
+   * per click. One source of truth, and one keyed container below, is what makes
+   * that impossible rather than unlikely.
    */ const selectedId = store.selectedEndpointId;
     const editing = selectedId ? store.endpoints.find((e)=>e.id === selectedId) ?? null : null;
     // Another connection is another set of calls. A form left open across the
@@ -57,20 +57,20 @@ export function EndpointsTab({ actions }) {
         // collapse to "pick one" — with the form still half-filled a moment ago.
         store.upsertEndpoint(saved);
         store.selectEndpoint(saved.id);
-        /**
-     * The sample described the call as it was BEFORE this save.
-     *
-     * Re-selecting was supposed to drop it, and does not: `selectEndpoint`
-     * returns early when the id has not changed, which on a save it never has —
-     * it is the guard that stops re-choosing the open call from throwing away a
-     * sample somebody just paid a real request for. Correct there, and the
-     * reason nothing was cleared here.
-     *
-     * So the sample sat under an edited call: change `responseRootPath` from
-     * empty to `data`, save, and the card still reports "Status 200, 0 records"
-     * with the old body keys — and the mapping's field list is built from those
-     * keys. The answer on screen belonged to a request that is no longer the one
-     * configured.
+        /**
+     * The sample described the call as it was BEFORE this save.
+     *
+     * Re-selecting was supposed to drop it, and does not: `selectEndpoint`
+     * returns early when the id has not changed, which on a save it never has —
+     * it is the guard that stops re-choosing the open call from throwing away a
+     * sample somebody just paid a real request for. Correct there, and the
+     * reason nothing was cleared here.
+     *
+     * So the sample sat under an edited call: change `responseRootPath` from
+     * empty to `data`, save, and the card still reports "Status 200, 0 records"
+     * with the old body keys — and the mapping's field list is built from those
+     * keys. The answer on screen belonged to a request that is no longer the one
+     * configured.
      */ store.setSample(null, null);
         setReloadToken((token)=>token + 1);
     };

package/dist/fe/components/IntegrationsPage/components/FieldMappingRow.js

@@ -4,13 +4,13 @@ import { cn } from '../../../utils/cn';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { FIELD_MAPPING_GRID, PARENT_PREFIX, TRANSFORM_LABEL, TRANSFORMS, toTransform } from './fieldMappingOptions';
-/**
- * One line of a field mapping: where the value comes from, what it becomes, and
- * which column it lands in.
- *
- * The row owns no state. It reports a patch and the editor above decides what
- * the list of rows now is, so ordering and validation live in one place instead
- * of being spread across however many rows are on screen.
+/**
+ * One line of a field mapping: where the value comes from, what it becomes, and
+ * which column it lands in.
+ *
+ * The row owns no state. It reports a patch and the editor above decides what
+ * the list of rows now is, so ordering and validation live in one place instead
+ * of being spread across however many rows are on screen.
  */ const theme = integrationsPageTheme;
 /** Label above each control on a phone; the header row replaces it from lg up. */ function Cell({ id, label, children }) {
     return /*#__PURE__*/ _jsxs("div", {