@revenexx/studio-integrations 1.4.1 → 2.0.0

package/CHANGELOG.md

@@ -1,5 +1,167 @@
 # @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

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.1",
+  "version": "2.0.0",
   "builder": {
     "@nuxt/module-builder": "1.0.2",
     "unbuild": "unknown"

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;

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

@@ -51,8 +51,7 @@ import { toast } from "vue-sonner";
 import WorkflowEdgeView from "./WorkflowEdgeView.vue";
 import { layoutWorkflowNodes } from "./workflowLayout";
 import { defaultsFor } from "../../utils/configDefaults";
-import { nodeDisplayLabel } from "../../utils/validationFindings";
-import { TRIGGER_TEMPLATES, findManifest, newestExecutableVersion } from "../../data/integrationNodeCatalog";
+import { TRIGGER_TEMPLATES, findManifest } from "../../data/integrationNodeCatalog";
 import { isTerminalManifest, portsForNode } from "../../data/nodeInputData";
 import { computeLoopBodies, iteratorNodeIds, nodeLoopData } from "../../data/loopBody";
 import { inputHandleId, outputHandleId, portFromHandleId } from "../../data/handleId";
@@ -865,17 +864,7 @@ function revealNode(id) {
     selectedId.value = id;
   }
 }
-function showNodeOnCanvas(id) {
-  const folded = collapsedGroupOf().get(id);
-  if (folded) patchGroup(folded.id, { collapsed: false });
-  if (blob.value.nodes.some((n) => n.id === id)) {
-    markBorn(id);
-    syncFromBlob();
-  }
-  if (paneReady.value) centerOnNode(id);
-  else pendingReveal.value = id;
-}
-defineExpose({ revealNode, showNodeOnCanvas, attachErrorStop });
+defineExpose({ revealNode });
 const selectedUpstreamOutputs = computed(() => {
   const id = selectedId.value;
   if (!id) return [];
@@ -1108,45 +1097,6 @@ function spliceIntoEdge(edgeId, payload) {
   syncFromBlob();
   push();
 }
-const STOP_AND_ERROR_SLUG = "revenexx:stop-and-error";
-function attachErrorStop(sourceNodeId, port) {
-  const source = blob.value.nodes.find((n) => n.id === sourceNodeId);
-  const version = newestExecutableVersion(STOP_AND_ERROR_SLUG);
-  const manifest = version ? findManifest(STOP_AND_ERROR_SLUG, version) : null;
-  if (!source || !manifest) return;
-  const at = nodePosition(sourceNodeId);
-  const id = `n-${Date.now()}`;
-  blob.value.nodes.push({
-    id,
-    nodeSlug: manifest.slug,
-    nodeVersion: manifest.version,
-    config: {
-      ...defaultsFor(manifest.config ?? []),
-      // The template convention verbatim: name the step that failed, then quote
-      // its own message, so the run record says what went wrong rather than only
-      // that something did. `errorCode` keeps the node's own default.
-      message: t("integration.editor.errorPath.message", {
-        label: nodeDisplayLabel(source),
-        nodeId: source.id,
-        port
-      })
-    },
-    // Below the source and on the grid, the way the templates place theirs.
-    // `freeSpotNear` keeps two of them off each other.
-    position: freeSpotNear({ x: at.x, y: at.y + 180 })
-  });
-  blob.value.edges.push({
-    id: `e-${Date.now().toString(36)}${Math.random().toString(36).slice(2, 6)}`,
-    from: { nodeId: sourceNodeId, output: port },
-    to: { nodeId: id, input: void 0 }
-  });
-  markBorn(id);
-  syncFromBlob();
-  if (paneReady.value) centerOnNode(id);
-  else pendingReveal.value = id;
-  push();
-  toast.info(t("integration.editor.errorPath.toast.added", { label: nodeDisplayLabel(source) }));
-}
 function nodeDims(id) {
   const d = flow.findNode(id)?.dimensions;
   return d && d.width > 0 ? d : { width: 220, height: 64 };

package/dist/runtime/components/Integrations/WorkflowEditor.vue.d.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;

package/dist/runtime/i18n/messages/de.json

@@ -28,8 +28,8 @@
   "integration.audit.table.column.actor": "Akteur",
   "integration.audit.table.column.resource": "Ressource",
   "integration.audit.table.column.when": "Wann",
-  "integration.audit.toast.copyFailed": "Kopieren fehlgeschlagen",
   "integration.audit.toast.copied": "Kopiert",
+  "integration.audit.toast.copyFailed": "Kopieren fehlgeschlagen",
   "integration.canvas.badge.trigger": "Trigger",
   "integration.canvas.color.amber": "Bernstein",
   "integration.canvas.color.blue": "Blau",
@@ -170,6 +170,8 @@
   "integration.credentials.error.oauthConnect": "OAuth-Verbindung konnte nicht gestartet werden.",
   "integration.credentials.error.save": "Zugangsdaten konnten nicht gespeichert werden.",
   "integration.credentials.error.testFailed": "Verbindungstest fehlgeschlagen.",
+  "integration.credentials.list.action.connect": "Verbinden",
+  "integration.credentials.list.action.connect.aria": "{name} verbinden",
   "integration.credentials.list.action.delete.aria": "{name} löschen",
   "integration.credentials.list.action.new": "Zugangsdaten anlegen",
   "integration.credentials.list.action.reconnect": "Erneut verbinden",
@@ -244,6 +246,7 @@
   "integration.credentials.sftpImport.empty": "Keine aktiven Plattform-SFTP-Konten. Zuerst eines unter Integration Studio → SFTP anlegen.",
   "integration.credentials.sftpImport.error.importFailed": "Import fehlgeschlagen.",
   "integration.credentials.sftpImport.error.readPassword": "Das Kontopasswort konnte nicht gelesen werden.",
+  "integration.credentials.sftpImport.state.loadFailed": "Die Plattform-SFTP-Konten konnten nicht geladen werden: {message}",
   "integration.credentials.sftpImport.state.loading": "SFTP-Konten werden geladen…",
   "integration.credentials.sftpImport.title": "Plattform-SFTP-Konto importieren",
   "integration.credentials.shared.action.testConnection": "Verbindung testen",
@@ -377,13 +380,6 @@
   "integration.editor.dropGhost.label": "Loslassen zum Hinzufügen",
   "integration.editor.emptyState.hint": "Ziehen Sie einen Trigger und eine Aktion aus dem Panel links.",
   "integration.editor.emptyState.title": "Leere Arbeitsfläche",
-  "integration.editor.errorPath.action.stop": "Fehlerausgang stoppen lassen",
-  "integration.editor.errorPath.advice": "{n} Node leitet Fehler auf einen Ausgang, an dem nichts hängt — der Fehler wird dort nicht behandelt. | {n} Nodes leiten Fehler auf einen Ausgang, an dem nichts hängt — der Fehler wird dort nicht behandelt.",
-  "integration.editor.errorPath.ariaFix": "Ausgang „{port}“ von {label} auf Stop und Fehler legen",
-  "integration.editor.errorPath.ariaReveal": "{label} auf der Canvas zeigen — der Ausgang „{port}“ ist nicht verbunden",
-  "integration.editor.errorPath.message": "{label} fehlgeschlagen: ${{ nodes.{nodeId}.outputs.{port}.message }}",
-  "integration.editor.errorPath.more": "…und {n} weitere",
-  "integration.editor.errorPath.toast.added": "Stop und Fehler an {label} gehängt — noch nicht gespeichert.",
   "integration.editor.event.toast.noneReceived": "Noch kein {topic}-Event empfangen.",
   "integration.editor.executionMode.async.hint": "Runs werden immer in die Warteschlange gestellt; der Trigger antwortet sofort.",
   "integration.editor.executionMode.async.label": "Nur asynchron",
@@ -983,10 +979,8 @@
   "integration.runs.toast.action.requested": "{action} angefordert",
   "integration.runs.toast.action.started": "Run #{id} gestartet",
   "integration.runs.toast.terminate.confirm": "Run #{id} terminieren?",
-  "integration.schedules.cell.cronExpression.aria": "Cron-Ausdruck",
   "integration.schedules.cell.customSchedule": "Individueller Zeitplan",
   "integration.schedules.cell.noSchedule": "Kein Zeitplan festgelegt",
-  "integration.schedules.cell.whenItFires.aria": "Wann er ausgelöst wird",
   "integration.schedules.cron.dailyAt": "Täglich um {time}",
   "integration.schedules.cron.day.daily": "Täglich",
   "integration.schedules.cron.day.weekdays": "Wochentags",
@@ -1229,6 +1223,7 @@
   "integration.workflows.state.action.remove.hint": "Das Entfernen nimmt diesem Workflow den Zugriff. Die gespeicherten Einträge bleiben bestehen.",
   "integration.workflows.state.dialog.description": "Was sich dieser Workflow zwischen Läufen merken darf. Er erreicht ausschließlich die hier deklarierten Namespaces — alles andere wird beim Lauf abgewiesen.",
   "integration.workflows.state.dialog.title": "Zustands-Namespaces",
+  "integration.workflows.state.empty": "Dieser Workflow merkt sich noch nichts zwischen Läufen.",
   "integration.workflows.state.error.invalidName": "Kleinbuchstaben, Ziffern und . - _, beginnend mit einem Buchstaben — zum Beispiel article oder crm.customers.",
   "integration.workflows.state.error.nameExists": "Dieser Workflow deklariert diesen Namespace bereits.",
   "integration.workflows.state.field.newName.label": "Namespace deklarieren",
@@ -1246,7 +1241,6 @@
   "integration.workflows.state.role.mapping.hint": "Verknüpft je eine ID auf beiden Seiten, damit ein späterer Lauf weiß, ob er anlegen oder aktualisieren muss.",
   "integration.workflows.state.role.mapping.label": "Zuordnung",
   "integration.workflows.state.row.aria": "Zustands-Namespace {namespace}",
-  "integration.workflows.state.empty": "Dieser Workflow merkt sich noch nichts zwischen Läufen.",
   "integration.workflows.state.visibility.private.hint": "Nur dieser Workflow liest und schreibt ihn, und er wird mit dem Workflow gelöscht.",
   "integration.workflows.state.visibility.private.label": "Diesen Workflow",
   "integration.workflows.state.visibility.shared.hint": "Jeder Workflow dieses Mandanten liest und schreibt diese Einträge, und der Namespace bleibt bestehen, wenn dieser Workflow gelöscht wird.",

package/dist/runtime/i18n/messages/en.json

@@ -28,8 +28,8 @@
   "integration.audit.table.column.actor": "Actor",
   "integration.audit.table.column.resource": "Resource",
   "integration.audit.table.column.when": "When",
-  "integration.audit.toast.copyFailed": "Could not copy",
   "integration.audit.toast.copied": "Copied",
+  "integration.audit.toast.copyFailed": "Could not copy",
   "integration.canvas.badge.trigger": "Trigger",
   "integration.canvas.color.amber": "Amber",
   "integration.canvas.color.blue": "Blue",
@@ -170,6 +170,8 @@
   "integration.credentials.error.oauthConnect": "Could not start OAuth connect.",
   "integration.credentials.error.save": "Could not save credential.",
   "integration.credentials.error.testFailed": "Connection test failed.",
+  "integration.credentials.list.action.connect": "Connect",
+  "integration.credentials.list.action.connect.aria": "Connect {name}",
   "integration.credentials.list.action.delete.aria": "Delete {name}",
   "integration.credentials.list.action.new": "New credential",
   "integration.credentials.list.action.reconnect": "Reconnect",
@@ -244,6 +246,7 @@
   "integration.credentials.sftpImport.empty": "No active platform SFTP accounts. Create one under Integration Studio → SFTP first.",
   "integration.credentials.sftpImport.error.importFailed": "Import failed.",
   "integration.credentials.sftpImport.error.readPassword": "Could not read the account password.",
+  "integration.credentials.sftpImport.state.loadFailed": "The platform SFTP accounts could not be loaded: {message}",
   "integration.credentials.sftpImport.state.loading": "Loading the SFTP accounts…",
   "integration.credentials.sftpImport.title": "Import platform SFTP account",
   "integration.credentials.shared.action.testConnection": "Connect",
@@ -377,13 +380,6 @@
   "integration.editor.dropGhost.label": "Drop to add",
   "integration.editor.emptyState.hint": "Drag a trigger and an action from the panel on the left.",
   "integration.editor.emptyState.title": "Empty canvas",
-  "integration.editor.errorPath.action.stop": "Stop the run on error",
-  "integration.editor.errorPath.advice": "{n} node routes failures to an output with nothing attached — nothing handles the failure there. | {n} nodes route failures to an output with nothing attached — nothing handles the failure there.",
-  "integration.editor.errorPath.ariaFix": "Route {label}'s \"{port}\" output to Stop and Error",
-  "integration.editor.errorPath.ariaReveal": "Show {label} on the canvas — its \"{port}\" output is not connected",
-  "integration.editor.errorPath.message": "{label} failed: ${{ nodes.{nodeId}.outputs.{port}.message }}",
-  "integration.editor.errorPath.more": "…and {n} more",
-  "integration.editor.errorPath.toast.added": "Stop and Error attached to {label} — not saved yet.",
   "integration.editor.event.toast.noneReceived": "No {topic} event received yet.",
   "integration.editor.executionMode.async.hint": "Runs are always queued; the trigger returns immediately.",
   "integration.editor.executionMode.async.label": "Async only",
@@ -983,10 +979,8 @@
   "integration.runs.toast.action.requested": "{action} requested",
   "integration.runs.toast.action.started": "Started run #{id}",
   "integration.runs.toast.terminate.confirm": "Terminate run #{id}?",
-  "integration.schedules.cell.cronExpression.aria": "Cron expression",
   "integration.schedules.cell.customSchedule": "Custom schedule",
   "integration.schedules.cell.noSchedule": "No schedule set",
-  "integration.schedules.cell.whenItFires.aria": "When it fires",
   "integration.schedules.cron.dailyAt": "Daily at {time}",
   "integration.schedules.cron.day.daily": "Daily",
   "integration.schedules.cron.day.weekdays": "Weekdays",
@@ -1229,6 +1223,7 @@
   "integration.workflows.state.action.remove.hint": "Removing the declaration takes this workflow's access away. The stored entries stay where they are.",
   "integration.workflows.state.dialog.description": "What this workflow may remember between runs. It can only reach the namespaces declared here — anything else is refused when the workflow runs.",
   "integration.workflows.state.dialog.title": "State namespaces",
+  "integration.workflows.state.empty": "This workflow remembers nothing between runs yet.",
   "integration.workflows.state.error.invalidName": "Use lowercase letters, digits and . - _, starting with a letter — for example article or crm.customers.",
   "integration.workflows.state.error.nameExists": "This workflow already declares that namespace.",
   "integration.workflows.state.field.newName.label": "Declare a namespace",
@@ -1246,7 +1241,6 @@
   "integration.workflows.state.role.mapping.hint": "Correlates an id on each side, so a later run knows whether to create or update.",
   "integration.workflows.state.role.mapping.label": "Mapping",
   "integration.workflows.state.row.aria": "State namespace {namespace}",
-  "integration.workflows.state.empty": "This workflow remembers nothing between runs yet.",
   "integration.workflows.state.visibility.private.hint": "Only this workflow reads and writes it, and it is deleted along with the workflow.",
   "integration.workflows.state.visibility.private.label": "This workflow",
   "integration.workflows.state.visibility.shared.hint": "Every workflow in this tenant reads and writes these entries, and the namespace stays when this workflow is deleted.",

package/dist/runtime/pages/integrations/credentials.vue

@@ -32,7 +32,7 @@ import {
 } from "@revenexx/studio";
 import { toast } from "../../utils/notify";
 import { apiRefusal, errorReason } from "../../utils/apiError";
-import { CREDENTIAL_STATES, credentialState, credentialStateLabel } from "../../utils/credentialState";
+import { CREDENTIAL_STATES, credentialState, credentialStateLabel, providerStepWord } from "../../utils/credentialState";
 import { hasRevenexxSource } from "../../utils/revenexxCredentialSource";
 import { resolveLocalized } from "../../utils/localize";
 const t = useIntegrationsT();
@@ -51,6 +51,17 @@ function typeName(slug) {
 function isOAuthAuthcode(t2) {
   return t2?.auth_kind === "oauth2-authcode";
 }
+function providerStep(c) {
+  if (!isOAuthAuthcode(typeFor(c.credential_type_slug))) return null;
+  const state = credentialState(c).key;
+  const word = providerStepWord(state);
+  if (!word) return null;
+  return {
+    label: t(`integration.credentials.list.action.${word}`),
+    aria: t(`integration.credentials.list.action.${word}.aria`, { name: c.name }),
+    expired: state === "needs_reauth"
+  };
+}
 function formatDateTime(iso) {
   if (!iso) return "\u2014";
   try {
@@ -306,15 +317,16 @@ async function confirmDelete() {
         <template #cell-actions="{ row: c }">
           <div class="flex items-center justify-end gap-2 text-sm" @click.stop>
             <Button
-              v-if="c.status === 'needs_reauth' && isOAuthAuthcode(typeFor(c.credential_type_slug))"
+              v-if="providerStep(c)"
               variant="outline"
               size="sm"
-              class="h-7 text-amber-600"
+              class="h-7"
+              :class="providerStep(c).expired ? 'text-amber-600' : ''"
               :disabled="connecting === c.id"
-              :aria-label="t('integration.credentials.list.action.reconnect.aria', { name: c.name })"
+              :aria-label="providerStep(c).aria"
               @click="connect(c)"
             >
-              {{ t("integration.credentials.list.action.reconnect") }}
+              {{ providerStep(c).label }}
             </Button>
             <button type="button" class="flex size-7 items-center justify-center rounded text-foreground/40 hover:text-rose-600 hover:bg-rose-500/10" :title="t('integration.credentials.list.action.delete.aria', { name: c.name })" :aria-label="t('integration.credentials.list.action.delete.aria', { name: c.name })" @click="pendingDelete = c">
               <TrashBin :size="13" />

package/dist/runtime/pages/integrations/schedules.vue

@@ -147,16 +147,16 @@ const columns = computed(() => [
                  at several named times is a long sentence, and half of one is
                  the wrong half. Its title is the expression, so there is no
                  tooltip left to carry the rest of the words. -->
-            <div v-if="describeCron(e.cron)" :aria-label="t('integration.schedules.cell.whenItFires.aria')" :title="e.cron ?? void 0" class="text-sm leading-snug">
+            <div v-if="describeCron(e.cron)" :title="e.cron ?? void 0" class="text-sm leading-snug">
               {{ describeCron(e.cron) }}
             </div>
             <template v-else-if="e.cron">
-              <div :aria-label="t('integration.schedules.cell.whenItFires.aria')" class="text-sm truncate">
+              <div class="text-sm truncate">
                 {{ t("integration.schedules.cell.customSchedule") }}
               </div>
-              <code :aria-label="t('integration.schedules.cell.cronExpression.aria')" class="block font-mono text-xs text-muted-foreground truncate">{{ e.cron }}</code>
+              <code class="block font-mono text-xs text-muted-foreground truncate">{{ e.cron }}</code>
             </template>
-            <div v-else :aria-label="t('integration.schedules.cell.whenItFires.aria')" class="text-sm text-muted-foreground truncate">
+            <div v-else class="text-sm text-muted-foreground truncate">
               {{ t("integration.schedules.cell.noSchedule") }}
             </div>
           </div>
@@ -170,12 +170,13 @@ const columns = computed(() => [
         </template>
 
         <!--
-          The two time cells carry the name their column header states, so each is
-          addressable by what it is rather than by how it is typeset. It is not the
-          accessible name a screen reader hears — the cell is a plain span, and
-          ARIA prohibits naming a generic element — that needs row and cell
-          semantics in the shared table (PO-233, and a gap in
-          `specs/accessibility.md`).
+          Neither time cell carries a name of its own, and that is the fix rather
+          than an omission. Since studio-shared 0.3.2 the cell is a `role="cell"`
+          under a `columnheader`, so a screen reader reads "Next run, in 5h" from
+          the table itself. A name written here would be read *instead of* the
+          value — the row announced "Next run" where the time should be — so the
+          labels these cells used to carry to be addressable by a test were
+          removed with the semantics that replaced them (PO-233).
         -->
         <!--
           The instant the platform holds, shown as a distance from now, with the
@@ -187,7 +188,6 @@ const columns = computed(() => [
         -->
         <template #cell-nextRun="{ row: e }">
           <span
-            :aria-label="t('integration.schedules.table.column.nextRun')"
             :title="e.nextRunLocal ?? void 0"
             class="text-sm tabular-nums"
           >{{ formatRelative(e.nextRunAt, e.timezone) }}</span>
@@ -202,7 +202,6 @@ const columns = computed(() => [
         -->
         <template #cell-lastRun="{ row: e }">
           <span
-            :aria-label="t('integration.schedules.table.column.lastRun')"
             :title="e.lastRunAt ?? void 0"
             class="text-sm tabular-nums text-muted-foreground"
           >{{ lastRunText(e) }}</span>

package/dist/runtime/pages/integrations/workflows/[id].vue

@@ -46,8 +46,6 @@ import { BUILD_SETTLE_POLL_MS, BUILD_SETTLE_TIMEOUT_MS, createBuildSettle, isBui
 import { splitRunOutputs } from "../../../utils/runOutputs";
 import { isTerminalRun, unwrapRun } from "../../../utils/runEnvelope";
 import { findingsSummary, groupFindingsByNode, nodeDisplayLabel } from "../../../utils/validationFindings";
-import { unwiredErrorPorts } from "../../../utils/errorPathAdvice";
-import { newestExecutableVersion } from "../../../data/integrationNodeCatalog";
 import { payloadFieldsFromBlob } from "../../../data/payloadForm";
 import WorkflowIconView from "../../../components/Integrations/WorkflowIconView.vue";
 const t = useIntegrationsT();
@@ -110,27 +108,6 @@ async function revealNode(nodeId) {
   await nextTick();
   editorRef.value?.revealNode(nodeId);
 }
-const errorPathAdvice = computed(() => {
-  const blob = shownBlob.value;
-  if (!blob) return [];
-  const byId = new Map(blob.nodes.map((n) => [n.id, n]));
-  return unwiredErrorPorts(blob).flatMap((a) => {
-    const node = byId.get(a.nodeId);
-    return node ? [{ ...a, label: nodeDisplayLabel(node) }] : [];
-  });
-});
-const adviceExpanded = ref(false);
-const canAttachErrorStop = computed(() => newestExecutableVersion("revenexx:stop-and-error") !== null);
-async function showNodeOnCanvas(nodeId) {
-  tab.value = "editor";
-  await nextTick();
-  editorRef.value?.showNodeOnCanvas(nodeId);
-}
-async function attachErrorStop(nodeId, port) {
-  tab.value = "editor";
-  await nextTick();
-  editorRef.value?.attachErrorStop(nodeId, port);
-}
 const { load: loadNodeCatalog } = useIntegrationsNodes();
 onMounted(() => {
   void loadNodeCatalog();
@@ -200,7 +177,6 @@ watch(id, async () => {
   if (!w) await leaveTo("/integrations/workflows");
   draft.value = null;
   warningsExpanded.value = false;
-  adviceExpanded.value = false;
   if (tab.value === "runs") void loadRuns(1);
   settleBuildStatus();
 }, { immediate: true });
@@ -1017,62 +993,6 @@ function formatDateTime(iso) {
         </ul>
       </div>
 
-      <!-- Error-path advice (PO-443, specs/workflow-advice.md).
-           Slate, NOT amber: amber already means "fix this before it runs" twice
-           over in this editor (the reauth strip, the validation banner) and on
-           the node cards, so a third would leave the colour meaning nothing.
-           This blocks nothing — the activation control stays operable while it
-           shows, which is the point of it not being a finding.
-
-           Editor tab only, unlike the validation banner above: every line here
-           acts on the canvas — reveal a card, attach a step to it — so over the
-           run list or the history preview it offers moves to a canvas that is not
-           on screen, and its node names read as part of whatever is. That is not
-           hypothetical: it put a current node's name over a preview of an
-           archived revision (workflow-history.md AC-3). -->
-      <div
-        v-if="tab === 'editor' && !openRunId && errorPathAdvice.length"
-        class="border-b border-slate-500/20 bg-slate-500/5 px-4 py-2 text-sm text-slate-700"
-      >
-        <p class="font-medium">
-          {{ t("integration.editor.errorPath.advice", errorPathAdvice.length) }}
-        </p>
-        <ul
-          class="mt-1 space-y-0.5"
-          :class="adviceExpanded ? 'max-h-36 overflow-y-auto pr-1' : ''"
-        >
-          <li
-            v-for="a in adviceExpanded ? errorPathAdvice : errorPathAdvice.slice(0, WARN_COLLAPSED)"
-            :key="`${a.nodeId}-${a.port}`"
-            class="flex items-baseline gap-1.5"
-          >
-            <span class="select-none text-slate-400">•</span>
-            <button
-              type="button"
-              class="text-left font-medium underline decoration-transparent underline-offset-2 hover:decoration-slate-700"
-              :aria-label="t('integration.editor.errorPath.ariaReveal', { label: a.label, port: a.port })"
-              @click="showNodeOnCanvas(a.nodeId)"
-            >
-              {{ a.label }}
-            </button>
-            <button
-              v-if="canAttachErrorStop"
-              type="button"
-              class="text-slate-600 underline underline-offset-2 hover:text-slate-900"
-              :aria-label="t('integration.editor.errorPath.ariaFix', { label: a.label, port: a.port })"
-              @click="attachErrorStop(a.nodeId, a.port)"
-            >
-              {{ t("integration.editor.errorPath.action.stop") }}
-            </button>
-          </li>
-          <li v-if="!adviceExpanded && errorPathAdvice.length > WARN_COLLAPSED" class="pl-3">
-            <button type="button" class="text-slate-600 underline underline-offset-2 hover:text-slate-900" @click="adviceExpanded = true">
-              {{ t("integration.editor.errorPath.more", { n: errorPathAdvice.length - WARN_COLLAPSED }) }}
-            </button>
-          </li>
-        </ul>
-      </div>
-
       <!-- Only the FAILED build state banners (its message matters); the
            working states live as the header chip — and inside a run the
            workflow's build state is noise, so nothing shows at all. -->

package/dist/runtime/utils/cockpitSources.d.ts

@@ -65,6 +65,23 @@
  * Two members exist here only because the code reads them off values the cockpit
  * may hand back as `null`: `getCredential` and `createCredential` both resolve to
  * `MailCredential | null`, and the callers have to say what they do about it.
+ *
+ * **What "narrowed to the members it reads" costs when it is wrong, measured on
+ * `sftp` (PO-387).** This declaration was five members behind what
+ * `SftpAccountImportDialog.vue` actually reads — `loading`, `activeTenantSlug`,
+ * an optional rather than required argument to `load`, and `server` and
+ * `home_directory` on an account. The cockpit has had all five throughout
+ * (`app/composables/useConsoleSftp.ts`, `app/types/consoleSftp.ts`), so nothing
+ * was ever broken for an operator; what was broken is that the playground's
+ * double is built from *this* file, so a host honouring the written contract
+ * threw `TypeError: Cannot read properties of undefined (reading 'value')` while
+ * drawing that dialog. **Vue's error handler turns such a throw into a
+ * `console.error` and unmounts the tree, so no `pageerror` fires** — the suite's
+ * usual way of catching this class (`e2e/credential-managed-source.spec.ts`,
+ * `pageErrors`) cannot see it, and the only evidence is a blank page. The dialog
+ * now takes its type from here (`Pick<CockpitSources['sftp'], …>`) rather than
+ * declaring its own, so the two cannot disagree again; nothing yet compares
+ * either against the cockpit, which is [PO-310](https://linear.app/revenexx/issue/PO-310).
  */
 export interface CockpitSources {
     tenants: {
@@ -102,7 +119,53 @@ export interface CockpitSources {
         accounts: {
             value: CockpitSftpAccount[];
         };
-        load: (tenant: string | null) => Promise<unknown>;
+        /**
+         * True while the cockpit's **account fetch** is in flight — which is narrower
+         * than "this source is busy", and a caller that needs the wider question has
+         * to keep its own answer beside this one.
+         *
+         * `useConsoleSftp.load()` resolves the tenant above the flag
+         * (`if (!tenantSlug) await loadTenants()` sits before `loading.value = true`),
+         * and leaves by two paths that never set it at all: no tenant resolved, and a
+         * load already in flight for another surface. `SftpAccountImportDialog.vue`
+         * learned this the expensive way — it drew its "there are none, go and create
+         * one" empty state throughout the tenants fetch on every first open.
+         */
+        loading: {
+            value: boolean;
+        };
+        /**
+         * Why the last account fetch failed, or `null`.
+         *
+         * The cockpit catches its own fetch errors — `load` never rejects — so this
+         * is the **only** way a caller learns the list is missing rather than empty.
+         * Without it a failed load and a tenant that owns no account are the same
+         * screen, and that screen tells the operator to go and create one.
+         *
+         * **Optional, and the only member here that is.** The standalone dev studio's
+         * stand-ins provide the other four and not this one
+         * (`integrations/studio-ui/app/composables/consoleStubs.ts`), so a required
+         * member would be this file's own defect a second time — PO-387 is exactly a
+         * dialog that dereferenced what a host did not have. Its absence costs only
+         * the message: a caller reading it with `?.` falls back to the empty state,
+         * which is what such a host showed before. A host that means to keep
+         * `specs/node-configuration.md` AC-34 has to provide it.
+         *
+         * It is also **not a verdict on the load that just returned.** It is a
+         * `useState` singleton shared by every surface in the host, and both early
+         * returns described under `loading` leave it at whatever it already held —
+         * so it can be stale and can be somebody else's. `SftpAccountImportDialog.vue`
+         * shows how much has to be true around it before it is worth repeating.
+         */
+        error?: {
+            value: string | null;
+        };
+        /** The tenant the accounts belong to — the org's only one, or `null`. */
+        activeTenantSlug: {
+            value: string | null;
+        };
+        /** The argument is **optional**: omitted, the cockpit falls back to `activeTenantSlug`. */
+        load: (tenant?: string | null) => Promise<unknown>;
         /** `null` while the account is still provisioning (the Console answers 404). */
         revealPassword: (tenant: string, id: number) => Promise<{
             username: string;
@@ -131,6 +194,10 @@ export interface CockpitSftpAccount {
     id: number;
     /** The gateway login. `null` until the account finished provisioning. */
     login_username: string | null;
+    /** The gateway host to connect to. */
+    server: string | null;
+    /** Where on the gateway the account lands; shown instead of `server` when set. */
+    home_directory: string | null;
     status: string;
     is_active: boolean;
     error_message: string | null;

package/dist/runtime/utils/credentialState.d.ts

@@ -28,6 +28,21 @@ export interface CredentialStateInfo {
 }
 type TestableCredential = Pick<Credential, 'status' | 'last_test_ok' | 'last_test_at' | 'last_test_message'>;
 /** Every state a credential can be in, in the order a reader is offered them. */
+/**
+ * Which of the two words a three-legged credential's provider step is offered under,
+ * or `null` where its state gives no reason to offer one at all.
+ *
+ * The distinction is whether anything has ever proved this credential connected. Only
+ * a credential nothing has — never tested, and for an `oauth2-authcode` type that is
+ * what a provider window which failed to open leaves behind — is offered the step as
+ * *connecting*. One whose test failed, or whose authorisation expired, was working at
+ * some point, so it is offered *reconnecting*: the word says which of the two happened
+ * (PO-478).
+ *
+ * It answers for a state rather than a credential because both surfaces that offer the
+ * step derive that state first, and the word may not disagree between them.
+ */
+export declare function providerStepWord(state: CredentialConnState): 'connect' | 'reconnect' | null;
 export declare const CREDENTIAL_STATES: readonly ["connected", "failed", "needs_reauth", "untested"];
 /**
  * What a state is called for the reader, keyed rather than derived from a

package/dist/runtime/utils/credentialState.js

@@ -1,4 +1,8 @@
 import { useIntegrationsT } from "../composables/useIntegrationsT.js";
+export function providerStepWord(state) {
+  if (state === "connected") return null;
+  return state === "untested" ? "connect" : "reconnect";
+}
 export const CREDENTIAL_STATES = ["connected", "failed", "needs_reauth", "untested"];
 const MESSAGE_KEY = {
   connected: "integration.credentials.state.connected",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@revenexx/studio-integrations",
-  "version": "1.4.1",
+  "version": "2.0.0",
   "type": "module",
   "description": "Integration Studio (core: workflows, node editor, runs, schedules, credentials, secrets, audit) as a standalone, publishable Nuxt module.",
   "repository": {
@@ -26,13 +26,13 @@
   },
   "dependencies": {
     "@nuxt/kit": "^4.0.0",
-    "@revenexx/studio-shared": "^0.3.0",
+    "@revenexx/studio-shared": "^0.3.2",
     "@solar-icons/nuxt": "^1.2.0",
     "marked": "^18.0.5"
   },
   "peerDependencies": {
     "@dagrejs/dagre": "^3.0.0",
-    "@revenexx/studio": "*",
+    "@revenexx/studio": "^0.2.3",
     "@tiptap/core": "^3.28.0",
     "@tiptap/extension-document": "^3.28.0",
     "@tiptap/extension-history": "^3.28.0",

package/dist/runtime/utils/errorPathAdvice.d.ts

@@ -1,60 +0,0 @@
-import type { WorkflowBlob } from '../types/integrations.js';
-/**
- * Nodes that route failures to an error output nothing is connected to
- * (specs/workflow-advice.md).
- *
- * A step that fails on a path its author drew is handled. A step that fails on a
- * path nobody drew is not: the engine ends the run there
- * (`specs/node-failure-handling.md` AC-8 in the service repository), and before
- * it did, the failure vanished and the run reported success. Either way the
- * author never chose it — they simply never saw the port.
- *
- * ## Why this is advice and not a finding
- *
- * The backend's validation findings feed the activation gate AND an
- * unconditional refusal to start a run. A finding here would therefore stop
- * every workflow with an unwired error port from running at all — turning
- * "delivers nothing quietly" into "does not start", for authors who never asked
- * for either. Computing it in the editor makes that impossible rather than
- * merely unlikely: there is no value for a blocking consumer to read.
- *
- * What the client cannot do is be authoritative — the catalogue may not be
- * loaded, and a workflow built through the API never passes here at all. For
- * advice that is the right trade; for a gate it would not be, which is why the
- * gate stays where the manifests are.
- *
- * ## Deliberately not in `validationFindings.ts`
- *
- * Everything there is a backend finding addressed by blob path, and the node
- * card counts those as *incomplete settings*. An unwired port is neither. Sent
- * through `groupFindingsByNode` it would type-check perfectly and quietly
- * corrupt two counts — the banner's and the card badge's.
- */
-export interface ErrorPathAdvice {
-    /** Blob node id — not an index, so it survives a node being added or removed. */
-    nodeId: string;
-    /** The error output with nothing attached. */
-    port: string;
-}
-/**
- * Every unwired error output in the blob, in node order.
- *
- * Runs against the blob the author is *editing*, not the saved one, so wiring a
- * port clears its line in the same tick — no save, and no second copy of this
- * rule to decide when the advice went stale.
- *
- * **Resolved against whichever manifest version the catalogue has.**
- * `findManifest` falls back to another version of the same slug when the pinned
- * one is absent, and that fallback is accepted here: a node pinned to a version
- * nobody serves any more is better described by a sibling version than by
- * silence. The cost is real though — where the versions disagree about their
- * ports, the advice describes the sibling's, so a port could be named that the
- * author's own node does not have.
- *
- * **Reads the manifest's static outputs only.** A node whose ports are named at
- * author time (`sourceFromConfig` / `resolveOutputs`) cannot be judged from the
- * declaration alone, so nothing is claimed about it — the same forbearance the
- * engine shows. No shipped node has a dynamic error port today; if one appears,
- * this is where it would silently escape notice.
- */
-export declare function unwiredErrorPorts(blob: Pick<WorkflowBlob, 'nodes' | 'edges'>): ErrorPathAdvice[];

package/dist/runtime/utils/errorPathAdvice.js

@@ -1,19 +0,0 @@
-import { findManifest } from "../data/integrationNodeCatalog.js";
-export function unwiredErrorPorts(blob) {
-  const advice = [];
-  for (const node of blob.nodes) {
-    const manifest = findManifest(node.nodeSlug, node.nodeVersion);
-    if (!manifest) continue;
-    const errorPorts = (manifest.outputs ?? []).filter((o) => o.kind === "error" && o.name).map((o) => o.name);
-    if (!errorPorts.length) continue;
-    if (!isReachable(node, blob, errorPorts)) continue;
-    for (const port of errorPorts) {
-      const wired = blob.edges.some((e) => e.from.nodeId === node.id && e.from.output === port);
-      if (!wired) advice.push({ nodeId: node.id, port });
-    }
-  }
-  return advice;
-}
-function isReachable(node, blob, errorPorts) {
-  return blob.edges.some((e) => e.to.nodeId === node.id) || blob.edges.some((e) => e.from.nodeId === node.id && !errorPorts.includes(e.from.output));
-}