premiere-pro-mcp 1.16.0 → 1.16.2

package/CHANGELOG.md

@@ -6,6 +6,70 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.16.2] - 2026-09-18
+
+### Fixed
+
+- Direct UXP `.ccx` packages now use a plugin-id bundle root and Unix 644/755
+  permission bits so Creative Cloud / UPI can extract plugin metadata. (#566)
+- Path-based UXP commands now resolve native paths through the granted
+  workspace folder instead of advertising them as unsupported on every host.
+  (#567)
+
+Automated checks do not establish licensed Premiere or After Effects playback or
+rendered-output verification.
+
+## [1.16.1] - 2026-09-17
+
+### Added
+
+- Editor-request tools on the production CEP bridge, each with preflight and
+  readback: `add_markers_batch` (up to 200 verified sequence or clip markers per
+  call for beat grids, chapters, silence reviews, and client notes),
+  `select_clips_by_pattern` (every-Nth selection with offset, name/regex,
+  duration, range, track, and enabled filters), `navigate_playhead`
+  (start/end/in/out/work-area/edit/marker/frame stepping),
+  `create_sequence_checkpoint` and `list_sequence_checkpoints` (named
+  `[checkpoint]` sequence clones plus a diff-ready snapshot), and
+  `export_sequence_edl` (CMX 3600 EDL generated from timeline readback with
+  drop-frame support, reel mapping, M2 motion lines, and self-validation through
+  the existing CMX parser, returned inline or written inside an approved
+  workspace).
+- Local review planners: `plan_client_notes_checklist` turns pasted reviewer
+  feedback into a categorized, prioritized checklist with timecodes, ranges,
+  approvals, questions, and an `add_markers_batch` payload;
+  `plan_multicam_angle_switches` plans active-speaker angle cuts for stacked
+  camera tracks with minimum holds, crosstalk cover shots, lead-in cuts,
+  periodic cutaways, razor times, per-camera enable ranges, and markers.
+- The `essential`, `inspection`, `delivery`, and `assistant-edit` tool packs
+  include the relevant new tools; both planners are classified as `inspect`
+  authority. See [docs/editor-requests.md](docs/editor-requests.md) for the
+  community and competitor evidence and verification boundaries.
+
+### Fixed
+
+- `insert_from_source`, `add_to_timeline`, `add_to_timeline_batch`, and
+  `apply_edit_plan` insert operations no longer report success after
+  `Sequence.insertClip` ripples only the named tracks. The public DOM has no
+  sync-lock API; these tools now read QE `isSyncLocked()`, razor spanning clips
+  on locked neighbours, shift later clips with `__writeClipSpan`, and verify
+  the result. Mid-clip inserts on a target track are treated as a
+  split-plus-insert (two new items), not a failure. Default `scope` is
+  `sync_locked` and requires the target sequence to be active so QE razors the
+  same timeline. A razor that does not split a spanning neighbour fails closed.
+  Pass `target_tracks` to opt in to the old target-only ripple; that path still
+  verifies the named pair, honors DOM `Track.isLocked()`, and warns that other
+  tracks may desync. If QE or lock state is unavailable the sync-locked path
+  refuses before mutating. `apply_spot_workflow_plan` uses `target_tracks`
+  because it inserts then trims to the planned duration; a sync-locked ripple
+  would shift overlays and music beds by the untrimmed source length. (#562)
+- `ripple_delete` now closes the gap on the clip's own track and every QE
+  sync-locked track, and refuses when a locked neighbour would be left
+  straddling the hole. (#561)
+
+Automated checks do not establish licensed Premiere or After Effects playback or
+rendered-output verification.
+
 ## [1.16.0] - 2026-09-16
 
 ### Added

package/README.md

@@ -12,7 +12,7 @@ Free, MIT licensed, local-first, and published to npm as [`premiere-pro-mcp`](ht
 
 [Website](https://premiere-pro-mcp.com/) · [Recorded demo](https://premiere-pro-mcp.com/demo/) · [Compare servers](https://premiere-pro-mcp.com/compare/) · [Setup guides](https://premiere-pro-mcp.com/blog/how-to-set-up-premiere-pro-mcp/) · [Search tools](https://premiere-pro-mcp.com/tools/) · [Troubleshooting](https://premiere-pro-mcp.com/docs/troubleshooting/) · [Release facts](https://premiere-pro-mcp.com/facts/)
 
-Development source: 373 core tools across 54 modules, 4 resources, and 18 guided workflows. A connected UXP host adds 95 capability-gated tools.
+Development source: 381 core tools across 56 modules, 4 resources, and 18 guided workflows. A connected UXP host adds 95 capability-gated tools.
 
 The [completed AE render handoff](docs/after-effects-render-handoff.md) previews and confirms importing one finished render into an existing Premiere bin, with host and file rechecks and an import receipt.
 
@@ -104,14 +104,14 @@ and repository before configuring a client. The new
 VS Code, or Codex settings that point directly to this installation. It is a
 feature included in v1.15.1 and later.
 
-The current source exposes 373 core tools for supported workflow steps spanning the supported ExtendScript, QE DOM, local media and interchange analysis, revisioned project-context retrieval, safe edit-planning, project-intake preview, review handoff, connection verification, and guarded After Effects MOGRT authoring, batch, library, render-queue, inspection, and Premiere-handoff workflows. A compatible, authenticated UXP panel adds 95 documented, capability-gated tools without replacing the production CEP bridge.
+The current source exposes 381 core tools for supported workflow steps spanning the supported ExtendScript, QE DOM, local media and interchange analysis, revisioned project-context retrieval, safe edit-planning, project-intake preview, review handoff, connection verification, and guarded After Effects MOGRT authoring, batch, library, render-queue, inspection, and Premiere-handoff workflows. A compatible, authenticated UXP panel adds 95 documented, capability-gated tools without replacing the production CEP bridge.
 
 <a id="latest-release"></a>
 
-### Latest release: 1.16.0
+### Latest release: 1.16.2
 
-The published v1.15.2 npm artifact contains **369 core tools**, 367 in its default profile,
-and 460 with a compatible UXP connection. The development catalog above can include
+The published v1.16.1 npm artifact contains **381 core tools**, 379 in its default profile,
+and 474 with a compatible UXP connection. The development catalog above can include
 unreleased work. See the [versioned facts and package provenance](https://premiere-pro-mcp.com/facts/).
 
 ### Try a bounded workflow
@@ -132,7 +132,7 @@ if the connection is unavailable.
 
 - **Editorial planning:** film evidence, transcript cleanup, caption authoring, shorts and chapter planning, rhythm and speaker layouts, timeline QA, and platform delivery plans.
 - **Cross-app handoff:** capability-aware workflow routes and guarded After Effects render-to-Premiere handoff.
-- **Editing correctness:** verified readback and explicit capability or committed-but-unverified failures across transition, import, effects, source identity, and track operations.
+- **Editing correctness:** verified readback and explicit capability or committed-but-unverified failures across transition, import, effects, source identity, and track operations. Insert edits ripple QE sync-locked tracks instead of silently desyncing neighbours.
 
 - **MOGRT studio:** an optional, separate After Effects CEP connector can
   author approval-gated title, callout, quote, and social recipes; constrain
@@ -160,7 +160,7 @@ if the connection is unavailable.
   local Premiere processes. See the generated [supported action catalog](docs/supported-actions.md)
   for individual capability and verification contracts.
 
-See the [v1.16.0 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.16.0)
+See the [v1.16.2 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.16.2)
 for complete details. Live installation in Premiere Pro still requires host verification.
 
 ### Current MCP protocol support
@@ -208,7 +208,7 @@ their bins, media rules, and organization rules before a facility uses one.
 > ### Install the published package (verify the name)
 >
 > ```bash
-> npm i -g premiere-pro-mcp@1.16.0
+> npm i -g premiere-pro-mcp@1.16.2
 > ```
 >
 > This repository publishes only **`premiere-pro-mcp`**. A differently named package (`adobe-premiere-pro-mcp`) may also declare a `premiere-pro-mcp` executable. Before configuring a client, confirm:
@@ -216,7 +216,7 @@ their bins, media rules, and organization rules before a facility uses one.
 > | Check | Expected |
 > | --- | --- |
 > | Package name | `premiere-pro-mcp` (not `adobe-premiere-pro-mcp`) |
-> | Version | `1.16.0` |
+> | Version | `1.16.2` |
 > | Homepage / repo | https://premiere-pro-mcp.com/ · https://github.com/leancoderkavy/premiere-pro-mcp |
 >
 > ```bash
@@ -229,9 +229,9 @@ their bins, media rules, and organization rules before a facility uses one.
 
 ### Easiest supported path: Claude Desktop
 
-1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.16.0/premiere-pro-mcp-1.16.0.mcpb).
+1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.16.2/premiere-pro-mcp-1.16.2.mcpb).
 2. In Claude Desktop, open **Settings > Extensions > Advanced settings > Install Extension**, select the downloaded bundle, and restart Claude Desktop.
-3. Download the separate [signed Premiere connector (`.zxp`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.16.0/MCPBridgeCEP.zxp). Open it with your trusted ZXP installer. If your computer has no ZXP installer, use the npm connector installer in **Advanced setup** below.
+3. Download the separate [signed Premiere connector (`.zxp`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.16.2/MCPBridgeCEP.zxp). Open it with your trusted ZXP installer. If your computer has no ZXP installer, use the npm connector installer in **Advanced setup** below.
 4. Restart Premiere, open a project, then open **Window > Extensions > MCP for Adobe Premiere Pro**.
 5. In Claude, enter: `Safely check my Premiere connection with verify_premiere_connection. Make no changes.`
 
@@ -760,7 +760,7 @@ The bounded UXP migration surface also exposes guarded static Color effect-param
 
 The bounded UXP migration surface also exposes guarded typed Project metadata schema-field creation. It requires the exact inspected active-project identity and 12 KiB-bounded panel XML, an explicit confirmation and operation ID, and serializes this bridge's schema and panel-replacement calls per project. Adobe provides no atomic compare-and-set or field-level schema getter: native acceptance and a changed panel XML are evidence only, so the command always returns `committed_unverified` and does not claim field presence, persistence, UI results, Undo, cancellation, or licensed-host validation.
 
-The panel now requests access to one operator-selected workspace instead of declaring full filesystem access. Choose the folder in the panel before invoking a path-based UXP workflow. Media, relink, preset, export, and Source Monitor file paths must remain inside it; the persistent capability token and native root path are never returned over MCP. Lexical containment alone cannot exclude symlink, junction, or reparse-point escapes, and Adobe's request-scoped UXP filesystem API does not document canonical-path resolution. Builds without a host-supplied canonical resolver therefore advertise path-based UXP commands as unsupported and fail closed at invocation; use the existing CEP fallback for those operations.
+The panel now requests access to one operator-selected workspace instead of declaring full filesystem access. Choose the folder in the panel before invoking a path-based UXP workflow. Media, relink, preset, export, and Source Monitor file paths must remain inside it; the persistent capability token and native root path are never returned over MCP. After a folder is granted, path-based commands resolve each native path through that folder's Entry tree and compare the host `nativePath` against the approved root, so symlink or junction targets outside the workspace still fail closed. If the host Entry cannot be walked and no resolver is supplied, those commands stay unsupported and the CEP fallback remains the path-based compatibility route.
 
 Native transcript editing starts with a read-only, revision-locked planning flow. Use
 `get_clip_transcript_uxp` to export the transcript Premiere generated for a source
@@ -859,7 +859,7 @@ reports revision-bound notes, VFX state, change impact and turnover exceptions.
 It performs local inspection; host edits and exports use separate guarded tools.
 See [usage, example and remaining execution adapters](docs/film-editorial-workflows.md).
 
-## Tools (373 core total; 371 under the default profile; 466 with a connected UXP bridge)
+## Tools (381 core total; 379 under the default profile; 474 with a connected UXP bridge)
 
 The [complete supported-actions catalog](docs/supported-actions.md) lists every
 registered core tool, the two tools restricted behind explicit `unsafe-script`
@@ -983,7 +983,7 @@ Premiere Pro 26.x host.
 | `get_value_at_time` | Query interpolated value at any time |
 | `set_color_value` | Set color properties on effects |
 
-### Export & Encoding (16)
+### Export & Encoding (17)
 
 | Tool | Description |
 | :--- | :---------- |
@@ -992,13 +992,17 @@ Premiere Pro 26.x host.
 | `verify_delivery_file` | Verify output size and calculate SHA-256/SHA-512 checksums |
 | `capture_frame` | Export frame as PNG, return as base64 image |
 | `export_as_fcp_xml` / `export_aaf` / `export_omf` | Interchange formats |
+| `export_sequence_edl` | CMX 3600 EDL for one track, generated from timeline readback and self-validated (cuts, reels, drop/non-drop timecode, M2 lines for retimed clips) |
 | `encode_project_item` / `encode_file` | Direct encoding |
 | `start_batch_encode` | Start render queue |
 
-Premiere's documented automation surfaces do not currently expose OTIO or EDL
-interchange, Render and Replace, cloud publishing, or Content Credentials export
-configuration. `get_capabilities` reports these delivery gaps explicitly rather
-than presenting UI-only operations as available tools.
+Premiere's documented automation surfaces do not currently expose OTIO or native
+EDL interchange, Render and Replace, cloud publishing, or Content Credentials
+export configuration. `export_sequence_edl` therefore builds the CMX 3600 list
+locally from the clips Premiere reads back and validates it with the same parser
+used by `inspect_cmx3600_edl`; it is not a Premiere-native export.
+`get_capabilities` reports the remaining delivery gaps explicitly rather than
+presenting UI-only operations as available tools.
 
 ### Source Monitor & Playback (7 + 4)
 
@@ -1052,6 +1056,30 @@ than presenting UI-only operations as available tools.
 | `diff_sequence_snapshots` | Added / removed / moved / trimmed / retimed / renamed / enabled changes between two sequence snapshots with frame deltas and EDL-like lines |
 | `audit_timeline_health` | Health score with flash-frame, gap, overlap, repeated-shot, coverage, overlength, and speed findings plus review-frame suggestions |
 
+### Editor Requests: markers, selection, checkpoints, navigation (5)
+
+| Tool | Description |
+| :--- | :---------- |
+| `add_markers_batch` | Up to 200 sequence or clip markers in one verified request; feed it beat grids from `detect_beats`, chapters from `plan_chapter_markers`, or client notes from `plan_client_notes_checklist` |
+| `select_clips_by_pattern` | "Select every other clip": every-Nth selection with offset, name/regex, duration, range, track, and enabled filters, read back after selecting |
+| `create_sequence_checkpoint` / `list_sequence_checkpoints` | Named `[checkpoint]` sequence clone before a risky edit, plus a `diff_sequence_snapshots`-ready snapshot of the original |
+| `navigate_playhead` | Start, end, in/out, work area, next/previous edit or marker, or frame stepping with position readback |
+
+### Review and Conversation Planning (2)
+
+| Tool | Description |
+| :--- | :---------- |
+| `plan_client_notes_checklist` | Pasted client or reviewer feedback → prioritized checklist (category, must/should/nice, approvals, questions, timecodes and ranges) and an `add_markers_batch` payload |
+| `plan_multicam_angle_switches` | Active-speaker angle switching for stacked camera tracks: minimum holds, crosstalk cover shots, lead-in cuts, cutaways, razor times, per-camera enable ranges, and markers |
+
+Both planners are local and deterministic. Premiere exposes no scripting API
+for switching angles inside a multicam source sequence, so the multicam plan
+targets synced clips stacked on separate video tracks and is applied through
+`razor_all_tracks`, `select_clips_in_range`, `batch_enable_disable`, and
+`add_markers_batch` on a checkpointed sequence. See
+[editor requests](docs/editor-requests.md) for the community and competitor
+evidence behind these tools and their verification boundaries.
+
 ### Speaker Layout (2)
 
 | Tool | Description |
@@ -1299,7 +1327,7 @@ premiere-pro-mcp/
 ├── src/
 │   ├── index.ts                 # Entry point — stdio transport setup
 │   ├── http-server.ts           # Entry point — HTTP/SSE transport (Fly.io / remote)
-│   ├── server.ts                # MCP server — registers 373 tools, filtered by authority profile
+│   ├── server.ts                # MCP server — registers 381 tools, filtered by authority profile
 │   ├── bridge/
 │   │   ├── file-bridge.ts       # File-based IPC (write .jsx, poll .json)
 │   │   └── script-builder.ts    # ExtendScript generator with ES3 helpers

package/after-effects-cep-plugin/CSXS/manifest.xml

@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.aftereffects.bridge" ExtensionBundleVersion="1.16.0" ExtensionBundleName="MCP for Adobe After Effects">
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.aftereffects.bridge" ExtensionBundleVersion="1.16.2" ExtensionBundleName="MCP for Adobe After Effects">
   <ExtensionList>
-    <Extension Id="com.mcp.aftereffects.bridge.panel" Version="1.16.0"/>
+    <Extension Id="com.mcp.aftereffects.bridge.panel" Version="1.16.2"/>
   </ExtensionList>
   <ExecutionEnvironment>
     <HostList>

package/cep-plugin/CSXS/manifest.xml

@@ -1,8 +1,8 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.16.0" ExtensionBundleName="MCP for Adobe Premiere Pro">
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.16.2" ExtensionBundleName="MCP for Adobe Premiere Pro">
   <ExtensionList>
-    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.16.0"/>
-    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.16.0"/>
+    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.16.2"/>
+    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.16.2"/>
   </ExtensionList>
   <ExecutionEnvironment>
     <HostList>

package/cep-plugin/index.html

@@ -81,7 +81,7 @@
     <section class="update-section" aria-live="polite">
       <div class="update-copy">
         <span class="section-label">MCP updates</span>
-        <strong id="updateTitle">Version 1.16.0</strong>
+        <strong id="updateTitle">Version 1.16.2</strong>
         <span id="updateDetail">Checking the global MCP server and connector release…</span>
       </div>
       <button id="btnUpdate" class="button button-update" onclick="handleUpdateClick()" type="button" aria-describedby="updateDetail" disabled>

package/cep-plugin/updater.cjs

@@ -7,7 +7,7 @@
 })(this, function () {
   "use strict";
 
-  var CURRENT_VERSION = "1.16.0";
+  var CURRENT_VERSION = "1.16.2";
   var PACKAGE_NAME = "premiere-pro-mcp";
   var LATEST_PACKAGE_API = "https://registry.npmjs.org/" + PACKAGE_NAME;
   var LATEST_RELEASE_API =

package/dist/ai/client-notes.d.ts

@@ -0,0 +1,116 @@
+/**
+ * Client / reviewer note triage (local-only).
+ *
+ * Editors paste feedback from email, chat, or a review tool and want a
+ * checklist plus timeline markers, not another pass of re-reading. This
+ * planner turns free text into structured items: it finds timecodes and
+ * ranges, classifies each note into an editorial category, infers a priority
+ * from the wording, separates approvals and questions from change requests,
+ * and emits an `add_markers_batch` payload.
+ *
+ * Everything is deterministic lexical work. Nothing contacts a model, the
+ * network, or Premiere; the caller applies the markers through the routes
+ * returned in the plan.
+ */
+export declare const MAX_NOTES_BYTES: number;
+export declare const MAX_NOTE_ITEMS = 500;
+export declare const DEFAULT_MAX_NOTE_ITEMS = 200;
+export declare const MAX_MARKER_NAME_LENGTH = 60;
+export declare const NOTE_CATEGORIES: readonly ["audio", "color", "graphics", "text", "timing", "cut", "legal", "delivery", "other"];
+export type NoteCategory = (typeof NOTE_CATEGORIES)[number];
+export declare const NOTE_PRIORITIES: readonly ["must", "should", "nice"];
+export type NotePriority = (typeof NOTE_PRIORITIES)[number];
+export declare const NOTE_KINDS: readonly ["change", "question", "approval"];
+export type NoteKind = (typeof NOTE_KINDS)[number];
+export declare const MARKER_COLOR_MODES: readonly ["priority", "category", "fixed"];
+export type MarkerColorMode = (typeof MARKER_COLOR_MODES)[number];
+export declare const TIMECODE_STYLES: readonly ["auto", "clock", "frames"];
+/**
+ * How a three-part `a:b:c` timecode is read. `clock` means hh:mm:ss,
+ * `frames` means mm:ss:ff, and `auto` picks `frames` only when the last
+ * field is a plausible frame number below the frame rate and the first field
+ * is too large to be an hour count in a normal edit (>= 10).
+ */
+export type TimecodeStyle = (typeof TIMECODE_STYLES)[number];
+export declare const CLIENT_NOTES_ROUTES: readonly string[];
+/** Premiere marker color indexes as used by add_marker / add_markers_batch. */
+export declare const MARKER_COLORS: Readonly<{
+    green: 0;
+    red: 1;
+    purple: 2;
+    orange: 3;
+    yellow: 4;
+    white: 5;
+    blue: 6;
+    cyan: 7;
+}>;
+export type ClientNoteOptions = {
+    notes?: unknown;
+    frame_rate?: unknown;
+    sequence_duration_seconds?: unknown;
+    timecode_style?: unknown;
+    marker_color_mode?: unknown;
+    fixed_marker_color?: unknown;
+    marker_name_prefix?: unknown;
+    include_approvals_as_markers?: unknown;
+    max_items?: unknown;
+};
+export type ClientNoteItem = {
+    index: number;
+    text: string;
+    raw_line: string;
+    line_number: number;
+    kind: NoteKind;
+    category: NoteCategory;
+    priority: NotePriority;
+    reviewer: string | null;
+    time_seconds: number | null;
+    end_seconds: number | null;
+    frame: number | null;
+    timecode: string | null;
+    duration_seconds: number | null;
+    also_mentioned_seconds: number[];
+    out_of_range: boolean;
+    marker: ClientNoteMarker | null;
+};
+export type ClientNoteMarker = {
+    time_seconds: number;
+    name: string;
+    comments: string;
+    color: number;
+    duration_seconds: number;
+};
+export type ClientNotesPlan = {
+    applied: boolean;
+    plan_revision: string;
+    frame_rate: number;
+    counts: {
+        lines: number;
+        items: number;
+        timed: number;
+        untimed: number;
+        ranges: number;
+        out_of_range: number;
+        markers: number;
+        by_kind: Record<NoteKind, number>;
+        by_category: Record<NoteCategory, number>;
+        by_priority: Record<NotePriority, number>;
+    };
+    items: ClientNoteItem[];
+    markers: ClientNoteMarker[];
+    checklist_markdown: string;
+    routes: readonly string[];
+    next_steps: string[];
+    warnings: string[];
+    assumptions: string[];
+};
+/** Formats seconds as hh:mm:ss:ff (non-drop) for the given frame rate. */
+export declare function secondsToTimecode(seconds: number, fps: number): string;
+/**
+ * Parses one timecode token into seconds. Returns null when the token cannot
+ * be a timecode (for example `12:75`).
+ */
+export declare function parseTimecodeToken(token: string, fps: number, style: TimecodeStyle): number | null;
+/** Turns pasted reviewer feedback into a checklist and marker payloads. */
+export declare function planClientNotesChecklist(options: ClientNoteOptions): ClientNotesPlan;
+//# sourceMappingURL=client-notes.d.ts.map