@hanzo/ui 8.1.5 → 8.1.7

package/dist/chat/pure.cjs

@@ -1,41 +1,22 @@
 "use strict";
-// @hanzo/ui/chat/pure — the conversation's decisions, without the conversation.
+// @hanzo/ui/chat/pure — the conversation's decisions, with nothing attached.
 //
-// Every module here is a function over values: no @hanzo/gui, no React, no DOM,
-// no side effects. Same shape and same reason as `@hanzo/ui/product/pure`, and
-// the reason is measured — `import('@hanzo/ui/chat')` in Node dies on
-// `SyntaxError: Unexpected token 'typeof'`, so a script, a Playwright spec or a
-// server-side caller could not reach these at all. They had to stand up a
-// browser to ask whether Enter sends.
+// No @hanzo/gui, no React, no DOM, no side effects, so these load in Node, in a
+// spec, and in a server component. `@hanzo/ui/chat` cannot: it is TSX behind a
+// client directive.
 //
 //   import { sends, ready, pinned, SLACK } from '@hanzo/ui/chat/pure'
 //
-// These are not chat rules and the chat-shaped import was hiding that. Of the
-// fifteen files in hanzo.app that import `sends`, TEN are not chat: a repo-URL
-// field, two project renames, the SQL editor, the file explorer, the SEO tab,
-// the workspace menu, the console prompt, an uploader and the command palette.
-// "Does this keystroke commit this field" is the same question wherever a field
-// takes Enter. `@hanzo/ui/product/pure` re-exports all four for exactly that
-// reader — the one who is not writing chat and would never look here.
-//
-// It is the same mistake `CopyButton` made, recorded in this module's own
-// barrel: a general thing reachable only through a chat-shaped door gets
-// rewritten by everyone who does not think to open that door. hanzo/chat had
-// THREE Enter rules, and two of them (`AnswerComposer`, `SelectionAsk`) tested
-// `Enter && !shiftKey` straight off the event — so Enter-to-accept an IME
-// candidate submitted a half-typed word for Japanese, Chinese and Korean
-// writers. `sends` had the fix from the day it was written and nobody could
-// reach it.
+// `@hanzo/ui/product/pure` re-exports all four, because none of them is a chat
+// rule and that is the door a non-chat surface looks behind.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.SLACK = exports.pinned = exports.sends = exports.ready = void 0;
-// Enter, and whether a draft may go. The IME guard is the whole point; read
-// `sends` before writing another one.
+// Enter, and whether a draft may go. Read `sends` before writing another one:
+// the IME guard is the point.
 var send_1 = require("./send.cjs");
 Object.defineProperty(exports, "ready", { enumerable: true, get: function () { return send_1.ready; } });
 Object.defineProperty(exports, "sends", { enumerable: true, get: function () { return send_1.sends; } });
-// Stay-at-the-bottom, as a distance test. The fleet's one answer to "am I at
-// the bottom", which had five: 50px twice, 97%-of-height, an
-// IntersectionObserver at a 0.85 ratio, and on one thread nothing at all.
+// Stay-at-the-bottom, as a distance test.
 var stick_1 = require("./stick.cjs");
 Object.defineProperty(exports, "pinned", { enumerable: true, get: function () { return stick_1.pinned; } });
 Object.defineProperty(exports, "SLACK", { enumerable: true, get: function () { return stick_1.SLACK; } });

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

@@ -1 +1 @@
-{"version":3,"file":"pure.d.ts","sourceRoot":"","sources":["../../src/chat/pure.ts"],"names":[],"mappings":"AA8BA,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,IAAI,EAAE,MAAM,QAAQ,CAAA;AAKhD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA"}
+{"version":3,"file":"pure.d.ts","sourceRoot":"","sources":["../../src/chat/pure.ts"],"names":[],"mappings":"AAaA,OAAO,EAAE,KAAK,EAAE,KAAK,EAAE,KAAK,IAAI,EAAE,MAAM,QAAQ,CAAA;AAGhD,OAAO,EAAE,MAAM,EAAE,KAAK,EAAE,KAAK,KAAK,EAAE,MAAM,SAAS,CAAA"}

package/dist/chat/pure.js

@@ -1,35 +1,16 @@
-// @hanzo/ui/chat/pure — the conversation's decisions, without the conversation.
+// @hanzo/ui/chat/pure — the conversation's decisions, with nothing attached.
 //
