@hanzo/ui 8.1.5 → 8.1.7

package/dist/chat/Step.js

@@ -4,51 +4,29 @@ import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
  * Step — something the assistant did on the way to the answer, and how it went.
  *
  * A tool call, a retrieval, a plan, a stretch of reasoning, a progress report:
- * every one of them is a named region that reports a state and opens to show
- * its detail. Two repos had written that arrangement NINE times without ever
- * naming it — hanzo/chat once (`ToolCall.tsx` + `ProgressText.tsx`), hanzo.app
- * eight (`chat-panel/index.tsx` `ToolDisplay`, `SyntheticErrorDisplay`,
- * `ReasoningDisplay`, `PlanDisplay`, `AgentDisplay`, `ProgressDisplay`, the
- * inline `project_context` block, and the builder's own `CollapsibleSection` in
- * `ask-ai/chat-thread.tsx:330`). Nine chances to order the header differently,
- * and they took most of them.
+ * each is a named region that reports a state and opens to show its detail.
+ * The header, the state mark, the disclosure and the frame are here; what goes
+ * inside is `children`.
  *
- * What goes INSIDE stays the surface's: chat renders the input as a code block
- * and the result through its own markdown, the app renders
- * `JSON.stringify(parameters, null, 2)`. That is `children`. The header, the
- * state mark, the disclosure and the frame are the same drawing in all nine and
- * they are here.
+ * Open/closed is `Collapsible`, so `aria-expanded`, `aria-controls` and the
+ * keyboard come from the primitive.
  *
- * The open/closed behaviour is `Collapsible`, not a hand-rolled height
- * animation. Both existing implementations rolled their own — chat measures
- * `scrollHeight` in a `useLayoutEffect`, keeps a `ResizeObserver` alive and
- * transitions an explicit pixel height — and that is the keyboard handling and
- * the `aria-expanded`/`aria-controls` pair re-derived by hand each time. The
- * primitive already has them.
- *
- * There is no duration and no elapsed time. Neither implementation shows one,
- * and chat's apparent progress is not measured at all: `useProgress.ts:54`
- * ticks a `setInterval` by 0.007 every 200ms and caps at 0.95 until the server
- * says otherwise. A number that is invented should not be given a place to
- * render.
+ * No duration: nothing upstream measures one, and a progress ratio ticked by a
+ * timer is not a measurement.
  */
 import { SizableText, XStack, YStack } from '@hanzo/gui';
 import { Ban, Check, ChevronDown, TriangleAlert } from '@hanzogui/lucide-icons-2';
 import { Collapsible, CollapsibleContent, CollapsibleTrigger, Spinner } from '../backends/gui/index.js';
 import { slot } from '../backends/gui/slot.js';
