@motionharness/cli-darwin-arm64 0.0.22 → 0.0.25

package/README.md

@@ -1,4 +1,4 @@
-# MH CLI
+# MotionHarness CLI
 
 Install the CLI with npm on macOS Apple Silicon / arm64 or Windows 10/11 x64:
 
@@ -24,35 +24,51 @@ or manage them. Project initialization needs registry access to the matching
 `@motionharness/sdk` and project dependencies. Run `mh skill` for the authoring
 and Agent guide.
 
+Use `mh render ./clip.wav --project ./my-project` to export the audio mix, or
+`mh render ./frames.zip --project ./my-project` for a numbered PNG sequence.
+PNG, APNG, PNG sequences and WAV work without FFmpeg. Studio also offers MP4
+(H.264 or HEVC), ProRes MOV, GIF and WebP when the host supports the encoder.
+
 For automatic AI marker delivery, ask your Agent to explain the feature and run
 `mh hook install --agent codex` (or `claude-code` / `kimi-code` for that Agent).
-Each new user message can then include the current MH project's pending markers
+Each new user message can then include the current MotionHarness project's pending markers
 and layer deletion requests. This does not start conversations. Complete any
 platform trust or session-reload step reported by the command. Studio shows
 configuration status and an off switch; reinstalling preserves a previous opt-out.
 
 `@motionharness/cli` provides the `mh` command and selects an exactly matching
-platform package. `@motionharness/cli-darwin-arm64` contains the macOS arm64 native
-binary; `@motionharness/cli-win32-x64` contains `mh.exe`. Install the main package
+platform package. `@motionharness/cli-darwin-arm64` contains `MotionHarness`;
+`@motionharness/cli-win32-x64` contains `MotionHarness.exe`. The native process uses
+this full product name; the command remains `mh`. Install the main package
 for the command. Windows ARM64, WSL and Linux packages are not provided; Linux
 can run from source. Keep optional dependencies enabled. Installation works with
 `--ignore-scripts`: there are no postinstall hooks or extra binary downloads.
 
+For installations predating this native filename, update with
+`npm install -g @motionharness/cli@latest --include=optional`.
+
 The npm command verifies the platform package and its version. On macOS it uses
 experimental `process.execve()` to replace Node with Rust; unavailable API support
-produces an upgrade prompt. On Windows it starts and waits for `mh.exe`, preserving
+produces an upgrade prompt. On Windows it starts and waits for `MotionHarness.exe`, preserving
 arguments, stdin/stdout/stderr and exit status.
-`mh open [directory]` returns a Studio URL and exits without opening a browser.
-Use `--browser` to open it explicitly. Project commands default to the current
-working directory (`--project` selects another) and start sessions on demand.
+`mh open [directory]` returns a Studio URL and exits. Project commands default to
+the current working directory (`--project` selects another) and start sessions
+on demand. First successful preparation automatically opens or reuses Studio
+once per session, without waiting for its connection. Edits and exports keep the
+user's page open and do not reopen a closed tab. Set `MH_NO_BROWSER=1` for batch
+or server use. `mh open --browser` explicitly reopens or reuses Studio and waits
+for its connection, even with automatic opening disabled. Browser launch failure
+reports the Studio URL without failing preparation or export.
 `mh status` and `mh close` inspect or release the current project; `mh daemon
 status` lists all projects and `mh daemon stop` explicitly stops everything.
-A session closes after 15 minutes without connected Studios or running work.
+A session closes after 30 idle minutes without connected Studios or running work.
 An empty daemon exits after 10 minutes. Busy projects and failed saves prevent
 normal close/reclamation. Node runs only for transient build/dependency tasks;
 Chrome automation uses Rust chromiumoxide.
+Keep the user's Studio open after creation; `close` and `daemon stop` are explicit
+management commands, not routine creation cleanup.
 
-The binary embeds MH's fixed runtime resources. On first use these expand into
+The binary embeds MotionHarness's fixed runtime resources. On first use these expand into
 `~/Library/Caches/mh/runtime/<payload-sha256>/` on macOS or
 `%LOCALAPPDATA%\mh\cache\runtime\<payload-sha256>\` on Windows. Windows authentication
 and daemon state use separate `auth` and `daemon` directories under `%LOCALAPPDATA%\mh`.
@@ -75,6 +91,29 @@ command output or exit status.
 
 ## Updates
 
+Studio also offers **Software update** directly beside the project dropdown.
+Automatic checks and background preparation are enabled by default, with a
+12-hour check interval. A visible **Update available** button opens release
+changes, preferences and **Update and reopen**. The host prepares all connected
+views, waits for confirmed writes and preserves their playheads, selections and
+view positions. Exports, builds, unfinished drafts and failed saves postpone
+installation. Installed DaVinci components must remain compatible.
+
+Studio installs a verified, complete npm release through a separate updater.
+It keeps the previous installation until executable/runtime checks and project
+reopening succeed, and restores it on handled installation or startup failures.
+**Install automatically after all project sessions end** is optional and off by
+default. This setting requires automatic checks and downloads. SDK dependencies
+and project lockfiles are not upgraded. Non-global or other package-manager
+installations use their original update commands. Updates do not elevate privileges.
+
+Settings and prepared releases live in the installation-specific `mh/updates`
+user data directory; `MH_SOFTWARE_UPDATE_DIR` overrides its absolute base.
+The previous installation and a replacement journal are retained for recovery.
+Forced process termination or power loss during directory replacement may
+require reinstalling with the original package manager; project files are retained.
+The explicit terminal command below retains its existing npm installation flow.
+
 ```sh
 mh update --check             # Query latest without installing
 mh update                    # Upgrade a confirmed npm global installation
@@ -89,7 +128,7 @@ installs the exact checked version with its matching platform package. Automatic
 installation requires the current package to be directly inside the active npm
 global root with a matching prefix; linked packages and detected pnpm/yarn layouts
 are excluded. If a different Node/npm installation is active, switch back to the
-one that owns MH. Project-local, npx and other package-manager installs receive
+one that owns MotionHarness. Project-local, npx and other package-manager installs receive
 manual instructions. Standalone binaries must be replaced manually.
 
 Close active sessions and finish exports before updating. Idle daemons stop

package/bin/MotionHarness

@@ -0,0 +1,4 @@
+[diffend] Oversized file quarantined before diffing.
+name: package/bin/MotionHarness
+size: 61070080 bytes
+sha256: ebb5c65586b6b103063f9036ce3a612b940013cd77f745494ac9f22509ee0974

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.0.22",
+  "version": "0.0.25",
   "license": "Apache-2.0",
   "type": "module",
   "engines": {
@@ -10,7 +10,7 @@
     "registry": "https://registry.npmjs.org/"
   },
   "name": "@motionharness/cli-darwin-arm64",
-  "description": "MH native binary for macOS arm64",
+  "description": "MotionHarness native binary for macOS arm64",
   "os": [
     "darwin"
   ],
@@ -18,7 +18,7 @@
     "arm64"
   ],
   "files": [
-    "bin/mh",
+    "bin/MotionHarness",
     "README.md",
     "LICENSE"
   ],

package/bin/mh

@@ -1,4 +0,0 @@
-[diffend] Oversized file quarantined before diffing.
-name: package/bin/mh
-size: 59532384 bytes
-sha256: 212b99eec690a6993e5a20300314431d5c4b50e20233223956bb6ef3436a90f9