premiere-pro-mcp 1.12.2 → 1.14.1

package/CHANGELOG.md

@@ -6,6 +6,49 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [1.14.1] - 2026-08-27
+
+### Fixed
+
+- Made npm package verification isolate its temporary tarball and select the
+  package matching `package.json`, avoiding a current npm CLI packaging
+  regression before publication.
+
+## [1.14.0] - 2026-08-27
+
+### Added
+
+- Added focused `essential`, `inspection`, `delivery`, and `captions` tool packs
+  so compatible MCP clients can begin with a smaller task-specific catalog.
+- Added `inspect_sequence_review_report`, a read-only, handoff-oriented sequence
+  report, and explicit MCP output schemas for every registered tool.
+
+### Safety
+
+- Tool packs change discoverability, not authority. Review reports redact media
+  paths by default and include marker comments only with explicit opt-in.
+- Package and response-contract checks remain distinct from licensed Premiere
+  host verification.
+
+## [1.13.0] - 2026-08-22
+
+### Added
+
+- Added `preview_project_intake`, a bounded, inspect-only project intake tool
+  that evaluates Premiere project organization against a facility-supplied
+  template and returns redacted findings plus proposed actions without changing
+  the project.
+- Added a deterministic intake rules engine, a guided workflow entry, a public
+  facts page, and design-partner/security pilot contracts for human-supervised
+  assistant-editor adoption.
+
+### Safety
+
+- File paths remain redacted unless explicitly requested, recursive capture and
+  outputs are bounded, and the intake workflow does not mutate or persist
+  project data. Automated tests passed, while licensed-host execution remains a
+  separate gate because Premiere 2026 hung before the CEP panel could open.
+
 ## [1.12.2] - 2026-08-22
 
 ### Fixed

package/README.md

@@ -2,11 +2,13 @@
 
 # MCP for Adobe Premiere Pro
 
