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
fix(release): remove manual acceptance checkbox
lefarcendcd5d16f1e96
diff --git a/.github/scripts/motion-release.mjs b/.github/scripts/motion-release.mjsindex ce070a8b..6f5fa06c 100644--- a/.github/scripts/motion-release.mjs+++ b/.github/scripts/motion-release.mjs@@ -35,9 +35,8 @@ export function releaseInputs(env = process.env) {const workflow = env.GITHUB_WORKFLOW_REF;if (workflow.includes(recoveryWorkflow)) assert.equal(env.MOTION_RELEASE_ACTION, 'archive-only', 'Recovery never publishes or moves a channel');if (env.MOTION_EXPECTED_SHA256) assert.match(env.MOTION_EXPECTED_SHA256, hashPattern);- assert.equal(env.MOTION_ACCEPTED, 'true', 'Explicit operator acceptance confirmation is required');checkReleaseVersion(env.MOTION_VERSION); assert(env.MOTION_VERSION.includes('-test.'), 'Only test versions may use this entry');- return { action: env.MOTION_RELEASE_ACTION, accepted: true, version: env.MOTION_VERSION, expectedSHA256: env.MOTION_EXPECTED_SHA256 };+ return { action: env.MOTION_RELEASE_ACTION, version: env.MOTION_VERSION, expectedSHA256: env.MOTION_EXPECTED_SHA256 };}export async function resolveCandidate(control, requested, version, env = process.env, run = runFile) {@@ -122,9 +121,9 @@ async function github(route, fetcher = fetch) {export function authorizationReceipt(candidate, run, action, observedAt = new Date().toISOString()) {const actor = run.triggering_actor?.login || run.actor?.login;assert(typeof actor === 'string' && actor.length > 0, 'Require the actual publication operator');- return { schemaVersion: 1, type: 'manual-workflow-dispatch', publicationRun: run.id, runAttempt: run.run_attempt,+ return { schemaVersion: 2, type: 'manual-workflow-dispatch', publicationRun: run.id, runAttempt: run.run_attempt,action, version: candidate.version, tgzSHA256: candidate.tgzSHA256, candidateRun: candidate.workflow,- actor, acceptanceConfirmed: true, observedAt };+ actor, observedAt };}export async function recordAuthorization(directory, inputs, fetcher = fetch, env = process.env) {@@ -140,8 +139,8 @@ export async function recordAuthorization(directory, inputs, fetcher = fetch, enasync function verifyAuthorization(directory, inputs, env = process.env) {const candidate = await verifyDownloaded(directory, inputs.expectedSHA256, inputs.version), authorization = await json(path.join(directory, 'authorization.json'));- assert.equal(inputs.accepted, true); assert.equal(authorization.schemaVersion, 1);- assert.equal(authorization.type, 'manual-workflow-dispatch'); assert.equal(authorization.acceptanceConfirmed, true);+ assert.equal(authorization.schemaVersion, 2);+ assert.equal(authorization.type, 'manual-workflow-dispatch');assert.equal(authorization.version, candidate.version); assert.equal(authorization.tgzSHA256, candidate.tgzSHA256);assert.equal(authorization.action, inputs.action); assert.deepEqual(authorization.candidateRun, candidate.workflow);assert.equal(String(authorization.publicationRun), env.GITHUB_RUN_ID, 'Authorization belongs to another publication run');diff --git a/.github/workflows/motion-candidate.yml b/.github/workflows/motion-candidate.ymlindex 2035deba..b50bda34 100644--- a/.github/workflows/motion-candidate.yml+++ b/.github/workflows/motion-candidate.yml@@ -126,5 +126,5 @@ jobs:import { readFileSync, appendFileSync } from 'node:fs';const c = JSON.parse(readFileSync(process.env.RUNNER_TEMP + '/candidate/candidate.json'));const run = `https://github.com/${process.env.GITHUB_REPOSITORY}/actions/runs/${process.env.GITHUB_RUN_ID}`;- appendFileSync(process.env.GITHUB_STEP_SUMMARY, `## Candidate ready for acceptance\n\nVersion: ${c.version}\n\nSource: ${c.sourceCommit}\n\nTGZ SHA256: ${c.tgzSHA256}\n\n[Download motion-candidate-${c.version}](${run}#artifacts), extract it and give the folder to your Agent with this instruction:\n\n> Follow candidate-install.md in this folder to install this exact local candidate into an isolated test profile, application home, project data and Skills directory. Complete prepare and verify host loading. Record requested template/edit/export acceptance results in a private copy of acceptance.md; mark unrun checks NOT RUN. Do not publish.\n\nUse candidate-install.md before publication, not the sibling registry install.md. After acceptance, manually open Motion test publication, enter ${c.version} and confirm acceptance. Nothing was published by this build.\n`);+ appendFileSync(process.env.GITHUB_STEP_SUMMARY, `## Candidate ready for acceptance\n\nVersion: ${c.version}\n\nSource: ${c.sourceCommit}\n\nTGZ SHA256: ${c.tgzSHA256}\n\n[Download motion-candidate-${c.version}](${run}#artifacts), extract it and give the folder to your Agent with this instruction:\n\n> Follow candidate-install.md in this folder to install this exact local candidate into an isolated test profile, application home, project data and Skills directory. Complete prepare and verify host loading. Record requested template/edit/export acceptance results in a private copy of acceptance.md; mark unrun checks NOT RUN. Do not publish.\n\nUse candidate-install.md before publication, not the sibling registry install.md. To publish, manually open Motion test publication and enter ${c.version}; no acceptance checkbox is required. Nothing was published by this build.\n`);JSdiff --git a/.github/workflows/motion-publication-recovery.yml b/.github/workflows/motion-publication-recovery.ymlindex 6463a0e3..f3da3976 100644--- a/.github/workflows/motion-publication-recovery.yml+++ b/.github/workflows/motion-publication-recovery.yml@@ -7,11 +7,6 @@ on:description: 'Exact existing candidate version; the identical package must already be public on npm'type: stringrequired: true- accepted:- description: 'I verified this exact candidate and authorize snapshot-only recovery'- type: boolean- required: true- default: falsepermissions:contents: read@@ -37,6 +32,5 @@ jobs:uses: ./.github/workflows/motion-publish-test.ymlwith:version: ${{ inputs.version }}- accepted: ${{ inputs.accepted }}archive_only: truesecrets: inheritdiff --git a/.github/workflows/motion-publish-test.yml b/.github/workflows/motion-publish-test.ymlindex fb20cfbb..d83a9dd0 100644--- a/.github/workflows/motion-publish-test.yml+++ b/.github/workflows/motion-publish-test.yml@@ -5,22 +5,14 @@ on:workflow_dispatch:inputs:version:- description: 'Exact accepted candidate version, e.g. 0.6.4-test.7; candidate identity is resolved automatically'+ description: 'Exact candidate version, e.g. 0.6.4-test.7; candidate identity is resolved automatically'type: stringrequired: true- accepted:- description: 'I completed the required acceptance for this exact candidate and authorize public test publication'- type: boolean- required: true- default: falseworkflow_call:inputs:version:type: stringrequired: true- accepted:- type: boolean- required: truearchive_only:type: booleanrequired: true@@ -35,7 +27,6 @@ concurrency:env:MOTION_VERSION: ${{ inputs.version }}- MOTION_ACCEPTED: ${{ inputs.accepted }}MOTION_RELEASE_ACTION: ${{ inputs.archive_only && 'archive-only' || 'publish-test' }}jobs:@@ -112,11 +103,11 @@ jobs:path: ${{ runner.temp }}/candidate- name: Use the pinned npm CLI with trusted dist-tag supportrun: npm install --global [email protected] --ignore-scripts --no-audit --no-fund- - name: Record explicit operator acceptance authorization+ - name: Record manual publication operatorenv:GH_TOKEN: ${{ github.token }}run: node .github/scripts/motion-release.mjs authorize "$RUNNER_TEMP/candidate"- - name: Publish the accepted bytes with npm trusted publishing, or verify an identical existing version+ - name: Publish the candidate bytes with npm trusted publishing, or verify an identical existing versionrun: node .github/scripts/motion-release.mjs npm "$RUNNER_TEMP/candidate"- name: Retain npm publication state even after a partial failureid: artifactdiff --git a/AGENTS.md b/AGENTS.mdindex 01344b6f..66f120ae 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -53,6 +53,6 @@ Phase one exposes eleven motion_ Tools (nine project tools plus catalog fetch an## Candidate and publication controls-Follow [the release workflow manual](docs/release-workflows.md): separate manual candidate-build and test-publication entries, plus snapshot-only recovery. Select `feature/motion` for all three entries; `main` only registers them and is rejected as an execution ref. Blank candidate versions use short workflow-counter `test.N` numbering; keep full run/source identities in the records. Download and accept the local tgz using candidate-install.md; keep completed acceptance.md private. The publication operator enters the accepted version and explicitly confirms acceptance, without manually copying hashes. No independent approval environment is enabled at this stage. Public candidates must use an exact reviewed source SHA integrated into `feature/motion`, a new test version and DEV template defaults. Scan tracked source plus the outer npm tgz and inner application; preserve the positive distribution list and licenses. Keep candidate, native registry installation, real Agent creation and human acceptance evidence separate.+Follow [the release workflow manual](docs/release-workflows.md): separate manual candidate-build and test-publication entries, plus snapshot-only recovery. Select `feature/motion` for all three entries; `main` only registers them and is rejected as an execution ref. Blank candidate versions use short workflow-counter `test.N` numbering; keep full run/source identities in the records. Use candidate-install.md for local testing and keep results private. The publication operator enters the exact version and starts the manual workflow; no acceptance checkbox or manual testing gate is required. Record failed and unrun checks honestly. No independent approval environment is enabled at this stage. Public candidates must use an exact reviewed source SHA integrated into `feature/motion`, a new test version and DEV template defaults. Scan tracked source plus the outer npm tgz and inner application; preserve the positive distribution list and licenses. Keep candidate, native registry installation, real Agent creation and human acceptance evidence separate.Publication uses the accepted candidate bytes, never a rebuild. Publish under `candidate` first; only the credential-isolated promotion job may move npm `test` after both matching DEV native reports pass. Stable publication, npm `latest` promotion and platform/marketplace Skills distribution are not implemented by these entries. Only the separately authorized manual test publication workflow may use npm OIDC or R2 credentials; validate candidate provenance and hashes first, archive immutable version records, and update the moving guide last. Archive-only work must not move tags or default entries. Never overwrite published versions, put private template payloads/internal acceptance material into public artifacts, or infer merge/publication authorization from green CI. Main registration, npm trust, main cutover and repository rename remain separate operations.diff --git a/CLAUDE.md b/CLAUDE.mdindex 97bc2a97..56ad32b3 100644--- a/CLAUDE.md+++ b/CLAUDE.md@@ -4,7 +4,7 @@ Read and follow [AGENTS.md](AGENTS.md) before working in this repository. It is## Candidate and publication controls-Follow [the release workflow manual](docs/release-workflows.md): separate manual candidate-build and test-publication entries, plus snapshot-only recovery. Select `feature/motion` for all three entries; `main` only registers them and is rejected as an execution ref. Blank candidate versions use short workflow-counter `test.N` numbering; keep full run/source identities in the records. Download and accept the local tgz using candidate-install.md; keep completed acceptance.md private. The publication operator enters the accepted version and explicitly confirms acceptance, without manually copying hashes. No independent approval environment is enabled at this stage. Public candidates must use an exact reviewed source SHA integrated into `feature/motion`, a new test version and DEV template defaults. Scan tracked source plus the outer npm tgz and inner application; preserve the positive distribution list and licenses. Keep candidate, native registry installation, real Agent creation and human acceptance evidence separate.+Follow [the release workflow manual](docs/release-workflows.md): separate manual candidate-build and test-publication entries, plus snapshot-only recovery. Select `feature/motion` for all three entries; `main` only registers them and is rejected as an execution ref. Blank candidate versions use short workflow-counter `test.N` numbering; keep full run/source identities in the records. Use candidate-install.md for local testing and keep results private. The publication operator enters the exact version and starts the manual workflow; no acceptance checkbox or manual testing gate is required. Record failed and unrun checks honestly. No independent approval environment is enabled at this stage. Public candidates must use an exact reviewed source SHA integrated into `feature/motion`, a new test version and DEV template defaults. Scan tracked source plus the outer npm tgz and inner application; preserve the positive distribution list and licenses. Keep candidate, native registry installation, real Agent creation and human acceptance evidence separate.Publication uses the accepted candidate bytes, never a rebuild. Publish under `candidate` first; only the credential-isolated promotion job may move npm `test` after both matching DEV native reports pass. Stable publication, npm `latest` promotion and platform/marketplace Skills distribution are not implemented by these entries. Only the separately authorized manual test publication workflow may use npm OIDC or R2 credentials; validate candidate provenance and hashes first, archive immutable version records, and update the moving guide last. Archive-only work must not move tags or default entries. Never overwrite published versions, put private template payloads/internal acceptance material into public artifacts, or infer merge/publication authorization from green CI. Main registration, npm trust, main cutover and repository rename remain separate operations.diff --git a/docs/product/architecture.md b/docs/product/architecture.mdindex 62bab929..78d52810 100644--- a/docs/product/architecture.md+++ b/docs/product/architecture.md@@ -266,7 +266,7 @@ Explicit test/DEV and stable/prod builds produce publishable artifact metadata w## 演进约束-The application npm format is the default; complete platform ZIPs are backups. Ordinary PR CI scans tracked source and both npm archive layers without publication credentials. Separate manual candidate-build and test-publication entries implement build → download/accept → publish. Candidate build, test publication and snapshot recovery run only from feature/motion; main registers their manual entries without aliasing Motion operations. The build freezes the selected dispatch commit (or an explicitly integrated source SHA) and automatically numbers an empty version as the next source patch plus short test.N using the candidate workflow counter with its historical offset, without rewriting the source baseline. Reruns add an attempt suffix; an explicit test-version override remains available. It builds one immutable DEV candidate and generates a local candidate-install.md plus an identity-filled acceptance checklist. Publication resolves a unique unexpired versioned artifact from a completed successful build, validates official ZIP/file hashes and source integration, and requires explicit operator acceptance. No independent approval environment is enabled; the manual operator receipt is not proof of private tests or independent review. The same tgz is published under npm candidate, checked anonymously on separate Mac/Windows runners, then promoted to test in an npm-OIDC-only job before archiving and conditionally advancing the default guide. Failed native checks leave test unchanged; the exact candidate version is already public. R2 failure after tag promotion can leave the guide on the earlier accepted version. Builds can continue during acceptance; publication-only serialization, version checks and ETag writes prevent late older candidates from rolling the moving entry backward. Snapshot-only recovery requires an existing identical npm version and does not move the default. DEV configuration is public; private template contents and credentials remain outside the artifacts. Stable publication is a separate authorized process. Trusted default-branch registration and npm OIDC setup remain separate prerequisites, not enabled by this feature PR. Build, native installation, real Agent creation and human playback remain separate evidence. See [release workflows](../release-workflows.md) and [package checks](../test-packages.md).+The application npm format is the default; complete platform ZIPs are backups. Ordinary PR CI scans tracked source and both npm archive layers without publication credentials. Separate manual candidate-build and test-publication entries implement build → optional local testing → manual publish. Candidate build, test publication and snapshot recovery run only from feature/motion; main registers their manual entries without aliasing Motion operations. The build freezes the selected dispatch commit (or an explicitly integrated source SHA) and automatically numbers an empty version as the next source patch plus short test.N using the candidate workflow counter with its historical offset, without rewriting the source baseline. Reruns add an attempt suffix; an explicit test-version override remains available. It builds one immutable DEV candidate and generates a local candidate-install.md plus an identity-filled acceptance checklist. Publication resolves a unique unexpired versioned artifact from a completed successful build, validates official ZIP/file hashes and source integration, and records the manual publication operator without requiring an acceptance checkbox. No independent approval environment is enabled; the manual operator receipt is not proof of private tests or independent review. The same tgz is published under npm candidate, checked anonymously on separate Mac/Windows runners, then promoted to test in an npm-OIDC-only job before archiving and conditionally advancing the default guide. Failed native checks leave test unchanged; the exact candidate version is already public. R2 failure after tag promotion can leave the guide on the earlier accepted version. Builds can continue during acceptance; publication-only serialization, version checks and ETag writes prevent late older candidates from rolling the moving entry backward. Snapshot-only recovery requires an existing identical npm version and does not move the default. DEV configuration is public; private template contents and credentials remain outside the artifacts. Stable publication is a separate authorized process. Trusted default-branch registration and npm OIDC setup remain separate prerequisites, not enabled by this feature PR. Build, native installation, real Agent creation and human playback remain separate evidence. See [release workflows](../release-workflows.md) and [package checks](../test-packages.md).Downstream publication jobs consume immutable producer artifact IDs retained across partial retries; native Mac and Windows jobs expose separate report identities. OIDC authenticates publication, but automatic npm provenance is disabled for prebuilt candidates because the publication workflow SHA differs from the application source. Candidate/manifest/hash records provide traceability without claiming a signed build attestation. Stable version construction and URL contracts exist; stable candidate/publication, npm latest promotion and Skills marketplace/platform publication are not implemented. The bundled Skills are installed into local hosts only.diff --git a/docs/release-guide.md b/docs/release-guide.mdindex 5763995e..b42d5acd 100644--- a/docs/release-guide.md+++ b/docs/release-guide.md@@ -18,7 +18,7 @@ Known limitations: the production Prism catalog returned HTTP 404. This candidat## Test candidate acceptance-Before any authorized publication to the npm `test` tag:+Recommended local checks before a test publication (not a manual workflow gate; record FAIL and NOT RUN honestly):1. Freeze a reviewed `feature/motion` commit. Run the required check/typecheck/Studio build, affected deterministic tests and current-head CI. Verify final package contents, public-boundary/secret scans, dependencies, licenses and disabled upstream telemetry.2. Build the **final tgz once** into a new directory. Check all identities and hashes. Copy only that tgz to a clean consumer directory; no application sidecar or source checkout may be required by setup.@@ -65,7 +65,7 @@ Each defect needs exact package/source/OS/host/environment/catalog identity, proOrdinary npm/DEV CI builds generate a **candidate-only** guide and retain it as an Actions artifact for 14 days. The publisher rejects candidate previews. Public guides require test/DEV or stable/prod identity; private builds cannot produce them.-Maintainers follow [build → download and accept → publish](release-workflows.md): first run Motion candidate build from `feature/motion` with version empty for automatic numbering (or an explicit new test version), download its frozen candidate and follow the included `candidate-install.md` to install the local tgz in an isolated host. Keep completed `acceptance.md` privately. After acceptance, run Motion test publication from `feature/motion` with that exact version and confirm acceptance. Candidate lookup and hashes are automatic; no independent approval environment is enabled. The same accepted bytes receive anonymous native registry checks and immutable snapshots before the moving test guide can advance. Snapshot-only recovery is a separate maintenance entry. The former CI guide-only upload route is removed so it cannot bypass these checks. Ordinary PR CI remains read-only.+Maintainers follow [build → download and accept → publish](release-workflows.md): first run Motion candidate build from `feature/motion` with version empty for automatic numbering (or an explicit new test version), download its frozen candidate and follow the included `candidate-install.md` to install the local tgz in an isolated host. Keep completed `acceptance.md` privately. Run Motion test publication from `feature/motion` with that exact version. Starting the manual workflow authorizes publication; no acceptance checkbox is required. Candidate lookup and hashes are automatic; no independent approval environment is enabled. The same accepted bytes receive anonymous native registry checks and immutable snapshots before the moving test guide can advance. Snapshot-only recovery is a separate maintenance entry. The former CI guide-only upload route is removed so it cannot bypass these checks. Ordinary PR CI remains read-only.These manual entries support test versions only. Stable package construction and the stable URL contract exist, but stable candidate/publication, npm `latest` promotion and Skills platform/marketplace distribution still require separate implementation and authorization. Bundling five Skills and registering them locally does not publish them to a platform. Partial retries retain the actual successful producer artifact IDs; automatic npm provenance is disabled for prebuilt candidates while OIDC authentication remains enabled. See the workflow manual for the source/hash evidence and recovery limits.diff --git a/docs/release-workflows.md b/docs/release-workflows.mdindex d8334ad9..84be2eeb 100644--- a/docs/release-workflows.md+++ b/docs/release-workflows.md@@ -1,14 +1,14 @@-# Motion test release: build, accept, publish+# Motion test release: build, test, publish-Use two manual Actions entries: **Motion candidate build**, then **Motion test publication** after acceptance. The daily flow is **build → download and accept → publish**. Neither entry runs on pushes, PR merges, tags or a schedule. The entries are registered on `main`; Motion application development stays on `feature/motion`. Merging a workflow change does not publish a package, configure npm permissions or switch the product main branch.+Use two manual Actions entries: **Motion candidate build**, then **Motion test publication**. The daily flow is **build → optional local testing → manual publish**. Neither entry runs on pushes, PR merges, tags or a schedule. The entries are registered on `main`; Motion application development stays on `feature/motion`. Merging a workflow change does not publish a package, configure npm permissions or switch the product main branch.| Operator step | Automated work || --- | --- || Build: select `feature/motion`, normally leave version empty | Freeze the current `feature/motion` SHA, check/build/scan once, retain the candidate and show download/install instructions |-| Download and accept | Use `candidate-install.md` and the local tgz in an isolated host; retain completed `acceptance.md` internally |-| Publish: enter the accepted version and confirm acceptance | Find the unique candidate automatically, verify its source/hashes, publish the same tgz under `candidate`, check native installations, then advance npm `test`, archive snapshots and update the default guide last |+| Optional local testing | Use `candidate-install.md` and the local tgz in an isolated host; retain completed `acceptance.md` internally |+| Publish: enter the exact candidate version | Find the unique candidate automatically, verify its source/hashes, publish the same tgz under `candidate`, check native installations, then advance npm `test`, archive snapshots and update the default guide last |-**No independent approval environment is enabled at this stage.** The publication checkbox is explicit authorization by the operator, not evidence of an independent review or proof that the tests happened. Anyone able to dispatch the trusted publication workflow can authorize publication; the team must control that access and keep the acceptance record. Adding a separate required reviewer later is a separate decision.+**No acceptance checkbox or manual testing gate is required.** Starting the trusted manual workflow authorizes the selected test publication. The operator receipt records who started it and the candidate identity; it does not claim human acceptance. Automated source, hash, scan and native installation checks remain mandatory.New public test packages use **DEV templates**; stable packages use prod. The `dev` URL path selects the test software channel, whose newly built packages now embed DEV configuration. Package visibility does not grant DEV network access or authorization; no private catalog snapshot or credential is embedded. Existing prod-based test versions are immutable and remain unchanged. Stable publication, npm `latest` promotion and Skills marketplace/platform upload are separate follow-ups; the five Skills are only included in the npm application and registered locally.@@ -63,13 +63,13 @@ The artifact contains nine files: `openmotion-app-<version>.tgz`, `release-npm.j3. Follow the actual supported host/platform isolation recipe in [npm installation](npm-installation.md). Setup and prepare must use the same explicit application home; `--home` alone does not isolate the host profile. The application is embedded: no source checkout or sidecar application/manifest download is needed. Native dependencies still need network access.4. Complete **`acceptance.md` privately** with PASS / FAIL / NOT RUN, supported OS/host, template/catalog identity, existing-data preservation, real Agent creation/edit/export, normal-speed human audio/video playback, known issues and recovery. [The acceptance guide](release-guide.md) defines the checks. Build success cannot fill human results.-Keep completed evidence against the generated candidate identity. Do not edit/re-upload the frozen candidate artifact or place private test results in public Actions artifacts. Stop on failed or incomplete required acceptance; code changes need a new candidate version. No run ID, tgz hash or private-record hash needs to be copied into the publication form.+Keep completed evidence against the generated candidate identity. Do not edit/re-upload the frozen candidate artifact or place private test results in public Actions artifacts. Record failed and unrun checks honestly; they are not a manual workflow gate. Code changes need a new candidate version. No run ID, tgz hash or private-record hash needs to be copied into the publication form.-## 3. Publish the accepted version+## 3. Publish the candidate version-Open **Actions → Motion test publication → Run workflow**, select **`feature/motion`**, enter the exact accepted **version**, and tick **accepted** only after its required acceptance passes. Click **Run workflow**. This is the explicit publication action; there is no later independent approval dialog. Leaving the checkbox false fails before any publication.+Open **Actions → Motion test publication → Run workflow**, select **`feature/motion`**, enter the exact candidate **version**, and click **Run workflow**. No acceptance checkbox or later independent approval dialog is required.-The workflow searches GitHub artifacts by the exact versioned name and requires exactly one unexpired match from a completed successful registered candidate build on `main` or `feature/motion` in this repository. Missing, ambiguous, expired or failed candidates stop instead of choosing a different run. Copy the exact version from the successful build summary. Entering `0.6.4-test.7` cannot rename an existing `0.6.4-test.42818506484.1` candidate: build `test.7` separately and accept its new bytes first. The official ZIP digest, frozen file hashes and source integration are checked; source and package scans run again. The current manual run's actual operator, candidate identity and acceptance confirmation are retained in `authorization.json`.+The workflow searches GitHub artifacts by the exact versioned name and requires exactly one unexpired match from a completed successful registered candidate build on `main` or `feature/motion` in this repository. Missing, ambiguous, expired or failed candidates stop instead of choosing a different run. Copy the exact version from the successful build summary. Entering `0.6.4-test.7` cannot rename an existing `0.6.4-test.42818506484.1` candidate: build `test.7` separately and accept its new bytes first. The official ZIP digest, frozen file hashes and source integration are checked; source and package scans run again. The current manual run's actual operator, candidate identity and publication action are retained in `authorization.json`.It then automatically:@@ -101,7 +101,7 @@ Actions artifacts and attempt records expire after **30 days**. R2 snapshots fol- Before clicking publish: building, downloading and testing publish nothing. Discard an unwanted candidate. Fix code under a new version when bytes change.- After clicking publish: the exact version and `candidate` tag are public even before native validation. A failed native check leaves `test` and the default guide unchanged. Once native checks and tag readback pass, `test` can advance before R2 finishes; if R2 fails it points to a verified version while the guide can remain on the previous version. npm and R2 are not one transaction. Inspect retained npm state and release-attempt/publication files; do not rebuild or blindly republish.- Use **Re-run failed jobs** for a partial publication failure. Consumers use successful producer artifact IDs rather than guessing their own attempt. Re-running publication reuses the existing candidate and original accepted version; it does not rebuild. A candidate build rerun is different: a successful new artifact must be accepted again, and duplicate version artifacts block publication.-- **Motion snapshot recovery** is a separate maintenance entry. Select `feature/motion`, enter the existing candidate version and confirm snapshot-only recovery. It requires an already published identical npm version, repeats native checks and fills missing immutable snapshots. It never builds, publishes npm, moves npm tags or accesses the moving guide. Missing/expired/ambiguous candidates stop.+- **Motion snapshot recovery** is a separate maintenance entry. Select `feature/motion`, enter the existing candidate version and start snapshot-only recovery. It requires an already published identical npm version, repeats native checks and fills missing immutable snapshots. It never builds, publishes npm, moves npm tags or accesses the moving guide. Missing/expired/ambiguous candidates stop.- Version writes use conditional create and byte comparison. Same bytes resume; different immutable bytes stop. A public readback error blocks promotion. A failure after `fixed-write-attempted` may mean the moving write completed: inspect storage and its canonical URL before retrying.- An unexpected npm `latest` change stops promotion. This workflow does not silently repair tags. Channel rollback is a separate reviewed operation and does not downgrade installed clients or restore their data.@@ -111,4 +111,4 @@ Source/package scans are not a scan of every historical Git object or business cRun the repository's release/scanner/guide tests and actionlint. The no-publication rehearsal uses temporary candidate files and simulated GitHub/npm/R2 responses to test the transition and failure cases. It does **not** exercise npm OIDC, hosted native installation or CDN routing.-After separately authorized default-branch/npm setup, build a new candidate and verify that building alone publishes nothing. A publication dispatch with acceptance unchecked must fail closed. A positive hosted publication rehearsal is a real publication and needs explicit release authorization. Ordinary PR CI remains credential-free. This implementation PR enables none of those administrative actions by itself.+After separately authorized default-branch/npm setup, build a new candidate and verify that building alone publishes nothing. A publication dispatch requires only the exact candidate version; automated validation failures must still stop promotion. A positive hosted publication rehearsal is a real publication and needs explicit release authorization. Ordinary PR CI remains credential-free. This implementation PR enables none of those administrative actions by itself.diff --git a/tests/release-fixture.mjs b/tests/release-fixture.mjsindex c354dccc..9ef66958 100644--- a/tests/release-fixture.mjs+++ b/tests/release-fixture.mjs@@ -32,10 +32,10 @@ export async function candidateFixture(t, branch = 'main') {const candidate = await sealCandidate(build, directory, root, env);const provenance = { head_branch: branch, head_sha: env.GITHUB_SHA, runId: 123, attempt: 1 };await writeJSON(path.join(directory, 'provenance.json'), provenance);- const inputs = { action: 'publish-test', version, accepted: true, expectedSHA256: candidate.tgzSHA256 };+ const inputs = { action: 'publish-test', version, expectedSHA256: candidate.tgzSHA256 };const publicationEnv = { GITHUB_REPOSITORY: repository, GITHUB_EVENT_NAME: 'workflow_dispatch', GITHUB_REF: 'refs/heads/feature/motion',GITHUB_RUN_ID: '800', GITHUB_SHA: env.GITHUB_SHA, GITHUB_WORKFLOW_REF: `${repository}/${publicationWorkflow}@refs/heads/feature/motion`,- MOTION_VERSION: version, MOTION_ACCEPTED: 'true', MOTION_RELEASE_ACTION: 'publish-test' };+ MOTION_VERSION: version, MOTION_RELEASE_ACTION: 'publish-test' };const authorization = authorizationReceipt(candidate, { id: 800, run_attempt: 1, actor: { login: 'operator' } }, inputs.action);await writeJSON(path.join(directory, 'authorization.json'), authorization);for (const platform of ['darwin-arm64', 'win32-x64']) await writeJSON(path.join(directory, `registry-${platform}.json`), {diff --git a/tests/release-workflows.test.mjs b/tests/release-workflows.test.mjsindex ef1f0b54..4a190988 100644--- a/tests/release-workflows.test.mjs+++ b/tests/release-workflows.test.mjs@@ -13,12 +13,12 @@ import { runFile } from '../scripts/runtime-assets.mjs';const config = { endpoint: 'https://example.r2.cloudflarestorage.com', bucket: 'example-releases', publicOrigin: 'https://download.example.invalid' };const valid = { GITHUB_REPOSITORY: repository, GITHUB_EVENT_NAME: 'workflow_dispatch', GITHUB_REF: 'refs/heads/feature/motion',- GITHUB_WORKFLOW_REF: `${repository}/${publicationWorkflow}@refs/heads/feature/motion`, MOTION_VERSION: '0.6.4-test.99', MOTION_ACCEPTED: 'true', MOTION_RELEASE_ACTION: 'publish-test', MOTION_EXPECTED_SHA256: 'a'.repeat(64) };+ GITHUB_WORKFLOW_REF: `${repository}/${publicationWorkflow}@refs/heads/feature/motion`, MOTION_VERSION: '0.6.4-test.99', MOTION_RELEASE_ACTION: 'publish-test', MOTION_EXPECTED_SHA256: 'a'.repeat(64) };const origin = { id: 123, run_attempt: 1, event: 'workflow_dispatch', head_branch: 'main', head_repository: { full_name: repository }, status: 'completed', conclusion: 'success', path: candidateWorkflow, head_sha: 'b'.repeat(40) };const artifact = { id: 456, name: 'motion-candidate-0.6.4-test.99', workflow_run: { id: 123 }, expired: false, size_in_bytes: 100, digest: 'sha256:' + 'a'.repeat(64) };test('manual entry and source selection reject untrusted callers, mutable refs and non-test versions', async () => {assert.equal(releaseInputs(valid).action, 'publish-test');- for (const [key, value] of Object.entries({ GITHUB_REPOSITORY: 'fork/repo', GITHUB_EVENT_NAME: 'push', GITHUB_REF: 'refs/heads/main', GITHUB_WORKFLOW_REF: `${repository}/evil.yml@refs/heads/feature/motion`, MOTION_EXPECTED_SHA256: 'bad', MOTION_ACCEPTED: 'false', MOTION_VERSION: '0.6.4', MOTION_RELEASE_ACTION: 'stable' })) assert.throws(() => releaseInputs({ ...valid, [key]: value }));+ for (const [key, value] of Object.entries({ GITHUB_REPOSITORY: 'fork/repo', GITHUB_EVENT_NAME: 'push', GITHUB_REF: 'refs/heads/main', GITHUB_WORKFLOW_REF: `${repository}/evil.yml@refs/heads/feature/motion`, MOTION_EXPECTED_SHA256: 'bad', MOTION_VERSION: '0.6.4', MOTION_RELEASE_ACTION: 'stable' })) assert.throws(() => releaseInputs({ ...valid, [key]: value }));const recovery = { ...valid, GITHUB_WORKFLOW_REF: `${repository}/${recoveryWorkflow}@refs/heads/feature/motion` };assert.throws(() => releaseInputs(recovery), /Recovery/);assert.equal(releaseInputs({ ...recovery, MOTION_RELEASE_ACTION: 'archive-only' }).action, 'archive-only');@@ -88,7 +88,7 @@ test('version lookup uses the exact artifact name and rejects missing, expired,await assert.rejects(findCandidate('0.6.4-test.99', async () => Response.json({ total_count: 101, artifacts: [artifact] })), /incomplete/);});-test('operator authorization requires explicit acceptance and records the actual manual caller without independent approval', async t => {+test('operator authorization records the actual manual caller without independent approval', async t => {const f = await candidateFixture(t);const run = { ...origin, head_branch: 'feature/motion', id: 800, path: publicationWorkflow, actor: { login: 'operator' }, triggering_actor: { login: 'rerunner' } };assert.equal(authorizationReceipt(f.candidate, run, 'publish-test').actor, 'rerunner');@@ -97,8 +97,7 @@ test('operator authorization requires explicit acceptance and records the actualawait recordAuthorization(f.directory, f.inputs, fetcher, f.env);const record = JSON.parse(await readFile(path.join(f.directory, 'authorization.json')));assert.equal(record.publicationRun, 800); assert.equal(record.tgzSHA256, f.candidate.tgzSHA256);- assert.equal(record.actor, 'rerunner'); assert.equal(record.acceptanceConfirmed, true);- await assert.rejects(recordAuthorization(f.directory, f.inputs, fetcher, { ...f.env, MOTION_ACCEPTED: 'false' }), /acceptance/);+ assert.equal(record.actor, 'rerunner'); assert.equal(record.schemaVersion, 2); assert(!Object.hasOwn(record, 'acceptanceConfirmed'));for (const patch of [{ id: 801 }, { event: 'push' }, { head_branch: 'main' }, { head_sha: 'f'.repeat(40) }, { path: candidateWorkflow }, { head_repository: { full_name: 'fork/repo' } }]) {await assert.rejects(recordAuthorization(f.directory, f.inputs, async () => Response.json({ ...run, ...patch }), f.env));}@@ -286,14 +285,14 @@ test('daily build and publication are separate manual entries without an indepenassert(build.includes('MOTION_VERSION: ${{ steps.source.outputs.version }}'));assert(build.includes('name: motion-candidate-${{ steps.source.outputs.version }}') && build.includes('candidate-install.md'));assert(!build.includes('concurrency:') && !build.includes('secrets.') && !build.includes('id-token:'));- assert(header.includes('version:') && header.includes('accepted:') && header.includes('default: false'));+ assert(header.includes('version:') && !header.includes('accepted:'));assert.match(header, /version:\n(?:[^\n]*\n)*? required: true/);for (const manualField of ['candidate_run_id:', 'source_sha:', 'tgz_sha256:', 'acceptance_sha256:', 'approved:', 'action:']) assert(!header.includes(manualField));assert(!workflow.includes(' candidate:') && !workflow.includes('environment:'));assert(header.includes('group: motion-test-publication') && header.includes('cancel-in-progress: false'));assert(workflow.includes('motion-release.mjs authorize') && workflow.includes('authorization.json'));assert(workflow.includes('MOTION_EXPECTED_SHA256: ${{ needs.verify.outputs.tgz_sha256 }}'));- assert(recovery.includes('version:') && recovery.includes('accepted:') && recovery.includes('archive_only: true'));+ assert(recovery.includes('version:') && !recovery.includes('accepted:') && recovery.includes('archive_only: true'));assert(recovery.includes('uses: ./.github/workflows/motion-publish-test.yml') && !recovery.includes('source_sha:'));});@@ -443,7 +442,7 @@ test('no-publication rehearsal carries one accepted candidate through npm and stassert.equal(npmWrites, 1);const release = JSON.parse(store.objects.get(`open-motion/dev/${f.candidate.version}/release-record.json`));assert.equal(release.schemaVersion, 2); assert.equal(release.authorization.actor, 'operator');- assert.equal(release.authorization.acceptanceConfirmed, true);+ assert.equal(release.authorization.schemaVersion, 2); assert(!Object.hasOwn(release.authorization, 'acceptanceConfirmed'));assert.equal(release.tgzSHA256, f.candidate.tgzSHA256);assert.equal(store.writes.at(-1), 'open-motion/dev/install.md');await publishNpm(f.directory, f.inputs, npm);