@revenexx/studio-integrations 1.4.0 → 2.0.0

package/CHANGELOG.md

@@ -1,5 +1,198 @@
 # @revenexx/studio-integrations
 
+## 2.0.0
+
+### Major Changes
+
+- 8397d7b: Every studio list is read as a table, its search box states its own name, and the Runs
+  filter works again on `@revenexx/studio-shared` 0.3.2 (PO-233).
+
+  **A row of any studio list used to be an unnamed sequence of values.** The shared table
+  rendered anonymous boxes, so nothing connected a column heading to the cell beneath it:
+  a schedule read as _"Order sync, Daily at 03:00, Europe/Berlin, in 18m, 1h ago, live"_,
+  with nothing saying which of the two times was the next run. Taking `studio-shared`
+  0.3.2 gives every list — Workflows, Runs, Schedules, Credentials, Secrets and the Audit
+  Log — `table`, `row`, `columnheader` and `cell`, so each value is announced under the
+  heading it belongs to. The search above each list now states its name on the field
+  itself, in the words of its own placeholder, instead of leaving the browser to work one
+  out from that placeholder — which is a fallback rather than a name, and a documented
+  failure pattern when it is the only one.
+
+  **Two cells on the Schedules page lost the labels they carried.** They were there so a
+  test could find them, and a name on a cell is read _instead of_ its contents — so with
+  the semantics in place they announced "Next run" where the time should be. The heading
+  above the column says which time it is now, which is what it is for.
+
+  **The Runs filter is rebuilt as two selects.** In 0.3.2 the shared filter trigger opens
+  a popover rather than a dropdown menu, and the sub-menus this page put inside it had no
+  menu to attach to: they rendered nothing at all, so the control was there and the
+  narrowing was gone. Outcome and trigger kind are now chosen from a select each, `All`
+  included, and the narrowing reaches the platform exactly as before.
+
+  **A host also owes the shared table two new catalogue entries.** `studio-shared`
+  translates through the host's own `shared.*` catalogue and renders the key itself when
+  an entry is missing, and 0.3.2 asks for `shared.datatable.toolbar.filter.apply` and
+  `…toolbar.filter.reset` — the two buttons of the filter panel, which a host without
+  them draws as the key names. The cockpit already carries both, in either language; any
+  other host has to add them. (`…toolbar.search.aria.label` is asked for too, but no list
+  in this module reaches it: the table names the search box after its own placeholder
+  unless a surface says otherwise, and all six pass a placeholder.)
+
+  **This is a major for two of the reasons [`docs/versioning.md`](docs/versioning.md)
+  names.** The peer floor on `@revenexx/studio` rises from `*` to `^0.2.3`, so a host on
+  the old range can no longer install — and four accessible names are removed rather than
+  renamed: `Next run`, `Last run`, `When it fires` and `Cron expression`, which anything
+  addressing a schedules cell by name was using. Both are things a host has to react to.
+
+  **Hosts must be on `@revenexx/studio` ^0.2.3.** The peer range was `*` and is now the
+  version that carries the search field's `label` prop; below it the name falls through to
+  a wrapper and the box stays anonymous.
+
+- c651aac: The editor no longer points out an error output nobody connected. The run says it instead
+  (PO-479).
+
+  **What goes.** A strip above the canvas read _"{n} node routes failures to an output with
+  nothing attached — nothing handles the failure there."_, named each step, and offered to
+  attach a **Stop and Error** step to the port in one click. The strip, that action, and the
+  five promises in `specs/workflow-advice.md` are withdrawn.
+
+  **Why, and what an author loses.** The strip and the platform behaviour it described
+  shipped together under PO-443. The platform half is the one that can speak with authority:
+  a failure routed to an output nothing leaves now **ends the run**, naming the step, what it
+  failed with, and which output had nowhere to send it — the `node-failure-handling` spec of
+  `revenexx/integrations`, AC-8. Before PO-443 such a failure vanished and the run was
+  recorded as a success, which is the world the strip was built for and which no longer
+  exists. What is genuinely lost is the timing: an author used to be told while drawing, and
+  is now told by the first run that actually fails.
+
+  **`revenexx:stop-and-error` is untouched.** It is still in the palette, still what all eight
+  shipped templates put behind each of their twenty-five error ports, and still the right
+  thing to attach. Only the editor's one-click attachment is gone.
+
+  **A major, for the reason [`docs/versioning.md`](docs/versioning.md) gives.** Seven strings
+  are removed rather than renamed, and three of them are accessible names or an action label
+  that a host or a test could be addressing:
+
+  | Removed                                    | What it was                                 |
+  | ------------------------------------------ | ------------------------------------------- |
+  | `integration.editor.errorPath.advice`      | the strip's own sentence                    |
+  | `integration.editor.errorPath.action.stop` | _Stop the run on error_                     |
+  | `integration.editor.errorPath.ariaReveal`  | accessible name of the step link            |
+  | `integration.editor.errorPath.ariaFix`     | accessible name of the attach action        |
+  | `integration.editor.errorPath.more`        | _…and {n} more_                             |
+  | `integration.editor.errorPath.message`     | the pre-filled message on the attached step |
+  | `integration.editor.errorPath.toast.added` | the toast after attaching                   |
+
+  Nothing else in the editor moves: the validation banner, the reauth strip and the build
+  notice keep their place above the canvas, and the activation gate is unchanged — the strip
+  never touched it, which was the whole point of it.
+
+### Patch Changes
+
+- a79380d: The dialog that imports a platform SFTP account can be drawn by any host built to the
+  written contract, and its wait is now a promise with a test behind it (PO-387).
+
+  **The studio's written contract for a host was five members behind what this dialog
+  reads.** `src/runtime/utils/cockpitSources.ts` says what the module expects of a cockpit
+  host, and its `sftp` entry declared neither `loading` nor `activeTenantSlug`, made
+  `load`'s tenant argument required where the cockpit makes it optional, and left `server`
+  and `home_directory` off an account. The dialog read all five. The cockpit has provided
+  all five throughout, so **nothing was ever wrong for an operator** — what was wrong is
+  that a host built to the contract instead of to the cockpit threw
+  `TypeError: Cannot read properties of undefined` while drawing the dialog. Vue's error
+  handler turns that into a console message and unmounts the tree, so the page went blank
+  with no error anything could catch.
+
+  **The consequence was that no test could reach the surface at all.** The playground's
+  stand-in for the cockpit is built from the contract, so switching it on crashed the
+  dialog and leaving it off gave a dialog that never waits — the only two states the suite
+  could produce. The waiting announcement PO-251 added here was therefore recorded as a
+  gap rather than a criterion. The contract and the stand-in now carry all five members,
+  the dialog takes its type from the contract rather than declaring its own, and
+  `specs/node-configuration.md` carries the wait as AC-33 with a test that fails when the
+  announcement is taken away.
+
+  **A failed fetch no longer reads as a tenant with no accounts.** The surrounding
+  application catches its own fetch errors, so the studio is handed an empty list and no
+  exception — and the dialog drew the same "No active platform SFTP accounts. Create one
+  under Integration Studio → SFTP first." for both. One of those two asks the operator to
+  go and create an account; the other does not, and nothing on screen let them tell which
+  they were looking at. The contract gains the `error` the cockpit has always exposed —
+  **optional**, because the standalone dev studio's stand-ins provide the other four
+  members and not that one, and a dialog that insisted on it would lose that host the
+  whole surface. Where it is absent the dialog keeps the empty state it showed before.
+  That is AC-34, and it adds one string in both languages: **"The platform SFTP accounts could not be loaded:
+  {message}"** / "Die Plattform-SFTP-Konten konnten nicht geladen werden: {message}".
+
+  **A patch.** `CockpitSftpAccount` gains two required members, which
+  [`docs/versioning.md`](docs/versioning.md) would put in the major column as a narrowed
+  type — but only for somebody who can reach it. Nobody can: `exports` in `package.json`
+  declares `"."` alone and no `typesVersions`, so every other subpath is sealed and
+  `require.resolve` of the file answers `ERR_PACKAGE_PATH_NOT_EXPORTED`. The type ships
+  inside the tarball and is importable from nowhere. The dialog reads exactly what it read
+  before, so a host that worked goes on working unchanged.
+
+- 8975a1f: The Credentials list offers the provider step to a credential that never took it, not
+  only to one whose authorisation expired (PO-478).
+
+  **A three-legged credential is created before its provider is asked.** The dialog closes
+  on the creation, and the window that asks for consent is opened after that — so when
+  that second step fails, there is no dialog left to say so. What remained was a
+  credential that cannot work, wearing the same _Not Connected_ badge as one nobody has
+  tested, with nothing in its row to finish what was started. The only way on was to
+  delete it and make it again.
+
+  **The row now offers the step wherever a three-legged credential is not known to be
+  connected**, and the wording says which of the two it is: **Connect** where nothing has
+  ever proved the credential connected, **Reconnect** where it was working and stopped —
+  an authorisation that expired, or a connection test that failed. The amber stays on the
+  expired one, which is the case this surface has always marked for attention. A
+  credential whose access data is a key, a host or a password never carries either, which
+  is what keeps the offer from becoming background noise.
+
+  It is generous by exactly one case: a credential that _was_ authorised but never tested
+  also carries the offer, because nothing the service returns tells that apart from one
+  that was never authorised. Taking the step again is the same window the operator was
+  expecting, so the cost of that guess is a click.
+
+  Promised behaviour: `specs/credentials.md` AC-2. The `## Gaps` entry in
+  `specs/credential-create.md` that asked what this surface says when the step after the
+  close fails is answered, and now points here.
+
+- c787791: No product change: a spec's `## Gaps` entry and a test comment now say only what was
+  measured about `canvas-navigation` AC-4 (PO-479).
+
+## 1.4.1
+
+### Patch Changes
+
+- 7bb1913: A refused credential save states each reason once: at its field, or below the form
+  when no field can show it (PO-477).
+
+  **What a field can carry is marked there and nowhere else.** Until now the service's
+  lead reason was also repeated in a red box above the Save button, so the one sentence
+  the operator had already read was the one thing on the surface they had to read twice
+  — and it crowded out the reasons that had no other place to appear.
+
+  **What no field can carry is what the box is for now.** The service keys a refusal by
+  validation rule, and several of those shapes name nothing either dialog draws an input
+  for: the access data taken as a whole, a field the credential type never handed out, a
+  field hidden while a managed revenexx resource is being reused, or a refusal that is
+  not field-keyed at all, such as a conflict or a gateway error. Any of them was silent
+  unless the service happened to lead with it. All of them are now stated below the form,
+  every message of them, still without the service's count of everything else it found.
+
+  **The refusal also puts the operator in the first marked field.** The box was what
+  guaranteed a refusal could not be rendered below the fold of a form that scrolls; the
+  focus is what guarantees it now, and it leaves the cursor where the correction has to
+  be typed.
+
+  Both dialogs read the refusal through one seam, so the create-and-edit dialog on
+  Credentials and the credential detail dialog answer the same way.
+
+  Promised behaviour: `specs/credential-create.md` AC-8 and AC-11,
+  `specs/credential-detail.md` AC-6.
+
 ## 1.4.0
 
 ### Minor Changes

