nucleus-core-ts 0.10.147 → 0.10.151

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

@@ -7,12 +7,12 @@ import { integrationsPageTheme } from '../theme';
 import { FieldMappingRow } from './FieldMappingRow';
 import { EMPTY_FIELD_MAPPING, FIELD_MAPPING_COLUMNS, FIELD_MAPPING_GRID, PARENT_PREFIX } from './fieldMappingOptions';
 import { Notice, Section } from './Primitives';
-/**
- * The rows that say which incoming value becomes which column.
- *
- * The order is kept because the writer applies the rows in it: two rows aimed at
- * the same column mean the later one wins, and that is only predictable if the
- * operator can see the order and change it.
+/**
+ * The rows that say which incoming value becomes which column.
+ *
+ * The order is kept because the writer applies the rows in it: two rows aimed at
+ * the same column mean the later one wins, and that is only predictable if the
+ * operator can see the order and change it.
  */ const theme = integrationsPageTheme;
 export function FieldMappingRows({ rows, sourceFields, targetFields, disabled, onChange }) {
     const labels = useLabels();

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

@@ -16,13 +16,13 @@ import { EndpointsTab } from './EndpointsTab';
 import { MappingsTab } from './MappingsTab';
 import { Notice } from './Primitives';
 import { RunsTab } from './RunsTab';
-/**
- * The shell.
- *
- * It owns three things and nothing else: the selection rail, which section of the
- * selected connection is on screen, and the one place an error is reported. Every
- * call it needs arrives as an injected action, and each section fetches its own
- * page from the server rather than being handed a list to slice.
+/**
+ * The shell.
+ *
+ * It owns three things and nothing else: the selection rail, which section of the
+ * selected connection is on screen, and the one place an error is reported. Every
+ * call it needs arrives as an injected action, and each section fetches its own
+ * page from the server rather than being handed a list to slice.
  */ gsap.registerPlugin(useGSAP);
 const theme = integrationsPageTheme;
 export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect an external service, describe the data you want and import it on your terms.', className, actions, labels: labelsOverride, focusTargetEntity, focusStep, onSubscribeProgress }) {
@@ -33,15 +33,15 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
     const labels = resolveIntegrationsLabels(labelsOverride);
     const containerRef = useRef(null);
     const contentRef = useRef(null);
-    /**
-   * Bumped after a connection is written, to pull the rail again.
-   *
-   * `ConnectionList` and `ConnectionSettingsTab` were both built to be told
-   * about a save and neither was ever told: the shell mounted them with only
-   * `actions`. Creating the first connection therefore selected a record the
-   * rail had never fetched, so the rail kept saying "0 connections" while the
-   * detail treated the missing record as still loading and sat on skeletons
-   * until the page was reloaded by hand. The write itself had succeeded.
+    /**
+   * Bumped after a connection is written, to pull the rail again.
+   *
+   * `ConnectionList` and `ConnectionSettingsTab` were both built to be told
+   * about a save and neither was ever told: the shell mounted them with only
+   * `actions`. Creating the first connection therefore selected a record the
+   * rail had never fetched, so the rail kept saying "0 connections" while the
+   * detail treated the missing record as still loading and sat on skeletons
+   * until the page was reloaded by hand. The write itself had succeeded.
    */ const [sourcesReloadToken, setSourcesReloadToken] = useState(0);
     const handleSourceSaved = (saved)=>{
         // Into the store FIRST. Bumping the token only tells the rail to refetch,
@@ -51,26 +51,26 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
         store.upsertSource(saved);
         setSourcesReloadToken((token)=>token + 1);
     };
-    /**
-   * A connection was deleted.
-   *
-   * Nothing about it is worth keeping on screen — the tabs below would be
-   * showing the calls and mappings of a record that no longer exists — so the
-   * selection is dropped, the rail comes back, and the list is asked again.
-   * `forgetFocusOnLeave` matters here too: arriving from a table set a focus
-   * that would otherwise re-select the next connection instantly.
+    /**
+   * A connection was deleted.
+   *
+   * Nothing about it is worth keeping on screen — the tabs below would be
+   * showing the calls and mappings of a record that no longer exists — so the
+   * selection is dropped, the rail comes back, and the list is asked again.
+   * `forgetFocusOnLeave` matters here too: arriving from a table set a focus
+   * that would otherwise re-select the next connection instantly.
    */ const handleSourceDeleted = ()=>{
         forgetFocusOnLeave();
         setSourcesReloadToken((token)=>token + 1);
     };
-    /**
-   * How far this connection has got, asked for directly.
-   *
-   * The step strip promises to say where you are, so it cannot depend on having
-   * VISITED the step that counts — on a fresh load every total was zero and the
-   * strip told an operator with five calls, three mappings and two finished
-   * imports to "finish the previous step first". Three counting requests, one
-   * row each, are the price of a strip that is telling the truth.
+    /**
+   * How far this connection has got, asked for directly.
+   *
+   * The step strip promises to say where you are, so it cannot depend on having
+   * VISITED the step that counts — on a fresh load every total was zero and the
+   * strip told an operator with five calls, three mappings and two finished
+   * imports to "finish the previous step first". Three counting requests, one
+   * row each, are the price of a strip that is telling the truth.
    */ const loadProgress = useEffectEvent((sourceId)=>{
         const one = {
             page: 1,
@@ -100,13 +100,13 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
         store.selectedSourceId,
         sourcesReloadToken
     ]);
-    /**
-   * Somebody arrived from the table they want filled.
-   *
-   * They have already said which table; being shown a connection chooser and
-   * four mappings is asking the same question again. So the entity is handed to
-   * the mappings step, and — when there is only one connection to be meant — it
-   * is chosen for them. With several, the choice is real and stays theirs.
+    /**
+   * Somebody arrived from the table they want filled.
+   *
+   * They have already said which table; being shown a connection chooser and
+   * four mappings is asking the same question again. So the entity is handed to
+   * the mappings step, and — when there is only one connection to be meant — it
+   * is chosen for them. With several, the choice is real and stays theirs.
    */ const takeFocus = useEffectEvent(()=>{
         if (!focusTargetEntity) return;
         store.setFocusTargetEntity(focusTargetEntity, focusStep ?? 'mapping');
@@ -117,13 +117,13 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
         focusTargetEntity,
         focusStep
     ]);
-    /**
-   * Chosen for them ONCE, and never again.
-   *
-   * This used to re-choose whenever nothing was selected — so pressing "Change"
-   * cleared the connection and the same effect immediately put it back. There
-   * was no way to reach the list again short of reloading the page, and the
-   * button looked broken rather than overruled.
+    /**
+   * Chosen for them ONCE, and never again.
+   *
+   * This used to re-choose whenever nothing was selected — so pressing "Change"
+   * cleared the connection and the same effect immediately put it back. There
+   * was no way to reach the list again short of reloading the page, and the
+   * button looked broken rather than overruled.
    */ const autoSelected = useRef(false);
     const followFocus = useEffectEvent(()=>{
         if (!store.focusTargetEntity) return;
@@ -136,13 +136,13 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
         }
         if (store.tab !== 'mappings') store.setTab('mappings');
     });
-    /**
-   * Leaving a connection spends the arrival.
-   *
-   * Somebody who pressed "Change" is choosing a different connection; the table
-   * they arrived asking about is no longer what they are doing, and carrying it
-   * forward would jump them into a mapping of a connection they had not picked
-   * yet.
+    /**
+   * Leaving a connection spends the arrival.
+   *
+   * Somebody who pressed "Change" is choosing a different connection; the table
+   * they arrived asking about is no longer what they are doing, and carrying it
+   * forward would jump them into a mapping of a connection they had not picked
+   * yet.
    */ const forgetFocusOnLeave = useEffectEvent(()=>{
         if (autoSelected.current && !store.selectedSourceId && store.focusTargetEntity) {
             store.setFocusTargetEntity(null);
@@ -195,13 +195,13 @@ export function IntegrationsPage({ title = 'Integrations', subtitle = 'Connect a
     };
     const tab = store.tab;
     const hasConnection = store.selectedSourceId !== null;
-    /**
-   * What each step can say about itself.
-   *
-   * Evidence rather than a bare count: "3 calls, all tried" answers a question a
-   * number does not — whether the thing was only declared or actually run. A
-   * step whose prerequisite is missing is marked locked rather than hidden,
-   * because a step you cannot see is one you cannot understand the order of.
+    /**
+   * What each step can say about itself.
+   *
+   * Evidence rather than a bare count: "3 calls, all tried" answers a question a
+   * number does not — whether the thing was only declared or actually run. A
+   * step whose prerequisite is missing is marked locked rather than hidden,
+   * because a step you cannot see is one you cannot understand the order of.
    */ const selectedSource = store.sources.find((s)=>s.id === store.selectedSourceId);
     const sampled = store.endpoints.filter((e)=>(e.sampleResponse?.records?.length ?? 0) > 0).length;
     const steps = {

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

@@ -4,21 +4,21 @@ import { useId } from 'react';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { Field, Notice, Section } from './Primitives';
-/**
- * A login for every person this import brings in.
- *
- * A directory carries people, not accounts. Importing eight hundred employees
- * and then creating eight hundred logins by hand — matching them up by e-mail,
- * one at a time — is the job nobody gets to, so the import that was supposed to
- * save the afternoon leaves a table of people who cannot sign in.
- *
- * Turned on here, it happens in the SAME import and the same transaction: the
- * person and their login both exist, or neither does. A record whose address is
- * already an account is linked to it rather than given a second one, so running
- * the import again is safe.
- *
- * The password is not on this screen. It belongs to the run — typed once, used
- * for every account that run creates, stored nowhere.
+/**
+ * A login for every person this import brings in.
+ *
+ * A directory carries people, not accounts. Importing eight hundred employees
+ * and then creating eight hundred logins by hand — matching them up by e-mail,
+ * one at a time — is the job nobody gets to, so the import that was supposed to
+ * save the afternoon leaves a table of people who cannot sign in.
+ *
+ * Turned on here, it happens in the SAME import and the same transaction: the
+ * person and their login both exist, or neither does. A record whose address is
+ * already an account is linked to it rather than given a second one, so running
+ * the import again is safe.
+ *
+ * The password is not on this screen. It belongs to the run — typed once, used
+ * for every account that run creates, stored nowhere.
  */ const theme = integrationsPageTheme;
 /** Columns that plausibly hold a password, so the guess is a good one. */ const PASSWORD_LIKE = /password|passwd|sifre|şifre|parola/i;
 /** Columns that plausibly point at the account row. */ const LINK_LIKE = /^(user_?id|account_?id|login_?id)$/i;

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

@@ -13,15 +13,15 @@ import { mappingDraftIssues } from './mappingDraft';
 import { Field, Section } from './Primitives';
 import { ReferenceCheckRows } from './ReferenceCheckRows';
 import { CardSkeleton } from './Skeletons';
-/**
- * Everything about one mapping, on one screen.
- *
- * The draft is local until Save: an import is not a text field where a stray
- * keystroke is harmless, and half a mapping saved between two thoughts is a
- * mapping that could be RUN in that state.
- *
- * Mount it with a `key` of the mapping id so switching rows starts a fresh
- * draft instead of pouring one mapping's edits into another.
+/**
+ * Everything about one mapping, on one screen.
+ *
+ * The draft is local until Save: an import is not a text field where a stray
+ * keystroke is harmless, and half a mapping saved between two thoughts is a
+ * mapping that could be RUN in that state.
+ *
+ * Mount it with a `key` of the mapping id so switching rows starts a fresh
+ * draft instead of pouring one mapping's edits into another.
  */ const theme = integrationsPageTheme;
 export function MappingEditor({ mapping, targets, targetsLoading, endpoints, freshSample, saving, deleting, onSave, onDelete, onCancel, onRunImport }) {
     const labels = useLabels();

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

@@ -10,12 +10,12 @@ import { Badge, Field, Notice } from './Primitives';
 import { formatMoment } from './runFormat';
 import { ListSkeleton } from './Skeletons';
 import { useInfiniteList } from './useInfiniteList';
-/**
- * The mappings of the selected connection, one page at a time.
- *
- * Searching and paging are the server's job; this list only shows what came
- * back. The write mode is on the row rather than only inside the editor because
- * `replace` is the one setting worth spotting before opening anything.
+/**
+ * The mappings of the selected connection, one page at a time.
+ *
+ * Searching and paging are the server's job; this list only shows what came
+ * back. The write mode is on the row rather than only inside the editor because
+ * `replace` is the one setting worth spotting before opening anything.
  */ const theme = integrationsPageTheme;
 const PAGE_SIZE = 20;
 const SEARCH_DEBOUNCE_MS = 300;
@@ -24,14 +24,14 @@ const WRITE_MODE_TONE = {
     append: 'neutral',
     replace: 'danger'
 };
-/**
- * When this mapping last ran, in a form that cannot tear on hydration.
- *
- * It used to be `toLocaleString()`, which reads the SERVER's locale and zone on
- * the server and the BROWSER's on the client — two different strings for the
- * same row, and React replacing one with the other after mount. It also meant a
- * Turkish installation was shown 8/2/2026, which in Turkey reads as the 8th of
- * February. `formatMoment` is UTC, fixed-width and labelled as such.
+/**
+ * When this mapping last ran, in a form that cannot tear on hydration.
+ *
+ * It used to be `toLocaleString()`, which reads the SERVER's locale and zone on
+ * the server and the BROWSER's on the client — two different strings for the
+ * same row, and React replacing one with the other after mount. It also meant a
+ * Turkish installation was shown 8/2/2026, which in Turkey reads as the 8th of
+ * February. `formatMoment` is UTC, fixed-width and labelled as such.
  */ function describeLastRun(value, labels) {
     if (!value) return labels.neverRun;
     const when = new Date(value);
@@ -40,15 +40,15 @@ const WRITE_MODE_TONE = {
 export function MappingList({ actions, sourceId, selectedId, reloadToken, onSelect, onRun }) {
     const t = useLabels().errors;
     const labels = useLabels();
-    /*
-   * Read AFTER mount, never during render.
-   *
-   * "How long ago" is a function of the clock, and the clock on the server that
-   * renders this HTML is not the one in the browser that hydrates it. Computing
-   * it in render is what put two different strings in the same row and had React
-   * swap one for the other on mount — the same fault the last-run timestamp was
-   * already fixed for. Null until mounted means the first paint has no age
-   * badges at all, which both renders agree on.
+    /*
+   * Read AFTER mount, never during render.
+   *
+   * "How long ago" is a function of the clock, and the clock on the server that
+   * renders this HTML is not the one in the browser that hydrates it. Computing
+   * it in render is what put two different strings in the same row and had React
+   * swap one for the other on mount — the same fault the last-run timestamp was
+   * already fixed for. Null until mounted means the first paint has no age
+   * badges at all, which both renders agree on.
    */ const [now, setNow] = useState(null);
     useEffect(()=>{
         setNow(Date.now());

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

@@ -4,18 +4,18 @@ import { useId } from 'react';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { Field } from './Primitives';
-/**
- * Where a shared opening password lands, if this import creates accounts.
- *
- * The mapping says WHICH COLUMN; the run says what the password is. Nothing
- * about the password is stored here — an import that creates eight hundred
- * accounts must not also leave the key to them sitting in a config table.
- *
- * Why a shared password at all: a source system carries people, not
- * credentials. Eight hundred generated passwords is eight hundred things
- * somebody has to deliver by hand. One opening password, typed at run time and
- * changed by each person afterwards, is the only version of this that a person
- * can actually carry out.
+/**
+ * Where a shared opening password lands, if this import creates accounts.
+ *
+ * The mapping says WHICH COLUMN; the run says what the password is. Nothing
+ * about the password is stored here — an import that creates eight hundred
+ * accounts must not also leave the key to them sitting in a config table.
+ *
+ * Why a shared password at all: a source system carries people, not
+ * credentials. Eight hundred generated passwords is eight hundred things
+ * somebody has to deliver by hand. One opening password, typed at run time and
+ * changed by each person afterwards, is the only version of this that a person
+ * can actually carry out.
  */ const theme = integrationsPageTheme;
 /** Column names that plausibly hold a password, offered first. */ const LIKELY = /password|passwd|sifre|şifre|parola/i;
 export function MappingPasswordField({ value, targetFields, disabled, onChange }) {

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

@@ -6,24 +6,24 @@ import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { describeNextRuns } from './nextRuns';
 import { Field, Notice, Section } from './Primitives';
-/**
- * Running this import without anybody clicking anything.
- *
- * The mapping has carried a cron, a timezone and an enabled flag since it was
- * first designed, and nothing read them — an operator could fill one in, save
- * it, see it on the screen, and it would never run. This is the screen for the
- * half that now does.
- *
- * The expression is checked as it is typed and read back in plain words. Cron is
- * a language people write once a year, and "0 2 * * *" and "2 0 * * *" look
- * alike until one of them has been importing at two minutes past midnight for a
- * month.
+/**
+ * Running this import without anybody clicking anything.
+ *
+ * The mapping has carried a cron, a timezone and an enabled flag since it was
+ * first designed, and nothing read them — an operator could fill one in, save
+ * it, see it on the screen, and it would never run. This is the screen for the
+ * half that now does.
+ *
+ * The expression is checked as it is typed and read back in plain words. Cron is
+ * a language people write once a year, and "0 2 * * *" and "2 0 * * *" look
+ * alike until one of them has been importing at two minutes past midnight for a
+ * month.
  */ const theme = integrationsPageTheme;
-/**
- * Offered because they are what people actually mean, spelled correctly.
- *
- * Built per render rather than held as a module constant: the cron strings are
- * fixed, the words beside them are whatever language the portal runs in.
+/**
+ * Offered because they are what people actually mean, spelled correctly.
+ *
+ * Built per render rather than held as a module constant: the cron strings are
+ * fixed, the words beside them are whatever language the portal runs in.
  */ const presetsOf = (t)=>[
         {
             label: t.nightly,
@@ -154,12 +154,12 @@ export function MappingScheduleFields({ enabled, cron, timezone, needsPassword,
 }
 /** The next few firings, listed. Its own component so it can hold the clock. */ function NextRunsList({ cron, timezone }) {
     const labels = useLabels();
-    /*
-   * The clock is read after mount, never during render.
-   *
-   * "From now" on the server and "from now" in the browser are different
-   * instants, so rendering this straight away would produce two different
-   * lists for one page and tear on hydration.
+    /*
+   * The clock is read after mount, never during render.
+   *
+   * "From now" on the server and "from now" in the browser are different
+   * instants, so rendering this straight away would produce two different
+   * lists for one page and tear on hydration.
    */ const [from, setFrom] = useState(null);
     useEffect(()=>setFrom(new Date()), [
         cron,

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

@@ -3,17 +3,17 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { Field, Notice } from './Primitives';
-/**
- * The choices that decide what an import DOES to the table.
- *
- * The first two are the destructive pair: one decides how the fetched records
- * land, the other decides what happens to the rows the source stopped sending.
- * Every other field on a mapping only moves values around.
- *
- * The rest appear once that second choice can remove something, and they are
- * the two things that separate a synchronisation from a data-loss incident: a
- * mark saying which rows this mapping owns, and a ceiling on how much of the
- * table one run may take away.
+/**
+ * The choices that decide what an import DOES to the table.
+ *
+ * The first two are the destructive pair: one decides how the fetched records
+ * land, the other decides what happens to the rows the source stopped sending.
+ * Every other field on a mapping only moves values around.
+ *
+ * The rest appear once that second choice can remove something, and they are
+ * the two things that separate a synchronisation from a data-loss incident: a
+ * mark saying which rows this mapping owns, and a ceiling on how much of the
+ * table one run may take away.
  */ const theme = integrationsPageTheme;
 const WRITE_MODES = [
     'upsert',
@@ -213,27 +213,27 @@ export function MappingWriteModeFields({ idPrefix, writeMode, missingRecordPolic
         ]
     });
 }
-/**
- * Stored as a share, typed as a percentage.
- *
- * The engine compares `removing / existing` against this number, so the column
- * holds 0.2 — but nobody sets a safety limit by thinking in fractions, and 0.2
- * typed into a box labelled "percent" would mean a fifth of a percent. The
- * conversion lives here so the two readings can never drift apart.
+/**
+ * Stored as a share, typed as a percentage.
+ *
+ * The engine compares `removing / existing` against this number, so the column
+ * holds 0.2 — but nobody sets a safety limit by thinking in fractions, and 0.2
+ * typed into a box labelled "percent" would mean a fifth of a percent. The
+ * conversion lives here so the two readings can never drift apart.
  */ export function shareToPercent(share) {
-    /*
-   * `unknown`, not `number`, because that is what actually arrives.
-   *
-   * A `numeric` column comes back from the API as TEXT — Postgres returns
-   * arbitrary-precision numbers as strings — so this was handed "0.2" and
-   * `Number.isFinite("0.2")` is false. It answered '' and the box rendered
-   * empty, which reads as "no ceiling set" for a mapping that had one.
-   *
-   * That is worse than a cosmetic bug: saving the form from that state sends
-   * the empty box back through `percentToShare`, which means 0, and the guard
-   * the operator thought was in place is quietly removed by a save they made
-   * for some other reason. On the customer's org-chart import the ceiling was
-   * stored as 0.2 the whole time and reported as absent for two days.
+    /*
+   * `unknown`, not `number`, because that is what actually arrives.
+   *
+   * A `numeric` column comes back from the API as TEXT — Postgres returns
+   * arbitrary-precision numbers as strings — so this was handed "0.2" and
+   * `Number.isFinite("0.2")` is false. It answered '' and the box rendered
+   * empty, which reads as "no ceiling set" for a mapping that had one.
+   *
+   * That is worse than a cosmetic bug: saving the form from that state sends
+   * the empty box back through `percentToShare`, which means 0, and the guard
+   * the operator thought was in place is quietly removed by a save they made
+   * for some other reason. On the customer's org-chart import the ceiling was
+   * stored as 0.2 the whole time and reported as absent for two days.
    */ const value = typeof share === 'string' ? Number(share) : share;
     if (typeof value !== 'number' || !Number.isFinite(value) || value <= 0) return '';
     return String(Math.round(value * 1000) / 10);

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

@@ -8,13 +8,13 @@ import { MappingEditor } from './MappingEditor';
 import { MappingList } from './MappingList';
 import { blankMappingDraft, toMappingDraft } from './mappingDraft';
 import { Notice } from './Primitives';
-/**
- * The mappings of the selected connection: the list on one side, the mapping
- * being edited on the other.
- *
- * Only this component talks to the injected actions — the list renders what it
- * is given and the editor edits a draft, so neither can save half a change on
- * its own or refetch behind the other's back.
+/**
+ * The mappings of the selected connection: the list on one side, the mapping
+ * being edited on the other.
+ *
+ * Only this component talks to the injected actions — the list renders what it
+ * is given and the editor edits a draft, so neither can save half a change on
+ * its own or refetch behind the other's back.
  */ const theme = integrationsPageTheme;
 function messageOf(error, fallback) {
     return error instanceof Error ? error.message : fallback;
@@ -46,25 +46,25 @@ export function MappingsTab({ actions }) {
     useEffect(()=>{
         loadTargets();
     }, []);
-    /**
-   * The connection's endpoints, when nothing has fetched them yet.
-   *
-   * `store.endpoints` is filled by the Endpoints tab, so opening a connection
-   * and going straight to Mappings met "No endpoints on this connection yet"
-   * and a disabled New mapping — about a connection with three of them. The
-   * only way through was to visit the other tab first, which nothing said.
-   *
-   * Its OWN list, not the one the Endpoints step is showing.
-   *
-   * `store.endpoints` holds whatever that step last fetched — including what a
-   * SEARCH narrowed it to. A mapping reads one call, and the picker offering
-   * them was reading that same array: typing "employee" into the endpoints
-   * search left the mapping editor able to choose only the calls matching it,
-   * and `loadEndpointsIfMissing` then declined to fetch because the array was
-   * not empty. Nothing said the list was a filtered one.
-   *
-   * Read to exhaustion rather than one page: a picker that silently stops at
-   * fifty is the same defect one step down.
+    /**
+   * The connection's endpoints, when nothing has fetched them yet.
+   *
+   * `store.endpoints` is filled by the Endpoints tab, so opening a connection
+   * and going straight to Mappings met "No endpoints on this connection yet"
+   * and a disabled New mapping — about a connection with three of them. The
+   * only way through was to visit the other tab first, which nothing said.
+   *
+   * Its OWN list, not the one the Endpoints step is showing.
+   *
+   * `store.endpoints` holds whatever that step last fetched — including what a
+   * SEARCH narrowed it to. A mapping reads one call, and the picker offering
+   * them was reading that same array: typing "employee" into the endpoints
+   * search left the mapping editor able to choose only the calls matching it,
+   * and `loadEndpointsIfMissing` then declined to fetch because the array was
+   * not empty. Nothing said the list was a filtered one.
+   *
+   * Read to exhaustion rather than one page: a picker that silently stops at
+   * fifty is the same defect one step down.
    */ const loadPickableEndpoints = useEffectEvent(()=>{
         if (sourceId === '') {
             setPickableEndpoints([]);
@@ -106,16 +106,16 @@ export function MappingsTab({ actions }) {
         setSelected(mapping);
         store.selectMapping(mapping.id);
     };
-    /**
-   * Opens the mapping for the table somebody arrived asking about.
-   *
-   * Asked of the SERVER by target entity rather than searched in the page this
-   * tab happens to be holding: the list is paged, so the mapping being looked
-   * for is frequently not in it. If there is none yet, a new one is started
-   * already aimed at that table — which is the other half of the answer.
-   *
-   * Consumed once. Left set, it would drag the selection back every time the
-   * operator clicked a different mapping.
+    /**
+   * Opens the mapping for the table somebody arrived asking about.
+   *
+   * Asked of the SERVER by target entity rather than searched in the page this
+   * tab happens to be holding: the list is paged, so the mapping being looked
+   * for is frequently not in it. If there is none yet, a new one is started
+   * already aimed at that table — which is the other half of the answer.
+   *
+   * Consumed once. Left set, it would drag the selection back every time the
+   * operator clicked a different mapping.
    */ const followFocus = useEffectEvent(()=>{
         const entity = store.focusTargetEntity;
         if (!entity || sourceId === '') return;
@@ -174,20 +174,20 @@ export function MappingsTab({ actions }) {
             // second earlier landed on "choose a mapping".
             store.upsertMapping(saved);
             store.selectMapping(saved.id);
-            /**
-         * The plan described the mapping as it WAS.
-         *
-         * A preview is an answer about one particular mapping, and editing that
-         * mapping makes the answer wrong — silently, because the import step
-         * prints its own heading from the saved record and the counts from the
-         * plan. Switching the write mode to `replace` after previewing gave a
-         * screen that said `replace` above numbers computed for `upsert`, and
-         * the destructive confirmation then combined the new mode with the old
-         * count: "1240 rows will be deleted", from a plan that never considered
-         * deleting anything.
-         *
-         * `selectMapping` cannot do this — it returns early when the id has not
-         * changed, and on a save it never does.
+            /**
+         * The plan described the mapping as it WAS.
+         *
+         * A preview is an answer about one particular mapping, and editing that
+         * mapping makes the answer wrong — silently, because the import step
+         * prints its own heading from the saved record and the counts from the
+         * plan. Switching the write mode to `replace` after previewing gave a
+         * screen that said `replace` above numbers computed for `upsert`, and
+         * the destructive confirmation then combined the new mode with the old
+         * count: "1240 rows will be deleted", from a plan that never considered
+         * deleting anything.
+         *
+         * `selectMapping` cannot do this — it returns early when the id has not
+         * changed, and on a save it never does.
          */ store.setPlan(null, null);
             setReloadToken((token)=>token + 1);
             then?.(saved);
@@ -196,12 +196,12 @@ export function MappingsTab({ actions }) {
             store.setError(messageOf(error, labels.errors.requestFailed));
         });
     };
-    /**
-   * Take this mapping to the import step.
-   *
-   * Saved first when it differs from what is stored: the operator is looking at
-   * the version they mean to run, and importing the older one instead — with no
-   * sign that it happened — is the worst kind of quiet.
+    /**
+   * Take this mapping to the import step.
+   *
+   * Saved first when it differs from what is stored: the operator is looking at
+   * the version they mean to run, and importing the older one instead — with no
+   * sign that it happened — is the worst kind of quiet.
    */ const runImport = (draft)=>{
         const stored = selected ? toMappingDraft(selected) : null;
         const dirty = !stored || JSON.stringify(stored) !== JSON.stringify(draft);