v0.38.1 — zoom-out curve fix

Fixes

Camera moves: zoom-out no longer snaps to 2.0x (#33, fixes #31) — thanks @geeksilva97

The zoom-out progress term was interpolated into 1+${progress}*${scale-1} without parentheses. ffmpeg's expression parser binds * tighter than +/-, so the composed expression parsed as 1 + 1 - (((in_time-H)/D) * (scale-1)) — the zoom-out began at 2.0 instead of the requested scale and ended at 3-scale instead of 1.0, producing a visible snap at both ends of every camera move.

The zoom-in and chained-pan expressions were already correctly parenthesized and were not affected. The substring assertion that had locked the bug in place is replaced with regression tests that evaluate the generated zoompan z= expression and assert on curve values — continuity at the hold boundary, arrival at 1.0, and never exceeding the requested scale.

argo record now honours video.captureMode / video.jpegQuality (#32) — thanks @jarkkosyrjala

The record command built its options object without captureMode and jpegQuality, so setting them in argo.config had no effect under argo record — they silently fell back to defaults (webm / quality 80–95). pipeline already forwarded both; record is now consistent.

Symptom: captureMode: 'jpeg-stitch' + jpegQuality: 100 were ignored under argo record, leaving saturated-colour content with a default-quality JPEG screencast and visible per-frame flicker on anti-aliased edges.

Maintenance

• Resolve all open security alerts + fix the flaky 6h CI hang (#29)
• Bump protobufjs 7.5.5 → 7.5.8 (#21, #20), @protobufjs/utf8 1.1.0 → 1.1.1 (#19, #18)
• Bump actions/checkout + actions/setup-node to v6 (#17)

Full changelog: v0.38.0...v0.38.1