known-errors

# Known Errors `edit_item` update raw shape: - Wrong: `{ "id": "abc", "fromFrame": 30 }` - Right: `{ "json": "{\"updates\":[{\"id\":\"abc\",\"fromFrame\":30}]}" }` - Use this same `updates` shape for common moves, trims, and track changes. `edit_item` add raw shape: - The new item goes inside the `adds` array of the `json` transaction: `{ "json": "{\"adds\":[{...}]}" }`. - Use `edit_item` for simple video placement, for example `{ "json": "{\"adds\":[{\"type\":\"video\",\"assetId\":\"...\",\"fromFrame\":0}]}" }`. Timeline overlap: - Error text: `Overlap: updated item at ... would overlap existing item at ... on this track.` - Do not force the write or delete the conflicting item silently. - Retry the `edit_item` transaction with an explicit available `trackId`, for example an update containing `"trackId":"V2"`, or ask the user which layer should win. Workspace path restrictions: - `push_asset` on the external MCP only accepts public http(s) URLs as `filePath`. It rejects local paths, workspace paths, and chat attachment paths. - For motion-graphic assets, pass the JSX source via `create_motion_graphic_from_code({ code:"...", name, width, height, durationInFrames })`. `push_asset` no longer accepts an inline `code` argument. - Copying local media into the workspace is not the fix for video/audio/image/GIF imports; use `asset-import` and `import_media` instead. - Use `import_media action=create_session`, then run the OpenChatCut media import helper once with the returne...