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

startos/versions/v0.2.43.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_43 = VersionInfo.of({
+  version: '0.2.43:0',
+  releaseNotes: {
+    en_US:
+      'Three real fixes from a Recap-app submission test. (1) Live job-discovery: the Jobs tab now polls /admin/jobs every 5s while open, picking up any in-flight job (admin test, Recap summarize-url, Recap transcribe-url) without manual refresh. Recap-app submissions land in the Jobs table as a pending synthetic row the moment the relay accepts the POST; the row updates through download → transcribe → analyze and morphs into the real audit-backed row as phases complete. Single-job case also engages the pizza-tracker breadcrumb. Polling stops automatically when the operator leaves the Jobs tab. (2) Silent-transcript-truncation now flips the job status to PARTIAL with an explanatory error string. Previous behavior: when Gemini hit a chunk\'s output-token cap mid-transcript (the still-recurring failure mode from gemini-2.5-flash and flash-lite even with maxOutputTokens=65536), the chunk "succeeded" silently with a short transcript and the Jobs table showed SUCCESS for a job that lost real minutes of speech. New behavior: server/backends/gemini.js compares each chunk\'s last-emitted timestamp to the chunk\'s expected duration; when coverage drops below 80%, it returns truncated_chunks: [...] in the result envelope. The summarize-url / transcribe-url / admin-test-run worker routes propagate that into the audit row as status="partial" with a `transcribe: N chunk(s) truncated — missing ~Xs of speech (model: ...)` error message. server/job-stats.js handles the new "partial" tx status — overall_status of the whole job becomes "partial" regardless of analyze success, since analyzing a truncated transcript produces a misleading result. (3) Column drag-reorder: added draggable="false" on the inner th-label span (added in v0.2.42) so browsers don\'t initiate a text-drag from the label text and confuse the column-reorder drag-tracking. Combined with the v0.2.39 render-gate fix, drag-reorder should now actually drop columns into their target positions.',
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})