known-errors

1# Known Errors
2 
3Treat the active MCP tool schema and returned structured error as authoritative. Do not retry with remembered legacy payloads when the current manifest differs.
4 
5## Mutation Rejections
6 
7- On same-track overlap, do not force the write or silently delete the conflicting item. Decide whether content is sequential or layered, choose an available track when appropriate, or ask which item should win.
8- On locked-track or stale-id failures, refresh the affected timeline scope and retry only with current ids and state.
9- On validation errors, change only the rejected field or transaction shape; preserve unrelated project state.
10 
11## Import And Media
12 
13- Hosted plugin surfaces use the `asset-import` adapter and `import_media`; do not substitute backend-only `push_asset` or `download_media` calls when they are absent.
14- If media conversion fails, use the helper's structured retry when provided. Otherwise explain the unsupported source and ask for a compatible replacement; do not repeat the same failing editor import path.
15- Wait for upload only before byte-dependent operations. A known asset id can be used for metadata and timeline placement while bytes continue uploading.
16 
17## Generation And Motion Graphics
18 
19- Use only generation tools visible on the current host. Codex, Claude Code and Antigravity plugins direct-author Motion Graphics with `create_motion_graphic_from_code`; the built-in ChatCut Agent may expose `submit_motion_graphic`.
20…