-// Every module here is a function over values: no @hanzo/gui, no React, no DOM,
-// no side effects. Same shape and same reason as `@hanzo/ui/product/pure`, and
-// the reason is measured — `import('@hanzo/ui/chat')` in Node dies on
-// `SyntaxError: Unexpected token 'typeof'`, so a script, a Playwright spec or a
-// server-side caller could not reach these at all. They had to stand up a
-// browser to ask whether Enter sends.
+// No @hanzo/gui, no React, no DOM, no side effects, so these load in Node, in a
+// spec, and in a server component. `@hanzo/ui/chat` cannot: it is TSX behind a
+// client directive.
 //
 //   import { sends, ready, pinned, SLACK } from '@hanzo/ui/chat/pure'
 //
-// These are not chat rules and the chat-shaped import was hiding that. Of the
-// fifteen files in hanzo.app that import `sends`, TEN are not chat: a repo-URL
-// field, two project renames, the SQL editor, the file explorer, the SEO tab,
-// the workspace menu, the console prompt, an uploader and the command palette.
-// "Does this keystroke commit this field" is the same question wherever a field
-// takes Enter. `@hanzo/ui/product/pure` re-exports all four for exactly that
-// reader — the one who is not writing chat and would never look here.
-//
-// It is the same mistake `CopyButton` made, recorded in this module's own
-// barrel: a general thing reachable only through a chat-shaped door gets
-// rewritten by everyone who does not think to open that door. hanzo/chat had
-// THREE Enter rules, and two of them (`AnswerComposer`, `SelectionAsk`) tested
-// `Enter && !shiftKey` straight off the event — so Enter-to-accept an IME
-// candidate submitted a half-typed word for Japanese, Chinese and Korean
-// writers. `sends` had the fix from the day it was written and nobody could
-// reach it.
-// Enter, and whether a draft may go. The IME guard is the whole point; read
-// `sends` before writing another one.
+// `@hanzo/ui/product/pure` re-exports all four, because none of them is a chat
+// rule and that is the door a non-chat surface looks behind.
+// Enter, and whether a draft may go. Read `sends` before writing another one:
+// the IME guard is the point.
 export { ready, sends } from './send.js';
-// Stay-at-the-bottom, as a distance test. The fleet's one answer to "am I at
-// the bottom", which had five: 50px twice, 97%-of-height, an
-// IntersectionObserver at a 0.85 ratio, and on one thread nothing at all.
+// Stay-at-the-bottom, as a distance test.
 export { pinned, SLACK } from './stick.js';
 //# sourceMappingURL=pure.js.map

package/dist/chat/pure.js.map

@@ -1 +1 @@
-{"version":3,"file":"pure.js","sourceRoot":"","sources":["../../src/chat/pure.ts"],"names":[],"mappings":"AAAA,gFAAgF;AAChF,EAAE;AACF,gFAAgF;AAChF,+EAA+E;AAC/E,sEAAsE;AACtE,gFAAgF;AAChF,0EAA0E;AAC1E,sCAAsC;AACtC,EAAE;AACF,sEAAsE;AACtE,EAAE;AACF,8EAA8E;AAC9E,+EAA+E;AAC/E,8EAA8E;AAC9E,+EAA+E;AAC/E,gFAAgF;AAChF,6EAA6E;AAC7E,sEAAsE;AACtE,EAAE;AACF,0EAA0E;AAC1E,yEAAyE;AACzE,6EAA6E;AAC7E,+EAA+E;AAC/E,0EAA0E;AAC1E,yEAAyE;AACzE,4EAA4E;AAC5E,YAAY;AAEZ,4EAA4E;AAC5E,sCAAsC;AACtC,OAAO,EAAE,KAAK,EAAE,KAAK,EAAa,MAAM,QAAQ,CAAA;AAEhD,6EAA6E;AAC7E,6DAA6D;AAC7D,0EAA0E;AAC1E,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA"}
+{"version":3,"file":"pure.js","sourceRoot":"","sources":["../../src/chat/pure.ts"],"names":[],"mappings":"AAAA,6EAA6E;AAC7E,EAAE;AACF,gFAAgF;AAChF,+EAA+E;AAC/E,oBAAoB;AACpB,EAAE;AACF,sEAAsE;AACtE,EAAE;AACF,+EAA+E;AAC/E,6DAA6D;AAE7D,8EAA8E;AAC9E,8BAA8B;AAC9B,OAAO,EAAE,KAAK,EAAE,KAAK,EAAa,MAAM,QAAQ,CAAA;AAEhD,0CAA0C;AAC1C,OAAO,EAAE,MAAM,EAAE,KAAK,EAAc,MAAM,SAAS,CAAA"}

