v2.54.3

v2.54.3

Follow-up to the v2.54.2 config-merge fix (#71): the JSONC sanitizer's
trailing-comma step was not string-aware.

Fixed

• _strip_jsonc removed trailing commas with a regex applied to the whole
  document, so a comma inside a string value followed by whitespace and a closing
  brace/bracket — e.g. "greeting": "hello, } world" — had the comma silently
  stripped from inside the string when merging a commented (JSONC) client
  config. (The JSONC path only runs when strict json.loads already failed, i.e.
  on real commented configs.) The trailing-comma pass is now string-aware,
  mirroring the comment stripper, so string contents are never altered while real
  trailing commas are still removed. Dropped the now-unused re import.

Validation

• Full offline unit/static suite green (1244 tests), including new regression
  tests for string values containing , } / , ]. Installer string-processing
  is fully offline-testable; no Resolve behavior changed, so no live run required.