@synthetic-ai/premiere-mcp 2.1.0 → 2.3.0-dev.0

package/CHANGELOG.md

@@ -1,123 +1,135 @@
-# Changelog
-
-## [v2.1.0] — CRITICAL: correct the version line, ship everything since 2.0.0
-
-`@synthetic-ai/premiere-mcp@2.0.0` (published 2026-06-10, the npm rename
-from unscoped `premiere-pro-mcp`) has been the only version ever actually
-published to the registry — `npm view` confirms `dist-tags.latest` and the
-full `versions` list both show only `2.0.0`, right up until this release.
-Six commits after the rename (v1.1.2 through v1.1.8, including v1.1.7's
-**server-side license enforcement**) bumped `package.json`'s version
-*backward* into a stale pre-rename 1.1.x line instead of continuing from
-2.0.0, and were committed/tested but never `npm publish`ed under that
-wrong version number. Net effect: every customer running
-`npx @synthetic-ai/premiere-mcp` has been getting the unmodified 2.0.0
-tarball — with **zero license checking on any of the 437 tools** — for
-over three months, discovered 2026-09-23 while shipping the macOS preset
-fix below. This release corrects the version line (2.0.0 → 2.1.0, a real
-semver increase) and ships every accumulated fix at once:
-- License enforcement (was v1.1.7): every tool except `ping` /
-  `get_version_info` now validates `PREMIERE_PRO_MCP_LICENSE`.
-- In-panel auto-update + local license storage (was v1.1.2).
-- ExtendScript obfuscation breaking `evalFile()` (was v1.1.4).
-- Bridge could wedge forever after a single failed command read (was v1.1.5).
-- macOS default sequence-preset paths (was v1.1.8, see below).
-
-## [v1.1.8] — macOS default preset paths (superseded by v2.1.0, never actually reached "latest" — see above)
-
-`create_sequence`, `create_sequence_from_clip`, and `get_default_sequence_presets`
-only ever probed Windows install paths for the default `.sqpreset` (and, for
-`create_sequence`, only a single hardcoded PP 2026 path with no probing at
-all). All three now check both Windows and macOS locations across PP
-2026/2025/2024/CC 2023, matching the pattern `export_sequence` already used
-for AME presets. When nothing is found, the tools return a clear error
-asking for an explicit `preset_path` instead of silently using a
-definitely-wrong fallback. Found via a site-wide macOS-compatibility audit
-of every Synthetic product (2026-09-23) — this was the one confirmed gap in
-an otherwise genuinely cross-platform architecture (no launch step to
-break, unlike ae-mcp). Unverified on real macOS hardware — no Mac available
-to test against yet.
-
-## [v1.1.7] — License enforcement
-
-The MCP server itself (all 437 tools) never actually validated
-`PREMIERE_PRO_MCP_LICENSE` — the CEP panel had a license field for its own
-auto-update, but the server side was wide open. Added the same
-`checkLicense()` gate ae-mcp and photoshop-mcp already have: every tool
-except `ping` / `get_version_info` now requires a valid license, validated
-against `https://synthetic.com.ar/api/v1/license/validate` and cached for an
-hour.
-
----
-
-All notable changes to this MCP server. Every fix below was discovered via
-**static audit + live runtime testing against Premiere Pro 2026.2.2 on
-Spanish-localized Windows**.
-
-The audit started at **31/100 sellability score** (22% green tools) and
-finished at **~78/100** (~75% green) after the rounds below.
-
----
-
-## [v1.2.0] — PP 2026 compatibility + locale resilience
-
-### Round 6 — Live runtime validation
-- `6f20892` capture_frame: honest error for PP 2026 host limitation
-- `8152021` bridge: sanitize NaN and Infinity to null
-- `a74ce33` Round 5: 8 more fixes from full smoke test (137 tools tested)
-- `45fdaba` track-targeting: locale-resilient set_clip_position/scale/rotation
-- `f9589cb` premiere.jsx: locale-resilient fadeIn/fadeOut/crossFadeClips
-- `29e941d` graceful fallbacks for setSpeed signature + track volume
-- `0533162` Live-test fixes: setSpeed signature, locale prop names, audio clip volume
-- `084ef49` Live-test fixes: set_clip_opacity locale, color_correct Lumetri name
-
-### Round 5 — Bridge JSON sanitization
-- `f3d83d7` Fix bridge JSON: ExtendScript ignores replacer; sanitize tree pre-stringify
-
-### Round 4 — premiere.jsx loading (single highest-impact fix)
-- `366f325` Fix premiere.jsx SyntaxError that broke ALL JSX helpers
-  - **1-char fix, ~30+ tools unblocked**
-  - `premiere.jsx` (22k lines) had `package:` as bare property name at line
-    22006. ExtendScript is strict ES3 where `package` is reserved → entire
-    file fails to parse → every JSX-helper-backed tool returns
-    `ReferenceError: <fn> is not a function`. Quoting fixes everything.
-- `b12a0d8` Round 4: bridge JSON-parse failure + locale-resilient transition lookup
-
-### Round 3 — Concrete code bugs from re-audit
-- `21bf821` Round 3 part 2: fix remaining 9 files
-- `e4534d5` Round 3: fix 32 concrete code bugs from re-audit
-  - ticks/Time correctness (markers, source-monitor, scripting, clipboard, audio)
-  - property-vs-method (media.check_offline_media)
-  - QE-only methods routed correctly (timeline.move_clip/speed_change, transitions)
-  - missing `app.enableQE()` guards
-  - nested Lumetri prop lookup via `__findProp`
-
-### Round 2 — Locale-resilient helpers
-- `bdaebaa` Round 2: guard QE multicam enumeration and proxy detach
-- `48d3648` Round 2 part 2: fix remaining 8 files
-- `2b718b3` Round 2 part 1: locale-resilient helpers + fix 13 tool files
-  - Added `__findIntrinsic(clip, key)` with matchName-first lookup
-  - Added `__findComponent`, `__findProp`, `__readMaybe`, `__findTransition`
-
-### Round 1 — Property-vs-method bugs
-- `ffe6931` Fix 21 red tools: property-vs-method bugs, missing APIs, stub handlers
-- `35ecbfa` Fix PP 2026 compatibility: sequence creation, tracks, audio, effects, export
-
----
-
-## Validated tool inventory
-
-### ✅ 66 tools confirmed working in runtime (PP 2026.2.2 es-ES)
-Inspection, transform, audio/video FX, timeline editing, selection, markers,
-sequence ops, project/bins, captions, source monitor, track management,
-metadata, scripting, export. Full list in [README.md](README.md).
-
-### ⚠️ Honest errors (PP 2026 host limitations, not bugs)
-- `set_track_volume`, `speed_change`, `capture_frame`, Lumetri-when-not-applied
-- All return clear errors with the recommended UI workaround
-
-### Validated against
-- Premiere Pro 2026.2.2 on Windows
-- Spanish (es-ES) locale — names like "Opacidad", "Movimiento", "Escala",
-  "Posición", "Disolvencia cruzada" all handled
-- 15-item test project with multi-track timeline, transitions, fades, Lumetri
+# Changelog
+
+## [v2.2.0] — `--doctor` diagnostic command
+
+`premiere-pro-mcp --doctor` runs a standalone setup check — no MCP client or
+Premiere Pro needs to be running: Node version, Premiere Pro install
+detected on disk, license key present + live-validated against
+synthetic.com.ar, and the CEP bridge temp directory is writable. Prints a
+pass/warn/fail summary and exits 1 if anything failed, so it's scriptable.
+Fixed a real crash found while building this: forcing `process.exit()`
+right after the live license check's `fetch()` call could crash with a
+libuv assertion on Windows (`UV_HANDLE_CLOSING`, src/win/async.c) — now
+sets `process.exitCode` and lets the event loop drain naturally instead.
+
+## [v2.1.0] — CRITICAL: correct the version line, ship everything since 2.0.0
+
+`@synthetic-ai/premiere-mcp@2.0.0` (published 2026-06-10, the npm rename
+from unscoped `premiere-pro-mcp`) has been the only version ever actually
+published to the registry — `npm view` confirms `dist-tags.latest` and the
+full `versions` list both show only `2.0.0`, right up until this release.
+Six commits after the rename (v1.1.2 through v1.1.8, including v1.1.7's
+**server-side license enforcement**) bumped `package.json`'s version
+*backward* into a stale pre-rename 1.1.x line instead of continuing from
+2.0.0, and were committed/tested but never `npm publish`ed under that
+wrong version number. Net effect: every customer running
+`npx @synthetic-ai/premiere-mcp` has been getting the unmodified 2.0.0
+tarball — with **zero license checking on any of the 437 tools** — for
+over three months, discovered 2026-09-23 while shipping the macOS preset
+fix below. This release corrects the version line (2.0.0 → 2.1.0, a real
+semver increase) and ships every accumulated fix at once:
+- License enforcement (was v1.1.7): every tool except `ping` /
+  `get_version_info` now validates `PREMIERE_PRO_MCP_LICENSE`.
+- In-panel auto-update + local license storage (was v1.1.2).
+- ExtendScript obfuscation breaking `evalFile()` (was v1.1.4).
+- Bridge could wedge forever after a single failed command read (was v1.1.5).
+- macOS default sequence-preset paths (was v1.1.8, see below).
+
+## [v1.1.8] — macOS default preset paths (superseded by v2.1.0, never actually reached "latest" — see above)
+
+`create_sequence`, `create_sequence_from_clip`, and `get_default_sequence_presets`
+only ever probed Windows install paths for the default `.sqpreset` (and, for
+`create_sequence`, only a single hardcoded PP 2026 path with no probing at
+all). All three now check both Windows and macOS locations across PP
+2026/2025/2024/CC 2023, matching the pattern `export_sequence` already used
+for AME presets. When nothing is found, the tools return a clear error
+asking for an explicit `preset_path` instead of silently using a
+definitely-wrong fallback. Found via a site-wide macOS-compatibility audit
+of every Synthetic product (2026-09-23) — this was the one confirmed gap in
+an otherwise genuinely cross-platform architecture (no launch step to
+break, unlike ae-mcp). Unverified on real macOS hardware — no Mac available
+to test against yet.
+
+## [v1.1.7] — License enforcement
+
+The MCP server itself (all 437 tools) never actually validated
+`PREMIERE_PRO_MCP_LICENSE` — the CEP panel had a license field for its own
+auto-update, but the server side was wide open. Added the same
+`checkLicense()` gate ae-mcp and photoshop-mcp already have: every tool
+except `ping` / `get_version_info` now requires a valid license, validated
+against `https://synthetic.com.ar/api/v1/license/validate` and cached for an
+hour.
+
+---
+
+All notable changes to this MCP server. Every fix below was discovered via
+**static audit + live runtime testing against Premiere Pro 2026.2.2 on
+Spanish-localized Windows**.
+
+The audit started at **31/100 sellability score** (22% green tools) and
+finished at **~78/100** (~75% green) after the rounds below.
+
+---
+
+## [v1.2.0] — PP 2026 compatibility + locale resilience
+
+### Round 6 — Live runtime validation
+- `6f20892` capture_frame: honest error for PP 2026 host limitation
+- `8152021` bridge: sanitize NaN and Infinity to null
+- `a74ce33` Round 5: 8 more fixes from full smoke test (137 tools tested)
+- `45fdaba` track-targeting: locale-resilient set_clip_position/scale/rotation
+- `f9589cb` premiere.jsx: locale-resilient fadeIn/fadeOut/crossFadeClips
+- `29e941d` graceful fallbacks for setSpeed signature + track volume
+- `0533162` Live-test fixes: setSpeed signature, locale prop names, audio clip volume
+- `084ef49` Live-test fixes: set_clip_opacity locale, color_correct Lumetri name
+
+### Round 5 — Bridge JSON sanitization
+- `f3d83d7` Fix bridge JSON: ExtendScript ignores replacer; sanitize tree pre-stringify
+
+### Round 4 — premiere.jsx loading (single highest-impact fix)
+- `366f325` Fix premiere.jsx SyntaxError that broke ALL JSX helpers
+  - **1-char fix, ~30+ tools unblocked**
+  - `premiere.jsx` (22k lines) had `package:` as bare property name at line
+    22006. ExtendScript is strict ES3 where `package` is reserved → entire
+    file fails to parse → every JSX-helper-backed tool returns
+    `ReferenceError: <fn> is not a function`. Quoting fixes everything.
+- `b12a0d8` Round 4: bridge JSON-parse failure + locale-resilient transition lookup
+
+### Round 3 — Concrete code bugs from re-audit
+- `21bf821` Round 3 part 2: fix remaining 9 files
+- `e4534d5` Round 3: fix 32 concrete code bugs from re-audit
+  - ticks/Time correctness (markers, source-monitor, scripting, clipboard, audio)
+  - property-vs-method (media.check_offline_media)
+  - QE-only methods routed correctly (timeline.move_clip/speed_change, transitions)
+  - missing `app.enableQE()` guards
+  - nested Lumetri prop lookup via `__findProp`
+
+### Round 2 — Locale-resilient helpers
+- `bdaebaa` Round 2: guard QE multicam enumeration and proxy detach
+- `48d3648` Round 2 part 2: fix remaining 8 files
+- `2b718b3` Round 2 part 1: locale-resilient helpers + fix 13 tool files
+  - Added `__findIntrinsic(clip, key)` with matchName-first lookup
+  - Added `__findComponent`, `__findProp`, `__readMaybe`, `__findTransition`
+
+### Round 1 — Property-vs-method bugs
+- `ffe6931` Fix 21 red tools: property-vs-method bugs, missing APIs, stub handlers
+- `35ecbfa` Fix PP 2026 compatibility: sequence creation, tracks, audio, effects, export
+
+---
+
+## Validated tool inventory
+
+### ✅ 66 tools confirmed working in runtime (PP 2026.2.2 es-ES)
+Inspection, transform, audio/video FX, timeline editing, selection, markers,
+sequence ops, project/bins, captions, source monitor, track management,
+metadata, scripting, export. Full list in [README.md](README.md).
+
+### ⚠️ Honest errors (PP 2026 host limitations, not bugs)
+- `set_track_volume`, `speed_change`, `capture_frame`, Lumetri-when-not-applied
+- All return clear errors with the recommended UI workaround
+
+### Validated against
+- Premiere Pro 2026.2.2 on Windows
+- Spanish (es-ES) locale — names like "Opacidad", "Movimiento", "Escala",
+  "Posición", "Disolvencia cruzada" all handled
+- 15-item test project with multi-track timeline, transitions, fades, Lumetri

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2025 Premiere Pro MCP Contributors
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2025 Premiere Pro MCP Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.