package/README.md

@@ -74,7 +74,7 @@ component styling silently breaks:
 Adjust the relative paths to reach `node_modules` from your CSS file.
 
 ## Peers
-`@revenexx/studio`, `@revenexx/studio-shared` ^0.2 (module form), `nuxt` ^4, `vue` ^3.5,
+`@revenexx/studio` ^0.2.3, `@revenexx/studio-shared` ^0.3.2 (module form), `nuxt` ^4, `vue` ^3.5,
 `@vue-flow/*` + `@dagrejs/dagre` (workflow editor), `lucide-vue-next`; register
 `@solar-icons/nuxt` in the host.
 

package/dist/module.json

@@ -1,7 +1,7 @@
 {
   "name": "@revenexx/studio-integrations",
   "configKey": "studioIntegrations",
-  "version": "1.4.0",
+  "version": "2.0.0",
   "builder": {
     "@nuxt/module-builder": "1.0.2",
     "unbuild": "unknown"

package/dist/runtime/components/Integrations/CredentialDetailDialog.vue

@@ -1,5 +1,5 @@
 <script setup>
-import { computed, reactive, ref, watch } from "vue";
+import { computed, nextTick, reactive, ref, watch } from "vue";
 import {
   CheckCircle as CheckCircle2,
   CloseCircle as XCircle,
@@ -30,7 +30,7 @@ import {
   SelectValue
 } from "@revenexx/studio";
 import { toast } from "../../utils/notify";
-import { apiFieldErrors, errorReason } from "../../utils/apiError";
+import { apiRefusal, errorReason } from "../../utils/apiError";
 import { credentialState, relativeTime } from "../../utils/credentialState";
 import { hasRevenexxSource } from "../../utils/revenexxCredentialSource";
 import { resolveLocalized } from "../../utils/localize";
@@ -53,14 +53,31 @@ const saving = ref(false);
 const deleting = ref(false);
 const testing = ref(false);
 const liveTest = ref(null);
-const saveError = ref(null);
-const fieldErrors = ref({});
+const saveRefusal = ref(null);
+const drawnKeys = computed(() => [
+  "name",
+  ...sourceActive.value ? [] : fieldsOf(props.type).map((f) => `config.${f.key}`)
+]);
+const refusal = computed(() => apiRefusal(saveRefusal.value, drawnKeys.value));
+const fieldErrors = computed(() => refusal.value.atFields);
+const summaryReasons = computed(() => {
+  if (!saveRefusal.value) return [];
+  if (refusal.value.unshown.length) return refusal.value.unshown.map((u) => u.message);
+  if (Object.keys(refusal.value.atFields).length) return [];
+  return [errorReason(saveRefusal.value, t("integration.credentials.error.save"))];
+});
 function configFieldAria(key) {
   return fieldErrors.value[`config.${key}`] ? { "aria-invalid": "true", "aria-describedby": `detail-field-${key}-error` } : {};
 }
+async function focusFirstRefusedField() {
+  await nextTick();
+  const key = drawnKeys.value.find((k) => k in fieldErrors.value);
+  if (!key) return;
+  const id = key === "name" ? "detail-cred-name" : `detail-field-${key.slice("config.".length)}`;
+  document.getElementById(id)?.focus();
+}
 function clearRefusal() {
-  saveError.value = null;
-  fieldErrors.value = {};
+  saveRefusal.value = null;
 }
 const connecting = ref(false);
 const typeName = computed(() => resolveLocalized(props.type?.name) || props.credential?.credential_type_slug || "");
@@ -103,6 +120,7 @@ async function runTest() {
   if (!props.credential) return;
   testing.value = true;
   liveTest.value = null;
+  clearRefusal();
   try {
     liveTest.value = await test(props.credential.id);
     await load(true);
@@ -121,9 +139,9 @@ async function save() {
     emit("update:open", false);
     toast.success(t("integration.credentials.toast.updated"));
   } catch (e) {
-    fieldErrors.value = apiFieldErrors(e);
-    saveError.value = errorReason(e, t("integration.credentials.error.save"));
-    toast.error(saveError.value);
+    saveRefusal.value = e;
+    void focusFirstRefusedField();
+    toast.error(errorReason(e, t("integration.credentials.error.save")));
   } finally {
     saving.value = false;
   }
@@ -182,8 +200,11 @@ async function connect() {
         <!-- Standard cockpit tab bar (violet underline) -->
         <TabBar :model-value="tab" :tabs="tabs" @update:model-value="(k) => tab = k" />
 
-        <!-- Tab 1: Credentials -->
-        <div v-if="tab === 'credentials'" class="space-y-5 max-h-[62vh] overflow-y-auto pr-1 pt-4">
+        <!-- Tab 1: Credentials. A `template` rather than a wrapping element: the
+             scrolling pane and the block below it are siblings, as they were when the
+             pane was the whole tab, so nothing about the spacing around them moves. -->
+        <template v-if="tab === 'credentials'">
+        <div class="space-y-5 max-h-[62vh] overflow-y-auto pr-1 pt-4">
         <!-- Connection state — the headline answer: are these credentials correct? -->
         <div class="rounded-lg border p-3" :class="state.toneClass">
           <div class="flex items-center gap-2">
@@ -243,7 +264,10 @@ async function connect() {
           <IntegrationsCredentialRevenexxSource
             v-if="hasRevenexxSource(type?.slug)"
             :type="type"
-            @update:active="(v) => sourceActive = v"
+            @update:active="(v) => {
+  sourceActive = v;
+  clearRefusal();
+}"
             @apply="(c) => Object.assign(form.config, c)"
           />
 
@@ -313,27 +337,35 @@ async function connect() {
             {{ liveTest.ok ? liveTest.message ?? t("integration.credentials.shared.test.ok") : liveTest.error ?? liveTest.message ?? t("integration.credentials.shared.test.failed") }}
           </div>
 
-          <!-- The save was refused. Same rule as the create dialog: stated here, and at
-               the field where the service keyed it. -->
-          <div v-if="saveError" role="alert" class="rounded-md bg-rose-500/10 px-3 py-2 text-sm text-rose-700">
-            {{ saveError }}
-          </div>
+        </div>
 
-          <div class="flex items-center gap-2 pt-1">
-            <div class="flex-1" />
-            <Button variant="outline" :disabled="testing || saving" @click="runTest">
-              <Loader2 v-if="testing" :size="14" class="mr-1 animate-spin" />
-              <TestIcon v-else :size="14" class="mr-1" />
-              {{ t("integration.credentials.shared.action.testConnection") }}
-            </Button>
-            <Button :disabled="saving || !form.name.trim()" @click="save">
-              <Loader2 v-if="saving" :size="14" class="mr-1 animate-spin" />
-              {{ t("integration.common.action.save") }}
-            </Button>
-          </div>
         </div>
 
+        <!-- Outside the scrolling pane on purpose, the way the create dialog has it:
+             a refusal puts the operator in the first marked field, which scrolls that
+             pane back to the top — and a summary rendered at the end of the form would
+             be carried out of sight by the very focus meant to make the refusal
+             visible. What is marked at a field is not repeated here; what has no field
+             to be marked at would otherwise be silent. -->
+        <div v-if="summaryReasons.length" role="alert" class="mt-3 space-y-1 rounded-md bg-rose-500/10 px-3 py-2 text-sm text-rose-700">
+          <!-- Keyed by position: two undrawn keys can be refused with the same
+               sentence, and a duplicate key is how one of them goes unrendered. -->
+          <p v-for="(reason, i) in summaryReasons" :key="i">{{ reason }}</p>
+        </div>
+
+        <div class="flex items-center gap-2 pt-3">
+          <div class="flex-1" />
+          <Button variant="outline" :disabled="testing || saving" @click="runTest">
+            <Loader2 v-if="testing" :size="14" class="mr-1 animate-spin" />
+            <TestIcon v-else :size="14" class="mr-1" />
+            {{ t("integration.credentials.shared.action.testConnection") }}
+          </Button>
+          <Button :disabled="saving || !form.name.trim()" @click="save">
+            <Loader2 v-if="saving" :size="14" class="mr-1 animate-spin" />
+            {{ t("integration.common.action.save") }}
+          </Button>
         </div>
+        </template>
 
         <!-- Tab 2: Details -->
         <div v-else class="space-y-5 max-h-[62vh] overflow-y-auto pr-1 pt-4">

package/dist/runtime/components/Integrations/RunsTable.vue

@@ -2,11 +2,11 @@
 import { computed, onMounted, onUnmounted, ref } from "vue";
 import {
   Badge,
-  DropdownMenuItem,
-  DropdownMenuSeparator,
-  DropdownMenuSub,
-  DropdownMenuSubContent,
-  DropdownMenuSubTrigger
+  Select,
+  SelectContent,
+  SelectItem,
+  SelectTrigger,
+  SelectValue
 } from "@revenexx/studio";
 import { DEFAULT_RUN_DIRECTION, DEFAULT_RUN_SORT } from "../../utils/runFeedQuery";
 import { RUN_STATUS_COLUMN_WIDTH, RUN_STATUS_WORDS, normalisedRunStatus, runStatusClass, runStatusLabel } from "../../utils/statusStyle";
@@ -85,8 +85,9 @@ function setStatus(word) {
 function setTrigger(kind) {
   emit("narrow", { triggerType: kind ?? "" });
 }
-const statusApplied = computed(() => chosenStatus.value[0] ? runStatusLabel(chosenStatus.value[0]) : "");
-const triggerApplied = computed(() => props.triggerType ? triggerTypeLabel(props.triggerType) : "");
+const ALL = "all";
+const statusChoice = computed(() => chosenStatus.value[0] ?? ALL);
+const triggerChoice = computed(() => props.triggerType || ALL);
 const searchText = ref("");
 function onTableState(state) {
   searchText.value = state.search;
@@ -171,46 +172,66 @@ const columns = computed(() => [
       (`filterTabs`) cannot be used here, because it compares the rows in hand and
       those are one page.
 
-      Built to the same shape as that control on purpose — a dimension per
-      sub-menu, "All" first, one value at a time — so this list is narrowed by the
-      same gesture as the five that narrow what they hold, and one test helper
-      still addresses all six (`e2e/support/studio-table.ts`). What is NOT copied
-      is the count beside each option: the built-in counts the rows in hand, and
-      counting a page here would put a number next to "failed" that describes this
-      page rather than the history the option narrows.
+      It is no longer the same gesture as the other lists. Theirs tick values and
+      apply them together; this one picks one value per dimension and applies it on
+      the spot, because each pick is a request to the platform and staging them
+      would only delay the same round trip. So the shared narrowing helper does not
+      reach this page and `runs.spec.ts` carries its own — said in both places
+      rather than left to be discovered (`e2e/support/studio-table.ts`).
+
+      What is still NOT copied is the count beside each option: the built-in counts
+      the rows in hand, and counting a page here would put a number next to
+      "failed" that describes this page rather than the history the option narrows.
     -->
     <template v-if="serverMode" #filter-menu>
-      <DropdownMenuSub>
-        <DropdownMenuSubTrigger class="gap-2">
-          <span class="flex-1">{{ t("integration.runs.table.column.status") }}</span>
-          <span v-if="statusApplied" class="text-xs text-primary">{{ statusApplied }}</span>
-        </DropdownMenuSubTrigger>
-        <DropdownMenuSubContent class="w-48">
-          <DropdownMenuItem @select="setStatus(null)">
-            {{ t("integration.runs.table.filter.all") }}
-          </DropdownMenuItem>
-          <DropdownMenuSeparator />
-          <DropdownMenuItem v-for="word in RUN_STATUS_WORDS" :key="word" @select="setStatus(word)">
-            {{ runStatusLabel(word) }}
-          </DropdownMenuItem>
-        </DropdownMenuSubContent>
-      </DropdownMenuSub>
+      <!--
+        Two selects rather than the sub-menus this slot used to hold. Since
+        `studio-shared` 0.3.2 the filter trigger opens a popover instead of a
+        dropdown menu, and a `DropdownMenuSub` outside a menu root has nothing to
+        attach to: it renders nothing at all, so the narrowing was there in the
+        markup and gone from the screen. A select is what the new surface is built
+        for — it sizes `[data-slot=select-trigger]` to its full width — and it
+        keeps what the menu promised, the widest setting included.
+      -->
+      <div class="space-y-1">
+        <span class="text-xs font-medium text-muted-foreground">{{ t("integration.runs.table.column.status") }}</span>
+        <Select
+          :model-value="statusChoice"
+          @update:model-value="(v) => setStatus(v === ALL ? null : String(v))"
+        >
+          <SelectTrigger :aria-label="t('integration.runs.table.column.status')" class="h-8 text-sm">
+            <SelectValue />
+          </SelectTrigger>
+          <SelectContent>
+            <SelectItem :value="ALL">
+              {{ t("integration.runs.table.filter.all") }}
+            </SelectItem>
+            <SelectItem v-for="word in RUN_STATUS_WORDS" :key="word" :value="word">
+              {{ runStatusLabel(word) }}
+            </SelectItem>
+          </SelectContent>
+        </Select>
+      </div>
 
-      <DropdownMenuSub>
-        <DropdownMenuSubTrigger class="gap-2">
-          <span class="flex-1">{{ t("integration.runs.table.column.trigger") }}</span>
-          <span v-if="triggerApplied" class="text-xs text-primary">{{ triggerApplied }}</span>
-        </DropdownMenuSubTrigger>
-        <DropdownMenuSubContent class="w-48">
-          <DropdownMenuItem @select="setTrigger(null)">
-            {{ t("integration.runs.table.filter.all") }}
-          </DropdownMenuItem>
-          <DropdownMenuSeparator />
-          <DropdownMenuItem v-for="kind in TRIGGER_TYPE_WORDS" :key="kind" @select="setTrigger(kind)">
-            {{ triggerTypeLabel(kind) }}
-          </DropdownMenuItem>
-        </DropdownMenuSubContent>
-      </DropdownMenuSub>
+      <div class="space-y-1">
+        <span class="text-xs font-medium text-muted-foreground">{{ t("integration.runs.table.column.trigger") }}</span>
+        <Select
+          :model-value="triggerChoice"
+          @update:model-value="(v) => setTrigger(v === ALL ? null : String(v))"
+        >
+          <SelectTrigger :aria-label="t('integration.runs.table.column.trigger')" class="h-8 text-sm">
+            <SelectValue />
+          </SelectTrigger>
+          <SelectContent>
+            <SelectItem :value="ALL">
+              {{ t("integration.runs.table.filter.all") }}
+            </SelectItem>
+            <SelectItem v-for="kind in TRIGGER_TYPE_WORDS" :key="kind" :value="kind">
+              {{ triggerTypeLabel(kind) }}
+            </SelectItem>
+          </SelectContent>
+        </Select>
+      </div>
     </template>
 
     <template #cell-status="{ row: run }">

package/dist/runtime/components/Integrations/SftpAccountImportDialog.vue

@@ -17,13 +17,24 @@ const sftp = typeof useConsoleSftp === "function" ? useConsoleSftp() : {
 const { create } = useIntegrationsCredentials();
 const busyId = ref(null);
 const error = ref(null);
-watch(open, (o) => {
-  if (o) {
-    error.value = null;
-    void sftp.load();
+const loadPending = ref(false);
+let openCycle = 0;
+watch(open, async (o) => {
+  if (!o) return;
+  const cycle = ++openCycle;
+  error.value = null;
+  loadPending.value = true;
+  try {
+    await sftp.load();
+  } finally {
+    if (cycle === openCycle) loadPending.value = false;
   }
 });
 const activeAccounts = computed(() => sftp.accounts.value.filter((a) => a.status === "active" && a.login_username));
+const waiting = computed(() => (loadPending.value || sftp.loading.value) && !activeAccounts.value.length);
+const loadFailed = computed(
+  () => !waiting.value && !activeAccounts.value.length && sftp.activeTenantSlug.value && sftp.error?.value ? t("integration.credentials.sftpImport.state.loadFailed", { message: sftp.error.value }) : null
+);
 async function importAccount(account) {
   const tenant = sftp.activeTenantSlug.value;
   if (!tenant || !account.login_username) return;
@@ -69,13 +80,16 @@ async function importAccount(account) {
            limit written down there (PO-251). -->
       <LoadingAnnouncement
         :label="t('integration.credentials.sftpImport.title')"
-        :loading="sftp.loading.value && !activeAccounts.length"
+        :loading="waiting"
         :text="t('integration.credentials.sftpImport.state.loading')"
       />
 
-      <div v-if="sftp.loading.value && !activeAccounts.length" aria-hidden="true" class="space-y-2">
+      <div v-if="waiting" aria-hidden="true" class="space-y-2">
         <div v-for="n in 3" :key="`sk-${n}`" class="h-9 rounded-md bg-black/[0.07] animate-pulse" />
       </div>
+      <p v-else-if="loadFailed" class="py-4 text-center text-sm text-rose-600">
+        {{ loadFailed }}
+      </p>
       <p v-else-if="!activeAccounts.length" class="py-4 text-center text-sm text-muted-foreground">
         {{ t("integration.credentials.sftpImport.empty") }}
       </p>

package/dist/runtime/components/Integrations/WorkflowEditor.d.vue.ts

@@ -42,42 +42,8 @@ type __VLS_Props = {
  * id that is on the canvas is in the blob by construction.
  */
 declare function revealNode(id: string): void;
-/**
- * Point at a node without opening it — for a reader who has to look at the
- * card's *surroundings* rather than at its settings.
- *
- * The deliberate difference from {@link revealNode} is the missing selection,
- * and with it the missing settings lightbox. That is the whole reason there are
- * two functions: the validation banner sends someone to a field at fault, and
- * the dialog is where that field is. The error-path advice sends them to a port
- * with nothing on it, and the question they have to answer — where should this
- * failure go? — is answered by the graph around the card, which a dialog over
- * the canvas covers up.
- *
- * Marked with the same pulse a newly created card gets, because the job is the
- * same one: say which of thirty cards is the one meant.
- */
-declare function showNodeOnCanvas(id: string): void;
-/**
- * Hang a Stop-and-Error step off a node's error output and wire it up
- * (specs/workflow-advice.md AC-3).
- *
- * The advice strip can tell an author their error output leads nowhere; on its
- * own that is a reprimand without a remedy, because the repair — drop a node,
- * pick the right one, connect it, write an expression quoting the failing step's
- * message — is four steps of tedium they have to already know. Every template we
- * ship does exactly this, twenty-five times over, so the shape is settled and
- * worth one click.
- *
- * Leaves the result unsaved and unopened, like every other insertion here: the
- * new step is highlighted and the author decides whether to keep it. Deleting it
- * is the undo, because this editor has no undo stack to hook into.
- */
-declare function attachErrorStop(sourceNodeId: string, port: string): void;
 declare const _default: import("vue").DefineComponent<__VLS_Props, {
     revealNode: typeof revealNode;
-    showNodeOnCanvas: typeof showNodeOnCanvas;
-    attachErrorStop: typeof attachErrorStop;
 }, {}, {}, {}, import("vue").ComponentOptionsMixin, import("vue").ComponentOptionsMixin, {
     run: () => any;
     toggleActive: () => any;