Package v0.2.12→v0.2.124: manifest, actions, version graph

startos/versions/v0.2.86.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_86 = VersionInfo.of({
+  version: '0.2.86:0',
+  releaseNotes: {
+    en_US:
+      "Two bug fixes uncovered while testing the v0.2.84/.85 Spark Control routing. (1) lan-fetch.js had headersTimeout=10s + bodyTimeout (implicit) on its undici Agent. Spark Control's diarize-chunk + transcribe routinely take 30–120s of compute before sending response headers (Sortformer + TitaNet + Parakeet on a 5-min audio chunk isn't fast), so EVERY hardware call was failing with a bare 'fetch failed' at the 10s mark — well before SC could respond. Set headersTimeout=0 and bodyTimeout=0 on the agent; per-request budgets are now controlled solely by the AbortSignal.timeout the caller passes (900s for hardware calls). The connectTimeout stays at 5s — it only governs TCP+TLS handshake, not the actual server compute. (2) Improved the hardware-backend network-error messages (transcribe, diarize, analyze) to surface the undici err.cause (ECONNREFUSED / ETIMEDOUT / TLS handshake / DNS) — 'fetch failed' alone gives you nothing to diagnose with. (3) Cosmetic: the analyze-window completion log added in v0.2.80 was printing '[object Object],[object Object] sections' because ownedSections is the array of section objects, not a count. Now logs the actual integer count via .length.",
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})