@xenosystem/agent-interface-panel 0.1.50 → 0.1.67

package/dist/index.d.ts

@@ -0,0 +1,116 @@
+/**
+ * `@xenosystem/agent-interface-panel` — the XENO Agent panel that renders the REAL interface.
+ *
+ * ONE agent surface, mounted wherever a XENO Panel host can put a tile: xeno-apps, Pixel,
+ * Motion, Canvas. Update the interface once and every host that mounts this panel gets it,
+ * because there is nothing here to keep in sync — this package contributes a mount, not a UI.
+ *
+ * ## What this is, precisely
+ *
+ * `@xenosystem/panel-agent` (xeno-core) is the GENERIC half: manifest, controller, projections,
+ * wiring, diff parsing, host-event translation. It depends on no product, which is why it lives
+ * in core, and it ships a deliberately minimal default view whose own docblock says what is not
+ * in it — no transcript, no tool timeline, no diff, no terminal.
+ *
+ * This package is the PRODUCT half. It supplies the view, and the view is the shipping XENO Agent
+ * interface itself, mounted through `@xenosystem/agent-interface-embed`.
+ *
+ * 🔴 **It renders the real interface rather than reproducing it, and that is the whole point.**
+ * `XENO AGENT PANEL - SPEC.md` D7d refuses a port: three agent UIs already exist because each
+ * began as a reasonable copy, and a fourth would drift from the day it was written. The
+ * conversation view is ~11.5k lines bound to six stores with no tests — reproducing it is not a
+ * task, it is a second product to maintain.
+ *
+ * ## What a host must supply
+ *
+ * 1. An `AgentHostClient` whose `surface` is `'panel-embed'`. The embed layer refuses a client
+ *    whose surface disagrees with the mount, deliberately — a surface that lies about which kind
+ *    it is gets the wrong chrome and the wrong lifecycle.
+ * 2. A platform bridge, installed before mount. The interface reads its data from the bridge, not
+ *    from props, exactly as it does under `hub-embed`.
+ *
+ * ⚠️ **Known limit, stated rather than hidden.** The mounted interface holds its own connection to
+ * the agent host. The panel's input ports still carry status and intents for host wiring, but they
+ * are not yet the interface's source of truth — D7c's "the panel OWNS the conversation" is only
+ * half done here. Closing it needs the interface to accept an injected session source, which does
+ * not exist today. Until it does, a host should treat this panel as the interface in a tile, and
+ * not wire a second conversation into it and expect them to agree.
+ *
+ * @packageDocumentation
+ */
+import type { PanelModule } from '@xenosystem/panel-sdk';
+import type { AgentHostClient } from '@xenosystem/agent-interface-client';
+import { type XenoAgentConversationProps } from '@xenosystem/agent-conversation';
+/**
+ * The platform bridge, structurally. Deliberately not `XenoAPI`: a panel host implements the
+ * capabilities the interface reaches and refuses the rest by name, so demanding the full type
+ * here would put back exactly the barrier this panel exists to remove.
+ */
+export type AgentPlatformBridgeLike = object;
+/**
+ * Options for {@link createXenoAgentInterfacePanel} — supply EITHER a client or a bridge.
+ *
+ * 🔴 **Two mount modes, because hosts differ in a way that is a security boundary, not a
+ * preference.**
+ *
+ * | mode | supply | for |
+ * |---|---|---|
+ * | **client** | `createClient` | a host that already holds an `AgentHostClient` — Hub, Shell, the Agent app |
+ * | **bridge** | `createBridge` | a PANEL host, which does not and must not |
+ *
+ * `AgentHostClient` takes a `transport` with a generic `request(method, input)`, so supplying one
+ * means the renderer can invoke ANY of the 141 host methods — `workspace.file.write`,
+ * `workspace.command.run`, every `workspace.pty.*` verb. That is fine in the Agent app, whose
+ * renderer is its own. It is not fine in a panel host, whose renderer runs user-authored panels.
+ * `xeno-apps`'s preload says so in its own words: the asymmetry "is the whole security design".
+ *
+ * ⚠️ The bridge mode exists because it was MEASURED to be sufficient, not assumed. Mounting the
+ * real interface against a recording bridge showed it reaches `workspace`, `agentContext` and
+ * `subagents` — platform-bridge members, not client methods — and it renders from a bridge alone.
+ * The client is the embed lifecycle; the component reads the bridge.
+ */
+export interface CreateXenoAgentInterfacePanelOptions {
+    /**
+     * Which conversation this panel opens, and how it behaves.
+     *
+     * Omitted, it opens the same personal assistant the full interface shows — from the same
+     * constants, so the panel and the desktop app open the SAME conversation rather than two that
+     * merely look alike.
+     *
+     * ⚠️ Merged OVER the defaults, so a host overrides one field without restating the rest. A host
+     * that wants a specific conversation passes `conversationId`; one embedding a project agent
+     * passes `agentId`/`agentName`/`model`.
+     */
+    conversation?: Partial<XenoAgentConversationProps>;
+    /**
+     * Build the client this panel mounts against — the EMBED path.
+     *
+     * 🔴 A FACTORY, not a client. A panel can be mounted more than once in one layout and can be
+     * closed and reopened without the host restarting; sharing a single client across those
+     * lifetimes means the second mount inherits the first one's teardown. One mount, one client.
+     *
+     * The client's `surface` must be `'panel-embed'` or the embed layer refuses the mount.
+     */
+    createClient?: () => AgentHostClient | Promise<AgentHostClient>;
+    /**
+     * Build the platform bridge this panel mounts against — the PANEL path, and the one a panel host
+     * should use.
+     *
+     * A factory for the same reason `createClient` is one. Returning `null` means this surface has no
+     * agent host, which is the ordinary state of a machine: the panel renders its own empty state
+     * rather than the host failing to start.
+     */
+    createBridge?: () => AgentPlatformBridgeLike | null | Promise<AgentPlatformBridgeLike | null>;
+    /** Called when a mount fails, so a host can surface it rather than showing an empty tile. */
+    onError?: (error: unknown) => void;
+}
+/** The surface kind this panel mounts as. */
+export declare const AGENT_PANEL_SURFACE: "panel-embed";
+/**
+ * Build the panel module: the generic agent panel, rendered by the real XENO Agent interface.
+ *
+ * @param options - How to build a client, and where to report a failed mount.
+ * @returns A `PanelModule` any XENO Panel host can register.
+ */
+export declare function createXenoAgentInterfacePanel(options: CreateXenoAgentInterfacePanelOptions): PanelModule;
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AAKH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,uBAAuB,CAAA;AAExD,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,oCAAoC,CAAA;AASzE,OAAO,EAML,KAAK,0BAA0B,EAChC,MAAM,gCAAgC,CAAA;AAGvC;;;;GAIG;AACH,MAAM,MAAM,uBAAuB,GAAG,MAAM,CAAA;AA8D5C;;;;;;;;;;;;;;;;;;;;;GAqBG;AACH,MAAM,WAAW,oCAAoC;IACnD;;;;;;;;;;OAUG;IACH,YAAY,CAAC,EAAE,OAAO,CAAC,0BAA0B,CAAC,CAAA;IAClD;;;;;;;;OAQG;IACH,YAAY,CAAC,EAAE,MAAM,eAAe,GAAG,OAAO,CAAC,eAAe,CAAC,CAAA;IAC/D;;;;;;;OAOG;IACH,YAAY,CAAC,EAAE,MAAM,uBAAuB,GAAG,IAAI,GAAG,OAAO,CAAC,uBAAuB,GAAG,IAAI,CAAC,CAAA;IAC7F,6FAA6F;IAC7F,OAAO,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,KAAK,IAAI,CAAA;CACnC;AAiBD,6CAA6C;AAC7C,eAAO,MAAM,mBAAmB,EAAG,aAAsB,CAAA;AAEzD;;;;;GAKG;AACH,wBAAgB,6BAA6B,CAC3C,OAAO,EAAE,oCAAoC,GAC5C,WAAW,CAiGb"}