package/dist/chat/send.cjs

@@ -1,11 +1,7 @@
 "use strict";
 /**
- * The two decisions a composer makes, as pure functions.
- *
- * Every Hanzo chat surface had re-implemented both inline, and they had drifted:
- * one sent on a bare Enter while composing an IME candidate (committing a
- * half-typed word), another let a whitespace-only draft through. Keeping them
- * here means the rules are asserted once, without a DOM.
+ * The two decisions a composer makes, as pure functions — asserted once,
+ * without a DOM.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ready = exports.sends = void 0;
@@ -14,12 +10,9 @@ const IME = 229;
 /**
  * Whether the IME owns this keystroke, from all three signals browsers use.
  *
- * `isComposing` alone is not enough. Safari does not set it reliably on the
- * keydown that accepts a candidate, and reports the key as `Process` or with
- * only the legacy `keyCode` of 229 — so a composer that trusts `isComposing`
- * by itself still submits a half-typed word out from under a Japanese, Chinese
- * or Korean writer. That is the bug this module exists to end, and it is not
- * ended by checking one flag.
+ * `isComposing` alone is not enough: Safari does not set it reliably on the
+ * keydown that accepts a candidate, reporting `Process` or only the legacy
+ * `keyCode` of 229.
  */
 const claimed = (key, mods) => mods.isComposing === true || key === 'Process' || mods.keyCode === IME;
 /**
@@ -28,12 +21,9 @@ const claimed = (key, mods) => mods.isComposing === true || key === 'Process' ||
  * every surface already taught its users, and it holds even with Shift down.
  * A keystroke the IME has claimed belongs to the IME, never to the composer.
  *
- * HAND IT `e.nativeEvent`, NEVER `e`. React's synthetic KeyboardEvent does not
- * carry `isComposing` or `keyCode`, so passing the synthetic event gets one of
- * the three IME signals instead of three, type-checks cleanly, reads correctly
- * at the call site, and puts the mid-candidate submit straight back for every
- * Japanese, Chinese and Korean writer. That is the entire bug this function
- * exists to end, and it is re-introducible in one character.
+ * Hand it `e.nativeEvent`, never `e`: React's synthetic event carries neither
+ * `isComposing` nor `keyCode`, so `e` type-checks and silently drops two of the
+ * three IME signals.
  *
  *     onKeyDown={(e) => { if (sends(e.key, e.nativeEvent)) { … } }}
  */

package/dist/chat/send.d.ts

