@anchrd/intel-ui 0.36.0 → 0.37.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@anchrd/intel-ui",
-  "version": "0.36.0",
+  "version": "0.37.0",
   "type": "module",
   "license": "UNLICENSED",
   "repository": {

package/src/app/view-toggle/view-toggle.tsx

@@ -1,10 +1,15 @@
 import { useNavigate, useRouterState } from "@tanstack/react-router";
-import { History, Network, PencilRuler } from "lucide-react";
+import { ListChecks, Network, PencilRuler } from "lucide-react";
 import { Tooltip, TooltipContent, TooltipProvider, TooltipTrigger } from "@/components/ui/tooltip";
 import { useI18n } from "@/i18n/i18n-context.tsx";
 import { type IntelView, viewFrom } from "@/router/selection-search.ts";
 
-const icons = { editor: PencilRuler, graph: Network, runs: History } as const;
+// ⚠️ `runs` is NOT `History`, and that is the point of this line rather than a taste in icons.
+// `History` is what the resource menu draws beside "Version history" (`resource-menu.tsx`), and both
+// are visible on the same flow header — one as this switch, one in the menu right below it. The same
+// clock for two different things was read as one: the switch was taken for the version history and
+// asked about as such (#635). Whatever stands here has to stay out of that menu.
+const icons = { editor: PencilRuler, graph: Network, runs: ListChecks } as const;
 const labels = {
   editor: "view.showEditor",
   graph: "view.showGraph",

package/src/flows/flows.tsx

@@ -675,6 +675,7 @@ function FlowsEditor() {
           saving={save.isPending}
           canMutate={canMutate}
           incomplete={stepsMissingServer.map((node) => ({ label: node.data.node.label }))}
+          scrollingView={selection.view === "runs"}
           onSave={() => save.mutate()}
           onPublish={() => setPublishing(true)}
         />
@@ -943,6 +944,7 @@ function FlowTitle({
   saving,
   canMutate,
   incomplete,
+  scrollingView,
   onSave,
   onPublish,
 }: {
@@ -950,6 +952,9 @@ function FlowTitle({
   dirty: boolean;
   saving: boolean;
   canMutate: boolean;
+  // Whether what stands below this line can scroll under it. The runs list can and earns its edge
+  // the usual way; the canvas and the graph pan instead, and would never get one (#634).
+  scrollingView: boolean;
   // Tool steps that name no server yet. They cannot be saved, so the refusal is shown here rather
   // than fetched from the server as a message that names no step.
   incomplete: Array<{ label: string }>;
@@ -974,7 +979,12 @@ function FlowTitle({
     // loudest thing in this line and used to hold the edge; the menu takes it, because a menu one can
     // hit without looking is worth more than the primary button being outermost. `TitleRow` is what
     // enforces that — nothing passed in here can get past the menu.
-    <TitleRow title={flow.title} description={flow.description} target={{ type: "flow", flow }}>
+    <TitleRow
+      title={flow.title}
+      description={flow.description}
+      target={{ type: "flow", flow }}
+      separated={!scrollingView}
+    >
       {/* ⚠️ #454: the toggle used to stand in the global header, beside the search — where what
           applies EVERYWHERE stands. But it says how THIS flow is shown, and so belongs in the line
           that names this flow. A flow is the only level with runs, and therefore the only one with

package/src/i18n/de.json

@@ -75,7 +75,6 @@
   "resource.archive": "Archivieren",
   "resource.columns": "Spalten",
   "resource.export": "Export",
-  "resource.exportExcludes": "Nimmt den aktuellen Stand mit. Frühere Versionen, Freigaben und Flow-Läufe bleiben zurück. Von einem veröffentlichten Flow reist der veröffentlichte Graph — spätere Änderungen am Entwurf bleiben zurück.",
   "resource.import": "Import",
   "resource.validate": "Prüfen",
   "resource.links": "Verweise",

package/src/i18n/en.json

@@ -75,7 +75,6 @@
   "resource.archive": "Archive",
   "resource.columns": "Columns",
   "resource.export": "Export",
-  "resource.exportExcludes": "Carries the current state. Earlier versions, shares and flow runs stay behind. A published flow travels as its published graph — changes drafted since stay behind.",
   "resource.import": "Import",
   "resource.validate": "Check",
   "resource.links": "Links",

package/src/i18n/es.json

@@ -75,7 +75,6 @@
   "resource.archive": "Archivar",
   "resource.columns": "Columnas",
   "resource.export": "Exportar",
-  "resource.exportExcludes": "Se lleva el estado actual. Las versiones anteriores, los permisos y las ejecuciones de flujo se quedan. Un flujo publicado viaja con su grafo publicado; los cambios redactados después se quedan.",
   "resource.import": "Importar",
   "resource.validate": "Comprobar",
   "resource.links": "Enlaces",

package/src/resource-menu/resource-menu.tsx

@@ -18,7 +18,7 @@ import {
   ShieldCheck,
 } from "lucide-react";
 import type * as React from "react";
-import { useId, useState } from "react";
+import { useState } from "react";
 import { AccessSummary } from "@/access-summary/access-summary.tsx";
 import { allTreeLevelsKey, moveErrorKey, useTreeMove } from "@/app/tree-move/tree-move.tsx";
 import {
@@ -154,11 +154,6 @@ export function ResourceMenu({
   // nowhere else: a person had strictly less reach on their own table than a model did.
   const isTable = node !== null && node.kind === "table";
   const bundleImport = useBundleImport({ where: title });
-  // ⚠️ Per instance, not a constant: the folder table renders one menu PER ROW, so a fixed id would
-  // put the same `id` in the document twenty times and every entry's name would resolve to the
-  // first one's.
-  const exportLabelId = useId();
-  const exportHintId = useId();
 
   // Everything a change here can make stale. The row sits in one level of the tree, the open screen
   // reads the record, and the flat collections behind the search, the link picker and the relation
@@ -323,38 +318,17 @@ export function ResourceMenu({
               (#534). That is the export's gap on every kind it can hit, not something this entry
               was covering — which is why it is fixed there and not by keeping a second entry.
 
-              ⚠️ The second line is not decoration and it belongs HERE rather than after the click
-              (#433, ADR-0006). A bundle carries one version per node; whoever moves an installation
-              this way loses every earlier one, and until now the only place that said so was
-              `excluded` in a `manifest.json` inside the zip — read, if ever, long after the source
-              installation is gone. A loss that cannot be undone has to be readable BEFORE the
-              gesture, and a menu item is where this gesture is chosen.
-
-              ⚠️ Its third clause is the flow half (#585), and it is a DIFFERENT loss from the first
-              two rather than an example of them: a published flow travels as its published graph,
-              so edits drafted since do not travel at all. Those edits are not an earlier version —
-              they are the newest state there is, and somebody reading only "earlier versions stay
-              behind" would expect the opposite of what happens. `Excluded` in `bundle.ts` names it
-              with a word of its own for the same reason.
-
-              ⚠️ It is the entry's DESCRIPTION, not part of its name: `aria-labelledby` keeps the
-              name at the one word every other entry here uses, and `aria-describedby` is what a
-              screen reader reads after it. Folding a whole sentence into the name would make this
-              the only entry in the menu somebody has to listen through to know what it does — and
-              the sentence is a condition of the action, which is what a description is for. */}
-          <DropdownMenuItem
-            className="items-start"
-            aria-labelledby={exportLabelId}
-            aria-describedby={exportHintId}
-            onSelect={() => exportBundle.mutate()}
-          >
-            <FolderDown aria-hidden="true" className="mt-0.5" />
-            <span className="flex flex-col gap-0.5">
-              <span id={exportLabelId}>{i18n.t("resource.export")}</span>
-              <span id={exportHintId} className="text-xs text-muted-foreground">
-                {i18n.t("resource.exportExcludes")}
-              </span>
-            </span>
+              ⚠️ The entry carried a three-clause description under its name until 2026-08-19, put
+              there by #433/ADR-0006 so that an irreversible loss was readable BEFORE the gesture: a
+              bundle takes one version per node, shares and runs stay behind, and a published flow
+              travels as its published graph (#585). Jack removed it — it was the only entry running
+              over two lines and it pushed the menu apart. What the reader now gets instead is
+              `excluded` in the zip's `manifest.json` and `BundleImportResult.excluded` after an
+              import, both of which are read only once the zip exists. That is a deliberate trade,
+              recorded in ADR-0006 and in #636, and NOT a leftover to be restored. */}
+          <DropdownMenuItem onSelect={() => exportBundle.mutate()}>
+            <FolderDown aria-hidden="true" />
+            {i18n.t("resource.export")}
           </DropdownMenuItem>
           {/* The other half of the same round trip, next to it rather than in the tree's plus
               (#346): one word in the menu, both sources under it. */}

package/src/title-row/title-row.tsx

@@ -69,11 +69,22 @@ export function TitleRow({
   title,
   description,
   target,
+  separated,
   children,
 }: {
   title: string;
   description?: string | null;
   target: ResourceTarget;
+  /**
+   * A separator that does NOT wait for a scroll.
+   *
+   * ⚠️ For a surface where scrolling cannot happen, and that is the only case it is for (#634). The
+   * edge below this row is normally `scrolled`, set by `TitleRowScrollArea` — which is right where
+   * content moves under the row. The flow canvas does not scroll, it pans: nothing ever sets
+   * `scrolled`, so the row sat on the dark canvas with no edge at all. Do not pass this where the
+   * content does scroll; a permanent edge there would replace a signal with decoration.
+   */
+  separated?: boolean;
   children?: ReactNode;
 }) {
   const scroll = useContext(TitleRowScrollContext);
@@ -88,7 +99,7 @@ export function TitleRow({
       data-scrolled={scroll?.scrolled || undefined}
       className={cn(
         "relative z-10 flex shrink-0 items-start justify-between gap-5 px-6 py-4 transition-shadow",
-        scroll?.scrolled && "shadow-[inset_0_-1px_0_var(--border)]",
+        (separated || scroll?.scrolled) && "shadow-[inset_0_-1px_0_var(--border)]",
       )}
     >
       <div className="flex min-w-0 items-center gap-3">