package/dist/index.js

@@ -0,0 +1,232 @@
+/**
+ * `@xenosystem/agent-interface-panel` — the XENO Agent panel that renders the REAL interface.
+ *
+ * ONE agent surface, mounted wherever a XENO Panel host can put a tile: xeno-apps, Pixel,
+ * Motion, Canvas. Update the interface once and every host that mounts this panel gets it,
+ * because there is nothing here to keep in sync — this package contributes a mount, not a UI.
+ *
+ * ## What this is, precisely
+ *
+ * `@xenosystem/panel-agent` (xeno-core) is the GENERIC half: manifest, controller, projections,
+ * wiring, diff parsing, host-event translation. It depends on no product, which is why it lives
+ * in core, and it ships a deliberately minimal default view whose own docblock says what is not
+ * in it — no transcript, no tool timeline, no diff, no terminal.
+ *
+ * This package is the PRODUCT half. It supplies the view, and the view is the shipping XENO Agent
+ * interface itself, mounted through `@xenosystem/agent-interface-embed`.
+ *
+ * 🔴 **It renders the real interface rather than reproducing it, and that is the whole point.**
+ * `XENO AGENT PANEL - SPEC.md` D7d refuses a port: three agent UIs already exist because each
+ * began as a reasonable copy, and a fourth would drift from the day it was written. The
+ * conversation view is ~11.5k lines bound to six stores with no tests — reproducing it is not a
+ * task, it is a second product to maintain.
+ *
+ * ## What a host must supply
+ *
+ * 1. An `AgentHostClient` whose `surface` is `'panel-embed'`. The embed layer refuses a client
+ *    whose surface disagrees with the mount, deliberately — a surface that lies about which kind
+ *    it is gets the wrong chrome and the wrong lifecycle.
+ * 2. A platform bridge, installed before mount. The interface reads its data from the bridge, not
+ *    from props, exactly as it does under `hub-embed`.
+ *
+ * ⚠️ **Known limit, stated rather than hidden.** The mounted interface holds its own connection to
+ * the agent host. The panel's input ports still carry status and intents for host wiring, but they
+ * are not yet the interface's source of truth — D7c's "the panel OWNS the conversation" is only
+ * half done here. Closing it needs the interface to accept an injected session source, which does
+ * not exist today. Until it does, a host should treat this panel as the interface in a tile, and
+ * not wire a second conversation into it and expect them to agree.
+ *
+ * @packageDocumentation
+ */
+import { createElement, useCallback, useEffect, useState } from 'react';
+import { createRoot } from 'react-dom/client';
+import { createAgentPanel } from '@xenosystem/panel-agent';
+import { mountXenoAgentInterface } from '@xenosystem/agent-interface-embed';
+/*
+ * 🔴 The conversation comes from its OWN package, not through the shell.
+ *
+ * That is the inversion this panel exists for. While the conversation lived inside
+ * `agent-interface-ui`, the shell was the canonical thing and this was a wrapper around it —
+ * improving the panel reached nobody, because nothing downstream depended on it. Now the shell and
+ * this panel are peers that render the same conversation.
+ */
+import { MAIN_ASSISTANT_ID, MAIN_ASSISTANT_MODEL, MAIN_ASSISTANT_NAME, XenoAgentConversation, configureAgentPlatformBridge, } from '@xenosystem/agent-conversation';
+import { disposeHubAgentCatalogClient } from '@xenosystem/agent-conversation/adapters/xenoAgentHostCatalog';
+/**
+ * What this panel actually renders: the CONVERSATION, not the shell around it.
+ *
+ * 🔴 Until now both mount paths rendered `XenoAgentInterface` — the whole desktop shell, with its
+ * session sidebar, its tab header and its editor/browser split. Dropped into a host that owns its
+ * own window that is an application inside a panel: a second sidebar beside the host's, a second
+ * tab strip, and two things competing to decide what "the current session" means.
+ *
+ * The panel is the conversation — the transcript and the composer and the logic behind them — and
+ * nothing else. The host supplies the surrounding chrome, because the host already has some.
+ */
+const AgentConversationComponent = XenoAgentConversation;
+/**
+ * The panel OWNS which conversation it shows.
+ *
+ * 🔴 It used to render the conversation once, with fixed props and no `onNavigateConversation`, so every
+ * way the conversation moves somewhere else was dead inside a panel host: "New chat" never rendered,
+ * opening a delegated sub-agent from the dock's tray did nothing, and a sub-agent's "Back to parent
+ * agent" never appeared. The Turn Modes Bench measurement found it — its chat frame has a New chat
+ * action the panel could not draw. Now the panel keeps the current conversation as state, moves itself,
+ * and still tells a host that wants to know.
+ */
+function PanelConversation(props) {
+    const { conversationId: named, onNavigateConversation, onConversationCreated } = props;
+    const [conversationId, setConversationId] = useState(named);
+    // a host that names a DIFFERENT conversation later still wins
+    useEffect(() => { if (named !== undefined)
+        setConversationId(named); }, [named]);
+    const navigate = useCallback((id) => { setConversationId(id); onNavigateConversation?.(id); }, [onNavigateConversation]);
+    // a conversation the view creates for itself becomes the panel's current one
+    const created = useCallback((id) => { setConversationId(id); onConversationCreated?.(id); }, [onConversationCreated]);
+    return createElement(AgentConversationComponent, {
+        ...props,
+        // omitted rather than `undefined` while no conversation is named or created yet
+        ...(conversationId !== undefined ? { conversationId } : {}),
+        onNavigateConversation: navigate,
+        onConversationCreated: created,
+    });
+}
+/**
+ * The conversation this panel opens when the host does not name one.
+ *
+ * Identical to what the full interface shows for the personal inbox, from the same constants —
+ * so a panel and the desktop app open the SAME conversation rather than two that merely look
+ * alike. Inventing an agent id here is how those quietly diverge.
+ */
+function defaultConversationProps() {
+    return {
+        agentId: MAIN_ASSISTANT_ID,
+        agentName: MAIN_ASSISTANT_NAME,
+        model: MAIN_ASSISTANT_MODEL,
+        isMainAssistant: true,
+        capabilities: { terminal: true, fileRead: true, fileWrite: true, appLaunch: true },
+        permissionProfile: 'standard',
+        // A host chrome draws its own workbench; the conversation must not draw a second one.
+        renderWorkbenchPanel: false,
+    };
+}
+/**
+ * The conversation fills the tile it is given. Its root (`.xa-app`) is `flex: 1; min-height: 0`
+ * inside a flex COLUMN — the bench's frame — so mounted into a plain block element it sizes to
+ * its content and the dock floats mid-tile with dead space beneath (Canvas, 2026-09-17). The
+ * mount element is the panel's to shape: every host hands over a box, none of them know the
+ * conversation's layout contract, and this is the one place that does.
+ */
+function fillTile(el) {
+    // the tile's SIZE stays the host's (a fixed box, a flex item, a grid cell); only its inside
+    // becomes the column the conversation's root expects
+    el.style.display = 'flex';
+    el.style.flexDirection = 'column';
+    el.style.minHeight = '0';
+}
+/** The surface kind this panel mounts as. */
+export const AGENT_PANEL_SURFACE = 'panel-embed';
+/**
+ * Build the panel module: the generic agent panel, rendered by the real XENO Agent interface.
+ *
+ * @param options - How to build a client, and where to report a failed mount.
+ * @returns A `PanelModule` any XENO Panel host can register.
+ */
+export function createXenoAgentInterfacePanel(options) {
+    return createAgentPanel({
+        render(el) {
+            let handle = null;
+            let root = null;
+            /* Restores whatever bridge was installed before this mount — a panel can be mounted twice. */
+            let restoreBridge = null;
+            /*
+             * 🔴 Disposal can be requested BEFORE the mount resolves, and a panel closed during its own
+             * startup is an ordinary thing in a dockable layout — drag a tile away while it is opening.
+             * Without this flag the late `.then` mounts into a container the host has already discarded
+             * and nothing ever unmounts it, which is the leak `panel-template` records for this shape.
+             */
+            let disposed = false;
+            void (async () => {
+                try {
+                    /*
+                     * The BRIDGE path first, because it is the one a panel host should take: configure the
+                     * platform bridge and render the interface directly. No AgentHostClient, so no generic
+                     * `request(method, input)`, so the host never has to widen its renderer's authority to
+                     * all 141 host methods in order to draw a panel.
+                     */
+                    if (options.createBridge) {
+                        const bridge = await options.createBridge();
+                        if (disposed)
+                            return;
+                        if (!bridge) {
+                            // No agent host on this machine — the ordinary state. The panel shows its own empty
+                            // state rather than the host treating a missing optional agent as a failure.
+                            return;
+                        }
+                        restoreBridge = configureAgentPlatformBridge(bridge);
+                        fillTile(el);
+                        root = createRoot(el);
+                        root.render(createElement(PanelConversation, {
+                            ...defaultConversationProps(),
+                            ...options.conversation,
+                        }));
+                        return;
+                    }
+                    if (!options.createClient) {
+                        throw new Error('createXenoAgentInterfacePanel needs either createBridge or createClient.');
+                    }
+                    const client = await options.createClient();
+                    const mounted = await mountXenoAgentInterface(el, {
+                        surface: AGENT_PANEL_SURFACE,
+                        client,
+                        renderer: {
+                            mount(container) {
+                                /*
+                                 * Mounted HERE, inside this package, so `react` and `react-dom` resolve to one
+                                 * copy. A host that calls `createRoot` on a view imported across a package
+                                 * boundary can end up with two Reacts, and every hook throws "Invalid hook call".
+                                 */
+                                fillTile(container);
+                                root = createRoot(container);
+                                root.render(createElement(PanelConversation, {
+                                    ...defaultConversationProps(),
+                                    ...options.conversation,
+                                }));
+                            },
+                            unmount() {
+                                root?.unmount();
+                                root = null;
+                            },
+                        },
+                    });
+                    if (disposed) {
+                        await mounted.unmount();
+                        return;
+                    }
+                    handle = mounted;
+                }
+                catch (error) {
+                    options.onError?.(error);
+                }
+            })();
+            return () => {
+                disposed = true;
+                void handle?.unmount();
+                handle = null;
+                root?.unmount();
+                root = null;
+                /*
+                 * The conversation's catalog adapter keeps ONE module-level host client, built from the
+                 * bridge on first use. It must go with the mount: a host disposes its bridge right after
+                 * this, and a client left behind would serve the NEXT mount from a dead transport —
+                 * close and reopen the tab and the catalog never loads again. `disposeHubAgentCatalogClient`
+                 * existed for exactly this and was called by nothing (2026-09-17).
+                 */
+                disposeHubAgentCatalogClient();
+                restoreBridge?.();
+                restoreBridge = null;
+            };
+        },
+    });
+}
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAuCG;AAEH,OAAO,EAAE,aAAa,EAAE,WAAW,EAAE,SAAS,EAAE,QAAQ,EAA0B,MAAM,OAAO,CAAA;AAC/F,OAAO,EAAE,UAAU,EAAa,MAAM,kBAAkB,CAAA;AACxD,OAAO,EAAE,gBAAgB,EAAE,MAAM,yBAAyB,CAAA;AAE1D,OAAO,EAAE,uBAAuB,EAAsC,MAAM,mCAAmC,CAAA;AAE/G;;;;;;;GAOG;AACH,OAAO,EACL,iBAAiB,EACjB,oBAAoB,EACpB,mBAAmB,EACnB,qBAAqB,EACrB,4BAA4B,GAE7B,MAAM,gCAAgC,CAAA;AACvC,OAAO,EAAE,4BAA4B,EAAE,MAAM,8DAA8D,CAAA;AAS3G;;;;;;;;;;GAUG;AACH,MAAM,0BAA0B,GAAG,qBAAsE,CAAA;AAEzG;;;;;;;;;GASG;AACH,SAAS,iBAAiB,CAAC,KAAiC;IAC1D,MAAM,EAAE,cAAc,EAAE,KAAK,EAAE,sBAAsB,EAAE,qBAAqB,EAAE,GAAG,KAAK,CAAA;IACtF,MAAM,CAAC,cAAc,EAAE,iBAAiB,CAAC,GAAG,QAAQ,CAA4B,KAAK,CAAC,CAAA;IACtF,8DAA8D;IAC9D,SAAS,CAAC,GAAG,EAAE,GAAG,IAAI,KAAK,KAAK,SAAS;QAAE,iBAAiB,CAAC,KAAK,CAAC,CAAA,CAAC,CAAC,EAAE,CAAC,KAAK,CAAC,CAAC,CAAA;IAC/E,MAAM,QAAQ,GAAG,WAAW,CAAC,CAAC,EAAU,EAAE,EAAE,GAAG,iBAAiB,CAAC,EAAE,CAAC,CAAC,CAAC,sBAAsB,EAAE,CAAC,EAAE,CAAC,CAAA,CAAC,CAAC,EAAE,CAAC,sBAAsB,CAAC,CAAC,CAAA;IAC/H,6EAA6E;IAC7E,MAAM,OAAO,GAAG,WAAW,CAAC,CAAC,EAAU,EAAE,EAAE,GAAG,iBAAiB,CAAC,EAAE,CAAC,CAAC,CAAC,qBAAqB,EAAE,CAAC,EAAE,CAAC,CAAA,CAAC,CAAC,EAAE,CAAC,qBAAqB,CAAC,CAAC,CAAA;IAC5H,OAAO,aAAa,CAAC,0BAA0B,EAAE;QAC/C,GAAG,KAAK;QACR,gFAAgF;QAChF,GAAG,CAAC,cAAc,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,cAAc,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QAC3D,sBAAsB,EAAE,QAAQ;QAChC,qBAAqB,EAAE,OAAO;KAC/B,CAAC,CAAA;AACJ,CAAC;AAED;;;;;;GAMG;AACH,SAAS,wBAAwB;IAC/B,OAAO;QACL,OAAO,EAAE,iBAAiB;QAC1B,SAAS,EAAE,mBAAmB;QAC9B,KAAK,EAAE,oBAAoB;QAC3B,eAAe,EAAE,IAAI;QACrB,YAAY,EAAE,EAAE,QAAQ,EAAE,IAAI,EAAE,QAAQ,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE,SAAS,EAAE,IAAI,EAAE;QAClF,iBAAiB,EAAE,UAAU;QAC7B,sFAAsF;QACtF,oBAAoB,EAAE,KAAK;KAC5B,CAAA;AACH,CAAC;AA4DD;;;;;;GAMG;AACH,SAAS,QAAQ,CAAC,EAAe;IAC/B,4FAA4F;IAC5F,qDAAqD;IACrD,EAAE,CAAC,KAAK,CAAC,OAAO,GAAG,MAAM,CAAA;IACzB,EAAE,CAAC,KAAK,CAAC,aAAa,GAAG,QAAQ,CAAA;IACjC,EAAE,CAAC,KAAK,CAAC,SAAS,GAAG,GAAG,CAAA;AAC1B,CAAC;AAED,6CAA6C;AAC7C,MAAM,CAAC,MAAM,mBAAmB,GAAG,aAAsB,CAAA;AAEzD;;;;;GAKG;AACH,MAAM,UAAU,6BAA6B,CAC3C,OAA6C;IAE7C,OAAO,gBAAgB,CAAC;QACtB,MAAM,CAAC,EAAe;YACpB,IAAI,MAAM,GAAyC,IAAI,CAAA;YACvD,IAAI,IAAI,GAAgB,IAAI,CAAA;YAC5B,8FAA8F;YAC9F,IAAI,aAAa,GAAwB,IAAI,CAAA;YAC7C;;;;;eAKG;YACH,IAAI,QAAQ,GAAG,KAAK,CAAA;YAEpB,KAAK,CAAC,KAAK,IAAI,EAAE;gBACf,IAAI,CAAC;oBACH;;;;;uBAKG;oBACH,IAAI,OAAO,CAAC,YAAY,EAAE,CAAC;wBACzB,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,YAAY,EAAE,CAAA;wBAC3C,IAAI,QAAQ;4BAAE,OAAM;wBACpB,IAAI,CAAC,MAAM,EAAE,CAAC;4BACZ,oFAAoF;4BACpF,6EAA6E;4BAC7E,OAAM;wBACR,CAAC;wBACD,aAAa,GAAG,4BAA4B,CAAC,MAAe,CAAC,CAAA;wBAC7D,QAAQ,CAAC,EAAE,CAAC,CAAA;wBACZ,IAAI,GAAG,UAAU,CAAC,EAAE,CAAC,CAAA;wBACrB,IAAI,CAAC,MAAM,CAAC,aAAa,CAAC,iBAAiB,EAAE;4BAC3C,GAAG,wBAAwB,EAAE;4BAC7B,GAAG,OAAO,CAAC,YAAY;yBACxB,CAAC,CAAC,CAAA;wBACH,OAAM;oBACR,CAAC;oBAED,IAAI,CAAC,OAAO,CAAC,YAAY,EAAE,CAAC;wBAC1B,MAAM,IAAI,KAAK,CAAC,0EAA0E,CAAC,CAAA;oBAC7F,CAAC;oBACD,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,YAAY,EAAE,CAAA;oBAC3C,MAAM,OAAO,GAAG,MAAM,uBAAuB,CAAC,EAAE,EAAE;wBAChD,OAAO,EAAE,mBAAmB;wBAC5B,MAAM;wBACN,QAAQ,EAAE;4BACR,KAAK,CAAC,SAAsB;gCAC1B;;;;mCAIG;gCACH,QAAQ,CAAC,SAAS,CAAC,CAAA;gCACnB,IAAI,GAAG,UAAU,CAAC,SAAS,CAAC,CAAA;gCAC5B,IAAI,CAAC,MAAM,CAAC,aAAa,CAAC,iBAAiB,EAAE;oCAC3C,GAAG,wBAAwB,EAAE;oCAC7B,GAAG,OAAO,CAAC,YAAY;iCACxB,CAAC,CAAC,CAAA;4BACL,CAAC;4BACD,OAAO;gCACL,IAAI,EAAE,OAAO,EAAE,CAAA;gCACf,IAAI,GAAG,IAAI,CAAA;4BACb,CAAC;yBACF;qBACF,CAAC,CAAA;oBACF,IAAI,QAAQ,EAAE,CAAC;wBACb,MAAM,OAAO,CAAC,OAAO,EAAE,CAAA;wBACvB,OAAM;oBACR,CAAC;oBACD,MAAM,GAAG,OAAO,CAAA;gBAClB,CAAC;gBAAC,OAAO,KAAK,EAAE,CAAC;oBACf,OAAO,CAAC,OAAO,EAAE,CAAC,KAAK,CAAC,CAAA;gBAC1B,CAAC;YACH,CAAC,CAAC,EAAE,CAAA;YAEJ,OAAO,GAAG,EAAE;gBACV,QAAQ,GAAG,IAAI,CAAA;gBACf,KAAK,MAAM,EAAE,OAAO,EAAE,CAAA;gBACtB,MAAM,GAAG,IAAI,CAAA;gBACb,IAAI,EAAE,OAAO,EAAE,CAAA;gBACf,IAAI,GAAG,IAAI,CAAA;gBACX;;;;;;mBAMG;gBACH,4BAA4B,EAAE,CAAA;gBAC9B,aAAa,EAAE,EAAE,CAAA;gBACjB,aAAa,GAAG,IAAI,CAAA;YACtB,CAAC,CAAA;QACH,CAAC;KACF,CAAC,CAAA;AACJ,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xenosystem/agent-interface-panel",
-  "version": "0.1.50",
+  "version": "0.1.67",
   "license": "UNLICENSED",
   "type": "module",
   "main": "./dist/index.js",