@@ -1,10 +1,6 @@
 /**
- * The two decisions a composer makes, as pure functions.
- *
- * Every Hanzo chat surface had re-implemented both inline, and they had drifted:
- * one sent on a bare Enter while composing an IME candidate (committing a
- * half-typed word), another let a whitespace-only draft through. Keeping them
- * here means the rules are asserted once, without a DOM.
+ * The two decisions a composer makes, as pure functions — asserted once,
+ * without a DOM.
  */
 /** Modifier state, in the shape web and native events agree on. */
 export interface Mods {
@@ -23,12 +19,9 @@ export interface Mods {
  * every surface already taught its users, and it holds even with Shift down.
  * A keystroke the IME has claimed belongs to the IME, never to the composer.
  *
- * HAND IT `e.nativeEvent`, NEVER `e`. React's synthetic KeyboardEvent does not
- * carry `isComposing` or `keyCode`, so passing the synthetic event gets one of
- * the three IME signals instead of three, type-checks cleanly, reads correctly
- * at the call site, and puts the mid-candidate submit straight back for every
- * Japanese, Chinese and Korean writer. That is the entire bug this function
- * exists to end, and it is re-introducible in one character.
+ * Hand it `e.nativeEvent`, never `e`: React's synthetic event carries neither
+ * `isComposing` nor `keyCode`, so `e` type-checks and silently drops two of the
+ * three IME signals.
  *
  *     onKeyDown={(e) => { if (sends(e.key, e.nativeEvent)) { … } }}
  */

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

@@ -1 +1 @@
-{"version":3,"file":"send.d.ts","sourceRoot":"","sources":["../../src/chat/send.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,mEAAmE;AACnE,MAAM,WAAW,IAAI;IACnB,QAAQ,CAAC,EAAE,OAAO,CAAA;IAClB,MAAM,CAAC,EAAE,OAAO,CAAA;IAChB,OAAO,CAAC,EAAE,OAAO,CAAA;IACjB,OAAO,CAAC,EAAE,OAAO,CAAA;IACjB,gFAAgF;IAChF,WAAW,CAAC,EAAE,OAAO,CAAA;IACrB,2EAA2E;IAC3E,OAAO,CAAC,EAAE,MAAM,CAAA;CACjB;AAkBD;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,KAAK,GAAI,KAAK,MAAM,EAAE,OAAM,IAAS,KAAG,OAIpD,CAAA;AAED;;;GAGG;AACH,eAAO,MAAM,KAAK,GAAI,OAAO,MAAM,EAAE,cAAY,EAAE,kBAAgB,KAAG,OACvB,CAAA"}
+{"version":3,"file":"send.d.ts","sourceRoot":"","sources":["../../src/chat/send.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,mEAAmE;AACnE,MAAM,WAAW,IAAI;IACnB,QAAQ,CAAC,EAAE,OAAO,CAAA;IAClB,MAAM,CAAC,EAAE,OAAO,CAAA;IAChB,OAAO,CAAC,EAAE,OAAO,CAAA;IACjB,OAAO,CAAC,EAAE,OAAO,CAAA;IACjB,gFAAgF;IAChF,WAAW,CAAC,EAAE,OAAO,CAAA;IACrB,2EAA2E;IAC3E,OAAO,CAAC,EAAE,MAAM,CAAA;CACjB;AAeD;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,KAAK,GAAI,KAAK,MAAM,EAAE,OAAM,IAAS,KAAG,OAIpD,CAAA;AAED;;;GAGG;AACH,eAAO,MAAM,KAAK,GAAI,OAAO,MAAM,EAAE,cAAY,EAAE,kBAAgB,KAAG,OACvB,CAAA"}

package/dist/chat/send.js

@@ -1,22 +1,15 @@
 /**
- * The two decisions a composer makes, as pure functions.
- *
- * Every Hanzo chat surface had re-implemented both inline, and they had drifted:
- * one sent on a bare Enter while composing an IME candidate (committing a
- * half-typed word), another let a whitespace-only draft through. Keeping them
- * here means the rules are asserted once, without a DOM.
+ * The two decisions a composer makes, as pure functions — asserted once,
+ * without a DOM.
  */
 /** The keyCode every browser reports for a keystroke an IME has claimed. */
 const IME = 229;
 /**
  * Whether the IME owns this keystroke, from all three signals browsers use.
  *
- * `isComposing` alone is not enough. Safari does not set it reliably on the
- * keydown that accepts a candidate, and reports the key as `Process` or with
- * only the legacy `keyCode` of 229 — so a composer that trusts `isComposing`
- * by itself still submits a half-typed word out from under a Japanese, Chinese
- * or Korean writer. That is the bug this module exists to end, and it is not
- * ended by checking one flag.
+ * `isComposing` alone is not enough: Safari does not set it reliably on the
+ * keydown that accepts a candidate, reporting `Process` or only the legacy
+ * `keyCode` of 229.
  */
 const claimed = (key, mods) => mods.isComposing === true || key === 'Process' || mods.keyCode === IME;
 /**
@@ -25,12 +18,9 @@ const claimed = (key, mods) => mods.isComposing === true || key === 'Process' ||
  * every surface already taught its users, and it holds even with Shift down.
  * A keystroke the IME has claimed belongs to the IME, never to the composer.
  *
- * HAND IT `e.nativeEvent`, NEVER `e`. React's synthetic KeyboardEvent does not
- * carry `isComposing` or `keyCode`, so passing the synthetic event gets one of
- * the three IME signals instead of three, type-checks cleanly, reads correctly
- * at the call site, and puts the mid-candidate submit straight back for every
- * Japanese, Chinese and Korean writer. That is the entire bug this function
- * exists to end, and it is re-introducible in one character.
+ * Hand it `e.nativeEvent`, never `e`: React's synthetic event carries neither
+ * `isComposing` nor `keyCode`, so `e` type-checks and silently drops two of the
+ * three IME signals.
  *
  *     onKeyDown={(e) => { if (sends(e.key, e.nativeEvent)) { … } }}
  */

package/dist/chat/send.js.map

@@ -1 +1 @@
-{"version":3,"file":"send.js","sourceRoot":"","sources":["../../src/chat/send.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAcH,4EAA4E;AAC5E,MAAM,GAAG,GAAG,GAAG,CAAA;AAEf;;;;;;;;;GASG;AACH,MAAM,OAAO,GAAG,CAAC,GAAW,EAAE,IAAU,EAAW,EAAE,CACnD,IAAI,CAAC,WAAW,KAAK,IAAI,IAAI,GAAG,KAAK,SAAS,IAAI,IAAI,CAAC,OAAO,KAAK,GAAG,CAAA;AAExE;;;;;;;;;;;;;;GAcG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,GAAW,EAAE,OAAa,EAAE,EAAW,EAAE;IAC7D,IAAI,GAAG,KAAK,OAAO,IAAI,OAAO,CAAC,GAAG,EAAE,IAAI,CAAC;QAAE,OAAO,KAAK,CAAA;IACvD,IAAI,IAAI,CAAC,OAAO,KAAK,IAAI,IAAI,IAAI,CAAC,OAAO,KAAK,IAAI;QAAE,OAAO,IAAI,CAAA;IAC/D,OAAO,IAAI,CAAC,QAAQ,KAAK,IAAI,IAAI,IAAI,CAAC,MAAM,KAAK,IAAI,CAAA;AACvD,CAAC,CAAA;AAED;;;GAGG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,KAAa,EAAE,IAAI,GAAG,KAAK,EAAE,QAAQ,GAAG,KAAK,EAAW,EAAE,CAC9E,CAAC,IAAI,IAAI,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,CAAA"}
+{"version":3,"file":"send.js","sourceRoot":"","sources":["../../src/chat/send.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAcH,4EAA4E;AAC5E,MAAM,GAAG,GAAG,GAAG,CAAA;AAEf;;;;;;GAMG;AACH,MAAM,OAAO,GAAG,CAAC,GAAW,EAAE,IAAU,EAAW,EAAE,CACnD,IAAI,CAAC,WAAW,KAAK,IAAI,IAAI,GAAG,KAAK,SAAS,IAAI,IAAI,CAAC,OAAO,KAAK,GAAG,CAAA;AAExE;;;;;;;;;;;GAWG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,GAAW,EAAE,OAAa,EAAE,EAAW,EAAE;IAC7D,IAAI,GAAG,KAAK,OAAO,IAAI,OAAO,CAAC,GAAG,EAAE,IAAI,CAAC;QAAE,OAAO,KAAK,CAAA;IACvD,IAAI,IAAI,CAAC,OAAO,KAAK,IAAI,IAAI,IAAI,CAAC,OAAO,KAAK,IAAI;QAAE,OAAO,IAAI,CAAA;IAC/D,OAAO,IAAI,CAAC,QAAQ,KAAK,IAAI,IAAI,IAAI,CAAC,MAAM,KAAK,IAAI,CAAA;AACvD,CAAC,CAAA;AAED;;;GAGG;AACH,MAAM,CAAC,MAAM,KAAK,GAAG,CAAC,KAAa,EAAE,IAAI,GAAG,KAAK,EAAE,QAAQ,GAAG,KAAK,EAAW,EAAE,CAC9E,CAAC,IAAI,IAAI,CAAC,QAAQ,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,MAAM,GAAG,CAAC,CAAA"}

package/dist/chat/stick.cjs

@@ -2,10 +2,8 @@
 /**
  * Stay-at-the-bottom, as a pure decision.
  *
- * A thread should follow a streaming answer, but it must stop following the
- * moment the reader scrolls up to re-read something — otherwise every new token
- * yanks them back down. The rule is a distance test against the bottom, and it
- * is the piece each surface had written slightly differently.
+ * A thread follows a streaming answer and stops the moment the reader scrolls
+ * up, or every new token yanks them back down. A distance test against the end.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.pinned = exports.SLACK = void 0;

package/dist/chat/stick.d.ts

@@ -1,10 +1,8 @@
 /**
  * Stay-at-the-bottom, as a pure decision.
  *
- * A thread should follow a streaming answer, but it must stop following the
- * moment the reader scrolls up to re-read something — otherwise every new token
- * yanks them back down. The rule is a distance test against the bottom, and it
- * is the piece each surface had written slightly differently.
+ * A thread follows a streaming answer and stops the moment the reader scrolls
+ * up, or every new token yanks them back down. A distance test against the end.
  */
 /** How far from the bottom still counts as "at the bottom", in px. */
 export declare const SLACK = 48;

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

@@ -1 +1 @@
-{"version":3,"file":"stick.d.ts","sourceRoot":"","sources":["../../src/chat/stick.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,sEAAsE;AACtE,eAAO,MAAM,KAAK,KAAK,CAAA;AAEvB,MAAM,WAAW,KAAK;IACpB,kCAAkC;IAClC,MAAM,EAAE,MAAM,CAAA;IACd,sCAAsC;IACtC,QAAQ,EAAE,MAAM,CAAA;IAChB,kCAAkC;IAClC,OAAO,EAAE,MAAM,CAAA;CAChB;AAED;;;GAGG;AACH,eAAO,MAAM,MAAM,GAAI,+BAA+B,KAAK,EAAE,cAAa,KAAG,OACvC,CAAA"}
+{"version":3,"file":"stick.d.ts","sourceRoot":"","sources":["../../src/chat/stick.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,sEAAsE;AACtE,eAAO,MAAM,KAAK,KAAK,CAAA;AAEvB,MAAM,WAAW,KAAK;IACpB,kCAAkC;IAClC,MAAM,EAAE,MAAM,CAAA;IACd,sCAAsC;IACtC,QAAQ,EAAE,MAAM,CAAA;IAChB,kCAAkC;IAClC,OAAO,EAAE,MAAM,CAAA;CAChB;AAED;;;GAGG;AACH,eAAO,MAAM,MAAM,GAAI,+BAA+B,KAAK,EAAE,cAAa,KAAG,OACvC,CAAA"}

package/dist/chat/stick.js

@@ -1,10 +1,8 @@
 /**
  * Stay-at-the-bottom, as a pure decision.
  *
- * A thread should follow a streaming answer, but it must stop following the
- * moment the reader scrolls up to re-read something — otherwise every new token
- * yanks them back down. The rule is a distance test against the bottom, and it
- * is the piece each surface had written slightly differently.
+ * A thread follows a streaming answer and stops the moment the reader scrolls
+ * up, or every new token yanks them back down. A distance test against the end.
  */
 /** How far from the bottom still counts as "at the bottom", in px. */
 export const SLACK = 48;

package/dist/chat/stick.js.map

@@ -1 +1 @@
-{"version":3,"file":"stick.js","sourceRoot":"","sources":["../../src/chat/stick.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,sEAAsE;AACtE,MAAM,CAAC,MAAM,KAAK,GAAG,EAAE,CAAA;AAWvB;;;GAGG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG,CAAC,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAS,EAAE,KAAK,GAAG,KAAK,EAAW,EAAE,CACrF,OAAO,GAAG,QAAQ,GAAG,MAAM,IAAI,KAAK,CAAA"}
+{"version":3,"file":"stick.js","sourceRoot":"","sources":["../../src/chat/stick.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,sEAAsE;AACtE,MAAM,CAAC,MAAM,KAAK,GAAG,EAAE,CAAA;AAWvB;;;GAGG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG,CAAC,EAAE,MAAM,EAAE,QAAQ,EAAE,OAAO,EAAS,EAAE,KAAK,GAAG,KAAK,EAAW,EAAE,CACrF,OAAO,GAAG,QAAQ,GAAG,MAAM,IAAI,KAAK,CAAA"}

package/dist/gallery.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"gallery.d.ts","sourceRoot":"","sources":["../src/gallery.tsx"],"names":[],"mappings":"AAiHA;;;GAGG;AACH,eAAO,MAAM,OAAO,+CA2gBnB,CAAA;AAED,eAAe,OAAO,CAAA"}
+{"version":3,"file":"gallery.d.ts","sourceRoot":"","sources":["../src/gallery.tsx"],"names":[],"mappings":"AAiHA;;;GAGG;AACH,eAAO,MAAM,OAAO,+CA6fnB,CAAA;AAED,eAAe,OAAO,CAAA"}