-/** Edge of the state mark, px. One size, so the header never reflows on a state
- *  change — a step that finishes must not move the text beside it. */
+/** Edge of the state mark, px. One size, so a state change never reflows the
+ *  header. */
 const MARK = 13;
 /**
  * The mark for each state. `running` is the one that moves.
  *
- * Tinted on the glyph, never on the box: `XStack` is a View and has no `color`,
- * so a colour set there type-errors rather than cascading — which is this
- * package's "a prop must actually arrive" rule catching a habit borrowed from
- * the DOM. Written as four call sites rather than a lookup table because the
- * Spinner and the three glyphs do not share a props type: the icons take a
- * themed `GetThemeValueForKey<'color'>` and the Spinner takes a plain string,
- * and the table that unified them only typechecked by widening both to `any`.
+ * Tinted on the glyph: `XStack` is a View and takes no `color`. Four call sites
+ * rather than a table because the Spinner and the icons do not share a props
+ * type — the icons take a themed colour, the Spinner a plain string.
  */
 const mark = (status) => {
     switch (status) {
@@ -63,17 +41,13 @@ const mark = (status) => {
     }
 };
 export function Step({ name, status = 'done', detail, children, defaultOpen, open, onOpenChange, ...props }) {
-    // A step with no body is a statement, not a control. Rendering a dead chevron
-    // and a focusable trigger over nothing is how a keyboard user is sent to a
-    // stop that does not answer.
+    // A step with no body is a statement, not a control: no chevron, no trigger,
+    // no keyboard stop that does not answer.
     const opens = children != null;
     const header = (_jsxs(XStack, { items: "center", gap: "$2", px: "$3", py: "$2", width: "100%", children: [_jsx(XStack, { width: MARK + 1, items: "center", justify: "center", shrink: 0, children: mark(status) }), _jsx(SizableText, { size: "$1", color: "$color12", numberOfLines: 1, children: name }), detail ? (_jsx(SizableText, { size: "$1", color: "$color10", numberOfLines: 1, shrink: 1, children: detail })) : null, _jsx(XStack, { flex: 1 }), opens ? _jsx(ChevronDown, { size: 13, color: "$color10" }) : null] }));
     return (_jsxs(Collapsible, { ...slot('step'), "data-status": status, open: open, defaultOpen: defaultOpen, onOpenChange: onOpenChange, width: "100%", rounded: "$4", borderWidth: 1, 
-        // The failure edge, not a red one. `product/tone.ts` states the rule this
-        // package works under — "this system has no colour to spend" — and marks
-        // its `stopped` register with a border rather than a fill. A step that
-        // errored is set apart the same way, so it still reads as a failure in a
-        // brand that retunes the whole ramp.
+        // An edge, not a red fill — `product/tone.ts` marks `stopped` the same
+        // way, so it survives a brand that retunes the ramp.
         borderColor: status === 'error' ? '$color9' : '$borderColor', bg: "$color2", overflow: "hidden", ...props, children: [opens ? _jsx(CollapsibleTrigger, { width: "100%", children: header }) : header, opens ? (_jsx(CollapsibleContent, { children: _jsx(YStack, { ...slot('step-body'), px: "$3", py: "$2.5", gap: "$2", borderTopWidth: 1, borderColor: "$borderColor", children: children }) })) : null] }));
 }
 //# sourceMappingURL=Step.js.map

package/dist/chat/Step.js.map

@@ -1 +1 @@
-{"version":3,"file":"Step.js","sourceRoot":"","sources":["../../src/chat/Step.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,OAAO,EAAE,WAAW,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,YAAY,CAAA;AACxD,OAAO,EAAE,GAAG,EAAE,KAAK,EAAE,WAAW,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAA;AAGjF,OAAO,EAAE,WAAW,EAAE,kBAAkB,EAAE,kBAAkB,EAAE,OAAO,EAAE,MAAM,iBAAiB,CAAA;AAC9F,OAAO,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAA;AAc3C;sEACsE;AACtE,MAAM,IAAI,GAAG,EAAE,CAAA;AAEf;;;;;;;;;;GAUG;AACH,MAAM,IAAI,GAAG,CAAC,MAAW,EAAE,EAAE;IAC3B,QAAQ,MAAM,EAAE,CAAC;QACf,KAAK,SAAS;YACZ,OAAO,KAAC,OAAO,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QACjD,KAAK,MAAM;YACT,OAAO,KAAC,KAAK,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QAC/C,KAAK,OAAO;YACV,OAAO,KAAC,aAAa,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QACvD,KAAK,WAAW;YACd,OAAO,KAAC,GAAG,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;IAC/C,CAAC;AACH,CAAC,CAAA;AAwBD,MAAM,UAAU,IAAI,CAAC,EACnB,IAAI,EACJ,MAAM,GAAG,MAAM,EACf,MAAM,EACN,QAAQ,EACR,WAAW,EACX,IAAI,EACJ,YAAY,EACZ,GAAG,KAAK,EACE;IACV,8EAA8E;IAC9E,2EAA2E;IAC3E,6BAA6B;IAC7B,MAAM,KAAK,GAAG,QAAQ,IAAI,IAAI,CAAA;IAE9B,MAAM,MAAM,GAAG,CACb,MAAC,MAAM,IAAC,KAAK,EAAC,QAAQ,EAAC,GAAG,EAAC,IAAI,EAAC,EAAE,EAAC,IAAI,EAAC,EAAE,EAAC,IAAI,EAAC,KAAK,EAAC,MAAM,aAC1D,KAAC,MAAM,IAAC,KAAK,EAAE,IAAI,GAAG,CAAC,EAAE,KAAK,EAAC,QAAQ,EAAC,OAAO,EAAC,QAAQ,EAAC,MAAM,EAAE,CAAC,YAC/D,IAAI,CAAC,MAAM,CAAC,GACN,EACT,KAAC,WAAW,IAAC,IAAI,EAAC,IAAI,EAAC,KAAK,EAAC,UAAU,EAAC,aAAa,EAAE,CAAC,YACrD,IAAI,GACO,EACb,MAAM,CAAC,CAAC,CAAC,CACR,KAAC,WAAW,IAAC,IAAI,EAAC,IAAI,EAAC,KAAK,EAAC,UAAU,EAAC,aAAa,EAAE,CAAC,EAAE,MAAM,EAAE,CAAC,YAChE,MAAM,GACK,CACf,CAAC,CAAC,CAAC,IAAI,EACR,KAAC,MAAM,IAAC,IAAI,EAAE,CAAC,GAAI,EAClB,KAAK,CAAC,CAAC,CAAC,KAAC,WAAW,IAAC,IAAI,EAAE,EAAE,EAAE,KAAK,EAAC,UAAU,GAAG,CAAC,CAAC,CAAC,IAAI,IACnD,CACV,CAAA;IAED,OAAO,CACL,MAAC,WAAW,OACN,IAAI,CAAC,MAAM,CAAC,iBACH,MAAM,EACnB,IAAI,EAAE,IAAI,EACV,WAAW,EAAE,WAAW,EACxB,YAAY,EAAE,YAAY,EAC1B,KAAK,EAAC,MAAM,EACZ,OAAO,EAAC,IAAI,EACZ,WAAW,EAAE,CAAC;QACd,0EAA0E;QAC1E,yEAAyE;QACzE,uEAAuE;QACvE,yEAAyE;QACzE,qCAAqC;QACrC,WAAW,EAAE,MAAM,KAAK,OAAO,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,cAAc,EAC5D,EAAE,EAAC,SAAS,EACZ,QAAQ,EAAC,QAAQ,KACb,KAAK,aAER,KAAK,CAAC,CAAC,CAAC,KAAC,kBAAkB,IAAC,KAAK,EAAC,MAAM,YAAE,MAAM,GAAsB,CAAC,CAAC,CAAC,MAAM,EAC/E,KAAK,CAAC,CAAC,CAAC,CACP,KAAC,kBAAkB,cACjB,KAAC,MAAM,OACD,IAAI,CAAC,WAAW,CAAC,EACrB,EAAE,EAAC,IAAI,EACP,EAAE,EAAC,MAAM,EACT,GAAG,EAAC,IAAI,EACR,cAAc,EAAE,CAAC,EACjB,WAAW,EAAC,cAAc,YAEzB,QAAQ,GACF,GACU,CACtB,CAAC,CAAC,CAAC,IAAI,IACI,CACf,CAAA;AACH,CAAC"}
+{"version":3,"file":"Step.js","sourceRoot":"","sources":["../../src/chat/Step.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;;;;;;;;GAaG;AACH,OAAO,EAAE,WAAW,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,YAAY,CAAA;AACxD,OAAO,EAAE,GAAG,EAAE,KAAK,EAAE,WAAW,EAAE,aAAa,EAAE,MAAM,0BAA0B,CAAA;AAGjF,OAAO,EAAE,WAAW,EAAE,kBAAkB,EAAE,kBAAkB,EAAE,OAAO,EAAE,MAAM,iBAAiB,CAAA;AAC9F,OAAO,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAA;AAM3C;cACc;AACd,MAAM,IAAI,GAAG,EAAE,CAAA;AAEf;;;;;;GAMG;AACH,MAAM,IAAI,GAAG,CAAC,MAAW,EAAE,EAAE;IAC3B,QAAQ,MAAM,EAAE,CAAC;QACf,KAAK,SAAS;YACZ,OAAO,KAAC,OAAO,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QACjD,KAAK,MAAM;YACT,OAAO,KAAC,KAAK,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QAC/C,KAAK,OAAO;YACV,OAAO,KAAC,aAAa,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;QACvD,KAAK,WAAW;YACd,OAAO,KAAC,GAAG,IAAC,IAAI,EAAE,IAAI,EAAE,KAAK,EAAC,UAAU,GAAG,CAAA;IAC/C,CAAC;AACH,CAAC,CAAA;AAoBD,MAAM,UAAU,IAAI,CAAC,EACnB,IAAI,EACJ,MAAM,GAAG,MAAM,EACf,MAAM,EACN,QAAQ,EACR,WAAW,EACX,IAAI,EACJ,YAAY,EACZ,GAAG,KAAK,EACE;IACV,6EAA6E;IAC7E,yCAAyC;IACzC,MAAM,KAAK,GAAG,QAAQ,IAAI,IAAI,CAAA;IAE9B,MAAM,MAAM,GAAG,CACb,MAAC,MAAM,IAAC,KAAK,EAAC,QAAQ,EAAC,GAAG,EAAC,IAAI,EAAC,EAAE,EAAC,IAAI,EAAC,EAAE,EAAC,IAAI,EAAC,KAAK,EAAC,MAAM,aAC1D,KAAC,MAAM,IAAC,KAAK,EAAE,IAAI,GAAG,CAAC,EAAE,KAAK,EAAC,QAAQ,EAAC,OAAO,EAAC,QAAQ,EAAC,MAAM,EAAE,CAAC,YAC/D,IAAI,CAAC,MAAM,CAAC,GACN,EACT,KAAC,WAAW,IAAC,IAAI,EAAC,IAAI,EAAC,KAAK,EAAC,UAAU,EAAC,aAAa,EAAE,CAAC,YACrD,IAAI,GACO,EACb,MAAM,CAAC,CAAC,CAAC,CACR,KAAC,WAAW,IAAC,IAAI,EAAC,IAAI,EAAC,KAAK,EAAC,UAAU,EAAC,aAAa,EAAE,CAAC,EAAE,MAAM,EAAE,CAAC,YAChE,MAAM,GACK,CACf,CAAC,CAAC,CAAC,IAAI,EACR,KAAC,MAAM,IAAC,IAAI,EAAE,CAAC,GAAI,EAClB,KAAK,CAAC,CAAC,CAAC,KAAC,WAAW,IAAC,IAAI,EAAE,EAAE,EAAE,KAAK,EAAC,UAAU,GAAG,CAAC,CAAC,CAAC,IAAI,IACnD,CACV,CAAA;IAED,OAAO,CACL,MAAC,WAAW,OACN,IAAI,CAAC,MAAM,CAAC,iBACH,MAAM,EACnB,IAAI,EAAE,IAAI,EACV,WAAW,EAAE,WAAW,EACxB,YAAY,EAAE,YAAY,EAC1B,KAAK,EAAC,MAAM,EACZ,OAAO,EAAC,IAAI,EACZ,WAAW,EAAE,CAAC;QACd,uEAAuE;QACvE,qDAAqD;QACrD,WAAW,EAAE,MAAM,KAAK,OAAO,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,CAAC,cAAc,EAC5D,EAAE,EAAC,SAAS,EACZ,QAAQ,EAAC,QAAQ,KACb,KAAK,aAER,KAAK,CAAC,CAAC,CAAC,KAAC,kBAAkB,IAAC,KAAK,EAAC,MAAM,YAAE,MAAM,GAAsB,CAAC,CAAC,CAAC,MAAM,EAC/E,KAAK,CAAC,CAAC,CAAC,CACP,KAAC,kBAAkB,cACjB,KAAC,MAAM,OACD,IAAI,CAAC,WAAW,CAAC,EACrB,EAAE,EAAC,IAAI,EACP,EAAE,EAAC,MAAM,EACT,GAAG,EAAC,IAAI,EACR,cAAc,EAAE,CAAC,EACjB,WAAW,EAAC,cAAc,YAEzB,QAAQ,GACF,GACU,CACtB,CAAC,CAAC,CAAC,IAAI,IACI,CACf,CAAA;AACH,CAAC"}

package/dist/chat/Thread.cjs

@@ -6,32 +6,9 @@ const jsx_runtime_1 = require("react/jsx-runtime");
 /**
  * Thread — the scrolling column of turns.
  *
- * It does the one thing every surface had re-solved: follow a streaming answer
- * to the bottom, and stop following the instant the reader scrolls up. The
- * decision is `pinned()`, asserted without a DOM; this component only wires it
- * to the platform's scroll view, so momentum and keyboard stay the host's.
- *
- * That decision is now the fleet's only answer to "am I at the bottom", which
- * had five: 50px in two places, 97%-of-height in a third, an
- * `IntersectionObserver` at a 0.85 ratio in a fourth, and on the thread itself
- * nothing at all — hanzo.app `/chat` ran `scrollIntoView({behavior:'smooth'})`
- * on every `messages` change, and since a streaming turn rewrites `messages`
- * per SSE delta, scrolling up to re-read was undone several times a second.
- *
- * Measured in Chromium against the packed tarball, 2500 tokens at 4ms:
- * following holds a 0px gap through 2501 commits; parked at offset 0 the reader
- * STAYS at 0 while content grows 1015 → 1375; returning to the end resumes
- * following at 0px.
- *
- * There is no `onLayout` here any more, and nothing is lost with it. It was
- * passed to keep a `track` ref current, gui does not implement it on this
- * component so React forwarded it to the DOM as an unknown handler — the noise
- * hanzo.app reported — and the ref it fed was WRITE-ONLY: `track` was read in
- * exactly one place, `onScroll`, which rebuilds all three numbers from the
- * event before reading them. So the handler was dead, the state it kept was
- * dead, and the measurement the two together looked like they were doing was
- * being done properly a few lines below the whole time. The scroll event
- * carries `layoutMeasurement`; nothing else needs to ask.
+ * Follows a streaming answer to the bottom and stops the moment the reader
+ * scrolls up. The decision is `pinned()`; this only wires it to the platform's
+ * scroll view, so momentum and keyboard stay the host's.
  */
 const gui_1 = require("@hanzo/gui");
 const react_1 = require("react");
@@ -42,7 +19,7 @@ const MEASURE = 768;
 exports.Thread = (0, react_1.forwardRef)(function Thread({ children, maxWidth = MEASURE, slack = stick_1.SLACK, gap = 24, onScroll, column, ...props }, ref) {
     const view = (0, react_1.useRef)(null);
     const follow = (0, react_1.useRef)(true);
-    // Ours to scroll with, the caller's because three consumers need this node.
+    // Ours to scroll with, and the caller's.
     const hold = (0, react_1.useCallback)((el) => {
         view.current = el;
         if (typeof ref === 'function')

package/dist/chat/Thread.d.ts

@@ -1,32 +1,9 @@
 /**
  * Thread — the scrolling column of turns.
  *
- * It does the one thing every surface had re-solved: follow a streaming answer
- * to the bottom, and stop following the instant the reader scrolls up. The
- * decision is `pinned()`, asserted without a DOM; this component only wires it
- * to the platform's scroll view, so momentum and keyboard stay the host's.
- *
- * That decision is now the fleet's only answer to "am I at the bottom", which
- * had five: 50px in two places, 97%-of-height in a third, an
- * `IntersectionObserver` at a 0.85 ratio in a fourth, and on the thread itself
- * nothing at all — hanzo.app `/chat` ran `scrollIntoView({behavior:'smooth'})`
- * on every `messages` change, and since a streaming turn rewrites `messages`
- * per SSE delta, scrolling up to re-read was undone several times a second.
- *
- * Measured in Chromium against the packed tarball, 2500 tokens at 4ms:
- * following holds a 0px gap through 2501 commits; parked at offset 0 the reader
- * STAYS at 0 while content grows 1015 → 1375; returning to the end resumes
- * following at 0px.
- *
- * There is no `onLayout` here any more, and nothing is lost with it. It was
- * passed to keep a `track` ref current, gui does not implement it on this
- * component so React forwarded it to the DOM as an unknown handler — the noise
- * hanzo.app reported — and the ref it fed was WRITE-ONLY: `track` was read in
- * exactly one place, `onScroll`, which rebuilds all three numbers from the
- * event before reading them. So the handler was dead, the state it kept was
- * dead, and the measurement the two together looked like they were doing was
- * being done properly a few lines below the whole time. The scroll event
- * carries `layoutMeasurement`; nothing else needs to ask.
+ * Follows a streaming answer to the bottom and stops the moment the reader
+ * scrolls up. The decision is `pinned()`; this only wires it to the platform's
+ * scroll view, so momentum and keyboard stay the host's.
  */
 import { ScrollView, YStack, type GetRef } from '@hanzo/gui';
 import { type ComponentProps, type ReactNode } from 'react';
@@ -43,14 +20,7 @@ export interface ThreadProps extends Omit<ComponentProps<typeof ScrollView>, 'ch
     /** How near the end still counts as "at the bottom", in px. */
     slack?: number;
     gap?: number;
-    /**
-     * The scroll, after the follow decision is made — with `at`, the answer.
-     *
-     * Three separate consumers need this element and this fact: the follow
-     * decision, a scroll-to-bottom button, and a surface's own turn-offset
-     * bookkeeping. Deciding privately and publishing nothing is what left each of
-     * them measuring the scroller again, differently.
-     */
+    /** The scroll, with the follow decision and the numbers it was made from. */
     onScroll?: (event: unknown, at: {
         pinned: boolean;
         track: Track;

package/dist/chat/Thread.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"Thread.d.ts","sourceRoot":"","sources":["../../src/chat/Thread.tsx"],"names":[],"mappings":"AAEA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,EAAE,KAAK,MAAM,EAAE,MAAM,YAAY,CAAA;AAC5D,OAAO,EAAmC,KAAK,cAAc,EAAE,KAAK,SAAS,EAAE,MAAM,OAAO,CAAA;AAG5F,OAAO,EAAiB,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA;AAKnD,KAAK,QAAQ,GAAG,MAAM,CAAC,OAAO,UAAU,CAAC,GAAG;IAAE,WAAW,CAAC,CAAC,EAAE;QAAE,QAAQ,EAAE,OAAO,CAAA;KAAE,GAAG,IAAI,CAAA;CAAE,CAAA;AAE3F,MAAM,WAAW,WACf,SAAQ,IAAI,CAAC,cAAc,CAAC,OAAO,UAAU,CAAC,EAAE,UAAU,GAAG,UAAU,CAAC;IACxE,QAAQ,CAAC,EAAE,SAAS,CAAA;IACpB,2DAA2D;IAC3D,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,+DAA+D;IAC/D,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ;;;;;;;OAOG;IACH,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE,EAAE;QAAE,MAAM,EAAE,OAAO,CAAC;QAAC,KAAK,EAAE,KAAK,CAAA;KAAE,KAAK,IAAI,CAAA;IAC1E,6EAA6E;IAC7E,MAAM,CAAC,EAAE,IAAI,CAAC,cAAc,CAAC,OAAO,MAAM,CAAC,EAAE,UAAU,CAAC,CAAA;CACzD;AAED,eAAO,MAAM,MAAM,+GAqDjB,CAAA"}
+{"version":3,"file":"Thread.d.ts","sourceRoot":"","sources":["../../src/chat/Thread.tsx"],"names":[],"mappings":"AAEA;;;;;;GAMG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,EAAE,KAAK,MAAM,EAAE,MAAM,YAAY,CAAA;AAC5D,OAAO,EAAmC,KAAK,cAAc,EAAE,KAAK,SAAS,EAAE,MAAM,OAAO,CAAA;AAG5F,OAAO,EAAiB,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA;AAKnD,KAAK,QAAQ,GAAG,MAAM,CAAC,OAAO,UAAU,CAAC,GAAG;IAAE,WAAW,CAAC,CAAC,EAAE;QAAE,QAAQ,EAAE,OAAO,CAAA;KAAE,GAAG,IAAI,CAAA;CAAE,CAAA;AAE3F,MAAM,WAAW,WACf,SAAQ,IAAI,CAAC,cAAc,CAAC,OAAO,UAAU,CAAC,EAAE,UAAU,GAAG,UAAU,CAAC;IACxE,QAAQ,CAAC,EAAE,SAAS,CAAA;IACpB,2DAA2D;IAC3D,QAAQ,CAAC,EAAE,MAAM,CAAA;IACjB,+DAA+D;IAC/D,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,GAAG,CAAC,EAAE,MAAM,CAAA;IACZ,6EAA6E;IAC7E,QAAQ,CAAC,EAAE,CAAC,KAAK,EAAE,OAAO,EAAE,EAAE,EAAE;QAAE,MAAM,EAAE,OAAO,CAAC;QAAC,KAAK,EAAE,KAAK,CAAA;KAAE,KAAK,IAAI,CAAA;IAC1E,6EAA6E;IAC7E,MAAM,CAAC,EAAE,IAAI,CAAC,cAAc,CAAC,OAAO,MAAM,CAAC,EAAE,UAAU,CAAC,CAAA;CACzD;AAED,eAAO,MAAM,MAAM,+GAqDjB,CAAA"}

package/dist/chat/Thread.js

@@ -3,32 +3,9 @@ import { jsx as _jsx } from "react/jsx-runtime";
 /**
  * Thread — the scrolling column of turns.
  *
- * It does the one thing every surface had re-solved: follow a streaming answer
- * to the bottom, and stop following the instant the reader scrolls up. The
- * decision is `pinned()`, asserted without a DOM; this component only wires it
- * to the platform's scroll view, so momentum and keyboard stay the host's.
- *
- * That decision is now the fleet's only answer to "am I at the bottom", which
- * had five: 50px in two places, 97%-of-height in a third, an
- * `IntersectionObserver` at a 0.85 ratio in a fourth, and on the thread itself
- * nothing at all — hanzo.app `/chat` ran `scrollIntoView({behavior:'smooth'})`
- * on every `messages` change, and since a streaming turn rewrites `messages`
- * per SSE delta, scrolling up to re-read was undone several times a second.
- *
- * Measured in Chromium against the packed tarball, 2500 tokens at 4ms:
- * following holds a 0px gap through 2501 commits; parked at offset 0 the reader
- * STAYS at 0 while content grows 1015 → 1375; returning to the end resumes
- * following at 0px.
- *
- * There is no `onLayout` here any more, and nothing is lost with it. It was
- * passed to keep a `track` ref current, gui does not implement it on this
- * component so React forwarded it to the DOM as an unknown handler — the noise
- * hanzo.app reported — and the ref it fed was WRITE-ONLY: `track` was read in
- * exactly one place, `onScroll`, which rebuilds all three numbers from the
- * event before reading them. So the handler was dead, the state it kept was
- * dead, and the measurement the two together looked like they were doing was
- * being done properly a few lines below the whole time. The scroll event
- * carries `layoutMeasurement`; nothing else needs to ask.
+ * Follows a streaming answer to the bottom and stops the moment the reader
+ * scrolls up. The decision is `pinned()`; this only wires it to the platform's
+ * scroll view, so momentum and keyboard stay the host's.
  */
 import { ScrollView, YStack } from '@hanzo/gui';
 import { forwardRef, useCallback, useRef } from 'react';
@@ -39,7 +16,7 @@ const MEASURE = 768;
 export const Thread = /* @__PURE__ */ forwardRef(function Thread({ children, maxWidth = MEASURE, slack = SLACK, gap = 24, onScroll, column, ...props }, ref) {
     const view = useRef(null);
     const follow = useRef(true);
-    // Ours to scroll with, the caller's because three consumers need this node.
+    // Ours to scroll with, and the caller's.
     const hold = useCallback((el) => {
         view.current = el;
         if (typeof ref === 'function')

package/dist/chat/Thread.js.map

@@ -1 +1 @@
-{"version":3,"file":"Thread.js","sourceRoot":"","sources":["../../src/chat/Thread.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,EAAe,MAAM,YAAY,CAAA;AAC5D,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,MAAM,EAAuC,MAAM,OAAO,CAAA;AAE5F,OAAO,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAA;AAC3C,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA;AAEnD,4CAA4C;AAC5C,MAAM,OAAO,GAAG,GAAG,CAAA;AAyBnB,MAAM,CAAC,MAAM,MAAM,GAAG,eAAe,CAAC,UAAU,CAAwB,SAAS,MAAM,CACrF,EAAE,QAAQ,EAAE,QAAQ,GAAG,OAAO,EAAE,KAAK,GAAG,KAAK,EAAE,GAAG,GAAG,EAAE,EAAE,QAAQ,EAAE,MAAM,EAAE,GAAG,KAAK,EAAE,EACrF,GAAG;IAEH,MAAM,IAAI,GAAG,MAAM,CAAkB,IAAI,CAAC,CAAA;IAC1C,MAAM,MAAM,GAAG,MAAM,CAAC,IAAI,CAAC,CAAA;IAE3B,4EAA4E;IAC5E,MAAM,IAAI,GAAG,WAAW,CACtB,CAAC,EAAmB,EAAE,EAAE;QACtB,IAAI,CAAC,OAAO,GAAG,EAAE,CAAA;QACjB,IAAI,OAAO,GAAG,KAAK,UAAU;YAAE,GAAG,CAAC,EAAE,CAAC,CAAA;aACjC,IAAI,GAAG;YAAG,GAA+C,CAAC,OAAO,GAAG,EAAE,CAAA;IAC7E,CAAC,EACD,CAAC,GAAG,CAAC,CACN,CAAA;IAED,MAAM,IAAI,GAAG,WAAW,CAAC,GAAG,EAAE;QAC5B,IAAI,MAAM,CAAC,OAAO;YAAE,IAAI,CAAC,OAAO,EAAE,WAAW,CAAC,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC,CAAA;IACpE,CAAC,EAAE,EAAE,CAAC,CAAA;IAEN,OAAO,CACL,KAAC,UAAU,IACT,GAAG,EAAE,IAAa,KACd,IAAI,CAAC,QAAQ,CAAC,EAClB,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,mBAAmB,EAAE,EAAE,EACvB,mBAAmB,EAAE,IAAI,EACzB,QAAQ,EAAE,CAAC,CAAM,EAAE,EAAE;YACnB,MAAM,EAAE,aAAa,EAAE,iBAAiB,EAAE,WAAW,EAAE,GAAG,CAAC,CAAC,WAAW,CAAA;YACvE,MAAM,KAAK,GAAU;gBACnB,MAAM,EAAE,aAAa,CAAC,CAAC;gBACvB,QAAQ,EAAE,iBAAiB,CAAC,MAAM;gBAClC,OAAO,EAAE,WAAW,CAAC,MAAM;aAC5B,CAAA;YACD,MAAM,CAAC,OAAO,GAAG,MAAM,CAAC,KAAK,EAAE,KAAK,CAAC,CAAA;YACrC,QAAQ,EAAE,CAAC,CAAC,EAAE,EAAE,MAAM,EAAE,MAAM,CAAC,OAAO,EAAE,KAAK,EAAE,CAAC,CAAA;QAClD,CAAC,KACG,KAAK,YAET,KAAC,MAAM,OACD,IAAI,CAAC,eAAe,CAAC,EACzB,KAAK,EAAC,MAAM,EACZ,GAAG,EAAE,GAAG,EACR,EAAE,EAAE,GAAG,KACH,CAAC,QAAQ,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,IAAI,EAAE,QAAiB,EAAE,EAAE,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,KACzE,MAAM,YAET,QAAQ,GACF,GACE,CACd,CAAA;AACH,CAAC,CAAC,CAAA"}
+{"version":3,"file":"Thread.js","sourceRoot":"","sources":["../../src/chat/Thread.tsx"],"names":[],"mappings":"AAAA,YAAY,CAAA;;AAEZ;;;;;;GAMG;AACH,OAAO,EAAE,UAAU,EAAE,MAAM,EAAe,MAAM,YAAY,CAAA;AAC5D,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,MAAM,EAAuC,MAAM,OAAO,CAAA;AAE5F,OAAO,EAAE,IAAI,EAAE,MAAM,sBAAsB,CAAA;AAC3C,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA;AAEnD,4CAA4C;AAC5C,MAAM,OAAO,GAAG,GAAG,CAAA;AAkBnB,MAAM,CAAC,MAAM,MAAM,GAAG,eAAe,CAAC,UAAU,CAAwB,SAAS,MAAM,CACrF,EAAE,QAAQ,EAAE,QAAQ,GAAG,OAAO,EAAE,KAAK,GAAG,KAAK,EAAE,GAAG,GAAG,EAAE,EAAE,QAAQ,EAAE,MAAM,EAAE,GAAG,KAAK,EAAE,EACrF,GAAG;IAEH,MAAM,IAAI,GAAG,MAAM,CAAkB,IAAI,CAAC,CAAA;IAC1C,MAAM,MAAM,GAAG,MAAM,CAAC,IAAI,CAAC,CAAA;IAE3B,yCAAyC;IACzC,MAAM,IAAI,GAAG,WAAW,CACtB,CAAC,EAAmB,EAAE,EAAE;QACtB,IAAI,CAAC,OAAO,GAAG,EAAE,CAAA;QACjB,IAAI,OAAO,GAAG,KAAK,UAAU;YAAE,GAAG,CAAC,EAAE,CAAC,CAAA;aACjC,IAAI,GAAG;YAAG,GAA+C,CAAC,OAAO,GAAG,EAAE,CAAA;IAC7E,CAAC,EACD,CAAC,GAAG,CAAC,CACN,CAAA;IAED,MAAM,IAAI,GAAG,WAAW,CAAC,GAAG,EAAE;QAC5B,IAAI,MAAM,CAAC,OAAO;YAAE,IAAI,CAAC,OAAO,EAAE,WAAW,CAAC,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC,CAAA;IACpE,CAAC,EAAE,EAAE,CAAC,CAAA;IAEN,OAAO,CACL,KAAC,UAAU,IACT,GAAG,EAAE,IAAa,KACd,IAAI,CAAC,QAAQ,CAAC,EAClB,IAAI,EAAE,CAAC,EACP,KAAK,EAAC,MAAM,EACZ,mBAAmB,EAAE,EAAE,EACvB,mBAAmB,EAAE,IAAI,EACzB,QAAQ,EAAE,CAAC,CAAM,EAAE,EAAE;YACnB,MAAM,EAAE,aAAa,EAAE,iBAAiB,EAAE,WAAW,EAAE,GAAG,CAAC,CAAC,WAAW,CAAA;YACvE,MAAM,KAAK,GAAU;gBACnB,MAAM,EAAE,aAAa,CAAC,CAAC;gBACvB,QAAQ,EAAE,iBAAiB,CAAC,MAAM;gBAClC,OAAO,EAAE,WAAW,CAAC,MAAM;aAC5B,CAAA;YACD,MAAM,CAAC,OAAO,GAAG,MAAM,CAAC,KAAK,EAAE,KAAK,CAAC,CAAA;YACrC,QAAQ,EAAE,CAAC,CAAC,EAAE,EAAE,MAAM,EAAE,MAAM,CAAC,OAAO,EAAE,KAAK,EAAE,CAAC,CAAA;QAClD,CAAC,KACG,KAAK,YAET,KAAC,MAAM,OACD,IAAI,CAAC,eAAe,CAAC,EACzB,KAAK,EAAC,MAAM,EACZ,GAAG,EAAE,GAAG,EACR,EAAE,EAAE,GAAG,KACH,CAAC,QAAQ,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,QAAQ,EAAE,IAAI,EAAE,QAAiB,EAAE,EAAE,EAAE,IAAI,EAAE,CAAC,CAAC,CAAC,IAAI,CAAC,KACzE,MAAM,YAET,QAAQ,GACF,GACE,CACd,CAAA;AACH,CAAC,CAAC,CAAA"}

package/dist/chat/index.cjs

@@ -4,73 +4,32 @@ exports.SourceCard = exports.Sources = exports.Failure = exports.Step = exports.
 /**
  * @hanzo/ui/chat — the one chat shell, on @hanzo/gui primitives.
  *
- * Shell only: Thread scrolls, Message presents a turn, Composer takes a draft,
- * Sidebar navigates between conversations, Header names the current one, and
- * Code, Step, Failure and Sources present the pieces of a turn every surface
- * renders the same way.
+ * Thread scrolls, Message presents a turn, Composer takes a draft, Sidebar
+ * navigates between conversations, Header names the current one, and Code,
+ * Step, Failure and Sources present the pieces of a turn.
  *
- * This file used to end that sentence with "Content rendering (markdown, tool
- * calls) stays with the surface — they disagree on the pipeline, and none of it
- * is presentational." Half of that was right and the half that was wrong cost
- * nine hand-drawn copies. Re-decided by reading what the three surfaces
- * actually render:
+ * The markdown pipeline is the surface's and arrives as `children`: the three
+ * surfaces run nine plugins, one plugin, and a regex under a bundle ceiling
+ * that cannot afford a parser. There is no `renderPart` prop for the same
+ * reason — the part union is per-surface too, so a callback here would take a
+ * Part type matching nobody's.
  *
- *   MARKDOWN STAYS OUT, and not as a preference. hanzo/chat runs seven remark
- *   plugins and two rehype plugins (`Content/Markdown.tsx:42-65`, including
- *   katex and highlight.js over a 35-language subset); hanzo.app runs
- *   remark-gfm and nothing else (`markdown-renderer/index.tsx:107`); the
- *   extension parses markdown with eighty lines of regex and no dependency at
- *   all (`answer/markdown.ts`) because `newtab.js` measures 485.9 KB against a
- *   500 KB ceiling that fails the build (`scripts/check-bundle-budgets.mjs:29`)
- *   and its MV3 policy is `script-src 'self'`. Fourteen kilobytes of headroom
- *   is not a pipeline disagreement to be reconciled; it is a surface that
- *   cannot afford a parser. So the pipeline is the surface's, and `children` is
- *   how it arrives — which is also why there is no `renderPart` prop: the part
- *   UNION is per-surface too (twelve item types in the app's
- *   `chat-panel/index.tsx` `TurnDisplay`, eight in chat's `Content/Part.tsx`,
- *   none in the extension), so a callback here would need a Part type that
- *   matches nobody's. The surface maps its own parts and passes nodes.
+ * Everything else about a turn is presentational and lives here: the code
+ * frame, the step disclosure, the failure, the streaming caret.
  *
- *   THE REST OF IT WAS ALWAYS PRESENTATIONAL. A code block with a language
- *   label and a copy control, a collapsible step with a state mark, a failure
- *   with a retry, a streaming caret — every surface draws these and no two draw
- *   them alike. `Step` alone replaces nine copies across two repos. What is
- *   inside each of them is still `children`; the frame, the header, the mark
- *   and the disclosure are here.
+ * Props-in, callbacks-out — no transport, no store, no routing. Each component
+ * spreads its residual props, and the three that own an inner part publish a
+ * way through to it (`Message body`, `Thread column`, `Composer field`).
  *
- * Everything is props-in, callbacks-out: no transport, no store, no routing, no
- * active-id resolution. The same components serve a live conversation, a shared
- * read-only transcript and a test fixture.
+ * `@hanzo/ui/chat/pure` carries `sends`, `ready`, `pinned` and `SLACK` with no
+ * imports, for Node and for callers that are not chat.
  *
- * Every component here spreads its residual props onto its own element, and
- * `Message`, `Thread` and `Composer` publish a way through to the part they own
- * (`body`, `column`, `field`). They did not, and that closed list was the ONE
- * thing keeping hanzo/chat from adopting `Message`: its scroll machinery
- * addresses turns by `id`, `SelectionAsk` finds one with
- * `closest('.message-render')`, and its turn wears a fleet-wide `glass`
- * material against a `bg` welded to `$color3`. None of it exotic, all of it
- * free with a spread — gui forwards what it does not recognise, which is the
- * mechanism `slot()` is already built on.
+ * Styling is `$` tokens throughout, never literal colours, so a brand retunes
+ * through its own theme and nothing here carries a mark.
  *
- * `@hanzo/ui/chat/pure` is the same module's decisions with nothing attached:
- * `sends`, `ready`, `pinned`, `SLACK`. It exists because `import('@hanzo/ui/chat')`
- * cannot load in Node, so no script and no spec could reach them. They are also
- * re-exported from `@hanzo/ui/product/pure`, because they are not chat rules —
- * ten of the fifteen files importing `sends` in hanzo.app are a SQL editor, a
- * file explorer, a command palette, a rename field.
- *
- * Styling is `$` tokens throughout, never literal colours, so each brand retunes
- * through its own theme and nothing here carries a Hanzo mark — which is what
- * lets the same shell ship on Lux and Zoo surfaces without leaking a brand.
- *
- * The model picker is not here: it already ships at `@hanzo/ui/models`, and it
- * is not chat-specific.
- *
- * `CopyButton` is not here either, for the same reason and after the same
- * mistake: it lived in `Code.tsx`, so the only way to reach it was
- * `@hanzo/ui/chat`, and no one hunting for a copy button looks in a chat module.
- * Six surfaces wrote their own instead. It now ships at `@hanzo/ui/product`;
- * `Code` imports it from there.
+ * The model picker and `CopyButton` are not here — neither is chat-specific, so
+ * they ship at `@hanzo/ui/models` and `@hanzo/ui/product`. Nobody hunting for a
+ * copy button looks in a chat module.
  */
 var Composer_1 = require("./Composer.cjs");
 Object.defineProperty(exports, "Composer", { enumerable: true, get: function () { return Composer_1.Composer; } });

package/dist/chat/index.d.ts

@@ -1,73 +1,32 @@
 /**
  * @hanzo/ui/chat — the one chat shell, on @hanzo/gui primitives.
  *
- * Shell only: Thread scrolls, Message presents a turn, Composer takes a draft,
- * Sidebar navigates between conversations, Header names the current one, and
- * Code, Step, Failure and Sources present the pieces of a turn every surface
- * renders the same way.
+ * Thread scrolls, Message presents a turn, Composer takes a draft, Sidebar
+ * navigates between conversations, Header names the current one, and Code,
+ * Step, Failure and Sources present the pieces of a turn.
  *
- * This file used to end that sentence with "Content rendering (markdown, tool
- * calls) stays with the surface — they disagree on the pipeline, and none of it
- * is presentational." Half of that was right and the half that was wrong cost
- * nine hand-drawn copies. Re-decided by reading what the three surfaces
- * actually render:
+ * The markdown pipeline is the surface's and arrives as `children`: the three
+ * surfaces run nine plugins, one plugin, and a regex under a bundle ceiling
+ * that cannot afford a parser. There is no `renderPart` prop for the same
+ * reason — the part union is per-surface too, so a callback here would take a
+ * Part type matching nobody's.
  *
- *   MARKDOWN STAYS OUT, and not as a preference. hanzo/chat runs seven remark
- *   plugins and two rehype plugins (`Content/Markdown.tsx:42-65`, including
- *   katex and highlight.js over a 35-language subset); hanzo.app runs
- *   remark-gfm and nothing else (`markdown-renderer/index.tsx:107`); the
- *   extension parses markdown with eighty lines of regex and no dependency at
- *   all (`answer/markdown.ts`) because `newtab.js` measures 485.9 KB against a
- *   500 KB ceiling that fails the build (`scripts/check-bundle-budgets.mjs:29`)
- *   and its MV3 policy is `script-src 'self'`. Fourteen kilobytes of headroom
- *   is not a pipeline disagreement to be reconciled; it is a surface that
- *   cannot afford a parser. So the pipeline is the surface's, and `children` is
- *   how it arrives — which is also why there is no `renderPart` prop: the part
- *   UNION is per-surface too (twelve item types in the app's
- *   `chat-panel/index.tsx` `TurnDisplay`, eight in chat's `Content/Part.tsx`,
- *   none in the extension), so a callback here would need a Part type that
- *   matches nobody's. The surface maps its own parts and passes nodes.
+ * Everything else about a turn is presentational and lives here: the code
+ * frame, the step disclosure, the failure, the streaming caret.
  *
- *   THE REST OF IT WAS ALWAYS PRESENTATIONAL. A code block with a language
- *   label and a copy control, a collapsible step with a state mark, a failure
- *   with a retry, a streaming caret — every surface draws these and no two draw
- *   them alike. `Step` alone replaces nine copies across two repos. What is
- *   inside each of them is still `children`; the frame, the header, the mark
- *   and the disclosure are here.
+ * Props-in, callbacks-out — no transport, no store, no routing. Each component
+ * spreads its residual props, and the three that own an inner part publish a
+ * way through to it (`Message body`, `Thread column`, `Composer field`).
  *
- * Everything is props-in, callbacks-out: no transport, no store, no routing, no
- * active-id resolution. The same components serve a live conversation, a shared
- * read-only transcript and a test fixture.
+ * `@hanzo/ui/chat/pure` carries `sends`, `ready`, `pinned` and `SLACK` with no
+ * imports, for Node and for callers that are not chat.
  *
- * Every component here spreads its residual props onto its own element, and
- * `Message`, `Thread` and `Composer` publish a way through to the part they own
- * (`body`, `column`, `field`). They did not, and that closed list was the ONE
- * thing keeping hanzo/chat from adopting `Message`: its scroll machinery
- * addresses turns by `id`, `SelectionAsk` finds one with
- * `closest('.message-render')`, and its turn wears a fleet-wide `glass`
- * material against a `bg` welded to `$color3`. None of it exotic, all of it
- * free with a spread — gui forwards what it does not recognise, which is the
- * mechanism `slot()` is already built on.
+ * Styling is `$` tokens throughout, never literal colours, so a brand retunes
+ * through its own theme and nothing here carries a mark.
  *
- * `@hanzo/ui/chat/pure` is the same module's decisions with nothing attached:
- * `sends`, `ready`, `pinned`, `SLACK`. It exists because `import('@hanzo/ui/chat')`
- * cannot load in Node, so no script and no spec could reach them. They are also
- * re-exported from `@hanzo/ui/product/pure`, because they are not chat rules —
- * ten of the fifteen files importing `sends` in hanzo.app are a SQL editor, a
- * file explorer, a command palette, a rename field.
- *
- * Styling is `$` tokens throughout, never literal colours, so each brand retunes
- * through its own theme and nothing here carries a Hanzo mark — which is what
- * lets the same shell ship on Lux and Zoo surfaces without leaking a brand.
- *
- * The model picker is not here: it already ships at `@hanzo/ui/models`, and it
- * is not chat-specific.
- *
- * `CopyButton` is not here either, for the same reason and after the same
- * mistake: it lived in `Code.tsx`, so the only way to reach it was
- * `@hanzo/ui/chat`, and no one hunting for a copy button looks in a chat module.
- * Six surfaces wrote their own instead. It now ships at `@hanzo/ui/product`;
- * `Code` imports it from there.
+ * The model picker and `CopyButton` are not here — neither is chat-specific, so
+ * they ship at `@hanzo/ui/models` and `@hanzo/ui/product`. Nobody hunting for a
+ * copy button looks in a chat module.
  */
 export { Composer, ASK, type ComposerProps } from './Composer.js';
 export { Caret, Message, type MessageProps, type Role } from './Message.js';

package/dist/chat/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/chat/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsEG;AACH,OAAO,EAAE,QAAQ,EAAE,GAAG,EAAE,KAAK,aAAa,EAAE,MAAM,YAAY,CAAA;AAC9D,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,KAAK,YAAY,EAAE,KAAK,IAAI,EAAE,MAAM,WAAW,CAAA;AACxE,OAAO,EAAE,MAAM,EAAE,KAAK,WAAW,EAAE,MAAM,UAAU,CAAA;AACnD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,IAAI,EAAE,MAAM,QAAQ,CAAA;AAChD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA;AAEnD,OAAO,EACL,OAAO,EACP,aAAa,EACb,iBAAiB,EACjB,cAAc,EACd,aAAa,EACb,cAAc,EACd,WAAW,EACX,aAAa,EACb,WAAW,EACX,KAAK,YAAY,EACjB,KAAK,kBAAkB,EACvB,KAAK,sBAAsB,EAC3B,KAAK,mBAAmB,EACxB,KAAK,mBAAmB,EACxB,KAAK,gBAAgB,EACrB,KAAK,kBAAkB,EACvB,KAAK,gBAAgB,GACtB,MAAM,WAAW,CAAA;AAElB,OAAO,EACL,MAAM,EACN,YAAY,EACZ,WAAW,EACX,WAAW,EACX,KAAK,EACL,KAAK,WAAW,EAChB,KAAK,iBAAiB,EACtB,KAAK,gBAAgB,EACrB,KAAK,gBAAgB,EACrB,KAAK,UAAU,GAChB,MAAM,UAAU,CAAA;AAEjB,OAAO,EAAE,IAAI,EAAE,KAAK,SAAS,EAAE,MAAM,QAAQ,CAAA;AAC7C,OAAO,EAAE,IAAI,EAAE,KAAK,SAAS,EAAE,KAAK,GAAG,EAAE,MAAM,QAAQ,CAAA;AACvD,OAAO,EAAE,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,WAAW,CAAA;AAEtD,OAAO,EACL,OAAO,EACP,UAAU,EACV,KAAK,MAAM,EACX,KAAK,YAAY,EACjB,KAAK,eAAe,GACrB,MAAM,WAAW,CAAA"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/chat/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAE,QAAQ,EAAE,GAAG,EAAE,KAAK,aAAa,EAAE,MAAM,YAAY,CAAA;AAC9D,OAAO,EAAE,KAAK,EAAE,OAAO,EAAE,KAAK,YAAY,EAAE,KAAK,IAAI,EAAE,MAAM,WAAW,CAAA;AACxE,OAAO,EAAE,MAAM,EAAE,KAAK,WAAW,EAAE,MAAM,UAAU,CAAA;AACnD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,IAAI,EAAE,MAAM,QAAQ,CAAA;AAChD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA;AAEnD,OAAO,EACL,OAAO,EACP,aAAa,EACb,iBAAiB,EACjB,cAAc,EACd,aAAa,EACb,cAAc,EACd,WAAW,EACX,aAAa,EACb,WAAW,EACX,KAAK,YAAY,EACjB,KAAK,kBAAkB,EACvB,KAAK,sBAAsB,EAC3B,KAAK,mBAAmB,EACxB,KAAK,mBAAmB,EACxB,KAAK,gBAAgB,EACrB,KAAK,kBAAkB,EACvB,KAAK,gBAAgB,GACtB,MAAM,WAAW,CAAA;AAElB,OAAO,EACL,MAAM,EACN,YAAY,EACZ,WAAW,EACX,WAAW,EACX,KAAK,EACL,KAAK,WAAW,EAChB,KAAK,iBAAiB,EACtB,KAAK,gBAAgB,EACrB,KAAK,gBAAgB,EACrB,KAAK,UAAU,GAChB,MAAM,UAAU,CAAA;AAEjB,OAAO,EAAE,IAAI,EAAE,KAAK,SAAS,EAAE,MAAM,QAAQ,CAAA;AAC7C,OAAO,EAAE,IAAI,EAAE,KAAK,SAAS,EAAE,KAAK,GAAG,EAAE,MAAM,QAAQ,CAAA;AACvD,OAAO,EAAE,OAAO,EAAE,KAAK,YAAY,EAAE,MAAM,WAAW,CAAA;AAEtD,OAAO,EACL,OAAO,EACP,UAAU,EACV,KAAK,MAAM,EACX,KAAK,YAAY,EACjB,KAAK,eAAe,GACrB,MAAM,WAAW,CAAA"}

package/dist/chat/index.js

@@ -1,73 +1,32 @@
 /**
  * @hanzo/ui/chat — the one chat shell, on @hanzo/gui primitives.
  *
- * Shell only: Thread scrolls, Message presents a turn, Composer takes a draft,
- * Sidebar navigates between conversations, Header names the current one, and
- * Code, Step, Failure and Sources present the pieces of a turn every surface
- * renders the same way.
+ * Thread scrolls, Message presents a turn, Composer takes a draft, Sidebar
+ * navigates between conversations, Header names the current one, and Code,
+ * Step, Failure and Sources present the pieces of a turn.
  *
- * This file used to end that sentence with "Content rendering (markdown, tool
- * calls) stays with the surface — they disagree on the pipeline, and none of it
- * is presentational." Half of that was right and the half that was wrong cost
- * nine hand-drawn copies. Re-decided by reading what the three surfaces
- * actually render:
+ * The markdown pipeline is the surface's and arrives as `children`: the three
+ * surfaces run nine plugins, one plugin, and a regex under a bundle ceiling
+ * that cannot afford a parser. There is no `renderPart` prop for the same
+ * reason — the part union is per-surface too, so a callback here would take a
+ * Part type matching nobody's.
  *
- *   MARKDOWN STAYS OUT, and not as a preference. hanzo/chat runs seven remark
- *   plugins and two rehype plugins (`Content/Markdown.tsx:42-65`, including
- *   katex and highlight.js over a 35-language subset); hanzo.app runs
- *   remark-gfm and nothing else (`markdown-renderer/index.tsx:107`); the
- *   extension parses markdown with eighty lines of regex and no dependency at
- *   all (`answer/markdown.ts`) because `newtab.js` measures 485.9 KB against a
- *   500 KB ceiling that fails the build (`scripts/check-bundle-budgets.mjs:29`)
- *   and its MV3 policy is `script-src 'self'`. Fourteen kilobytes of headroom
- *   is not a pipeline disagreement to be reconciled; it is a surface that
- *   cannot afford a parser. So the pipeline is the surface's, and `children` is
- *   how it arrives — which is also why there is no `renderPart` prop: the part
- *   UNION is per-surface too (twelve item types in the app's
- *   `chat-panel/index.tsx` `TurnDisplay`, eight in chat's `Content/Part.tsx`,
- *   none in the extension), so a callback here would need a Part type that
- *   matches nobody's. The surface maps its own parts and passes nodes.
+ * Everything else about a turn is presentational and lives here: the code
+ * frame, the step disclosure, the failure, the streaming caret.
  *
- *   THE REST OF IT WAS ALWAYS PRESENTATIONAL. A code block with a language
- *   label and a copy control, a collapsible step with a state mark, a failure
- *   with a retry, a streaming caret — every surface draws these and no two draw
- *   them alike. `Step` alone replaces nine copies across two repos. What is
- *   inside each of them is still `children`; the frame, the header, the mark
- *   and the disclosure are here.
+ * Props-in, callbacks-out — no transport, no store, no routing. Each component
+ * spreads its residual props, and the three that own an inner part publish a
+ * way through to it (`Message body`, `Thread column`, `Composer field`).
  *
- * Everything is props-in, callbacks-out: no transport, no store, no routing, no
- * active-id resolution. The same components serve a live conversation, a shared
- * read-only transcript and a test fixture.
+ * `@hanzo/ui/chat/pure` carries `sends`, `ready`, `pinned` and `SLACK` with no
+ * imports, for Node and for callers that are not chat.
  *
- * Every component here spreads its residual props onto its own element, and
- * `Message`, `Thread` and `Composer` publish a way through to the part they own
- * (`body`, `column`, `field`). They did not, and that closed list was the ONE
- * thing keeping hanzo/chat from adopting `Message`: its scroll machinery
- * addresses turns by `id`, `SelectionAsk` finds one with
- * `closest('.message-render')`, and its turn wears a fleet-wide `glass`
- * material against a `bg` welded to `$color3`. None of it exotic, all of it
- * free with a spread — gui forwards what it does not recognise, which is the
- * mechanism `slot()` is already built on.
+ * Styling is `$` tokens throughout, never literal colours, so a brand retunes
+ * through its own theme and nothing here carries a mark.
  *
- * `@hanzo/ui/chat/pure` is the same module's decisions with nothing attached:
- * `sends`, `ready`, `pinned`, `SLACK`. It exists because `import('@hanzo/ui/chat')`
- * cannot load in Node, so no script and no spec could reach them. They are also
- * re-exported from `@hanzo/ui/product/pure`, because they are not chat rules —
- * ten of the fifteen files importing `sends` in hanzo.app are a SQL editor, a
- * file explorer, a command palette, a rename field.
- *
- * Styling is `$` tokens throughout, never literal colours, so each brand retunes
- * through its own theme and nothing here carries a Hanzo mark — which is what
- * lets the same shell ship on Lux and Zoo surfaces without leaking a brand.
- *
- * The model picker is not here: it already ships at `@hanzo/ui/models`, and it
- * is not chat-specific.
- *
- * `CopyButton` is not here either, for the same reason and after the same
- * mistake: it lived in `Code.tsx`, so the only way to reach it was
- * `@hanzo/ui/chat`, and no one hunting for a copy button looks in a chat module.
- * Six surfaces wrote their own instead. It now ships at `@hanzo/ui/product`;
- * `Code` imports it from there.
+ * The model picker and `CopyButton` are not here — neither is chat-specific, so
+ * they ship at `@hanzo/ui/models` and `@hanzo/ui/product`. Nobody hunting for a
+ * copy button looks in a chat module.
  */
 export { Composer, ASK } from './Composer.js';
 export { Caret, Message } from './Message.js';

package/dist/chat/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/chat/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAsEG;AACH,OAAO,EAAE,QAAQ,EAAE,GAAG,EAAsB,MAAM,YAAY,CAAA;AAC9D,OAAO,EAAE,KAAK,EAAE,OAAO,EAAgC,MAAM,WAAW,CAAA;AACxE,OAAO,EAAE,MAAM,EAAoB,MAAM,UAAU,CAAA;AACnD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAa,MAAM,QAAQ,CAAA;AAChD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA;AAEnD,OAAO,EACL,OAAO,EACP,aAAa,EACb,iBAAiB,EACjB,cAAc,EACd,aAAa,EACb,cAAc,EACd,WAAW,EACX,aAAa,EACb,WAAW,GASZ,MAAM,WAAW,CAAA;AAElB,OAAO,EACL,MAAM,EACN,YAAY,EACZ,WAAW,EACX,WAAW,EACX,KAAK,GAMN,MAAM,UAAU,CAAA;AAEjB,OAAO,EAAE,IAAI,EAAkB,MAAM,QAAQ,CAAA;AAC7C,OAAO,EAAE,IAAI,EAA4B,MAAM,QAAQ,CAAA;AACvD,OAAO,EAAE,OAAO,EAAqB,MAAM,WAAW,CAAA;AAEtD,OAAO,EACL,OAAO,EACP,UAAU,GAIX,MAAM,WAAW,CAAA"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/chat/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6BG;AACH,OAAO,EAAE,QAAQ,EAAE,GAAG,EAAsB,MAAM,YAAY,CAAA;AAC9D,OAAO,EAAE,KAAK,EAAE,OAAO,EAAgC,MAAM,WAAW,CAAA;AACxE,OAAO,EAAE,MAAM,EAAoB,MAAM,UAAU,CAAA;AACnD,OAAO,EAAE,KAAK,EAAE,KAAK,EAAa,MAAM,QAAQ,CAAA;AAChD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA;AAEnD,OAAO,EACL,OAAO,EACP,aAAa,EACb,iBAAiB,EACjB,cAAc,EACd,aAAa,EACb,cAAc,EACd,WAAW,EACX,aAAa,EACb,WAAW,GASZ,MAAM,WAAW,CAAA;AAElB,OAAO,EACL,MAAM,EACN,YAAY,EACZ,WAAW,EACX,WAAW,EACX,KAAK,GAMN,MAAM,UAAU,CAAA;AAEjB,OAAO,EAAE,IAAI,EAAkB,MAAM,QAAQ,CAAA;AAC7C,OAAO,EAAE,IAAI,EAA4B,MAAM,QAAQ,CAAA;AACvD,OAAO,EAAE,OAAO,EAAqB,MAAM,WAAW,CAAA;AAEtD,OAAO,EACL,OAAO,EACP,UAAU,GAIX,MAAM,WAAW,CAAA"}