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.

Align migration notes with manual publication prerequisites

luogaode45dadea282
diff --git a/docs/release-guide.md b/docs/release-guide.md
index fde1780f..fb0c713c 100644
--- a/docs/release-guide.md
+++ b/docs/release-guide.md
@@ -70,4 +70,4 @@ The short test/stable version URL contract and historical `/versions/` URLs rema
The configured destination bucket is `open-design-releases` and the public origin is `https://releases.open-design.ai`. After stable publication, the website can give the Agent a short prompt: "Read `https://releases.open-design.ai/open-motion/install.md`, install OpenMotion MCP and Skills for my current supported Agent host, preserve existing projects/settings, and report installation and preparation results." Use `https://releases.open-design.ai/open-motion/dev/install.md` for the test software channel. The test guide now pins `@openmotion/[email protected]`, with an immutable copy at `open-motion/dev/0.6.4-test.6/install.md`; both canonical public URLs were verified byte-for-byte against guide SHA256 `4b6f6b25c782c23d5529d225c6c0506d524b245a242f54d84fbf8d4dd61f4f05` after the [upload run](https://github.com/nexu-io/html-anything/actions/runs/42633147999). The short test.6 URL was added by [run 42638072025](https://github.com/nexu-io/html-anything/actions/runs/42638072025), with the same verified bytes as the retained legacy `/versions/0.6.4-test.6/install.md` URL. The older test.5 and test.4 immutable instructions remain unchanged; test.4 records the historical `@open-design/motion` name. Their existence does not imply those old npm versions were published. The stable entry is untouched and currently returns HTTP 404. Guide publication and npm publication remain separate operations.
-The new entries require separate trusted default-branch registration, npm trusted-publisher setup before use. Those administrative steps are not performed by this feature PR. Existing R2 credentials are reused only in the final snapshot job. No workflow was dispatched or package published as part of implementing these controls. See [setup, records and recovery](release-workflows.md).
+The new entries require separate trusted default-branch registration and npm trusted-publisher setup before use. Those administrative steps are not performed by this feature PR. Existing R2 credentials are reused only in the final snapshot job. No workflow was dispatched or package published as part of implementing these controls. See [setup, records and recovery](release-workflows.md).
diff --git a/docs/repository-migration.md b/docs/repository-migration.md
index 48d2feac..acafc170 100644
--- a/docs/repository-migration.md
+++ b/docs/repository-migration.md
@@ -43,6 +43,6 @@ Upstream Studio/template attribution and font notices remain intact. Motion remo
## CI and acceptance
-`.github/workflows/ci.yml` installs locked dependencies, checks/builds Studio, runs focused packaging/workflow/recreation tests and Studio regression, and exercises the phase-one ZIP through all eleven public Tools (nine project Tools and two catalog Tools). npm is the default manual artifact format; complete Mac/Windows ZIP assembly remains available. This CI workflow rejects publication and retains a candidate installation-guide preview for review; it does not publish npm/R2/Release artifacts or merge PRs. Separate manual [candidate and test publication controls](release-workflows.md) retain complete candidates and publish only after explicit authorization and their documented default-branch, environment and npm-trust prerequisites are configured.
+`.github/workflows/ci.yml` installs locked dependencies, checks/builds Studio, runs focused packaging/workflow/recreation tests and Studio regression, and exercises the phase-one ZIP through all eleven public Tools (nine project Tools and two catalog Tools). npm is the default manual artifact format; complete Mac/Windows ZIP assembly remains available. This CI workflow rejects publication and retains a candidate installation-guide preview for review; it does not publish npm/R2/Release artifacts or merge PRs. Separate manual [candidate and test publication controls](release-workflows.md) retain complete candidates and publish only after explicit authorization and their documented default-branch and npm-trust prerequisites are configured.
Build success does not prove target-machine installation, loaded host Skills/MCP, model creation or visual acceptance. Validate exact artifacts independently, using isolated profiles. Current platform limits and instructions are in [test packages](test-packages.md).