+<!-- mcp-name: io.github.leancoderkavy/premiere-pro -->
+
 [![MCP Toplist](https://mcptoplist.com/badge/glama%2Fleancoderkavy%2Fpremiere-pro-mcp.svg)](https://mcptoplist.com/server/glama%2Fleancoderkavy%2Fpremiere-pro-mcp)
 
 **Give compatible AI assistants structured control over supported Adobe Premiere Pro workflows.**
 
-287 core tools across 33 modules, 4 resources, and 10 guided workflows. A connected UXP host adds 50 capability-gated tools.
+319 core tools across 37 modules, 14 resources, and 11 guided workflows. A connected UXP host adds 50 capability-gated tools.
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 [![Node.js](https://img.shields.io/badge/Node.js-20.19%2B-green.svg)](https://nodejs.org)
@@ -29,35 +31,72 @@ An [MCP (Model Context Protocol)](https://modelcontextprotocol.io) server that l
 "Add the B-roll clips to V2, apply a cross dissolve between each, color correct them to match the A-roll, and export a 1080p ProRes."
 ```
 
-The AI handles the entire workflow through 287 core tools spanning the supported ExtendScript, QE DOM, revisioned project-context retrieval, safe edit-planning, and connection-verification surfaces. A compatible, authenticated UXP panel adds 50 documented, capability-gated tools without replacing the production CEP bridge.
+The AI handles the entire workflow through 319 core tools spanning the supported ExtendScript, QE DOM, local media and interchange analysis, revisioned project-context retrieval, safe edit-planning, project-intake preview, review handoff, and connection-verification surfaces. A compatible, authenticated UXP panel adds 50 documented, capability-gated tools without replacing the production CEP bridge.
 
-### Latest release: 1.12.2
+### Latest release: 1.14.1
 
-- **MOGRT text and graphics:** `set_effect_property` now accepts string-backed
-  parameters with safe serialization and readback status.
-- **Effect discovery clarity:** an empty legacy QE effect catalog now returns a
-  no-mutation capability response and directs connected hosts to the documented
-  UXP catalog/add workflow.
-- **Verification clarity:** property readback remains distinct from playback or
-  exported-frame verification in a licensed Premiere Pro host.
+- **Focused discovery:** compatible MCP clients can select essential,
+  inspection, delivery, or captions tool packs instead of beginning with the
+  full catalog.
+- **Review handoff:** `inspect_sequence_review_report` returns a read-only,
+  path-redacted sequence report, with marker comments only when requested.
+- **Interoperability:** all registered MCP tools now declare explicit output
+  schemas; this release does not substitute automated checks for licensed-host
+  verification.
+- **Reliable packaging:** npm package verification now isolates its temporary
+  tarball, keeping the validated distribution path compatible with the current
+  npm CLI.
 
-See the [v1.12.2 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.12.2)
+See the [v1.14.1 release notes](https://github.com/leancoderkavy/premiere-pro-mcp/releases/tag/v1.14.1)
 for complete details. Live installation in Premiere Pro still requires host verification.
 
 ---
 
+## For editors evaluating an AI workflow
+
+Before an assistant changes an active project, use the
+[Premiere Pro AI workflow checklist](https://premiere-pro-mcp.com/blog/premiere-pro-ai-workflow-checklist/)
+to define the target and no-change boundaries, verify the local connection, request
+a bounded plan, and inspect the returned result. It is a practical starting point for
+assistant editors and post leads testing a repeatable workflow on a duplicate project
+or small test sequence.
+
+For product context, see the [Adobe Premiere AI Assistant and MCP comparison](https://premiere-pro-mcp.com/blog/adobe-premiere-ai-assistant-vs-mcp/)
+and the [Claude Desktop setup guide](https://premiere-pro-mcp.com/blog/claude-desktop-premiere-pro-mcp-setup/).
+
+If you are deciding between a single local project, an Adobe Production on shared
+storage, or a remote Team Project, use the [Premiere Pro collaboration workflow
+guide](https://premiere-pro-mcp.com/premiere-pro-collaboration-workflow/) before
+you evaluate an MCP path. It links the relevant Adobe guidance, makes no project
+inspection request, and ends with the same read-only connection check.
+
+---
+
 ## Quick Start
 
 ### Easiest supported path: Claude Desktop
 
-1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.12.2/premiere-pro-mcp-1.12.2.mcpb).
+1. Download the current [Claude Desktop bundle (`.mcpb`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.14.1/premiere-pro-mcp-1.14.1.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.12.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.
+3. Download the separate [signed Premiere connector (`.zxp`)](https://github.com/leancoderkavy/premiere-pro-mcp/releases/download/v1.14.1/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.`
 
 The Claude bundle contains the local MCP server, so this route does not require Node.js. The Premiere connector is a separate required install. The first prompt is read-only and reports whether the server is installed, configured, connected, and live-verified.
 
+### First proof, before the first edit
+
+![Illustrated local Premiere MCP workflow](landing/public/premiere-pro-mcp-demo-poster.png)
+
+*This is an illustrated workflow, not a Premiere panel screenshot or licensed-host proof.*
+
+1. Open a copied test project and an active sequence in Premiere.
+2. Open **Window > Extensions > MCP for Adobe Premiere Pro**. “Running” means the local panel bridge is available; it does not show that an edit completed.
+3. Run `premiere-pro-mcp --doctor` to check only local package/configuration readiness.
+4. Ask the AI client: `Run verify_premiere_connection. Make no changes.` The returned check is read-only and avoids project names, paths, and media details.
+
+If a bridge, project, or active sequence is missing, fix that setup state before allowing a mutation. For a concise, translatable version of this path, see [quick starts in English, Spanish, and Japanese](docs/quickstart/README.md). The translations are machine-assisted drafts and retain command names in English.
+
 ### Other AI assistants
 
 Cursor, VS Code/Copilot, Windsurf, and other MCP clients do not currently have a project-provided one-click installer. Use their MCP settings with the advanced npm route below. Keep the assistant, server, connector, and Premiere on the same computer.
@@ -114,6 +153,16 @@ premiere-pro-mcp --doctor
 
 Then ask your MCP client to run `verify_premiere_connection`. The check is read-only.
 
+#### Remove the CEP connector
+
+Fully quit Premiere, then remove only this connector:
+
+```bash
+premiere-pro-mcp --uninstall-cep
+```
+
+The uninstaller intentionally leaves Adobe's shared `PlayerDebugMode` setting in place so it does not disrupt other CEP extensions. Remove the MCP server from your AI client's configuration and uninstall the npm package separately if you no longer use it. On macOS, `--uninstall-cep` removes the per-user npm/source install; the signed system-wide `.pkg` route has a separate privileged removal command in [distribution readiness](docs/distribution-readiness.md#connector-removal).
+
 </details>
 
 ---
@@ -276,11 +325,11 @@ From a clone of this repository:
 ```bash
 codex plugin marketplace add .
 codex plugin add premiere-pro@premiere-pro-mcp
-npx -y premiere-pro-mcp@1.12.2 --install-cep
+npx -y premiere-pro-mcp@1.14.1 --install-cep
 ```
 
 Restart Premiere Pro and start a new Codex session after installation. The plugin
-launches `premiere-pro-mcp@1.12.2` through `npx`; the separate CEP installation is
+launches `premiere-pro-mcp@1.14.1` through `npx`; the separate CEP installation is
 required because the MCP server communicates with the running Premiere host through
 the local bridge.
 
@@ -300,7 +349,7 @@ For Claude Code, add this repository as a marketplace and install the plugin:
 Then install the Premiere bridge and start a new Claude Code session:
 
 ```bash
-npx -y premiere-pro-mcp@1.12.2 --install-cep
+npx -y premiere-pro-mcp@1.14.1 --install-cep
 ```
 
 The Claude Code package lives in
@@ -339,13 +388,36 @@ installed separately.
 QE-backed tools are reported as `experimental` because QE is undocumented and can vary between Premiere builds. Authority availability is reported separately from implementation support, so disabling `edit`, for example, does not incorrectly label editing tools as unsupported. Static metadata never claims that a Premiere operation succeeded; use `ping` and inspect each tool result for runtime evidence.
 
 MCP `tools/list` is filtered to the active authority profile. The default
-`inspect,edit,export,filesystem` profile advertises 285 of the 287 registered
+`inspect,edit,export,filesystem` profile advertises 317 of the 319 registered
 tools and omits `execute_extendscript` and `evaluate_expression`, which require
 explicit `unsafe-script` authority. `ping` and `get_capabilities` remain visible
 under every profile so a restricted or misconfigured server can still explain
 its state. The call-time capability guard remains authoritative even if listing
 metadata is wrong.
 
+### Workflow-scoped discovery packs and structured outputs
+
+By default, the full permitted catalog remains available. Set
+`PREMIERE_MCP_TOOL_PACKS` to `essential`, `inspection`, `delivery`, `captions`,
+or a comma-separated combination such as `inspection,captions` to reduce the
+tool discovery and registered session surface for a focused client. `full` is the explicit
+full-catalog mode and cannot be combined with another pack. `ping` and
+`get_capabilities` remain listed for diagnosis, and every registered call still
+passes through the same capability guard; a pack never grants authority.
+
+Every listed tool now declares the same machine-readable result envelope through
+MCP `outputSchema`: `ok`, `tool`, plus `data` on success or `error` on failure.
+The tool-specific `data` shape remains versioned by the individual tool result,
+so clients can reliably distinguish transport success from a Premiere or local
+operation failure without parsing the text block.
+
+`inspect_sequence_review_report` creates one read-only handoff report from
+Premiere timeline readback: sequence structure, primary-track gaps, disabled
+clips, muted tracks, marker timing, and offline-source evidence. It never
+returns media paths; marker comments are omitted unless explicitly requested.
+The report is not proof of rendered pixels, audio quality, caption accuracy,
+rights, or editorial approval.
+
 The MCP handshake reads `serverInfo.version` from the installed `package.json`,
 so clients receive the package version that is actually running rather than a
 separately maintained literal.
@@ -494,7 +566,7 @@ The file-based IPC bridge is simple, reliable, and works across macOS and Window
 
 ---
 
-## Tools (287 core total; 285 under the default profile; 335 with a connected UXP bridge)
+## Tools (319 core total; 317 under the default profile; 367 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`
@@ -694,15 +766,29 @@ Track targeting, batch operations, markers, audio levels, motion/transform, meta
 
 ## MCP Resources
 
-The server exposes four LLM context resources and ten workflow prompts:
+The server exposes fourteen LLM context resources and eleven workflow prompts:
 
 | Resource URI | Description |
 | :----------- | :---------- |
 | `config://premiere-instructions` | Best practices: workflow order, timeline rules, effect tips, error handling |
 | `config://extendscript-reference` | Complete ExtendScript API reference for writing custom scripts |
 | `config://premiere-workflows` | Machine-readable catalog for rough cuts, dialogue cleanup, captions, and delivery |
-
-These are automatically available to MCP clients that support resources, giving the AI deep context about how to drive Premiere Pro effectively.
+| `config://premiere-project-context` | Revisioned local project-context indexing and retrieval workflow |
+| `premiere://project/info` | Fresh, path-redacted current-project and active-sequence summary |
+| `premiere://project/sequences` | Bounded sequence inventory with stable Premiere IDs |
+| `premiere://project/media` | Bounded, path-redacted project-media inventory |
+| `premiere://project/bins` | Bounded, path-redacted project-bin inventory |
+| `premiere://timeline/active` | Bounded active-timeline tracks, clips, and markers snapshot |
+| `premiere://effects/available` | Bounded video/audio effect catalog for planning |
+| `premiere://effects/applied` | Bounded active-timeline component inventory |
+| `premiere://transitions/available` | Bounded video/audio transition catalog for planning |
+| `premiere://export/presets` | Bounded export-preset names and formats, without native paths |
+| `premiere://project/metadata` | Read-only project and active-timeline summary, without paths or timestamps |
+
+The ten `premiere://` snapshots are read-only CEP bridge requests. They include a
+revision token for stale-state detection and omit native media, project-tree, preset,
+and output paths. A successful snapshot proves bridge readback only—not licensed-host
+feature coverage, playback, rendering, or editorial correctness.
 
 ---
 
@@ -787,10 +873,18 @@ Then connect with:
 | `POSTHOG_DISTINCT_ID` | Optional stable anonymous server identifier | Fly machine ID or random boot ID |
 
 When PostHog is enabled, the server records `mcp_connection_attempt`,
-`mcp_request`, `mcp_request_rejected`, and `mcp_tool_call`. Events contain operational fields such as
-method, tool name, outcome, status code, and duration. Authentication tokens,
-IP addresses, MCP arguments, project paths, media names, and tool results are
-never sent. Person profiles are disabled for these events.
+`mcp_request`, `mcp_request_rejected`, and `mcp_tool_call`. It also records
+`premiere_mcp_activation_completed` only after the read-only
+`verify_premiere_connection` check confirms the selected bridge, an open
+project, and an active sequence. Events contain bounded operational fields such
+as method, tool name, outcome, status code, duration, and selected bridge.
+Authentication tokens, IP addresses, MCP arguments, project paths, media names,
+and tool results are never sent. Person profiles are disabled for these events.
+
+This signal is an aggregate emission, not proof that an analytics provider
+received it, a count of unique people or editors, or evidence that an editing
+workflow succeeded. It does not carry a person or editor identifier, so it
+cannot safely infer "first value."
 
 ---
 
@@ -801,7 +895,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 287 tools, filtered by authority profile
+│   ├── server.ts                # MCP server — registers 319 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/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.12.2" ExtensionBundleName="MCP for Adobe Premiere Pro">
+<ExtensionManifest Version="7.0" ExtensionBundleId="com.mcp.premiere.bridge" ExtensionBundleVersion="1.14.1" ExtensionBundleName="MCP for Adobe Premiere Pro">
   <ExtensionList>
-    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.12.2"/>
-    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.12.2"/>
+    <Extension Id="com.mcp.premiere.bridge.panel" Version="1.14.1"/>
+    <Extension Id="com.mcp.premiere.bridge.headless" Version="1.14.1"/>
   </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">Connector updates</span>
-        <strong id="updateTitle">Version 1.12.2</strong>
+        <strong id="updateTitle">Version 1.14.1</strong>
         <span id="updateDetail">Checking for updates…</span>
       </div>
       <button id="btnUpdate" class="button button-update" onclick="handleUpdateClick()" type="button" disabled>

package/cep-plugin/main.js

@@ -136,6 +136,21 @@ function writeFile(filePath, content) {
   }
 }
 
+// Publish responses atomically so the MCP process never sees a partially-written
+// JSON file. The staging suffix is not a response filename the server will read.
+function writeResponseFile(filePath, content) {
+  var stagedPath = filePath + ".staged";
+  try {
+    fs.writeFileSync(stagedPath, content, "utf-8");
+    fs.renameSync(stagedPath, filePath);
+    return true;
+  } catch (e) {
+    deleteFile(stagedPath);
+    log("Error publishing " + filePath + ": " + e.message, "err");
+    return false;
+  }
+}
+
 function deleteFile(filePath) {
   try {
     if (fs.existsSync(filePath)) fs.unlinkSync(filePath);
@@ -234,7 +249,7 @@ function processOneCommand(cmdFileName) {
       }
     }
 
-    writeFile(resFilePath, response);
+    writeResponseFile(resFilePath, response);
   });
 }
 

package/cep-plugin/updater.cjs

@@ -7,7 +7,7 @@
 })(this, function () {
   "use strict";
 
-  var CURRENT_VERSION = "1.12.2";
+  var CURRENT_VERSION = "1.14.1";
   var LATEST_RELEASE_API =
     "https://api.github.com/repos/leancoderkavy/premiere-pro-mcp/releases/latest";
   var RELEASES_URL =

package/dist/bridge/file-bridge.d.ts

@@ -12,7 +12,8 @@ export declare function getTempDir(options?: BridgeOptions): string;
  * Send a command (ExtendScript) to the CEP plugin and wait for a response.
  *
  * Protocol:
- * 1. Write script to <tempDir>/cmd_<id>.jsx
+ * 1. Write the script to a staging file, then atomically publish it as
+ *    <tempDir>/cmd_<id>.jsx. The CEP panel only sees complete commands.
  * 2. CEP plugin picks it up, executes, writes result to <tempDir>/res_<id>.json
  * 3. We poll for the response file and parse it.
  */

package/dist/bridge/file-bridge.js

@@ -1,11 +1,11 @@
-import { mkdirSync, writeFileSync, readFileSync, unlinkSync, existsSync, readdirSync, statSync, chmodSync, watch } from "node:fs";
+import { mkdirSync, writeFileSync, readFileSync, unlinkSync, existsSync, readdirSync, renameSync, statSync, chmodSync, watch } from "node:fs";
 import { basename, dirname, join } from "node:path";
 import { tmpdir } from "node:os";
+import { randomUUID } from "node:crypto";
 import { getHelpersSource, helpersFileName, buildBootstrap } from "./script-builder.js";
 const DEFAULT_TEMP_DIR = join(tmpdir(), "premiere-mcp-bridge");
 const POLL_FALLBACK_MS = 250;
 const DEFAULT_TIMEOUT_MS = 30000;
-let commandCounter = 0;
 /**
  * Create the bridge temp dir private to this user, and — critically — refuse to trust
  * one we didn't create.
@@ -59,7 +59,8 @@ function ensureHelpers(tempDir) {
  * Send a command (ExtendScript) to the CEP plugin and wait for a response.
  *
  * Protocol:
- * 1. Write script to <tempDir>/cmd_<id>.jsx
+ * 1. Write the script to a staging file, then atomically publish it as
+ *    <tempDir>/cmd_<id>.jsx. The CEP panel only sees complete commands.
  * 2. CEP plugin picks it up, executes, writes result to <tempDir>/res_<id>.json
  * 3. We poll for the response file and parse it.
  */
@@ -67,22 +68,27 @@ export async function sendCommand(script, options) {
     const tempDir = getTempDir(options);
     const timeoutMs = options?.timeoutMs || DEFAULT_TIMEOUT_MS;
     ensureDir(tempDir);
-    const id = `${Date.now()}_${++commandCounter}`;
+    const id = randomUUID();
     const cmdFile = join(tempDir, `cmd_${id}.jsx`);
+    const stagedCmdFile = `${cmdFile}.staged`;
     const resFile = join(tempDir, `res_${id}.json`);
     const busyFile = join(tempDir, `busy_${id}.json`);
     // Validate script
     validateScript(script);
-    // Write command file (bootstrap loads the helpers into the engine if needed)
-    writeFileSync(cmdFile, `${ensureHelpers(tempDir)}
+    try {
+        // Write a complete command before its .jsx name makes it visible to CEP.
+        // renameSync is atomic when both paths are in the bridge directory.
+        writeFileSync(stagedCmdFile, `${ensureHelpers(tempDir)}
 ${script}`, "utf-8");
-    // Poll for response
-    const result = await pollForResponse(resFile, busyFile, timeoutMs);
-    // Cleanup
-    safeUnlink(cmdFile);
-    safeUnlink(resFile);
-    safeUnlink(busyFile);
-    return result;
+        renameSync(stagedCmdFile, cmdFile);
+        return await pollForResponse(resFile, busyFile, timeoutMs);
+    }
+    finally {
+        safeUnlink(stagedCmdFile);
+        safeUnlink(cmdFile);
+        safeUnlink(resFile);
+        safeUnlink(busyFile);
+    }
 }
 function validateScript(script, allowUnsafe = false) {
     const MAX_SCRIPT_SIZE = 500 * 1024; // 500KB
@@ -112,18 +118,24 @@ export async function sendRawCommand(script, options) {
     const tempDir = getTempDir(options);
     const timeoutMs = options?.timeoutMs || DEFAULT_TIMEOUT_MS;
     ensureDir(tempDir);
-    const id = `${Date.now()}_${++commandCounter}`;
+    const id = randomUUID();
     const cmdFile = join(tempDir, `cmd_${id}.jsx`);
+    const stagedCmdFile = `${cmdFile}.staged`;
     const resFile = join(tempDir, `res_${id}.json`);
     const busyFile = join(tempDir, `busy_${id}.json`);
     validateScript(script, true);
-    writeFileSync(cmdFile, `${ensureHelpers(tempDir)}
+    try {
+        writeFileSync(stagedCmdFile, `${ensureHelpers(tempDir)}
 ${script}`, "utf-8");
-    const result = await pollForResponse(resFile, busyFile, timeoutMs);
-    safeUnlink(cmdFile);
-    safeUnlink(resFile);
-    safeUnlink(busyFile);
-    return result;
+        renameSync(stagedCmdFile, cmdFile);
+        return await pollForResponse(resFile, busyFile, timeoutMs);
+    }
+    finally {
+        safeUnlink(stagedCmdFile);
+        safeUnlink(cmdFile);
+        safeUnlink(resFile);
+        safeUnlink(busyFile);
+    }
 }
 async function pollForResponse(resFile, busyFile, timeoutMs) {
     const start = Date.now();
@@ -134,6 +146,7 @@ async function pollForResponse(resFile, busyFile, timeoutMs) {
     // misreporting "is the plugin running?".
     const hardCapMs = Math.max(timeoutMs * 4, 120_000);
     let sawBusy = false;
+    let lastResponseParseError;
     const busyIsFresh = () => {
         try {
             if (!existsSync(busyFile))
@@ -172,15 +185,20 @@ async function pollForResponse(resFile, busyFile, timeoutMs) {
                 try {
                     const raw = readFileSync(resFile, "utf-8");
                     const result = JSON.parse(raw);
-                    finish(result);
+                    if (typeof result !== "object" || result === null || typeof result.success !== "boolean") {
+                        lastResponseParseError = "Failed to parse response: missing boolean success field";
+                    }
+                    else {
+                        finish(result);
+                        return;
+                    }
                 }
                 catch (e) {
-                    finish({
-                        success: false,
-                        error: `Failed to parse response: ${e instanceof Error ? e.message : String(e)}`,
-                    });
+                    // A CEP response can be observed while an older connector is still writing it.
+                    // Keep polling the same response file; never resend the host operation.
+                    lastResponseParseError =
+                        `Failed to parse response: ${e instanceof Error ? e.message : String(e)}`;
                 }
-                return;
             }
             const elapsed = Date.now() - start;
             if (elapsed >= timeoutMs) {
@@ -189,6 +207,10 @@ async function pollForResponse(resFile, busyFile, timeoutMs) {
                     scheduleFallback();
                     return;
                 }
+                if (lastResponseParseError) {
+                    finish({ success: false, error: lastResponseParseError });
+                    return;
+                }
                 finish({
                     success: false,
                     error: sawBusy

package/dist/http-server.js

@@ -89,8 +89,25 @@ function serveLanding(req, res, scriptNonce) {
         relativePath.startsWith(`..${path.sep}`) ||
         path.isAbsolute(relativePath))
         return false;
-    if (!fs.existsSync(filePath))
-        return false;
+    if (!fs.existsSync(filePath)) {
+        // Next static exports store dynamic-route Flight payloads in nested folders
+        // (for example, __next.blog/$d$slug/__PAGE__.txt), while the client asks
+        // for a flattened filename (__next.blog.$d$slug.__PAGE__.txt). Map only
+        // that generated shape after every original URL segment has passed the
+        // containment check above. Without this, guide-to-guide navigation falls
+        // back to a full-document load and emits avoidable 404s.
+        const requestedFlightFile = safeSegments.at(-1);
+        const flightParts = requestedFlightFile?.split(".") ?? [];
+        const isNestedFlightPayload = flightParts.length >= 4 &&
+            flightParts[0] === "__next" &&
+            flightParts.at(-1) === "txt";
+        if (!isNestedFlightPayload)
+            return false;
+        const remappedFlightPath = path.join(LANDING_DIR, ...safeSegments.slice(0, -1), `${flightParts[0]}.${flightParts[1]}`, ...flightParts.slice(2, -2), `${flightParts.at(-2)}.txt`);
+        if (!fs.existsSync(remappedFlightPath))
+            return false;
+        filePath = remappedFlightPath;
+    }
     let fileStats;
     try {
         fileStats = fs.statSync(filePath);

package/dist/index.js

@@ -21,11 +21,12 @@ function debugLog(message) {
 const args = process.argv.slice(2);
 if (args.includes("--help") || args.includes("-h")) {
     console.log(`
-premiere-pro-mcp — MCP server for Adobe Premiere Pro (285 default-profile tools)
+premiere-pro-mcp — MCP server for Adobe Premiere Pro (317 default-profile tools)
 
 Usage:
   premiere-pro-mcp              Start the MCP server (stdio transport)
   premiere-pro-mcp --install-cep   Install the CEP plugin into Premiere Pro
+  premiere-pro-mcp --uninstall-cep Remove this CEP plugin from Premiere Pro
   premiere-pro-mcp --diagnose-cep  Check the CEP install, debug keys, and Premiere signature logs
   premiere-pro-mcp --doctor        Check local install/configuration without reading a project
   premiere-pro-mcp --doctor --json Print the same local check as machine-readable JSON
@@ -37,6 +38,7 @@ Environment variables:
   PREMIERE_TEMP_DIR     Shared temp directory (default: OS temp + /premiere-mcp-bridge)
   PREMIERE_TIMEOUT_MS   Command timeout in ms (default: 30000)
   PREMIERE_MCP_CAPABILITIES  Comma-separated authority profile
+  PREMIERE_MCP_TOOL_PACKS    Comma-separated discovery packs: full, essential, inspection, delivery, captions
   PREMIERE_MCP_DEBUG    Set to 1/true to enable verbose stderr diagnostics
   PREMIERE_UXP_TOKEN    Enable the authenticated local UXP bridge (minimum 16 characters)
   PREMIERE_UXP_PORT     UXP loopback WebSocket port (default: 7777)
@@ -66,9 +68,18 @@ if (args.includes("--doctor") || args.includes("--support-bundle")) {
     }
     process.exit(0);
 }
-if (args.includes("--install-cep") || args.includes("--diagnose-cep")) {
-    const diagnose = args.includes("--diagnose-cep");
-    console.log(diagnose ? "Diagnosing CEP plugin...\n" : "Installing CEP plugin...\n");
+const cepActions = ["--install-cep", "--uninstall-cep", "--diagnose-cep"].filter((flag) => args.includes(flag));
+if (cepActions.length > 1) {
+    console.error("Use only one CEP action at a time: --install-cep, --uninstall-cep, or --diagnose-cep.");
+    process.exit(1);
+}
+if (cepActions.length === 1) {
+    const action = cepActions[0];
+    const diagnose = action === "--diagnose-cep";
+    const uninstall = action === "--uninstall-cep";
+    console.log(uninstall
+        ? "Removing CEP plugin...\n"
+        : diagnose ? "Diagnosing CEP plugin...\n" : "Installing CEP plugin...\n");
     const isWindows = process.platform === "win32";
     const isMacOS = process.platform === "darwin";
     if (!isWindows && !isMacOS) {
@@ -81,20 +92,27 @@ if (args.includes("--install-cep") || args.includes("--diagnose-cep")) {
             const powershellArgs = ["-NoProfile", "-ExecutionPolicy", "Bypass", "-File", scriptPath];
             if (diagnose)
                 powershellArgs.push("-Diagnose");
+            if (uninstall) {
+                powershellArgs[4] = path.join(projectRoot, "scripts", "uninstall-cep.ps1");
+            }
             execFileSync("powershell.exe", powershellArgs, { stdio: "inherit", cwd: projectRoot });
         }
         else {
-            execFileSync("bash", [scriptPath, diagnose ? "--diagnose" : "--copy"], {
+            const macosScriptPath = uninstall
+                ? path.join(projectRoot, "scripts", "uninstall-cep.sh")
+                : scriptPath;
+            execFileSync("bash", [macosScriptPath, uninstall ? "--user" : diagnose ? "--diagnose" : "--copy"], {
                 stdio: "inherit",
                 cwd: projectRoot,
             });
         }
     }
     catch {
-        console.error(`CEP ${diagnose ? "diagnostics" : "installation"} failed. Try running manually:`);
+        const operation = uninstall ? "uninstallation" : diagnose ? "diagnostics" : "installation";
+        console.error(`CEP ${operation} failed. Try running manually:`);
         console.error(isWindows
-            ? `  powershell -ExecutionPolicy Bypass -File "${scriptPath}"${diagnose ? " -Diagnose" : ""}`
-            : `  bash "${scriptPath}" ${diagnose ? "--diagnose" : "--copy"}`);
+            ? `  powershell -ExecutionPolicy Bypass -File "${uninstall ? path.join(projectRoot, "scripts", "uninstall-cep.ps1") : scriptPath}"${diagnose ? " -Diagnose" : ""}`
+            : `  bash "${uninstall ? path.join(projectRoot, "scripts", "uninstall-cep.sh") : scriptPath}" ${uninstall ? "--user" : diagnose ? "--diagnose" : "--copy"}`);
         process.exit(1);
     }
     process.exit(0);