v0.2.10 hardware backend URL normalization + path fallback

startos/versions/index.ts

@@ -10,8 +10,9 @@ import { v_0_2_6 } from './v0.2.6'
 import { v_0_2_7 } from './v0.2.7'
 import { v_0_2_8 } from './v0.2.8'
 import { v_0_2_9 } from './v0.2.9'
+import { v_0_2_10 } from './v0.2.10'
 
 export const versionGraph = VersionGraph.of({
-  current: v_0_2_9,
-  other: [v_0_2_8, v_0_2_7, v_0_2_6, v_0_2_5, v_0_2_4, v_0_2_3, v_0_2_2, v_0_2_1, v_0_2_0, v_0_1_0],
+  current: v_0_2_10,
+  other: [v_0_2_9, v_0_2_8, v_0_2_7, v_0_2_6, v_0_2_5, v_0_2_4, v_0_2_3, v_0_2_2, v_0_2_1, v_0_2_0, v_0_1_0],
 })

startos/versions/v0.2.10.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_10 = VersionInfo.of({
+  version: '0.2.10:0',
+  releaseNotes: {
+    en_US:
+      'Hardware backend (Parakeet + Gemma) is now robust to two common URL-config mistakes: (1) base URLs that already end in /v1 no longer produce /v1/v1/... requests — the trailing /v1 is stripped before path-appending, (2) wrappers that expose the endpoint at /audio/transcriptions or /chat/completions (without the /v1 prefix) are auto-tried as a fallback when the standard path 404s. Failure messages now include the exact attempted URL so misconfigured endpoints are obvious in the relay logs and the audit log.',
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})