nucleus-core-ts 0.10.147 → 0.10.151

package/LICENSE

@@ -1,48 +1,48 @@
-Nucleus Core - Proprietary Software License
-
-Copyright (c) 2024-2026 Hidayet Can Özcan <hidayetcan@gmail.com>
-All Rights Reserved.
-
-TERMS AND CONDITIONS
-
-1. GRANT OF LICENSE
-   This software and associated documentation files (the "Software") are 
-   licensed, not sold. Subject to the terms of this license, you are granted 
-   a non-exclusive, non-transferable, limited license to use the Software 
-   solely for your internal business purposes.
-
-2. RESTRICTIONS
-   You may NOT:
-   - Copy, modify, or distribute the Software
-   - Reverse engineer, decompile, or disassemble the Software
-   - Sublicense, rent, lease, or lend the Software
-   - Use the Software to create derivative works
-   - Remove or alter any proprietary notices or labels on the Software
-   - Share, publish, or make the Software available to third parties
-
-3. INTELLECTUAL PROPERTY
-   The Software is protected by copyright and other intellectual property 
-   laws. The author retains all right, title, and interest in and to the 
-   Software, including all intellectual property rights.
-
-4. NO WARRANTY
-   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
-   OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-
-5. LIMITATION OF LIABILITY
-   IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
-   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
-   FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
-   DEALINGS IN THE SOFTWARE.
-
-6. TERMINATION
-   This license is effective until terminated. It will terminate automatically 
-   if you fail to comply with any term of this license. Upon termination, 
-   you must destroy all copies of the Software.
-
-7. GOVERNING LAW
-   This license shall be governed by and construed in accordance with the 
-   laws of Turkey.
-
-For licensing inquiries, please contact: hidayetcan@gmail.com
+Nucleus Core - Proprietary Software License
+
+Copyright (c) 2024-2026 Hidayet Can Özcan <hidayetcan@gmail.com>
+All Rights Reserved.
+
+TERMS AND CONDITIONS
+
+1. GRANT OF LICENSE
+   This software and associated documentation files (the "Software") are 
+   licensed, not sold. Subject to the terms of this license, you are granted 
+   a non-exclusive, non-transferable, limited license to use the Software 
+   solely for your internal business purposes.
+
+2. RESTRICTIONS
+   You may NOT:
+   - Copy, modify, or distribute the Software
+   - Reverse engineer, decompile, or disassemble the Software
+   - Sublicense, rent, lease, or lend the Software
+   - Use the Software to create derivative works
+   - Remove or alter any proprietary notices or labels on the Software
+   - Share, publish, or make the Software available to third parties
+
+3. INTELLECTUAL PROPERTY
+   The Software is protected by copyright and other intellectual property 
+   laws. The author retains all right, title, and interest in and to the 
+   Software, including all intellectual property rights.
+
+4. NO WARRANTY
+   THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
+   OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
+   FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+
+5. LIMITATION OF LIABILITY
+   IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
+   LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING 
+   FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER 
+   DEALINGS IN THE SOFTWARE.
+
+6. TERMINATION
+   This license is effective until terminated. It will terminate automatically 
+   if you fail to comply with any term of this license. Upon termination, 
+   you must destroy all copies of the Software.
+
+7. GOVERNING LAW
+   This license shall be governed by and construed in accordance with the 
+   laws of Turkey.
+
+For licensing inquiries, please contact: hidayetcan@gmail.com

package/dist/.build-ok

@@ -1 +1 @@
-0.10.147
+0.10.151

package/dist/fe/components/AuthorizationPage/labels.js

