v2.57.5

v2.57.5

Fixes a silent data-loss bug on Reel Name writes (#77) and bundles the
community-contributed API-limitation entries from PR #76 (#75).

Fixed

• (#77) Reel Name writes that silently don't persist. set_clip_property /
  set_metadata returned success: true when writing the Reel Name clip
  property even though Resolve dropped the value. Resolve gates Reel Name
  behind General Options > Assist using reel names from the: — when that
  derives reel names automatically, scripted writes are ignored but still return
  True. On a batch ingest this meant clips believed to have reel names when
  none stuck. The server now reads the value back after writing known-unreliable
  keys and refuses to report success on mismatch, surfacing the project-setting
  gate as a hint. Wired into set_clip_property, set_metadata (both forms),
  and the bulk normalize_metadata path.

Added

• (PR #76, thanks @swayll) Four submit: missing API-limitation entries
  verified on Resolve 21.0.0: per-subtitle text/timing editing, subtitle track
  styling/presets, speech-recognition engine selection + SRT import, and Media
  Pool folder rename. These document the API ceiling behind subtitle feature
  request #75 — direct subtitle text editing and SRT round-trip are not exposed
  by the Blackmagic scripting API. The limitations report now lists 18 missing
  capabilities + 11 bugs.

Validation

• Offline: full unit suite green; new tests/test_reel_name_writeback.py (10
  tests) plus the api_truth / api-limitations drift guards.
• Live Resolve validation of the Reel Name read-back is recommended but not
  performed in this release — forcing the gate would require writing reel
  names into a live project's media metadata.