@artemis-studio/plugin-sdk 2026.9.50 → 2026.9.52

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artemis-studio/plugin-sdk",
-  "version": "2026.9.50",
+  "version": "2026.9.52",
   "description": "Build the UI of an Artemis Studio plugin: typings for the Studio APIs a plugin may use, and a Vite preset.",
   "license": "Apache-2.0",
   "repository": {

package/types/kernel/api/polling.d.ts

@@ -1,17 +1,12 @@
-import type { Query, QueryClient } from '@tanstack/react-query';
+import { type Query, type QueryClient } from '@tanstack/react-query';
 /**
- * `refetchInterval` for a hook that should stop polling while paused.
+ * Make TanStack's focus state mean "may refresh on its own": the tab is visible and
+ * refreshing is not paused. Called once, beside the `QueryClient`.
  *
- * Returning `false` suspends the interval; TanStack Query calls this again on the
- * next cycle, so resuming needs no remount.
- *
- * ponytail: the interval is re-resolved when the *current* timer fires, so one
- * further poll can land up to `ms` after pausing. Closing that gap means
- * cancelling in-flight fetches, which throws away work the operator did not ask
- * to discard and can leave a screen mid-update. Accepted and recorded in
- * ADR-0055; revisit only if an operator can actually observe it.
+ * A side effect: the retryer also waits for focus, so a request that fails while
+ * paused retries on resume rather than during the pause.
  */
-export declare function poll(ms: number | false): () => number | false;
+export declare function installPauseSeam(): void;
 /**
  * `refetchOnMount` for the QueryClient default, so pausing covers opening a view
  * and not only the intervals.
@@ -32,19 +27,11 @@ export declare function markPendingChange(): void;
 export declare function usePollingPaused(): boolean;
 export declare function usePendingChange(): boolean;
 /**
- * Refetch everything the current screen is observing, and resolve when it is done.
- *
- * `refetchType: 'active'` is the point: it refetches what is on the display and
- * leaves the rest of the cache alone — the same scope the freshness indicator
- * reports on, so the button and the label can never disagree.
- *
- * `cancelRefetch: false` is the other point. TanStack's default aborts the
- * in-flight fetch and starts another, which is right after a mutation (the
- * in-flight response is known-stale) and wrong for a refresh control (the
- * in-flight response is exactly what was asked for). With it, a second activation
- * joins the first instead of restarting it.
+ * Refetch everything the current screen is observing: what resuming does, because the
+ * first thing an operator needs after unpausing is current data.
  *
- * The returned promise is what lets the control show *the operator's* refresh
- * rather than every background poll.
+ * `refetchType: 'active'` scopes it to what is on the display, the same scope the
+ * freshness indicator reports on. `cancelRefetch: false` lets a fetch already in
+ * flight finish rather than aborting it for an identical one.
  */
 export declare function refreshActiveQueries(qc: QueryClient): Promise<void>;

package/types/kernel/api/schema.d.ts

@@ -596,22 +596,6 @@ export interface paths {
         patch?: never;
         trace?: never;
     };
-    "/api/v1/clusters/{clusterId}/rediscover": {
-        parameters: {
-            query?: never;
-            header?: never;
-            path?: never;
-            cookie?: never;
-        };
-        get?: never;
-        put?: never;
-        post: operations["rediscover"];
-        delete?: never;
-        options?: never;
-        head?: never;
-        patch?: never;
-        trace?: never;
-    };
     "/api/v1/clusters/{clusterId}/queues": {
         parameters: {
             query?: never;
@@ -6669,28 +6653,6 @@ export interface operations {
             };
         };
     };
-    rediscover: {
-        parameters: {
-            query?: never;
-            header?: never;
-            path: {
-                clusterId: string;
-            };
-            cookie?: never;
-        };
-        requestBody?: never;
-        responses: {
-            /** @description OK */
-            200: {
-                headers: {
-                    [name: string]: unknown;
-                };
-                content: {
-                    "*/*": components["schemas"]["TopologyView"];
-                };
-            };
-        };
-    };
     queues: {
         parameters: {
             query: {

package/types/kernel/shell/ColorSchemeToggle.d.ts

@@ -0,0 +1,8 @@
+/**
+ * Light or dark, from the header. Mantine's own manager remembers the choice in this
+ * browser; dark stays the first-visit default (`main.tsx`).
+ *
+ * The name says where the control goes, not where it is: an operator reading
+ * "Switch to light theme" knows what activating it will do.
+ */
+export declare function ColorSchemeToggle(): import("react").JSX.Element;

package/types/kernel/shell/CommandPalette.d.ts

@@ -8,8 +8,7 @@
  * A view the operator may not open is still listed, disabled, with the reason: the rail shows it the
  * same way.
  *
- * Refresh and pause live here rather than on a hotkey: the browser owns both
- * shortcuts an operator would reach for (⌘R and ⇧⌘R), and taking either would be
- * worse than not having one (ADR-0052).
+ * Pause and the colour scheme are here too, so every header control is reachable from the keyboard
+ * without a hotkey of its own (ADR-0052, ADR-0118).
  */
 export declare function CommandPalette(): import("react").JSX.Element;

package/types/kernel/shell/useColorSchemeToggle.d.ts

@@ -0,0 +1,5 @@
+/** The toggle and its name, shared with the command palette's entry. */
+export declare function useColorSchemeToggle(): {
+    toggle: () => void;
+    label: string;
+};

package/types/sdk/index.d.ts

@@ -20,7 +20,7 @@ export { gateFor, type GateVerdict } from '../ui/capabilityGate.ts';
 export { useMe } from '../kernel/auth/api.ts';
 export { CodeEditor, type CodeDiagnostic, type CodeEditorProps } from '../ui/CodeEditor.tsx';
 export { ConfirmByTyping } from '../ui/ConfirmByTyping.tsx';
-export { DiagramView, type DiagramEdge, type DiagramNode, type DiagramViewProps } from '../ui/DiagramView.tsx';
+export { DiagramView, type DiagramAction, type DiagramChoice, type DiagramEdge, type DiagramNode, type DiagramViewProps } from '../ui/DiagramView.tsx';
 export { NodeOutcomeSummary, OutcomeSummary, type OutcomeRow } from '../ui/NodeOutcomeSummary.tsx';
 export { Pager } from '../ui/Pager.tsx';
 export { VirtualTable, type GridColumn } from '../ui/VirtualTable.tsx';

package/types/ui/DiagramView.d.ts

@@ -1,5 +1,5 @@
-import { type DiagramEdge, type DiagramNode } from './diagram.ts';
-export type { DiagramEdge, DiagramNode };
+import { type DiagramAction, type DiagramChoice, type DiagramEdge, type DiagramNode } from './diagram.ts';
+export type { DiagramAction, DiagramChoice, DiagramEdge, DiagramNode };
 export interface DiagramViewProps {
     nodes: DiagramNode[];
     edges: DiagramEdge[];
@@ -7,19 +7,29 @@ export interface DiagramViewProps {
     onSelect?: (id: string) => void;
     /** Which way the arrows run. Default: down. */
     direction?: 'DOWN' | 'RIGHT';
-    /** The frame's height in pixels. Default 480. */
-    height?: number;
+    /** The frame's height: pixels, or any CSS length such as '100%' to fill a sized parent. Default 480. */
+    height?: number | string;
     /** Names the diagram for screen readers. */
     'aria-label': string;
+    /** What can be inserted on an arrow marked `insertable`. With `onInsert`, each such arrow offers them. */
+    insertChoices?: DiagramChoice[];
+    /** A choice was made on an arrow. The diagram changes nothing itself. */
+    onInsert?: (edgeId: string, value: string) => void;
+    /** The actions a box offers in its menu. With `onNodeAction`, every box that has some offers them. */
+    nodeActions?: (node: DiagramNode) => DiagramAction[];
+    /** An action was chosen on a box. The diagram changes nothing itself. */
+    onNodeAction?: (nodeId: string, actionId: string) => void;
 }
 /**
- * A read-only diagram of boxes and arrows, laid out automatically (ELK layered, in a worker) and
- * drawn in Studio's theme (ADR-0117). Nothing is dragged, connected or deleted: it shows a
- * structure and reports which box was chosen.
+ * A diagram of boxes and arrows, laid out automatically (ELK layered, in a worker) and drawn in
+ * Studio's theme (ADR-0117). Nothing is dragged, connected or deleted: it shows a structure and
+ * reports which box was chosen. A caller may offer things to insert on arrows and actions on boxes
+ * (ADR-0120); the diagram reports the choice and the caller changes the nodes.
  *
  * <p>The diagram is one tab stop. Arrow keys move between boxes in reading order, Enter or Space
  * selects one, and the selection is announced. A box with a problem says so in words, on the box
  * and in its accessible name, so colour is never the only signal. Positions change only when the
- * boxes or arrows do, never when a label does.
+ * boxes or arrows do, never when a label does. A box's actions open from its "⋯", a right-click,
+ * or Shift+F10; Insert on a box offers what can go on the arrows into it.
  */
-export declare function DiagramView({ nodes, edges, selectedId, onSelect, direction, height, 'aria-label': ariaLabel, }: DiagramViewProps): import("react").JSX.Element;
+export declare function DiagramView({ nodes, edges, selectedId, onSelect, direction, height, 'aria-label': ariaLabel, insertChoices, onInsert, nodeActions, onNodeAction, }: DiagramViewProps): import("react").JSX.Element;

package/types/ui/diagram.d.ts

@@ -21,6 +21,24 @@ export interface DiagramEdge {
     label?: string;
     /** Drawn dashed: a secondary path. Its meaning belongs in its label. */
     dashed?: boolean;
+    /** Something can be inserted on this arrow: it offers the diagram's `insertChoices`. */
+    insertable?: boolean;
+}
+/** One thing a `DiagramView` offers to insert on an arrow ("Call a service"). */
+export interface DiagramChoice {
+    value: string;
+    label: string;
+    /** A heading the choice is listed under. */
+    group?: string;
+}
+/** One action in a box's menu. The diagram only reports it: the caller changes the nodes. */
+export interface DiagramAction {
+    id: string;
+    label: string;
+    /** Why it cannot be taken here. It stays listed, with the reason, rather than disappearing. */
+    disabledReason?: string;
+    /** Destroys something: shown in the danger colour. The label still says so in words. */
+    danger?: boolean;
 }
 /** What positions depend on: which nodes exist and how they connect. A new label moves nothing. */
 export declare function layoutSignature(nodes: DiagramNode[], edges: DiagramEdge[], direction: string): string;