Export the package

1. Resolve the project folder (absolute). It must have been rendered; otherwise offer the render skill.

2. Call mcp__plugin_video-studio_engine__export {project_dir} (optionally quality: "final" or "preview"; default is the latest render). Add sign: true when the user wants content credentials (C2PA) or an AI disclosure in the files themselves.

   • It signs reel.mp4, clean-master.mp4 and every dist/<target>/video.mp4 with the local c2patool.
   • The manifest says the video was created by video-studio, gives its title, and has an IPTC digital source type. The type is compositeWithTrainedAlgorithmicMedia when any part was made by a model, which includes synthesized voice even from the system TTS, and digitalCreation otherwise.
   • result.dist.c2pa lists the signed files and ai_generated.
   • With certificate: "test", c2patool's built-in test certificate signed the files. Say that validators show such credentials as untrusted until the user configures their own signer in c2patool's settings.
   • Without c2patool the export still succeeds, unsigned, and result.dist.warnings says how to install it.
   • Signing changes the files, so an export without sign produces unsigned files again.

   Add timeline: ["fcpxml", "otio"] (or just one) when the user wants to keep editing in an editor (DaVinci Resolve, Final Cut Pro, anything that reads OpenTimelineIO).

   • It recreates dist/timeline/: media/ (the scene clips, audio.wav = the final mix, captions.srt), project.fcpxml (FCPXML 1.10), project.otio and a README.md with the import steps.
   • Scenes sit back to back at the reel's exact frame bounds. Transitions are markers on the incoming clip (the blend itself is not rebuilt). Captions are an SRT sidecar to import separately.
   • result.timeline.warnings names clips that were conformed (a clip shorter than its slot gets its last frame held, as in the reel).
   • The format is import-tested (a real import succeeded on 2026-09-27); still ask the user to check clips and audio after importing, and point them at dist/timeline/README.md.
   • An export without timeline leaves an older dist/timeline/ in place; re-export with timeline after a re-render.
3. List the packages in one short block: for each result.dist.targets[], dist/<id>/ with its files, the video size and fps, whether it was re-encoded (transcode_reasons), and its qa.json status. Then the shared files (reel.mp4, clean-master.mp4, video-spec.json, storyboard.md, render-manifest.json, provenance.json; cover.jpg and cover-square-preview.jpg when the spec has a cover). Any target whose qa.json has errors: list them with their fixes and offer the lint skill's fix loop.
4. Read the brief (project/creative-brief.yaml), then refine the post copy per target. Each dist/<target>/post.json has the copy for that platform (source: "generated" is a deterministic draft) and its limits. Write the refined copy into project/video-spec.json as publish.<target> {post_caption, hashtags, ai_disclosure} (brief's tone, the desired action, 3-6 relevant hashtags, claims only from the sources, within limits), then run export again so every post.json picks it up. Editing the spec is durable; dist/ files are regenerated on each export.