bunnyquery 1.9.7 → 1.10.0

package/src/widget.css

@@ -659,23 +659,42 @@
     background: var(--bq-paper);
 }
 
+/* ZERO HEIGHT IN FLOW, DELIBERATELY. Mirrors agent.vue, where the reasoning is
+   written out in full: this bar mounts when a history fetch starts and unmounts
+   when the page lands, both while the reader sits at the top of the list, and as
+   an in-flow sticky element it moved every row by its own height each time
+   (measured in Chrome with overflow-anchor:none). The outer box now contributes
+   nothing to layout and the inner strip overflows it, so the bar still sits
+   pinned at the top of the viewport while mounting it moves nothing. */
 .bq-history-loading {
     position: sticky;
     top: 0;
     z-index: 1;
+    height: 0;
+    padding: 0;
+    overflow: visible;
+    pointer-events: none;
+}
+.bq-history-loading-inner {
     display: flex;
+    align-items: center;
     justify-content: center;
     gap: 0.1em;
     padding: 0.5rem 0 1rem;
     font-size: 0.8rem;
     color: var(--bq-muted);
-    background: var(--bq-paper);
+    background: linear-gradient(to bottom, var(--bq-paper) 70%, transparent);
 }
-/* initial first-page load: center it in the (empty) messages area */
+/* initial first-page load: center it in the (empty) messages area. A full-box
+   overlay rather than a top strip, so it takes its height back - and it replaces
+   an EMPTY messages area, so it has nothing to move. */
 .bq-history-loading.is-initial {
     position: absolute;
     inset: 0;
+    height: auto;
+    display: flex;
     align-items: center;
+    justify-content: center;
     padding: 0;
 }
 

package/styles/chat.css

@@ -154,6 +154,38 @@
 .bq-cancel-queue-btn:hover:not(.is-disabled) { background: var(--bq-warning-bg); color: var(--bq-warning); }
 .bq-cancel-queue-btn.is-disabled { opacity: 0.3; cursor: not-allowed; pointer-events: none; }
 
+/* ---- unfinalized streamed answer (ask for it) ----------------------------
+   A turn whose answer was streamed and never finalized keeps its bytes in the
+   chunk store, and this bubble is what the reader gets when nothing is currently
+   fetching them: the per-load recovery cap left this one behind, or a read failed.
+   It is deliberately NOT the danger red of an error bubble - nothing is broken and
+   nothing is lost, the answer is simply not here yet - and deliberately not a
+   spinner, which would promise an arrival nobody has scheduled. Shared by both
+   chatboxes (this file is bunnyquery/styles/chat.css, which agent.vue imports). */
+.bq-stream-recover-note {
+    display: block;
+    font-size: 0.72rem;
+    color: var(--bq-muted);
+    font-style: italic;
+}
+.bq-bubble.is-stream-failed .bq-stream-recover-note { color: var(--bq-warning); }
+.bq-stream-recover-btn {
+    display: inline-block;
+    margin-top: 0.4rem;
+    padding: 0.18rem 0.55rem;
+    min-height: 0;
+    border: 1px solid var(--bq-line);
+    background: transparent;
+    color: inherit;
+    font-size: 0.72rem;
+    line-height: 1.3;
+    cursor: pointer;
+    box-shadow: none;
+    border-radius: 0;
+}
+.bq-stream-recover-btn:hover { background: rgba(127, 127, 127, 0.12); }
+.bq-bubble.is-stream-failed .bq-stream-recover-btn { border-color: var(--bq-warning-border); color: var(--bq-warning); }
+
 /* ---- collapsed background-indexing group ---------------------------------*/
 /* One file's many indexing passes (first pass + every CONTINUE pass, each with
    a request AND a response bubble) render as a single status row instead of