@@ -1,16 +1,16 @@
-/**
- * Every word the authorization screens say, so a portal can say them in its
- * own language.
- *
- * This is the screen an administrator opens to decide who may do what, and
- * until now it said "Roles", "Show assigned only", "No claims match your
- * filters" and "Are you sure you want to delete this role?" in English no
- * matter what language the rest of the portal spoke. `title` was already a
- * prop — which is the tell: an installation could translate the heading and
- * nothing underneath it.
- *
- * Defaults stay English, so an installation that passes no labels is
- * completely unaffected.
+/**
+ * Every word the authorization screens say, so a portal can say them in its
+ * own language.
+ *
+ * This is the screen an administrator opens to decide who may do what, and
+ * until now it said "Roles", "Show assigned only", "No claims match your
+ * filters" and "Are you sure you want to delete this role?" in English no
+ * matter what language the rest of the portal spoke. `title` was already a
+ * prop — which is the tell: an installation could translate the heading and
+ * nothing underneath it.
+ *
+ * Defaults stay English, so an installation that passes no labels is
+ * completely unaffected.
  */ export const DEFAULT_AUTHORIZATION_LABELS = {
     locale: 'en-US',
     title: 'Authorization Management',

package/dist/fe/components/Captcha/labels.js

@@ -1,20 +1,20 @@
-/**
- * Every word the security check says.
- *
- * This is the most-read component in the kit and the one nobody thought to
- * translate: it sits on the sign-in form, so on an installation of 879 people
- * it is shown several hundred times a morning. A portal could pass `label` and
- * change the heading — and the box under the heading still said "Enter the
- * result", "New challenge", "Expires in 1:30" and, when somebody was slow,
- * "Captcha expired. Please refresh." Four sentences of English on the first
- * screen of a portal that is otherwise entirely in its own language.
- *
- * The placeholders are per challenge type because the instruction is different
- * for each: a sum wants its result, an image wants the letters in it, and the
- * puzzle wants an order. `expiresIn` takes the formatted clock as `{time}` so a
- * translation can put it where its own grammar wants it.
- *
- * Defaults stay English, so an installation that passes nothing is unchanged.
+/**
+ * Every word the security check says.
+ *
+ * This is the most-read component in the kit and the one nobody thought to
+ * translate: it sits on the sign-in form, so on an installation of 879 people
+ * it is shown several hundred times a morning. A portal could pass `label` and
+ * change the heading — and the box under the heading still said "Enter the
+ * result", "New challenge", "Expires in 1:30" and, when somebody was slow,
+ * "Captcha expired. Please refresh." Four sentences of English on the first
+ * screen of a portal that is otherwise entirely in its own language.
+ *
+ * The placeholders are per challenge type because the instruction is different
+ * for each: a sum wants its result, an image wants the letters in it, and the
+ * puzzle wants an order. `expiresIn` takes the formatted clock as `{time}` so a
+ * translation can put it where its own grammar wants it.
+ *
+ * Defaults stay English, so an installation that passes nothing is unchanged.
  */ export const DEFAULT_CAPTCHA_LABELS = {
     heading: 'Security Check',
     clickRefresh: 'Click refresh to load captcha',

package/dist/fe/components/ChatPanel/helpers.js

@@ -14,16 +14,16 @@ export function initialsOf(name) {
     const initials = parts.map((p)=>p[0]?.toUpperCase() ?? '').join('');
     return initials || '?';
 }
-/**
- * The age of a message, in the panel's own words.
- *
- * The units used to be English letters written into the source (`5m`, `3h`,
- * `2d`), which no installation could change, and the fallback past a week was a
- * bare `toLocaleDateString()` — no locale, so the string came out in the
- * SERVER's locale during the server render and the BROWSER's after hydration.
- * The same row rendered twice, differently, and React tore. Both halves now
- * come from the labels: the units as functions of the number, the date under
- * the named `locale`.
+/**
+ * The age of a message, in the panel's own words.
+ *
+ * The units used to be English letters written into the source (`5m`, `3h`,
+ * `2d`), which no installation could change, and the fallback past a week was a
+ * bare `toLocaleDateString()` — no locale, so the string came out in the
+ * SERVER's locale during the server render and the BROWSER's after hydration.
+ * The same row rendered twice, differently, and React tore. Both halves now
+ * come from the labels: the units as functions of the number, the date under
+ * the named `locale`.
  */ export function formatRelativeTime(iso, labels) {
     if (!iso) return '';
     const date = new Date(iso);
@@ -37,13 +37,13 @@ export function initialsOf(name) {
     if (days < 7) return labels.daysAgo(days);
     return date.toLocaleDateString(labels.locale);
 }
-/**
- * The clock beneath a message.
- *
- * `hour12` is pinned as well as the locale: left to the environment, a locale
- * that prints "2:32 PM" on one machine prints "14:32" on the other, which is
- * the same hydration tear by a different route. A 24-hour clock is the one both
- * ends can agree on without asking anybody.
+/**
+ * The clock beneath a message.
+ *
+ * `hour12` is pinned as well as the locale: left to the environment, a locale
+ * that prints "2:32 PM" on one machine prints "14:32" on the other, which is
+ * the same hydration tear by a different route. A 24-hour clock is the one both
+ * ends can agree on without asking anybody.
  */ export function formatClockTime(iso, labels) {
     return new Date(iso).toLocaleTimeString(labels.locale, {
         hour: '2-digit',

package/dist/fe/components/ChatPanel/labels.js

@@ -1,19 +1,19 @@
-/**
- * Every word the chat says, so a portal can say them in its own language.
- *
- * The panel wrote them in English inside the components, and the one label the
- * consumer COULD pass — `title` — was the tell: an intranet in Turkish set the
- * heading to "Sohbetler" and the panel underneath it still said "No
- * conversations yet" and "Select a conversation to start chatting". Two
- * sentences of English on the one screen in the product where people talk to
- * each other.
- *
- * Defaults stay English, so nothing that does not pass labels changes.
- *
- * Anything that interpolates a value is a FUNCTION of that value, never a
- * translated fragment glued to an untranslated one: "3 participants" is
- * "3 katılımcı" in Turkish but "typing" moves to the end of its sentence, and
- * a concatenation would produce a sentence in neither language.
+/**
+ * Every word the chat says, so a portal can say them in its own language.
+ *
+ * The panel wrote them in English inside the components, and the one label the
+ * consumer COULD pass — `title` — was the tell: an intranet in Turkish set the
+ * heading to "Sohbetler" and the panel underneath it still said "No
+ * conversations yet" and "Select a conversation to start chatting". Two
+ * sentences of English on the one screen in the product where people talk to
+ * each other.
+ *
+ * Defaults stay English, so nothing that does not pass labels changes.
+ *
+ * Anything that interpolates a value is a FUNCTION of that value, never a
+ * translated fragment glued to an untranslated one: "3 participants" is
+ * "3 katılımcı" in Turkish but "typing" moves to the end of its sentence, and
+ * a concatenation would produce a sentence in neither language.
  */ export const DEFAULT_CHAT_LABELS = {
     loadingConversations: 'Loading conversations...',
     noConversations: 'No conversations yet',

package/dist/fe/components/DataTable/labels.js

@@ -1,19 +1,19 @@
-/**
- * Every word this table says on its own, so a portal can say them in its own
- * language.
- *
- * The DataTable is the one component in the kit that almost every screen of an
- * installation is built out of — every list of employees, documents, requests
- * and announcements is this table. Column headers and cell contents already
- * come from the caller, which hid the problem: the words the table supplies
- * *itself* were welded into the components. A Turkish intranet could name its
- * columns "Ad", "Birim", "Tarih" and still show "No data available" when the
- * list was empty, "Loading..." while it filled, "Save"/"Cancel" on every
- * inline edit, and "3 item selected" over a selection toolbar whose own buttons
- * were Turkish. Half a screen in one language and half in another.
- *
- * Defaults stay English, so an installation that passes no labels keeps the
- * words it has today.
+/**
+ * Every word this table says on its own, so a portal can say them in its own
+ * language.
+ *
+ * The DataTable is the one component in the kit that almost every screen of an
+ * installation is built out of — every list of employees, documents, requests
+ * and announcements is this table. Column headers and cell contents already
+ * come from the caller, which hid the problem: the words the table supplies
+ * *itself* were welded into the components. A Turkish intranet could name its
+ * columns "Ad", "Birim", "Tarih" and still show "No data available" when the
+ * list was empty, "Loading..." while it filled, "Save"/"Cancel" on every
+ * inline edit, and "3 item selected" over a selection toolbar whose own buttons
+ * were Turkish. Half a screen in one language and half in another.
+ *
+ * Defaults stay English, so an installation that passes no labels keeps the
+ * words it has today.
  */ export const DEFAULT_DATA_TABLE_LABELS = {
     tableLabel: 'Data table',
     empty: 'No data available',

package/dist/fe/components/DevicesPage/components/DeviceCard.js

@@ -76,16 +76,16 @@ function getTrustScoreColor(score) {
     if (score >= 40) return 'bg-orange-500';
     return 'bg-red-500';
 }
-/**
- * When a device was last here, in a form that cannot tear on hydration.
- *
- * It used to be `toLocaleDateString(undefined, …)`, which reads the SERVER's
- * locale while the page renders on the server and the BROWSER's once React
- * takes over — two different strings for the same row, and React replacing one
- * with the other after mount. It also printed 8/5/2026, which in Turkey reads
- * as the 8th of May. The locale is now named by the labels, and the clock is
- * pinned to 24 hours so "14:32" does not become "2:32 PM" between the two
- * passes.
+/**
+ * When a device was last here, in a form that cannot tear on hydration.
+ *
+ * It used to be `toLocaleDateString(undefined, …)`, which reads the SERVER's
+ * locale while the page renders on the server and the BROWSER's once React
+ * takes over — two different strings for the same row, and React replacing one
+ * with the other after mount. It also printed 8/5/2026, which in Turkey reads
+ * as the 8th of May. The locale is now named by the labels, and the clock is
+ * pinned to 24 hours so "14:32" does not become "2:32 PM" between the two
+ * passes.
  */ function formatDate(dateString, say) {
     if (!dateString) return say.unknown;
     const date = new Date(dateString);
@@ -100,11 +100,11 @@ function getTrustScoreColor(score) {
         timeZone: say.timeZone || undefined
     });
 }
-/**
- * The device kind, in words. The server sends `mobile` / `tablet` / `desktop`
- * and the card used to print that raw value, so a Turkish portal read
- * "mobile • Chrome". Anything else the server sends is named as unknown rather
- * than shown in the server's vocabulary.
+/**
+ * The device kind, in words. The server sends `mobile` / `tablet` / `desktop`
+ * and the card used to print that raw value, so a Turkish portal read
+ * "mobile • Chrome". Anything else the server sends is named as unknown rather
+ * than shown in the server's vocabulary.
  */ function deviceTypeWord(deviceType, say) {
     switch(deviceType?.toLowerCase()){
         case 'mobile':

package/dist/fe/components/DevicesPage/components/DevicesPage.js

@@ -12,15 +12,15 @@ import { devicesPageTheme } from '../theme';
 import { DeviceCard } from './DeviceCard';
 import { DevicesHeader } from './DevicesHeader';
 gsap.registerPlugin(useGSAP);
-/**
- * When a waiting device asked, in a form that cannot tear on hydration.
- *
- * It used to be a bare `toLocaleString()`, which reads the SERVER's locale
- * while the page renders on the server and the BROWSER's once React takes over
- * — two different strings for the same tile, and React replacing one with the
- * other after mount. It also printed 8/5/2026, which in Turkey reads as the 8th
- * of May. The locale comes from the labels now, and the clock is pinned to 24
- * hours so the two passes cannot disagree over "14:32" and "2:32 PM".
+/**
+ * When a waiting device asked, in a form that cannot tear on hydration.
+ *
+ * It used to be a bare `toLocaleString()`, which reads the SERVER's locale
+ * while the page renders on the server and the BROWSER's once React takes over
+ * — two different strings for the same tile, and React replacing one with the
+ * other after mount. It also printed 8/5/2026, which in Turkey reads as the 8th
+ * of May. The locale comes from the labels now, and the clock is pinned to 24
+ * hours so the two passes cannot disagree over "14:32" and "2:32 PM".
  */ function formatRequestedAt(value, say) {
     if (!value) return say.unknown;
     const when = new Date(value);

package/dist/fe/components/DevicesPage/labels.js

@@ -1,15 +1,15 @@
-/**
- * Every word this page says, so a portal can say them in its own language.
- *
- * `title` and `subtitle` were already props — which is the tell: an
- * installation could rename the heading and nothing underneath it, so the page
- * that lists where an account is signed in read "Etkin Cihazlar" over "Manage
- * devices that have access to your account", "Last Active", "Trust Score: 80%"
- * and "Are you sure you want to revoke access for this device?". This is the
- * screen an employee opens when they think somebody else is on their account,
- * and every word on it has to be one they can act on.
- *
- * Defaults stay English, so an installation that passes no labels is unchanged.
+/**
+ * Every word this page says, so a portal can say them in its own language.
+ *
+ * `title` and `subtitle` were already props — which is the tell: an
+ * installation could rename the heading and nothing underneath it, so the page
+ * that lists where an account is signed in read "Etkin Cihazlar" over "Manage
+ * devices that have access to your account", "Last Active", "Trust Score: 80%"
+ * and "Are you sure you want to revoke access for this device?". This is the
+ * screen an employee opens when they think somebody else is on their account,
+ * and every word on it has to be one they can act on.
+ *
+ * Defaults stay English, so an installation that passes no labels is unchanged.
  */ export const DEFAULT_DEVICES_PAGE_LABELS = {
     title: 'Active Devices',
     subtitle: 'Manage devices that have access to your account',

package/dist/fe/components/ForgotPasswordPage/labels.js

@@ -1,11 +1,11 @@
-/**
- * Every word this page says, so a portal can say them in its own language.
- *
- * `title` and `subtitle` were already props; everything under them was English
- * — including the whole success state, which is the only screen somebody who
- * has lost their password actually reads.
- *
- * Defaults stay English, so nothing that does not pass labels changes.
+/**
+ * Every word this page says, so a portal can say them in its own language.
+ *
+ * `title` and `subtitle` were already props; everything under them was English
+ * — including the whole success state, which is the only screen somebody who
+ * has lost their password actually reads.
+ *
+ * Defaults stay English, so nothing that does not pass labels changes.
  */ export const DEFAULT_FORGOT_PASSWORD_LABELS = {
     emailLabel: 'Email',
     emailPlaceholder: 'you@example.com',

package/dist/fe/components/FormBuilder/components/FormField.js

@@ -195,11 +195,11 @@ export function FormField({ column, config, value, onChange, error, size = 'md',
         children: renderInput()
     });
 }
-/**
- * The values a dropdown offers. Without a contract these were the raw database
- * enum members with their underscores taken out — `in_progress` shown to a
- * Turkish employee as "In Progress" — so they go through `optionLabel`, which
- * an installation can point at its own words.
+/**
+ * The values a dropdown offers. Without a contract these were the raw database
+ * enum members with their underscores taken out — `in_progress` shown to a
+ * Turkish employee as "In Progress" — so they go through `optionLabel`, which
+ * an installation can point at its own words.
  */ function getSelectOptions(column, say, locale, customOptions) {
     if (customOptions) {
         return customOptions;

package/dist/fe/components/FormBuilder/utils/fieldMapping.js

@@ -211,15 +211,15 @@ export function getDefaultValue(column) {
             return '';
     }
 }
-/**
- * Turns a database name into something readable — `first_name` into
- * "First Name".
- *
- * The locale is not decoration: `toUpperCase()` applies English casing rules
- * wherever it runs, so a column named `iban` came out "Iban" on a Turkish
- * portal where the language wants "İban". Passing the locale makes the first
- * letter the one the reader's language uses, and makes the server render and
- * the browser render agree on it.
+/**
+ * Turns a database name into something readable — `first_name` into
+ * "First Name".
+ *
+ * The locale is not decoration: `toUpperCase()` applies English casing rules
+ * wherever it runs, so a column named `iban` came out "Iban" on a Turkish
+ * portal where the language wants "İban". Passing the locale makes the first
+ * letter the one the reader's language uses, and makes the server render and
+ * the browser render agree on it.
  */ export function formatLabel(name, locale) {
     return name.replace(/_/g, ' ').replace(/([a-z])([A-Z])/g, '$1 $2').replace(/\b\w/g, (char)=>locale ? char.toLocaleUpperCase(locale) : char.toUpperCase());
 }

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

@@ -7,14 +7,14 @@ import { ConnectionOauthFields } from './ConnectionOauthFields';
 import { usesHeaderName, usesQueryParam } from './connectionDraft';
 import { describedBy } from './formSupport';
 import { Field } from './Primitives';
-/**
- * How the connection proves who it is.
- *
- * Only the boxes the chosen auth type reads are on screen. A form that showed
- * all of them would invite an operator to fill in a token URL that a bearer
- * connection never looks at, and then to spend an afternoon on why it changed
- * nothing. The secrets themselves are not here — they live in CredentialFields,
- * because they are written and never read back.
+/**
+ * How the connection proves who it is.
+ *
+ * Only the boxes the chosen auth type reads are on screen. A form that showed
+ * all of them would invite an operator to fill in a token URL that a bearer
+ * connection never looks at, and then to spend an afternoon on why it changed
+ * nothing. The secrets themselves are not here — they live in CredentialFields,
+ * because they are written and never read back.
  */ const theme = integrationsPageTheme;
 export function ConnectionAuthFields(props) {
     const labels = useLabels();

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

@@ -5,9 +5,9 @@ import { useLabels } from '../text/context';
 import { integrationsPageTheme } from '../theme';
 import { describedBy } from './formSupport';
 import { Field } from './Primitives';
-/**
- * What the connection IS: its name, where it lives, and the two switches that
- * decide whether it is used and how carefully.
+/**
+ * What the connection IS: its name, where it lives, and the two switches that
+ * decide whether it is used and how carefully.
  */ const theme = integrationsPageTheme;
 const CHECKBOX = 'h-4 w-4 shrink-0 accent-sky-600 dark:accent-sky-500';
 export function ConnectionBasicFields({ draft, errors, disabled, onChange }) {

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

@@ -5,29 +5,29 @@ import { useIntegrationsStore } from '../store';
 import { useLabels } from '../text/context';
 import { integrationsPageTheme as theme } from '../theme';
 import { Notice } from './Primitives';
-/**
- * Taking one whole integration somewhere else.
- *
- * A connection is the address, 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.
- *
- * ## Why this is not next to Import
- *
- * It was, and it could not be pressed. Both buttons lived in the connection
- * rail, and Export is only meaningful once a connection is CHOSEN — but
- * choosing one replaces the rail with the connection's own screens, taking the
- * button with it. So the button existed, was correct, and was reachable only in
- * the state where it was disabled.
- *
- * Import belongs where there is nothing chosen yet, because that is when you
- * bring one in. Export belongs here, on the connection being exported.
- *
- * 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.
+/**
+ * Taking one whole integration somewhere else.
+ *
+ * A connection is the address, 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.
+ *
+ * ## Why this is not next to Import
+ *
+ * It was, and it could not be pressed. Both buttons lived in the connection
+ * rail, and Export is only meaningful once a connection is CHOSEN — but
+ * choosing one replaces the rail with the connection's own screens, taking the
+ * button with it. So the button existed, was correct, and was reachable only in
+ * the state where it was disabled.
+ *
+ * Import belongs where there is nothing chosen yet, because that is when you
+ * bring one in. Export belongs here, on the connection being exported.
+ *
+ * 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.
  */ /** A filename somebody can still recognise a week later. */ const fileNameFor = (slug)=>`integration-${slug || 'connection'}.json`;
 export function ConnectionExport({ actions, source }) {
     const labels = useLabels();

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

@@ -10,12 +10,12 @@ import { draftFromSource, draftPatchFromSource, draftToSource, emptyConnectionDr
 import { errorText } from './formSupport';
 import { Badge } from './Primitives';
 import { CardSkeleton } from './Skeletons';
-/**
- * Add or edit one connection.
- *
- * The form holds a draft rather than editing the record in place, so abandoning
- * a half-finished change costs nothing and the saved record is never a mixture
- * of what was stored and what is being typed.
+/**
+ * Add or edit one connection.
+ *
+ * The form holds a draft rather than editing the record in place, so abandoning
+ * a half-finished change costs nothing and the saved record is never a mixture
+ * of what was stored and what is being typed.
  */ const theme = integrationsPageTheme;
 export function ConnectionForm({ actions, source, loading = false, onSaved }) {
     const t = useLabels().errors;
@@ -59,22 +59,22 @@ export function ConnectionForm({ actions, source, loading = false, onSaved }) {
             // it into the list, and selecting an id the list does not hold is the
             // state every card below renders a skeleton for.
             onSaved?.(saved);
-            /**
-         * The boxes are re-derived from what was actually STORED.
-         *
-         * The effect above resets them only when the id changes, so a create
-         * showed the truth and an edit never did. Two ways that was visible:
-         * emptying "Timeout" and saving left the box empty while the connection
-         * went on timing out at the stored value — the draft omits a blank
-         * timeout, so the patch never mentions it and the server rightly keeps
-         * what it had; and a trailing space in the name was trimmed on the way
-         * out, so the switcher above showed "Acme" while the box below still
-         * read "Acme ". One screen, disagreeing with itself, until F5.
-         *
-         * MERGED rather than replaced: a field-scoped patch claim can strip
-         * columns out of the reply, and re-deriving wholesale from a partial
-         * record would blank the boxes those columns fill. Nothing can have been
-         * typed in the meantime — every field is disabled while `saving`.
+            /**
+         * The boxes are re-derived from what was actually STORED.
+         *
+         * The effect above resets them only when the id changes, so a create
+         * showed the truth and an edit never did. Two ways that was visible:
+         * emptying "Timeout" and saving left the box empty while the connection
+         * went on timing out at the stored value — the draft omits a blank
+         * timeout, so the patch never mentions it and the server rightly keeps
+         * what it had; and a trailing space in the name was trimmed on the way
+         * out, so the switcher above showed "Acme" while the box below still
+         * read "Acme ". One screen, disagreeing with itself, until F5.
+         *
+         * MERGED rather than replaced: a field-scoped patch claim can strip
+         * columns out of the reply, and re-deriving wholesale from a partial
+         * record would blank the boxes those columns fill. Nothing can have been
+         * typed in the meantime — every field is disabled while `saving`.
          */ if (source) setDraft((current)=>({
                     ...current,
                     ...draftPatchFromSource(saved)

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

@@ -9,13 +9,13 @@ import { ConnectionTransfer } from './ConnectionTransfer';
 import { Badge, Field, Notice } from './Primitives';
 import { ListSkeleton } from './Skeletons';
 import { useInfiniteList } from './useInfiniteList';
-/**
- * The rail of connections.
- *
- * The server owns the list: what the operator types goes back out as a `search`
- * on the next request, and the next page arrives when the sentinel comes into
- * view. Nothing here narrows what has already been fetched, so the rail behaves
- * the same at four connections and at four hundred.
+/**
+ * The rail of connections.
+ *
+ * The server owns the list: what the operator types goes back out as a `search`
+ * on the next request, and the next page arrives when the sentinel comes into
+ * view. Nothing here narrows what has already been fetched, so the rail behaves
+ * the same at four connections and at four hundred.
  */ const theme = integrationsPageTheme;
 const PAGE_SIZE = 20;
 const SEARCH_DEBOUNCE_MS = 300;