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.
TypeScript agent-skillsagentic-aiai-agentsai-videobyokclaude-codecodexdeepseek-harnessdsh-plugingenerative-ailocal-firstmcpmotionmotion-graphicsmultimodalopenmotionreverse-engineeringvideo-editingvideo-generationworkbuddy
docs: clarify release control ownership and pending activation
luogaobfc3b0f63d3b
diff --git a/AGENTS.md b/AGENTS.mdindex 7d102196..965372a4 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -6,12 +6,20 @@ This version has breaking changes — APIs, conventions, and file structure may## Workspace Shape-- Root is the public harness boundary only: workspace metadata, `.github/workflows/ci.yml`, `scripts/guard.ts`, and repository docs.+- Root is the public harness boundary: workspace metadata, repository workflows, release-control helpers and tests, `scripts/guard.ts`, and repository docs.+- `.github/scripts/` owns Motion release controls; `scripts/*.mjs` supplies their shared helpers, and `tests/` holds their deterministic tests. Browser tests remain under `e2e/`.- `next/` owns the complete Next application: app routes, components, app libraries, public assets, Next config, app TypeScript config, and app unit tests.- `e2e/` owns browser-level tests as the only source of truth: Playwright config, e2e TypeScript config, helper scripts, and flat `ui/*.test.ts` cases.- Do not add Playwright tests under `next/`. Do not add app source back at root `src/` or root `app/`.- Root `package.json` must not proxy app or e2e scripts. Use pnpm workspace filters from the repository root.+## Motion release controls++- Motion application development remains on `feature/motion`. Registering manual workflows on `main` does not move the application or authorize publication.+- After registration is merged, manual release jobs execute the trusted controls from `main` and select integrated application source from `feature/motion`. Before registration, those manual entries are not available on the default branch.+- Use Node 26.11.1 for control checks: `node --test tests/release-workflows.test.mjs tests/release-scan.test.mjs tests/install-guide.test.ts`. These tests need no workspace dependency installation and simulate publication services.+- Follow [activation and operation](docs/motion-release-activation.md). Keep completed acceptance evidence private; do not merge or publish without the task's explicit authorization.+## Commands- Install: `pnpm install --frozen-lockfile`diff --git a/docs/motion-release-activation.md b/docs/motion-release-activation.mdindex 942140a3..68cdd91b 100644--- a/docs/motion-release-activation.md+++ b/docs/motion-release-activation.md@@ -1,12 +1,12 @@# Motion release controls on the legacy default branch-This branch retains the legacy HTML Anything application. The Motion application still lives at the root of `feature/motion`. These additions register manual Actions entries on the default branch; they do not replace the application, change package/workspace metadata, merge Motion into main, or publish anything on a push/merge.+This branch retains the legacy HTML Anything application. The Motion application still lives at the root of `feature/motion`. Registration takes effect only after this PR is merged into `main`; until then, its manual entries are not available on the default branch. These additions do not replace the application, change package/workspace metadata, merge Motion into main, or publish anything on a push/merge.## Scope and provenance-The three manual workflows, their runtime helpers, installation/acceptance templates and deterministic tests are copied without modification from reviewed PR [#214](https://github.com/nexu-io/html-anything/pull/214), source commit `de45dadea282214762c7b3123cea7e6b1044f26f`. No private Git history or application files are imported. The extra `Motion release controls` CI job runs only syntax checks and simulated-service tests with read-only permissions; the legacy CI commands and permissions are preserved. Its runner is pinned to Ubuntu 24.04 because the locked Playwright cannot install browsers on the Ubuntu 26.04 image now selected by ubuntu-latest.+The three manual workflows, their runtime helpers, installation/acceptance templates and deterministic tests are copied without modification from reviewed PR [#214](https://github.com/nexu-io/html-anything/pull/214), source commit `de45dadea282214762c7b3123cea7e6b1044f26f`. No application business logic or private Git history is imported; shared runtime helpers and tests are included as control dependencies. The extra `Motion release controls` CI job runs only syntax checks and simulated-service tests with read-only permissions; the legacy CI commands and permissions are preserved. Its runner is pinned to Ubuntu 24.04 because the locked Playwright cannot install browsers on the Ubuntu 26.04 image now selected by ubuntu-latest.-GitHub requires a manual workflow to exist on the default branch before its Run workflow entry is available. Our controls additionally require execution from `main`; they fetch the Motion application from a reviewed commit integrated into `feature/motion`. See [GitHub manual workflows](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manually-run-a-workflow).+GitHub requires a manual workflow to exist on the default branch before its Run workflow entry is available. After registration, our controls additionally require execution from `main`; they fetch the Motion application from a reviewed commit integrated into `feature/motion`. See [GitHub manual workflows](https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manually-run-a-workflow).## Activation order@@ -30,7 +30,7 @@ Before npm publication, use the candidate's **local** `candidate-install.md`, no- Registration is a capability change: users who can dispatch the trusted publication workflow can confirm and start a public release. There is no independent approval gate at this stage. Protect workflow edits and restrict operational access; the operator confirmation records intent, not proof of private testing.- Builds do not publish. The publication form defaults acceptance to false and rejects missing, expired, ambiguous or untrusted candidates, changed bytes and unintegrated source. Do not rebuild a published version or guess among duplicate candidate artifacts.- npm publication cannot be rolled back atomically with later checks. If native verification or R2 upload fails, npm may already be public while the default guide stays unchanged. Inspect retained records before using Re-run failed jobs; those retries reuse successful producer artifact IDs and never rebuild the candidate.-- Motion snapshot recovery is maintenance only: an exact already published identical version is required; no build, npm publication, tag movement or default-guide access is allowed. Channel rollback and client/data recovery require separate decisions.+- Motion snapshot recovery writes versioned R2 snapshots for an already published identical npm package; it does not build, publish npm, move tags or access the default guide. Channel rollback and client/data recovery require separate decisions.- A single publication concurrency group and version/ETag checks protect channel promotion. Operate one release at a time; GitHub does not provide a durable FIFO queue.- Disabling/removing these workflow registrations later does not undo a published npm version, restore user projects or revoke npm trust. Those are separate operations.