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

startos/versions/v0.2.65.ts

@@ -0,0 +1,13 @@
+import { VersionInfo } from '@start9labs/start-sdk'
+
+export const v_0_2_65 = VersionInfo.of({
+  version: '0.2.65:0',
+  releaseNotes: {
+    en_US:
+      'The actual root cause of "Discovery ON · found: 0 running" surfaced — a one-line import bug. Two modules both export a function named `snapshotJobs`: `server/jobs.js` returns the in-memory job tracker ({id, kind, status, progress, started_at, ...}) which is what the dashboard\'s discovery poll expects; `server/job-credits.js` returns the credit ledger ({key, backend, tier, charged_at, refunded}) — totally different shape used by the billing path. `server/routes/admin.js`\'s /admin/jobs route was importing snapshotJobs from `../job-credits.js`, so every discovery poll got credit-ledger records back. The records DID have entries (e.g. "total entries: 1") but the discovery filter requires `status === "running"` and `kind` in a known set — credit records have neither field, so they all matched `kind: "unknown" / status: "unknown"` and `found: 0 running`. This was identifiable only after the v0.2.61 raw-JSON-viewer landed, which let the operator paste the actual response payload and see {key, backend, tier, charged_at, refunded} instead of {id, kind, status}. Fix: import from `../jobs.js` instead. Added a long inline comment so future changes don\'t accidentally swap it back. Net effect: in-flight Recap submissions now appear as pending rows in the Jobs table within ~3 seconds of relay-side createJob() (the discovery poll interval), the pizza tracker engages, the global in-flight pill shows up on non-Jobs tabs, and loadJobs() auto-refreshes the table when each job completes. No relay-side state changes — purely an import correction.',
+  },
+  migrations: {
+    up: async ({ effects }) => {},
+    down: async ({ effects }) => {},
+  },
+})