@kitn.ai/ui 0.27.0 → 0.29.0

package/dist/store-7eoadydQ.js

@@ -1 +0,0 @@
-import{$ as u,K,L as P,N as w,g as z}from"./define-CGGX-7Vg.js";const h=Symbol("store-raw"),y=Symbol("store-node"),f=Symbol("store-has"),m=Symbol("store-self");function v(t){let r=t[u];if(!r&&(Object.defineProperty(t,u,{value:r=new Proxy(t,L)}),!Array.isArray(t))){const o=Object.keys(t),e=Object.getOwnPropertyDescriptors(t),c=Object.getPrototypeOf(t),n=c!==null&&t!==null&&typeof t=="object"&&!Array.isArray(t)&&c!==Object.prototype;if(n){const i=Object.getOwnPropertyDescriptors(c);o.push(...Object.keys(i)),Object.assign(e,i)}for(let i=0,l=o.length;i<l;i++){const s=o[i];n&&s==="constructor"||e[s].get&&Object.defineProperty(t,s,{configurable:!0,enumerable:e[s].enumerable,get:e[s].get.bind(r)})}}return r}function g(t){let r;return t!=null&&typeof t=="object"&&(t[u]||!(r=Object.getPrototypeOf(t))||r===Object.prototype||Array.isArray(t))}function a(t,r=new Set){let o,e,c,n;if(o=t!=null&&t[h])return o;if(!g(t)||r.has(t))return t;if(Array.isArray(t)){Object.isFrozen(t)?t=t.slice(0):r.add(t);for(let i=0,l=t.length;i<l;i++)c=t[i],(e=a(c,r))!==c&&(t[i]=e)}else{Object.isFrozen(t)?t=Object.assign({},t):r.add(t);const i=Object.keys(t),l=Object.getOwnPropertyDescriptors(t);for(let s=0,d=i.length;s<d;s++)n=i[s],!l[n].get&&(c=t[n],(e=a(c,r))!==c&&(t[n]=e))}return t}function _(t,r){let o=t[r];return o||Object.defineProperty(t,r,{value:o=Object.create(null)}),o}function b(t,r,o){if(t[r])return t[r];const[e,c]=z(o,{equals:!1,internal:!0});return e.$=c,t[r]=e}function F(t,r){const o=Reflect.getOwnPropertyDescriptor(t,r);return!o||o.get||!o.configurable||r===u||r===y||(delete o.value,delete o.writable,o.get=()=>t[u][r]),o}function $(t){w()&&b(_(t,y),m)()}function R(t){return $(t),Reflect.ownKeys(t)}const L={get(t,r,o){if(r===h)return t;if(r===u)return o;if(r===P)return $(t),o;const e=_(t,y),c=e[r];let n=c?c():t[r];if(r===y||r===f||r==="__proto__")return n;if(!c){const i=Object.getOwnPropertyDescriptor(t,r);w()&&(typeof n!="function"||t.hasOwnProperty(r))&&!(i&&i.get)&&(n=b(e,r,n)())}return g(n)?v(n):n},has(t,r){return r===h||r===u||r===P||r===y||r===f||r==="__proto__"?!0:(w()&&b(_(t,f),r)(),r in t)},set(){return!0},deleteProperty(){return!0},ownKeys:R,getOwnPropertyDescriptor:F};function p(t,r,o,e=!1){if(r==="__proto__"||!e&&t[r]===o)return;const c=t[r],n=t.length;o===void 0?(delete t[r],t[f]&&t[f][r]&&c!==void 0&&t[f][r].$()):(t[r]=o,t[f]&&t[f][r]&&c===void 0&&t[f][r].$());let i=_(t,y),l;if((l=b(i,r,c))&&l.$(()=>o),Array.isArray(t)&&t.length!==n){for(let s=t.length;s<n;s++)(l=i[s])&&l.$();(l=b(i,"length",n))&&l.$(t.length)}(l=i[m])&&l.$()}function D(t,r){const o=Object.keys(r);for(let e=0;e<o.length;e+=1){const c=o[e];k(c)||p(t,c,r[c])}}function k(t){return t==="__proto__"||t==="constructor"||t==="prototype"}function M(t,r){if(typeof r=="function"&&(r=r(t)),r=a(r),Array.isArray(r)){if(t===r)return;let o=0,e=r.length;for(;o<e;o++){const c=r[o];t[o]!==c&&p(t,o,c)}p(t,"length",e)}else D(t,r)}function O(t,r,o=[]){let e,c=t;if(r.length>1){e=r.shift();const i=typeof e,l=Array.isArray(t);if(i==="string"&&(e==="__proto__"||r.length>1&&k(e)))return;if(Array.isArray(e)){for(let s=0;s<e.length;s++)O(t,[e[s]].concat(r),o);return}else if(l&&i==="function"){for(let s=0;s<t.length;s++)e(t[s],s)&&O(t,[s].concat(r),o);return}else if(l&&i==="object"){const{from:s=0,to:d=t.length-1,by:x=1}=e;for(let A=s;A<=d;A+=x)O(t,[A].concat(r),o);return}else if(r.length>1){O(t[e],r,[e].concat(o));return}c=t[e],o=[e].concat(o)}let n=r[0];typeof n=="function"&&(n=n(c,o),n===c)||e===void 0&&n==null||(n=a(n),e===void 0||g(c)&&g(n)&&!Array.isArray(n)?D(c,n):p(t,e,n))}function N(...[t,r]){const o=a(t||{}),e=Array.isArray(o),c=v(o);function n(...i){K(()=>{e&&i.length===1?M(o,i[0]):O(o,i)})}return[c,n]}const j=new WeakMap,S={get(t,r){if(r===h)return t;const o=t[r];if(r===u||r===P||r===y||r===f||r==="__proto__")return o;let e;return g(o)?j.get(o)||(j.set(o,e=new Proxy(o,S)),e):o},set(t,r,o){return p(t,r,a(o)),!0},deleteProperty(t,r){return p(t,r,void 0,!0),!0}};function W(t){return r=>{if(g(r)){let o;(o=j.get(r))||j.set(r,o=new Proxy(r,S)),t(o)}return r}}export{N as c,W as p,a as u};

