v2.55.1

v2.55.1

Deep-QC P1 — settings/options whitelisting + DeleteProject reliability.

Fixed

• Options/settings dicts passed to several Resolve APIs are now whitelisted to
  their documented keys, so a typo'd key is reported (ignored_options /
  ignored_settings / ignored_state_keys) instead of silently dropped:
  media_pool.import_timeline, timeline.import_into_timeline, raw
  render.set_settings, render.quick_export, and set_voice_isolation_state
  (track + item).
• ProjectManager.DeleteProject is flaky — it silently returns False when the
  target is/was the current project. All callers (safe + raw
  project_manager.delete, granular delete_project) now route through
  delete_project_safely (switch-away + retry) and report delete_detail. Added
  an api_truth entry.

Added

• A destructive-registry drift guard (tests/test_destructive_registry_drift.py)
  asserting token-gated actions map to real handlers and locking in the media-pool
  delete governance from v2.55.0. It also surfaced a pre-existing registry
  mis-keying issue (some destructive actions registered under the wrong tool key),
  now tracked for a dedicated audit.

Validation

• Full offline unit/static suite green (1280 tests). Whitelisting only drops keys
  Resolve already ignored; DeleteProject routing uses the existing tested helper —
  no Resolve behavior change for valid inputs, so no live run required.