Skip to content

The open-source full-stack studio for Opus 5.5 motion video. Reverse engineering for any video. Code video with HTML: recreate, edit and render. BYOA + BYOK · Motion.md · Images, Video, Music & Voice.

fix(skills): rewind preview after playback verification

罗高9effb6ca4266
diff --git a/skills/openmotion-production/references/native.md b/skills/openmotion-production/references/native.md
index c39ea8ac..cd857a64 100644
--- a/skills/openmotion-production/references/native.md
+++ b/skills/openmotion-production/references/native.md
@@ -18,6 +18,8 @@ The first output of original creation, reference-video recreation and editable-t
First delivery must complete steps 1–5 under [Continuing edits](#continuing-edits) too: preparing the preview is only the first step. Hidden-tab playback, screenshots, `markDeliverable()` and a completed MP4 export do not prove editor delivery. Before finishing, either confirm the native panel is visible with the latest content, or state the specific display failure/deferred status and give the project URL. Do not silently replace the editor with files.
+After verifying playback, pause the preview first, then seek to 0 seconds (`seek(0)`) through the host's supported preview controls. Before recording display confirmation or delivering the editor, observe that the playhead is at the start and playback remains paused. This applies to first delivery, unchanged first-run templates and continued edits; do not leave the preview playing or parked on a middle/end frame. An explicit user request for another playback state takes precedence. If the controls or resulting state cannot be verified, report that limitation instead of claiming the reset succeeded.
+
The Tool runs lint and selects an existing project in Studio; it does not create a project or open the host browser. Preserve the URL's embed/query/hash, verify that the intended project and current content loaded, and reuse its browser tab on continued work. If lint fails, fix the reported source problem before retrying. If preview or browser capability is unavailable, provide the project URL when available and state the concrete gap; report the page as opened only after observing it. Do not substitute the system `open` command, AppleScript or a separately launched visible browser for the host's browser. For an independent folder/ZIP, use a supported managed-project handoff if available; the public MCP has no general folder/ZIP adoption Tool. Preserve the actual source and report that limitation rather than opening an unrelated carrier.
Preview preflight, export preflight and the OpenMotion command `node <runtimeRoot>/scripts/lint-project.mjs <runtimeRoot> <projectDirectory>` use the native linter with `host: "studio"`. Structural errors therefore fail before the editor is opened or rendering begins; ordinary warnings remain non-blocking. A direct upstream `hyperframes lint` still uses its own CLI warning policy and is not proof that Studio will accept a project.
diff --git a/skills/openmotion-template-to-video/SKILL.md b/skills/openmotion-template-to-video/SKILL.md
index 450c4f65..78df8534 100644
--- a/skills/openmotion-template-to-video/SKILL.md
+++ b/skills/openmotion-template-to-video/SKILL.md
@@ -47,6 +47,8 @@ Once this turn's requested HTML is ready, complete the [editable preview handoff
For an unchanged request, confirm in the editor that the intended template loaded and plays; unless the user asks for a video file, do not render, export or compare it. For an edited request, play the changed content and its related motion and sound in the editor preview; native snapshots help with layout but do not show motion. Do not export unless the user asks for a video file, then verify that actual MP4.
+After the playback check, complete the shared [editable preview handoff](../openmotion-production/references/native.md#editable-preview-handoff): pause, seek to 0 seconds, and verify the editor remains paused at the start before delivery.
+
For an edited request, inspect the requested content, its related layout/timing and unchanged sections against the template's `preview.mp4`. Verify that supplied replacement assets are actually used and old brand content does not remain at another relevant appearance. Record passed, failed and unrun checks separately in the copy's `TEMPLATE.md`. The project open in the editor is the deliverable. Do not copy, link or attach MP4s or other files unless the user asks for them; save requested files in the current workspace and link them by absolute local path, with only the plain path in each link target. For the editable Studio page, use the exact previewUrl from the handoff. Keep the reply short and in the user's words: one or two sentences on what changed and only the limitations the user would notice. For an unchanged request, use one completion sentence; the editable page remains open in the host. An accepted first-run experience follows the [first-run delivery and contextual invitation](../openmotion-production/references/templates.md#first-run-experience-defaults), including its limited exceptions, instead of adding project screenshots or technical evidence. Humans decide visual acceptance; do not give a subjective pass/fail verdict. Do not claim independent-agent verification unless a separate session actually performed it.
For edited or freshly rendered requests, apply the relevant [review standards](../openmotion-director/references/motion-review.md); changed multi-scene relationships use [production decisions](../openmotion-director/references/production-decisions.md), and sound changes load the shared context's sound references. These standards do not restart original creative intake or impose a new style on the template. For a fresh managed export, follow [verification](../openmotion-production/references/verification.md) using the completed job/revision; reuse a matching existing job. Without a request for a video file, create no export job. Stop at the user's requested delivery stage; a draft or review-only request does not automatically render.