@@ -22,12 +22,15 @@
   "publishConfig": {
     "access": "public"
   },
+  "scripts": {
+    "build": "tsc -p tsconfig.json"
+  },
   "dependencies": {
-    "@xenosystem/panel-agent": "^0.1.0",
-    "@xenosystem/agent-conversation": "0.1.50",
-    "@xenosystem/agent-interface-client": "0.1.50",
-    "@xenosystem/agent-interface-embed": "0.1.50",
-    "@xenosystem/agent-interface-contract": "0.1.50"
+    "@xenosystem/agent-conversation": "workspace:*",
+    "@xenosystem/agent-interface-client": "workspace:*",
+    "@xenosystem/agent-interface-contract": "workspace:*",
+    "@xenosystem/agent-interface-embed": "workspace:*",
+    "@xenosystem/panel-agent": "^0.1.0"
   },
   "peerDependencies": {
     "@xenosystem/panel-sdk": "^1.1.0",
@@ -42,8 +45,5 @@
     "@xenosystem/workbench": "^1.0.0",
     "react": "^19.0.0",
     "react-dom": "^19.0.0"
-  },
-  "scripts": {
-    "build": "tsc -p tsconfig.json"
   }
-}
+}

package/LICENSE

@@ -1,67 +0,0 @@
-XENO Agent — Proprietary Software License
-Copyright © 2026 XENO Corporation. All rights reserved.
-
-This software, including its source code, compiled binaries, published packages,
-assets, and accompanying documentation (collectively, the "Software"), is the
-proprietary and confidential property of XENO Corporation ("XENO"). The Software
-is licensed for use, not sold, and no title to or ownership of the Software is
-transferred to any user.
-
-1. GRANT OF USE
-   Subject to a separate written agreement and/or the terms of service published
-   at https://xenostudio.ai, XENO grants the end user a limited, non-exclusive,
-   non-transferable, revocable license to install and use the Software for its
-   intended purpose. The standalone desktop application ("the Agent") may be used
-   locally at no charge; connected platform features — hosted agent runs, model
-   inference, credits, and account services — are governed by the applicable
-   subscription and the XENO terms of service.
-
-2. PACKAGE DISTRIBUTION
-   The `@xeno-corporation/xeno-agent-interface-*` and
-   `@xeno-corporation/xeno-agents-client` packages are published to a PRIVATE
-   registry and are licensed for use solely by XENO products and by parties
-   holding a separate written agreement with XENO. Access credentials to that
-   registry do not grant redistribution rights. Publication of any package in
-   this repository to a public registry is prohibited without written
-   authorization from XENO.
-
-3. RESTRICTIONS
-   Except to the extent expressly permitted by applicable law or by a separate
-   written agreement with XENO, you may NOT: (a) copy, redistribute, sell, rent,
-   lease, sublicense, or otherwise transfer the Software; (b) modify, adapt,
-   translate, or create derivative works of the Software; (c) reverse-engineer,
-   decompile, or disassemble the Software, or attempt to derive its source code;
-   (d) remove, obscure, or alter any proprietary notices; or (e) use the Software
-   to build a competing product.
-
-4. RESERVATION OF RIGHTS
-   All rights not expressly granted are reserved by XENO Corporation. The Software
-   is protected by copyright and other intellectual-property laws and treaties.
-
-5. DISCLAIMER OF WARRANTY
-   THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY
-   KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-   MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THE
-   SOFTWARE EXECUTES AGENT-DIRECTED OPERATIONS AGAINST A USER-SELECTED WORKSPACE,
-   INCLUDING FILE AND PROCESS ACTIONS; THE USER IS RESPONSIBLE FOR THE WORKSPACES
-   AND PERMISSIONS THEY GRANT IT.
-
-6. LIMITATION OF LIABILITY
-   TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL XENO CORPORATION BE
-   LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE
-   DAMAGES, OR ANY LOSS OF PROFITS OR DATA, ARISING FROM OR RELATED TO THE USE OF
-   OR INABILITY TO USE THE SOFTWARE.
-
-7. THIRD-PARTY COMPONENTS
-   The Software includes third-party open-source components, each licensed under
-   its own terms; those terms govern those components and are not superseded by
-   this license. It also composes third-party agent providers over the Agent
-   Client Protocol and hosted APIs; use of those providers is governed by their
-   own terms.
-
-For licensing inquiries, contact: legal@xenostudio.ai
-
-NOTE TO OPERATOR: confirm the exact legal entity name and notice/contact details
-with counsel before public distribution and code-signing (the code-signing
-publisher name must match the registered entity). No public distribution of this
-product is authorized by this file — see docs/PRODUCT_STATUS.md.