arcane-os 0.33.5 → 0.33.6

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.33.6
+
+- Resume transcript bottom-follow when an accepted non-synthetic user message
+  is sent, including when the reader had scrolled upward. Preserve reading
+  position for incoming content, synthetic requests, and canceled submissions.
+- Keep HTTP 529 on its existing bounded retry path when reading its diagnostic
+  body fails. Preserve the actual parser or body-read error in retry observations
+  and final failure, with cancellation and other HTTP behavior unchanged.
+
 ## 0.33.5
 
 - Deliver the first visible streamed chat chunk to speech exactly once, without

package/README.md

@@ -19,7 +19,7 @@ version-locked SDK runtime, while an integrated Arcane checkout uses its live
 `arcane/` runtime. Both profiles share the theme, packaging, event, cancellation,
 and browser run contracts while retaining their selected application layout.
 
-This checkout defines the `0.33.5` SDK contract. Applications pin one exact npm
+This checkout defines the `0.33.6` SDK contract. Applications pin one exact npm
 version and lockfile; registry state is deliberately not baked into application
 artifacts.
 
@@ -85,7 +85,7 @@ Create one browser application, install its pinned SDK, and start its source
 server:
 
 ```bash
-npx arcane-os@0.33.5 new hello-speech --path ./hello-speech --target browser
+npx arcane-os@0.33.6 new hello-speech --path ./hello-speech --target browser
 cd hello-speech
 npm install
 ```

package/browser-runtime/ai/twin-cloud.mjs

@@ -170,16 +170,23 @@ export async function fetchHTTPResponse(url, options, {onRetry = null} = {}) {
             if (response?.ok) {
                 return response;
             }
+            const status = response?.status ?? null;
             if (response) {
                 const contentType = response.headers.get('content-type') || '';
-                error = contentType.includes('application/json')
-                    ? await response.json()
-                    : await response.text();
+                try {
+                    error = contentType.includes('application/json')
+                        ? await response.json()
+                        : await response.text();
+                } catch (bodyError) {
+                    if (status !== 529 || isAIRequestAbort(bodyError, signal)) {
+                        throw bodyError;
+                    }
+                    error = bodyError;
+                }
                 if (signal?.aborted) {
                     throw normalizeAIRequestAbort(signal.reason);
                 }
             }
-            const status = response?.status ?? null;
             const message = is.string(error)
                 ? error
                 : error?.error?.message ?? error?.message;

package/docs/reference/ai/twin-cloud.md

@@ -81,8 +81,11 @@ two failure types share that three-retry budget. HTTP `429` with a message
 containing `overload` (case-insensitive) retains its unlimited three-second
 retry behavior and does not consume that budget. Each attempt reuses the exact
 destination, Fetch options, serialized request, and signal. Other HTTP errors,
-response decoding failures, and application callback failures do not retry.
-The last complete failure is thrown unchanged when recovery is exhausted.
+successful-response decoding failures, and application callback failures do not
+retry. A known HTTP `529` also retries when reading or parsing its diagnostic
+body fails; `onRetry.error` retains that exact failure, which is thrown unchanged
+if recovery is exhausted. Diagnostic-body failures for other HTTP statuses do
+not retry. The last complete failure is thrown unchanged when recovery is exhausted.
 Pass a fresh
 `AbortController`'s `signal` and call `abort()` to cancel. Cancellation during
 the request, response-body read, retry wait, or callback settlement prevents

package/docs/reference/runtime-components.md

@@ -342,7 +342,9 @@ transcript is a masked vertical scroll viewport; status and composer remain
 outside it. Initial restoration follows the true bottom. User, assistant, tool,
 streaming, progress, and failure updates continue following it, including later
 message-card, status, composer, or viewport resizing, until the reader scrolls
-toward earlier content. Scrolling down to the bottom resumes following. Layout
+toward earlier content. Scrolling down to the bottom or submitting an accepted
+non-synthetic user message resumes following. Canceled or rejected submissions
+and synthetic requests preserve the reader's position. Layout
 clamping, hidden views, and BFCache restoration preserve that choice;
 destruction releases scroll observation. Each
 restored or new message uses a separate semantic `<time>` element at the card's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arcane-os",
-  "version": "0.33.5",
+  "version": "0.33.6",
   "description": "Arcane OS JavaScript SDK, project-local CLI, browser runtime, and repository-portable application packager.",
   "type": "module",
   "main": "./src/index.mjs",

package/runtime/arcane/components/chat.html

@@ -1161,9 +1161,13 @@
         scrollTranscriptToBottom();
     }
 
-    function scrollTranscriptToBottom() {
+    function scrollTranscriptToBottom(resumeFollowing = false) {
         // Read movement before writing: a reader's scroll event may still be queued.
-        if(!trackTranscriptScrollPosition() || !transcriptFollowing) return false;
+        const visible = trackTranscriptScrollPosition();
+        if(resumeFollowing === true && !destroyed) {
+            transcriptFollowing = true;
+        }
+        if(!visible || !transcriptFollowing) return false;
         chatOutput.scrollTop = chatOutput.scrollHeight;
         transcriptScrollTop = chatOutput.scrollTop;
         return true;
@@ -3831,7 +3835,7 @@
                 const visibleMessage=appendTranscriptMessage('user',text,host.name);
                 visibleMessage.dataset.operationId=operationId;
             }
-            scrollTranscriptToBottom();
+            scrollTranscriptToBottom(!eventContext.synthetic);
 
             if(host.aiAvailability.tts&&speech.muted===false){
                 const aiRuntime=boundChatAI??globalThis.ai;