package/dist/x-C5m1JFgi.js

@@ -1 +0,0 @@
-import{I as o}from"./Icon-BnFKqqtY.js";import{c as m,q as r}from"./define-CGGX-7Vg.js";var e=[["path",{d:"M18 6 6 18",key:"1bl5f8"}],["path",{d:"m6 6 12 12",key:"d8bk6v"}]],t=a=>m(o,r(a,{name:"X",iconNode:e})),p=t;export{p as x};

package/src/agent-tooling/archetypes.ts

@@ -1,205 +0,0 @@
-import type { Archetype } from './types';
-
-/**
- * The archetypes are PRESETS over a components list, not the surface axis.
- *
- * `renderSurface({ framework, components, integration })` renders any components
- * list; each entry below is a named point in that space plus a default placement.
- * Read the table as "components + placement" and the CLI's feature multi-select
- * falls out of it: placement is the layout question, `components` is the features.
- *
- * Adding an entry here adds a PRESET. It does not add a capability, and it is not
- * how a new component reaches the renderers — that is `components` at the call
- * site. See `listCapabilityGroups` below for what this catalog does still decide.
- */
-export const archetypes: Archetype[] = [
-  {
-    id: 'drop-in-chat',
-    title: 'Drop-in chat',
-    components: ['kai-chat'],
-    defaultPlacement: 'full-page',
-    docsSlug: 'examples/drop-in-chat',
-  },
-  {
-    id: 'support-widget',
-    title: 'Support widget',
-    components: ['kai-chat'],
-    defaultPlacement: 'docked-widget',
-    docsSlug: 'examples/support-widget',
-  },
-  {
-    id: 'knowledge-base',
-    title: 'Knowledge base / RAG',
-    components: ['kai-chat', 'kai-sources'],
-    defaultPlacement: 'full-page',
-    docsSlug: 'examples/knowledge-base',
-  },
-  {
-    id: 'agentic',
-    title: 'Agentic assistant',
-    components: ['kai-chat', 'kai-tool', 'kai-reasoning'],
-    defaultPlacement: 'side',
-    docsSlug: 'examples/agentic-assistant',
-  },
-  /**
-   * THE FIRST OFFICIAL BLOCK (recast spec 2026-08-20 § 3b; F-16).
-   *
-   * This preset used to carry `kai-artifact` + `kai-resizable` — an UNWIRED
-   * artifact split — while omitting the conversation rail, the one thing its
-   * name promised (rung-3 finding F-16). It now names the workspace BLOCK: the
-   * chat-agnostic `kai-workspace` layout shell, a WIRED `kai-conversations`
-   * rail, `kai-chat` in the main region, and the `@kitn.ai/ui/state` thread
-   * helpers (bindThreadMessages / createThreadSessions / createSaveScheduler /
-   * parseStoredThread) with the persistence POLICY left in consumer-owned
-   * lines. `examples/apps/workspace/` is the block's reference implementation.
-   *
-   * The artifact split did not vanish — it moved to `artifact-split` below, so
-   * its renderer branch keeps its cells in `verify:scaffold`.
-   */
-  {
-    id: 'workspace',
-    title: 'Agentic workspace',
-    components: ['kai-chat', 'kai-workspace', 'kai-conversations'],
-    defaultPlacement: 'full-page',
-    docsSlug: 'examples/workspace',
-  },
-  /**
-   * THE PRESET THAT KEEPS A CAPABILITY ON THE AXIS — the same reason the
-   * `attachments` preset exists (see its comment below): `listCapabilityGroups`
-   * derives the gate's surface axis from this table, so when the recast moved
-   * the artifact pair off `workspace`, this entry is what kept
-   * `kai-artifact`+`kai-resizable` compiling in `verify:scaffold` instead of
-   * silently losing every cell. The pair is ONE capability because `isArtifactSplit`
-   * in scaffold.ts requires both: a split with no preview pane is an empty
-   * panel, and a preview with no split has nowhere to sit.
-   */
-  {
-    id: 'artifact-split',
-    title: 'Artifact preview split',
-    components: ['kai-chat', 'kai-artifact', 'kai-resizable'],
-    defaultPlacement: 'side',
-    docsSlug: 'examples/workspace',
-  },
-  {
-    id: 'voice',
-    title: 'Voice assistant',
-    components: ['kai-chat', 'kai-voice-input'],
-    defaultPlacement: 'full-page',
-    docsSlug: 'examples/voice-assistant',
-  },
-  /**
-   * THE PRESET THAT EXISTS TO MAKE A CAPABILITY REACHABLE, not to name a product
-   * shape someone asked for.
-   *
-   * `kai-file-upload` and `kai-attachments` were registered elements that NO
-   * preset composed, and `listCapabilityGroups` derives its answer from this
-   * table — so the attachments capability reached neither `listSurfaceProbes`
-   * nor `verify:scaffold`, and `renderSurface` had no branch that emitted either
-   * tag. A caller could pass them in `components` (the axis takes any list) and
-   * get two bare `<kai-file-upload></kai-file-upload>` / `<kai-attachments>`
-   * siblings with nothing wired to them: on screen, inert, silent.
-   *
-   * The pair is ONE capability for the same reason `kai-artifact` +
-   * `kai-resizable` are: a dropzone with no list is a black hole, and a list
-   * with no dropzone can never fill. `hasAttachments` in scaffold.ts requires
-   * both for exactly that reason.
-   *
-   * The components match the create-kai spec's own feature table
-   * (`attachments` -> `kai-file-upload`, `kai-attachments`), so the CLI's
-   * multi-select and this preset name the same surface rather than two.
-   */
-  {
-    id: 'attachments',
-    title: 'File attachments',
-    components: ['kai-chat', 'kai-file-upload', 'kai-attachments'],
-    defaultPlacement: 'full-page',
-    docsSlug: 'examples/attachments',
-  },
-];
-
-/** The component every surface composes around, so never a capability by itself. */
-export const BASE_COMPONENT = 'kai-chat';
-
-/** One capability: the components a preset adds on top of `BASE_COMPONENT`. */
-export interface CapabilityGroup {
-  /** derived from the components, e.g. `tool+reasoning` — not a preset name */
-  id: string;
-  components: string[];
-}
-
-/**
- * The distinct capabilities the presets know about, DERIVED from them.
- *
- * A capability is one preset's components minus `kai-chat`, deduped across the
- * catalog (run `listCapabilityGroups()` for the current list — `drop-in-chat`
- * and `support-widget` collapse onto the same empty capability because both add
- * nothing and differ only in `defaultPlacement`).
- *
- * Derived rather than listed for the reason the verify script's other axes are:
- * a hand-written list would have to be edited by the same hand that adds a
- * preset, so a new capability could land with nothing covering it and nothing
- * failing to say so. Registering a preset whose components are new moves the
- * cell count in `verify:scaffold` by itself.
- *
- * The grouping is real and not an artifact of the derivation: `kai-tool` and
- * `kai-reasoning` are one capability because a tool panel with no reasoning
- * disclosure is not a surface anyone asks for, `kai-artifact` /
- * `kai-resizable` are one because `isArtifactSplit` in scaffold.ts only fires when BOTH are present
- * — split them and the renderer emits a bare artifact with no pane to put it in
- * — and `kai-file-upload` / `kai-attachments` are one because `hasAttachments`
- * fires the same way, for the same kind of reason.
- */
-export function listCapabilityGroups(): CapabilityGroup[] {
-  const seen = new Map<string, CapabilityGroup>();
-  for (const a of archetypes) {
-    const components = a.components.filter((c) => c !== BASE_COMPONENT);
-    if (components.length === 0) continue;
-    const key = [...components].sort().join(',');
-    if (seen.has(key)) continue;
-    seen.set(key, { id: components.map((c) => c.replace(/^kai-/, '')).join('+'), components });
-  }
-  return [...seen.values()];
-}
-
-/** One surface the scaffolder's gate compiles across every integration × framework. */
-export interface SurfaceProbe {
-  id: string;
-  components: string[];
-}
-
-/**
- * The surface axis for `verify:scaffold`: each capability ALONE, plus none, plus
- * ALL of them.
- *
- * WHY THESE AND NOT THE PRESETS. The presets are seven cells covering six
- * distinct components lists (`support-widget` repeats `drop-in-chat`'s, and the
- * matrix holds `placement` at one value, so that pair compiled the same types
- * twice). More importantly they cover no combination at all — every preset is
- * exactly one capability — so the surfaces the multi-select makes reachable,
- * which is most of them, had nothing compiling them.
- *
- * WHY NOT THE POWER SET. 2^groups x integrations x frameworks is thousands of
- * cells to exercise no new branch. The renderers compose capabilities
- * INDEPENDENTLY: each companion tag is emitted on its own terms, and the
- * multi-component predicates (`isArtifactSplit`, `isWorkspaceBlock`) each read
- * components from within a single group. So
- * "every capability alone" reaches every branch, and "all capabilities together"
- * makes every PAIR of capabilities co-occur, which is what proves they compose.
- *
- * THE LIMIT, STATED: a defect needing exactly two capabilities and masked by a
- * third would survive this. That is a real gap and the honest reason it is
- * accepted is cost, not safety — no such branch exists in the renderers today,
- * and `assertSurfacesAreDistinct` fails if the axis ever degenerates so that this
- * reasoning is quietly checking less than it claims.
- */
-export function listSurfaceProbes(): SurfaceProbe[] {
-  const groups = listCapabilityGroups();
-  return [
-    { id: 'chat-only', components: [BASE_COMPONENT] },
-    ...groups.map((g) => ({ id: g.id, components: [BASE_COMPONENT, ...g.components] })),
-    {
-      id: 'every-capability',
-      components: [BASE_COMPONENT, ...groups.flatMap((g) => g.components)],
-    },
-  ];
-}