v2.37.1

v2.37.1

Test-suite hygiene and CI reliability. No DaVinci Resolve behavior changed.

Fixed

• The legacy live-harness scripts (test_all_tools, test_phase2–test_phase5) exited at import when Resolve was unavailable, crashing pytest collection and surfacing as five loader errors under unittest discovery. They now skip cleanly under both runners while keeping the hard-exit behavior when run as standalone scripts. (Adapted from a contribution by @diesdaas — thanks!)
• pytest mis-collected test_resolve20_api.py's internal test() helper as a test function; renamed to run_live_check().
• The batch-CLI synthetic-job test no longer depends on which transcription backends the host has installed.

CI

• The npm publish workflow no longer reports failure when the registry accepted the publish but npm's retried request re-presented a consumed OIDC token; it verifies the published tarball shasum before failing.
• Runner actions bumped to their Node 24 majors ahead of GitHub's June 16, 2026 forcing date.

Validation

• Offline unit suite fully clean under both runners for the first time: unittest discovery 1,019 tests / 0 errors / 5 clean skips; pytest collection 19 passed / 5 skipped on the touched files. Standalone script behavior verified unchanged.
• No Resolve behavior changed; live test not required.