@writepanda/mcp 1.225.0 → 1.227.0

package/bin/server.mjs

@@ -2186,7 +2186,7 @@ const TOOLS = [
 	{
 		name: "project_add_3d_captions",
 		description:
-			"3D camera captions on a talking-head HOOK (5-20 s, 16:9, locked medium shot): the camera whips in and trucks between caption groups at different depths, a hero word hides behind the head, an optional ring of words turns in front of the speaker, a staircase finale. Rendered from the clip's footage, matte and transcript; placed over [startMs, endMs] (editor captions hidden there). Do it after the cuts. Refuses a moving camera or extreme close-up. ASYNC: job_wait gives overlayId, beats[].still (look at each), qc, warnings. Re-run replaces; reference/3d-captions.md.",
+			"3D camera captions on a talking-head HOOK (5-20 s, 16:9 or vertical 9:16, also 1:1 / 4:5; locked medium shot; in 9:16 built from the crop the Short shows, laid out inside the Shorts-safe area): the camera whips in and trucks between caption groups at different depths, a hero word hides behind the head, an optional ring of words turns in front of the speaker, a staircase finale. Rendered from the clip's footage, matte and transcript; placed over [startMs, endMs] (editor captions hidden there). Do it after the cuts. Refuses a moving camera or extreme close-up. ASYNC: job_wait gives overlayId, beats[].still (look at each), qc, warnings. Re-run replaces; reference/3d-captions.md.",
 		inputSchema: {
 			type: "object",
 			properties: {
@@ -6777,6 +6777,8 @@ Before an editing pass, read the skill's "Which tool for which moment" section (
 Report the real count each step returned. No music, intro/outro cards or FX overlays unless the recipe or the user asks for them.
 A single named operation ("just add captions", "remove the silences") is exactly that: no recipe.
 
+End every turn that changed a project with a plain summary: what changed (with the counts the tools returned), what you tried and put back or skipped and why, and what is left. Say so plainly when the work is only partly done or a step failed. To take a run back: agent_run_restore (works from inside your current turn), or the chat's Undo this run button.
+
 Destructive actions need the user's own confirmation: project_delete, workspace_delete, recipe_delete, memory_forget, export_delete, export_clear_thumbnail, youtube_disconnect, social_disconnect. Ask plainly in chat first ("Delete project 'Demo'? This can't be undone.") and call only after they agree. PandaStudio then confirms with them itself: in its own chat the call returns confirmation_required and changes nothing while a Delete / Cancel card waits (tell them to press it; don't call again; the outcome arrives as their next message); from other apps a dialog asks, and the call is refused when nobody is at the app. Nothing you send can approve it.
 
 Publishing has daily limits (YouTube uploads and updates per license, social posts per workspace, and PandaStudio's shared YouTube quota). A failure with code daily_limit or youtube_quota_exceeded carries resetsAt: tell the user when it resets and do not retry, loop or switch accounts to get around it before then. It is not a bug to report.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@writepanda/mcp",
-	"version": "1.225.0",
+	"version": "1.227.0",
 	"description": "Model Context Protocol server for PandaStudio. Exposes the desktop video editor's automation surface to Cursor, Continue, Cline, Claude Desktop, and any MCP-compliant client.",
 	"keywords": [
 		"pandastudio",