import { VersionInfo } from '@start9labs/start-sdk'

export const v_0_2_58 = VersionInfo.of({
  version: '0.2.58:0',
  releaseNotes: {
    en_US:
      'Three dashboard diagnosability fixes after 0.2.57\'s pizza-tracker still didn\'t engage for Recap-submitted jobs on a real test. (1) Discovery polling now ALSO starts on a fresh login (form-submit handler), not just on initial boot. Previously, an admin who logged in after a session timeout would leave _discoverPollHandle null forever — no pending row ever showed up for Recap submissions until the operator hard-refreshed the page. The boot() path already started discovery; the login handler did not. Fixed by mirroring the boot()\'s post-auth initialization (tryResumeActiveSingleRuns + startInFlightDiscoveryPoll) in the login handler. (2) New "Discovery" diagnostic strip at the top of the Jobs tab. Always visible (not gated on having active jobs), it shows: polling state (ON / OFF / STALE / ERROR), seconds since the last poll, how many running jobs the last poll found, current active-jobs count, total polls since auth, and the last error message if any. Surface for debugging "I submitted a job but no pending row appeared" — operator can immediately see whether the discovery code is running, whether /admin/jobs is returning the expected jobs, or whether something is silently 401-ing. (3) Source classification on the in-flight callout now uses job.kind directly instead of inferring from metadata fields. Previously, a Recap summarize-url job was mislabeled as "Test run" because its metadata included transcribe_backend/analyze_backend (which the summarize-url route stamps for its own bookkeeping). The classification now reads "Recap (summarize)" / "Recap (transcribe)" / "Test run" based on the relay-side kind string, which is the authoritative source.',
  },
  migrations: {
    up: async ({ effects }) => {},
    down: async ({ effects }) => {},
  },
})