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

startos/versions/v0.2.50.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_50 = VersionInfo.of({
+  version: '0.2.50:0',
+  releaseNotes: {
+    en_US:
+      'Editable LLM prompts + removal of duplicate "Set Backend Routing & Models" StartOS action. (1) Two new textareas in the dashboard Settings tab: "Transcribe prompt (Gemini only)" and "Analyze prompt (Gemini + operator-hardware)". Both default to the current hardcoded prompt body; operator can edit the instruction text while keeping the auto-prepended metadata block (transcribe) and template variables {{transcript}} / {{windowMin}} / {{targetSections}} (analyze) intact. Each textarea has a "Reset to default" button and a "Show current default" toggle that reveals the latest built-in prompt at any time — important because saving with the default text intentionally stores empty string so future default-prompt changes in code flow through to the operator without any action. Save-time validation enforces that the analyze prompt still contains {{transcript}} and a "JSON" output instruction; the relay refuses to save an override that would silently break the pipeline. The transcribe-prompt override applies to the Gemini path only — operator-hardware (Parakeet) is pure STT with no prompt input; the analyze-prompt override applies to both Gemini and operator-hardware (Gemma) analyze paths since both accept the same instruction text. (2) Removed the "Set Backend Routing & Models" StartOS action. Backend routing + Gemini model selection have been in the dashboard Settings tab since v0.2.49 and the duplicate surface was a source of "which one wins" confusion. The four config fields (relay_gemini_transcription_model, relay_gemini_analysis_model, relay_transcribe_backend_preference, relay_analyze_backend_preference) stay where they were in relay-config.json — only the StartOS action UI is gone. setBackendRouting.ts deleted; actions/index.ts no longer imports or registers it.',
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})