npm - @osmo.inc/cli - Versions diffs - 0.1.15 → 0.1.16 - Mend

@osmo.inc/cli 0.1.15 → 0.1.16

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (7) hide show

package/DEPLOY.md CHANGED Viewed

@@ -1,64 +1,39 @@
-# Share videos and deploy Studio projects
+# Share videos for review
 [Back to the CLI overview](README.md)
-## Choose a sharing workflow
-The public release exposes video sharing. The entire `osmo studio` namespace
-is disabled and hidden from help by default. The Studio workflow below is for
-internal testing with `OSMO_STUDIO_ENABLED=1`; it will launch later.
-- `osmo share --video FILE.mp4`: upload a rendered video made in **any tool**, including drafts and work in progress, for
-  comments and review version history. No editable source is uploaded. Works from
-  any folder, without `osmo studio init`, Git, or an Osmo project. Requires `osmo login`
-  and ffprobe (included with FFmpeg).
-- `osmo studio deploy [scene.tsx]`: deploy a **full-featured editable Osmo project**,
-  including source files, assets, and tracked Git history, plus a rendered review
-  video and layer outline. Requires an initialized and published Osmo project
-  (`osmo studio init`, `osmo login`, `osmo studio publish`). Edit with local Studio or code;
-  shared cloud reviews are read-only. When Studio is enabled, AI agents should choose this command when
-  sharing an Osmo Studio project, to preserve editable source and project history.
+Share a rendered video from any tool, including drafts and work in progress. Requires an Osmo login and ffprobe, with no project setup or Git repository.
 ```sh
 osmo login
 osmo share --video ./film.mp4 --name "Launch film"
-# Use the project ID printed above to add a version to the same review:
 osmo share --video ./film-v2.mp4 --project PROJECT_ID
+```
+Without `--project`, each upload creates a new review. With `--project`, the upload adds a version to that review. The command does not initialize or write anything in the working folder.
+Add `--json` for machine-readable output containing `project`, `render`, `link`, and `versionLink`. A failed upload reports the project ID for retrying; only completed uploads appear in review history.
+## Supported videos
+Upload MP4 with H.264 8-bit 4:2:0 video and optional AAC audio, up to 2 GiB. Files are uploaded as supplied; export a compatible MP4 from your video tool before sharing. Uploads stream from disk without buffering the full file.
+Fractional frame rates are preserved. Variable-frame-rate videos retain playback duration and seconds-based comments; timeline frame positions use the average frame rate.
+## Review links and comments
+`link` is the stable review URL. Refresh it after a successful upload to see the newest completed version. An already open review stays on its version while you comment. Failed uploads leave the previous video available.
+`versionLink` points to one specific video version. Comments stay attached to that version, and existing version links continue to work while sharing is enabled. Anyone with a review link can access the review.
+```sh
 osmo comments list --project PROJECT_ID --open --json
 osmo comments reply COMMENT_ID "Updated in the latest version." --project PROJECT_ID
 osmo comments resolve COMMENT_ID --project PROJECT_ID
+osmo comments reopen COMMENT_ID --project PROJECT_ID
 ```
-Without `--project`, each video share creates a new cloud review project. The
-command does not initialize or write anything in the working folder. `--json`
-returns `project`, `render`, `link`, and `versionLink`. A failed upload prints the
-project ID for retrying; only completed uploads appear in review history.
-Video import accepts MP4 with H.264 8-bit 4:2:0 video and optional AAC audio, up to
-2 GB. Unsupported codecs are rejected before creating a cloud project; export a
-compatible MP4 from your video tool first. Fractional frame rates are preserved;
-variable-rate videos retain exact playback duration and seconds-based comments
-(the timeline's frame positions use the average frame rate). Imported videos
-support time ranges, canvas annotations, replies, and resolution, without an
-editable layer outline. Uploads stream from disk without buffering the full file.
-## Cloud review links
-Both workflows upload a version and print one stable project
-review URL (`/share/project/<project-id>`). Reopen or refresh it after a successful
-deployment to see the newest completed version; failed uploads leave the previous
-video available. An already open review stays on its version while you comment.
-With `--json`, `link` is the stable project URL and `versionLink` is the permanent
-URL for that particular render. Comments stay attached to their render. Existing
-version links continue to work while sharing is enabled. The stable route requires the matching web/backend
-update; source and revision access still require login, while review links retain
-the existing anyone-with-the-link access.
-Studio deployments include a public layer outline (names, hierarchy and timing),
-without source properties or asset URLs. Cloud comments preserve the local
-comment shape, including time ranges, canvas/element targets and replies. Older
-deployments remain viewable without the layer outline.
+Reviews support time ranges, canvas annotations, replies, and resolving comments.
 ## Disable review links
@@ -66,22 +41,10 @@ deployments remain viewable without the layer outline.
 osmo unshare --project PROJECT_ID
 ```
-Requires login and owner or editor access to the project. Works from any folder,
-without a local project, Git, FFmpeg, or Studio enabled. Add `--json` for
-`{ "status": "undeployed", "project": "PROJECT_ID" }`. Repeating it is safe.
-This is soft revocation: the project, videos, comments, and source history stay
-stored. The main review link, all version links, public comment reads/writes, and
-new public download links stop working. Authenticated project access is retained.
-Previously obtained direct media URLs and downloaded copies are not revoked;
-media currently uses public object storage, and already issued signed downloads
-can remain valid until expiry.
-A successful new `osmo share --video FILE.mp4 --project PROJECT_ID` restores
-sharing for the project and all its existing versions. Studio projects can also
-be shared again with a new `osmo studio deploy`. Uploads begun before revocation,
-failed uploads, and retries of old completion requests do not restore sharing.
-The backend update and its `0065_review_link_revocation` and
-`0066_review_upload_generation` migrations must be deployed before using this
-command. Existing uploads without a captured sharing generation may finish, but
-cannot restore disabled links; start a new deployment to restore sharing.
+Requires login and owner or editor access to the project. Works from any folder without local project files, Git, or FFmpeg. Add `--json` for `{ "status": "undeployed", "project": "PROJECT_ID" }`. Repeating the command is safe.
+Videos, comments, and history remain stored. The main review link, all version links, public comment reads/writes, and new public download links stop working. Authenticated project access is retained.
+Previously obtained direct media URLs and downloaded copies are not revoked; already issued signed downloads can remain valid until expiry.
+A successful new `osmo share --video FILE.mp4 --project PROJECT_ID` restores the review links for the project and its existing versions. Uploads begun before links were disabled, failed uploads, and retries of old completion requests do not restore them. Start a new upload to restore sharing.

package/README.md CHANGED Viewed

@@ -1,243 +1,23 @@
-# Osmo CLI / Studio — public release
+# Osmo CLI
-Video sharing and review with timeline comments. Studio authoring and rendering
-are unreleased and disabled by default.
-This release targets **macOS on Apple Silicon with arm64 Node 22**. Cloud commands
-use **https://studio.osmo.inc** by default.
-For preview testing, explicitly set `OSMO_BASE_URL=https://preview.osmo.inc`.
-Credentials are stored separately for each origin; changing the default does not
-move preview credentials or repoint existing published projects.
+Share videos. Collect feedback.
-## Installation
+Upload a video from any tool and get a review link with timestamped comments and version history.
 ```sh
 npm install -g @osmo.inc/cli
-osmo login --json
+osmo login
+osmo share --video ./video.mp4
 ```
-No npm account is needed to install the public package. Building this repository
-does not publish to npm.
-**Prerequisites:** Node 22 and npm; FFmpeg with the `libx264` encoder and ffprobe
-on PATH for rendering/video workflows. Project authoring also requires Git with
-SHA-256 repository support (Git 2.29+). Rust, Cargo and this checkout are not
-needed on end-user machines. FFmpeg is not bundled.
-Share a rendered video from any tool, including drafts and work in progress, from any directory:
-```sh
-osmo share --video ./animation.mp4
-```
-This needs login and ffprobe, with no project, Git or `init`.
-Disable a project's public review links with `osmo unshare --project PROJECT_ID`.
-Videos, comments, and history are retained. A successful new deployment to the
-same project restores sharing. See the [revocation details](DEPLOY.md#disable-review-links).
-## Internal Studio preview
-All `osmo studio …` commands are hidden from help and disabled by default,
-including Studio comments. For internal testing, explicitly enable them in the
-shell with `export OSMO_STUDIO_ENABLED=1`. Any other value leaves them disabled.
-This is a local release switch, not an authorization or security boundary.
-Project initialization is `osmo studio init`; the former top-level `osmo init`
-is removed. Project publishing, push, pull, sync, clone, and history also live
-under `osmo studio`; their former top-level commands are removed. Authentication,
-resources, video sharing, and video comments remain at the top level.
-With Studio enabled, the editable source, assets and Git history workflow is:
-```sh
-osmo studio init my-animation
-cd my-animation
-osmo studio check scene.tsx
-osmo studio render scene.tsx --out exports/animation.mp4
-osmo studio publish --name "My animation"
-osmo studio deploy scene.tsx
-```
-See the [sharing and deployment guide](DEPLOY.md) and [setup prompt](SETUP.md).
-Local authoring and rendering work without an Osmo account.
-## Build and verify an archive
-From this checkout on an Apple Silicon Mac (Rust, wasm-pack, the wasm32 target,
-Node 22.18+, FFmpeg and Xcode command-line tools required):
+Add a version, read feedback, or disable the link:
 ```sh
-npm ci
-npm -w @osmo/cli run package:internal
-node packages/cli/tools/smoke-package.mjs ./dist/osmo-cli-0.1.15-darwin-arm64.tgz
-npm install -g ./dist/osmo-cli-0.1.15-darwin-arm64.tgz
+osmo share --video ./video-v2.mp4 --project PROJECT_ID
+osmo comments list --project PROJECT_ID --open --json
+osmo unshare --project PROJECT_ID
 ```
-The CLI source is strict TypeScript. The archive runs the compiled `dist/osmo.js`
-bundle, including the editor; raw CLI TypeScript is not shipped. A checkout
-requires Node 22.18+ for source tests; the installed CLI supports any Node 22.
-The CLI renderer excludes the standalone desktop UI. Resources are fetched when
-requested; the starter uses only text and built-in primitives. See the
-[package size audit](RELEASE.md#package-size-audit) for included runtime files.
-The internal archive is private and ad-hoc signed, for validation only. The build
-rebuilds native and WASM renderers, clears Studio output, gathers dependency and
-font notices, embeds Mediabunny's matching MPL source, and records artifact hashes
-in `release.json`. The archive test installs outside this checkout and exercises
-both deploy workflows against a local server. Nothing is published or uploaded
-to Osmo cloud by these commands.
-Public packaging needs no Apple credentials or new first-party license approval.
-It preserves existing license metadata and uses ad-hoc signing by default;
-certificate signing and notarization are optional. See [release instructions](RELEASE.md).
-The source workspace remains `private: true`; only the complete `--npm` package
-can be published as `@osmo.inc/cli` with public access and the `latest` tag.
-`osmo studio init` installs the matching `@osmo/scene` archive from `.osmo/vendor`, without an
-Osmo registry lookup. Keep that archive with the project. Existing scene/config
-files and user instructions outside the managed AGENTS.md section are preserved.
-Existing projects with scene API version 0.1.0 remain compatible. No scene API
-changes are introduced by this packaging work.
-## Copy-paste agent prompt
-> Initialize an Osmo project in this folder with `osmo studio init`. Read `AGENTS.md`, create an animation using the supported primitives and Strict API, validate it with `osmo studio check scene.tsx`, and open it with `osmo studio open scene.tsx`. When I ask you to address feedback, read open Studio comments through the CLI. Validate completed fixes, reply only “Done.” and resolve them. Keep a comment open only for ambiguity, an incomplete fix, or a specific uncertainty needing my verification; leave one short sentence explaining what needs checking. Here is what I want to animate: …
-## Account login
-```sh
-npx @osmo.inc/cli login --json
-# Open the returned URL, confirm the code, then poll using its sessionId:
-npx @osmo.inc/cli login status SESSION_ID --json
-npx @osmo.inc/cli whoami --json
-npx @osmo.inc/cli logout --json
-```
-`login` returns immediately so an agent can share the approval link. `login status`
-returns pending/connected/denied/expired; respect `retryAfter` before polling again.
-An unexpired attempt is reused. `--name "My laptop"` labels the connection.
-`whoami` calls the backend and refreshes expired tokens automatically. `logout`
-revokes that computer's connection; it preserves credentials when the server is
-unreachable so revocation can be retried. Cancelling an unapproved pending login
-removes it locally; its browser code expires on the server after ten minutes.
-Preview is the default. Set `OSMO_BASE_URL=https://studio.osmo.inc` to explicitly
-use production when its backend supports these commands; each origin has separate credentials.
-Projects already connected to a cloud origin retain that origin. Account commands work outside a
-Studio project. Secrets stay in `~/.osmo/auth` (directory 0700, files 0600), with
-atomic writes and a cross-process lock for polling/refresh. They never appear in
-CLI output. `OSMO_CONFIG_DIR` overrides the config root for isolated testing.
-After a killed auth process, an `auth_busy` error names the lock directory to
-remove once no auth command is running.
-Account login also authorizes resource-package downloads. Generative tool execution is not
-implemented. Studio's local preview and rendering still need no Osmo login.
-## Resources
-In editing mode, Studio shows project resources in the inspector when nothing is
-selected. Drag a tile onto the timeline or canvas; compatible layer drops apply a
-shader effect or a Group background. Drops use existing scene syntax and undo/redo.
-```sh
-osmo resources examples
-osmo resources import ./image.png
-osmo resources import ./video.mp4
-osmo resources import ./shader.wgsl
-osmo resources import ./model.glb
-osmo resources local --json
-```
-These local commands require an initialized project, with no login. Files live
-under `resources/<id>/` and appear automatically in the panel. Images, videos,
-shaders, and GLB models are supported. Imported shaders are clip-only unless their
-descriptor supplies an effect entry; the bundled tint example includes both.
-```sh
-osmo resources list --json
-osmo resources list --category shader --json
-osmo resources show silk --preset petrol --json
-osmo resources add silk --preset petrol --json
-osmo resources add liquid-glass --version 1.0.0 --preset frosted --json
-```
-List/show work without login or a project. They include public previews and links;
-show reports compatibility with the running CLI. Add requires an initialized project
-and Osmo login. It installs authenticated, checksum-verified files into
-`resources/<id>/`: `shader.wgsl`, `shader.d.ts`, and `resource.json`. No lockfile or
-scene edits. An identical installed package is a no-op; different, incomplete or
-symlinked destinations are preserved and reported as conflicts. Presets share code;
-`--preset` selects the uniforms/usage returned to the agent, not different files.
-Use `Shader` with a relative `.wgsl` src and explicit uniforms. Uniform numbers and
-vectors support motion/knob bindings; shader source stays static. Read the installed
-types and the add command's usage instead of recreating a resource. CLI compatibility
-is authoritative for this version; early manifests may still say Strict is unsupported.
-The generated AGENTS.md requires resource discovery at the start of each animation
-task. Re-run `osmo studio init` to update that managed section in an existing project.
-`--json` errors include a stable error code; `login_required` includes the next login
-command. Approve login in the browser, poll the returned session, and retry add.
-The same OSMO_BASE_URL selects both the catalog and its separate credential store.
-## Commands
-```sh
-osmo studio init [folder]
-osmo studio open [scene.tsx] [--port NUMBER] [--no-open]
-osmo studio check [scene.tsx] [--json]
-osmo studio render [scene.tsx] --out animation.mp4 [--supersample 1|2]
-osmo studio render [scene.tsx] --frame 90 --out frame.png [--supersample 1|2]
-osmo studio comments list --open --json
-osmo studio comments list --scene scene.tsx
-osmo studio comments start COMMENT_ID [EMOJI]
-osmo studio comments stop COMMENT_ID
-osmo studio comments react COMMENT_ID [EMOJI|none]
-osmo studio comments reply COMMENT_ID "Done."
-osmo studio comments resolve COMMENT_ID
-osmo studio comments reopen COMMENT_ID
-```
-A render holds every frame in memory and stops when the compiled scene passes
-1 GB. For a long or dense scene, raise the limit in megabytes:
-`OSMO_SNAPSHOT_LIMIT_MB=4096 osmo studio render scene.tsx --out film.mp4`.
-Run project commands from the initialized folder (or a child folder). `open` prints a stable project URL such as `http://127.0.0.1:4310/my-animation-k7m2` and opens the browser. The first launch picks an available port starting at 4310 and saves it with a folder-derived ID and random access token in gitignored `.osmo/studio.json`. Later launches reuse them, including after a folder rename. `--port NUMBER` saves a different port (`--port 0` chooses an available one). A saved port occupied by another app produces an error; Studio never silently moves it. Reopening a running project reuses its server and switches to the requested scene. The clean page URL establishes an HttpOnly, SameSite cookie; authenticated API calls also require a custom header. The server binds only to 127.0.0.1 and rejects foreign Host/Origin headers. Existing tabs reconnect automatically after a restart. Ctrl+C stops its HTTP server, renderer and child processes. `render` defaults to 2× supersampling and preserves existing files. No login or backend is required.
-The browser provides play/pause, frame steps, scrubbing, looped playback, audio mute, timestamp/range comments, replies, filters, resolution, and MP4 export/download. Canvas hover previews a selection while paused. Click selects the outer group, double-click enters it, and Cmd/Ctrl-click selects the deepest element. Escape selects the parent or clears selection; empty canvas clears it. Clicking during playback pauses on the displayed frame. Canvas selections reveal their timeline rows. Hit testing uses native projected bounds, not per-pixel alpha or exact clipping. The centred switch changes between Comment mode (a compact time scale, seek bar and comments sidebar) and Interactive mode (properties/keyframes and read-only inspector). The seek bar expands smoothly to reveal layers in Interactive mode. Selection, playhead and layer expansion persist between modes. Its read-only timeline shows collapsible scene nesting, active durations, animation intervals, motion/effect/knob counts and expandable keyframes. Click a row for source locations, properties and a canvas outline; click a key to seek. Selection follows native layout bounds on the displayed frame, including nested groups and camera projection. The outline is a browser overlay and never appears in exports. Audio/Camera and Model Surface content have no standalone canvas outline; Models use their placement box. Effects can paint outside layout bounds. Drag the divider to resize the timeline. Inspection follows the successful preview revision and never edits source. Saving source/assets reloads the native scene. Compilation/render errors retain the last good preview and outline. Browser export uses the frozen preview snapshot; edits during export do not affect that export. CLI render compiles the source on disk.
-Single-frame PNG exports use zero-based frame numbers: `--frame 90` is 3 seconds at 30 fps. The frame must exist in the scene. PNGs preserve transparency and scene dimensions; supersampling improves edges without enlarging the output. Both render modes validate Strict syntax/types and refuse to overwrite existing files.
-## Comments
-Press **C** for Comment mode or **E** for Interactive mode. Mode changes take 180ms; hold Shift while clicking a mode or using its shortcut to inspect the 1.8-second transition.
-In Comment mode, click the canvas for a point or drag a dashed rectangle around an area. Click the time scale for a timestamp or drag for a period. Open **Layers** to comment on a particular scene element without leaving Comment mode. Avatar pins on the canvas and time scale open the thread; hovering shows a preview. Clicking away discards empty drafts. With unsent text, the first outside click or Escape shakes the composer and keeps it open; repeating the same action discards it. Editing or clicking back inside resets that confirmation. Drafts do not survive a page reload. Drag a selected comment’s timeline handles to adjust its range, including after posting; an end handle can extend a point comment into a range. Click a sidebar comment card to seek to and highlight its timestamp or range. Saved threads support replies and resolution.
-Use the avatar button in the comments sidebar to set your local name and photo. The comment cursor uses your photo when available, otherwise the default comment icon. Profile settings live in `.osmo/comment-profile.json`; new comments include a snapshot of their author's profile. Area coordinates are relative to the preview dimensions, and element targets reference the preview's outline IDs. Canvas annotations appear at their timestamp or throughout their selected period; earlier-revision comments stay available on the timeline without projecting old bounds onto the new preview.
-`.osmo/comments.json` is persistent, versioned project data. UI and CLI share cross-process locking and atomic writes. Every comment contains a scene-relative filename, seconds (and optional endTime), an ID, preview content revision, status, text, replies and timestamps. Earlier revisions are flagged in the UI; timestamps are not automatically remapped after retiming. The agent never needs a running viewer to read/reply/resolve. An idle agent is not automatically notified: ask it to apply your comments through the CLI. Reopen is available to undo a resolution.
-## Boundaries
-- Strict checks run before preview and export; this remains an authoring contract, not a sandbox. Only open trusted local source/assets.
-- v1 streams PNG frames on demand from one persistent native renderer, with a bounded 32 MB server frame cache. Preview drops frames to keep wall-clock timing under load; export renders every frame. Large scenes may not sustain their authored FPS. Incremental TSX compilation, adaptive preview resolution and video compression are future work.
-- Preview currently renders at 1×; export defaults to 2×. Audio uses the native frozen mix. No hosted sharing, multiplayer identities, spatial annotations, editable knob inspector, MCP server, or automatic agent wake-up yet.
-- The old desktop viewer remains available. The Studio worker is an additional native entry point.
-## Development
-```sh
-cargo build --locked --manifest-path apps/native/Cargo.toml
-node packages/cli/bin/osmo.mjs studio init /tmp/my-osmo-project
-cd /tmp/my-osmo-project
-node /path/to/ai-motion-designer-web/packages/cli/bin/osmo.mjs studio open scene.tsx --no-open
-```
-Storage tests: `npm -w @osmo/cli test`. Native integration tests:
-`npm -w @osmo/cli run test:integration`. Integration tests start the real native renderer on loopback and use temporary projects. Build the native executable first. Browser UI components and adapted visual tokens live in `packages/studio`.
-## Deployment and review
+Requires **Apple Silicon macOS, Node 22, and ffprobe**. Accepts H.264 MP4 with optional AAC audio, up to 2 GiB. No project setup or Git required.
-See the [sharing and deployment guide](DEPLOY.md) for choosing between video-only sharing with
-`osmo share --video` and full editable projects with `osmo studio deploy`,
-including version updates, comments, and review links.
+[Sharing guide](DEPLOY.md) · [AI agent setup](SETUP.md)

package/SETUP.md CHANGED Viewed

@@ -1,60 +1,30 @@
-# Osmo public setup
+# Osmo CLI setup
-The release is for macOS on Apple Silicon with arm64 Node 22. It uses
-**https://studio.osmo.inc**, including login, uploads, and resource downloads.
-Existing project cloud pointers are preserved. Credentials are isolated by origin.
-The install command uses the default `latest` release.
+Requires an Apple Silicon Mac, arm64 Node 22, and ffprobe (included with FFmpeg). The default service is **https://studio.osmo.inc**.
-## Share an existing video
+## Install
+```sh
+npm install -g @osmo.inc/cli
+osmo login
+osmo share --video ./video.mp4
+```
+## Setup prompt for an AI agent
 ```text
 Install @osmo.inc/cli from npm. Check for arm64 Node 22 and ffprobe.
 Run osmo login --json and show me the approval link and code. After I approve,
 poll login status with the returned sessionId, respecting retryAfter.
-Run osmo whoami --json, then osmo share --video /path/to/video.mp4.
-No Osmo project, Git repository or init is needed. Return the share link.
+Run osmo whoami --json, then osmo share --video /path/to/video.mp4 --json.
+No project setup or Git repository is needed. Return the review link and project ID.
 Never read or print stored credentials.
 ```
-Use H.264 MP4, 8-bit yuv420p, optionally with AAC audio, up to 2 GB.
-For later versions use `osmo share --video FILE.mp4 --project PROJECT_ID`.
-Disable review links with `osmo unshare --project PROJECT_ID`, preserving the data.
-Use `osmo comments list --project PROJECT_ID --open --json` to read feedback.
-## Internal Studio preview (not part of the public launch)
+Use H.264 MP4, 8-bit 4:2:0 video, optionally with AAC audio, up to 2 GiB. Files are uploaded as supplied.
-Studio commands are hidden and disabled by default. Public video sharing and
-comments do not require enabling Studio.
-```text
-For internal testing only, set OSMO_STUDIO_ENABLED=1 in the command environment.
-Set up Osmo Studio with the internal CLI archive.
-Check for an Apple Silicon Mac, arm64 Node 22, npm, Git 2.29+ with SHA-256
-support, FFmpeg with libx264, and ffprobe. Report missing prerequisites.
-Run osmo studio init my-animation in a new folder, preserving files.
-Read the generated AGENTS.md and the @osmo/scene declarations.
-Run studio check scene.tsx, then studio render scene.tsx --out exports/check.mp4.
-Use another output filename if that file already exists.
-Open studio open scene.tsx and share the local preview URL.
-Use the osmo prefix for all commands and preserve the Studio flag in their environment.
-Wait for my animation brief after verifying setup.
-When I ask to share the project, use osmo login, osmo studio publish, and osmo studio deploy.
-That workflow includes editable source, assets and tracked Git history.
-```
-Local rendering needs no account. Cloud sharing requires `osmo login`.
-The cloud review page is read-only; editing happens locally in Studio or code.
-See [DEPLOY.md](DEPLOY.md) for video sharing and Studio project deployment.
-## Test an unpublished archive
-```sh
-npm install -g /path/to/osmo-cli-0.1.15-darwin-arm64.tgz
-osmo --version
-export OSMO_STUDIO_ENABLED=1
-osmo studio init my-animation
-```
+For later versions, use `osmo share --video FILE.mp4 --project PROJECT_ID`.
+Read feedback with `osmo comments list --project PROJECT_ID --open --json`.
+Disable review links with `osmo unshare --project PROJECT_ID`, preserving the data.
-The internal archive is ad-hoc signed and intended for local validation. It is
-marked private to prevent accidental npm publication. It includes the renderer, Studio,
-scene library and compiler; Rust and this repository are not needed to use it.
+See the [sharing guide](DEPLOY.md) for version history, comments, and link access.

package/package.json CHANGED Viewed

@@ -1,13 +1,13 @@
 {
   "name": "@osmo.inc/cli",
-  "version": "0.1.15",
+  "version": "0.1.16",
   "private": false,
   "publishConfig": {
     "access": "public",
     "tag": "latest",
     "registry": "https://registry.npmjs.org/"
   },
-  "description": "Local Osmo Studio: native rendering, browser preview, and timeline feedback",
+  "description": "Share videos. Collect feedback.",
   "type": "module",
   "bin": {
     "osmo": "bin/osmo.mjs"
@@ -26,8 +26,7 @@
     "LICENSE",
     "THIRD_PARTY_NOTICES.md",
     "third-party",
-    "release.json",
-    "RELEASE.md"
+    "release.json"
   ],
   "engines": {
     "node": ">=22 <23"

package/release.json CHANGED Viewed

@@ -1,9 +1,9 @@
 {
-  "version": "0.1.15",
+  "version": "0.1.16",
   "platform": "darwin-arm64",
   "channel": "latest",
   "defaultCloudOrigin": "https://studio.osmo.inc",
-  "sourceCommit": "0bb14b4541e8e9955714ce24cdbac68869935b02",
+  "sourceCommit": "2a7c1a5e37e17f0508f123b86af67e584d5fd0a6",
   "sourceDirty": false,
   "signing": "ad-hoc",
   "licenseFileIncluded": false,
@@ -16,8 +16,8 @@
     }
   },
   "contents": {
-    "totalBytes": 59066771,
-    "fileCount": 948,
+    "totalBytes": 59037117,
+    "fileCount": 947,
     "groups": {
       "vendor": 16948891,
       "studio": 15935597,
@@ -29,12 +29,11 @@
       "node_modules/esbuild": 143795,
       "runtime": 137478,
       "node_modules/fflate": 96377,
-      "README.md": 17083,
-      "RELEASE.md": 9545,
-      "DEPLOY.md": 4829,
-      "SETUP.md": 2811,
+      "DEPLOY.md": 2902,
+      "SETUP.md": 1138,
       "THIRD_PARTY_NOTICES.md": 1088,
-      "package.json": 951,
+      "package.json": 889,
+      "README.md": 636,
       "bin": 544
     },
     "largestFiles": [
@@ -129,7 +128,7 @@
     "third-party/inventory.json": "6ff4e90c6583a67ca8bfe95b3f4399cfcdc080d39585dce1314a8dd91ee6fecb"
   },
   "lockfiles": {
-    "package-lock.json": "86a27a636faac94ee6a7d93fbfddd5b6f9fff296738eb9f702095e5a73b70f07",
+    "package-lock.json": "d355ffdb350a8fa57d7f4b06f28ef986ec0bd1ddc082094a4367f370ed3893d4",
     "apps/native/Cargo.lock": "cf31d67cf167c5f32438abfeb42159eb50da61d36e4e482bae50ed3d71241373",
     "packages/render-engine/Cargo.lock": "a1a68051e1eea30ef0fa46bf17cd0685bb2c6a327defed0405e0d63dd61017a7"
   }

package/vendor/platform.json CHANGED Viewed

	@@ -1 +1 @@
1	- {"os":"darwin","arch":"arm64","version":"0.1.15"}
1	+ {"os":"darwin","arch":"arm64","version":"0.1.16"}

package/RELEASE.md DELETED Viewed

@@ -1,164 +0,0 @@
-# Public release
-Release branch: `feat/cli-public-beta-typescript`, based on preview after TypeScript migration
-PR #1045. The previous implementation remains on `feat/cli-public-beta`. End-user cloud default:
-`https://studio.osmo.inc`. Preview testing requires an explicit
-`OSMO_BASE_URL=https://preview.osmo.inc` override. Existing project origins and
-per-origin credentials are preserved; preview logins are not reused for production.
-Initial supported distribution: macOS Apple Silicon, arm64 Node 22. Other
-platforms must have their own build and clean-machine validation before support
-is declared. The current host's native deployment target is recorded by the
-binary; older macOS versions have not been certified by this change.
-## Studio release switch
-`OSMO_STUDIO_ENABLED=1` enables the unreleased `osmo studio` namespace for internal
-testing, including `osmo studio init [folder]`. Initialization and its generated
-AGENTS.md guide belong to Studio; the former top-level `osmo init` is removed.
-Studio defaults off in both checkout and installed builds, independently of the
-cloud origin. Other values do not enable it. Disabled commands return
-`feature_disabled` with `--json` before project lookup, rendering, or cloud writes;
-help and video-share usage omit Studio commands. This local switch does not
-provide account-based access control.
-Project commands (`publish`, `push`, `pull`, `sync`, `clone`, and `history`) also
-live under `osmo studio` and require the same opt-in; their top-level forms are
-removed. Top-level authentication, resources, video sharing, and video comments
-are unchanged. The archive still contains
-the full runtime for internal opt-in; this flag alone does not shrink the payload.
-The release manifest records the default and environment variable. Installed
-smoke tests cover the disabled public surface and explicitly opt in for Studio
-rendering/deploy tests. Video deployment tests run with Studio disabled.
-## Build and package
-1. Use a clean checkout, `npm ci`, arm64 Node 22.18+, Rust/Cargo, wasm-pack,
-   the wasm32-unknown-unknown Rust target, Xcode command-line tools, Git, and FFmpeg.
-   The package builds both renderer targets from source, then bundles Studio.
-   It also rebuilds the TypeScript CLI into `dist/osmo.js`; only that bundle and
-   its starter/resource templates are shipped, not raw CLI or editor source.
-   Compilation defaults to two Cargo jobs to limit memory usage.
-2. Run unit tests, build the package and validate the installed archive:
-```sh
-npm -w @osmo/cli test
-npm -w @osmo/studio test
-npm -w @osmo/cli run test:package
-npm -w @osmo/cli run package:npm
-node packages/cli/tools/smoke-package.mjs dist/osmo.inc-cli-0.1.15-darwin-arm64.tgz
-```
-`package:npm` builds a publishable archive without requiring a first-party
-LICENSE file or Apple credentials. Existing first-party license metadata and an
-optional LICENSE file are preserved; the build does not choose new license terms.
-`package:internal` performs the same builds and checks but sets `private: true`
-for a local test archive. Neither command publishes to npm.
-### Optional Apple signing
-Both archive types use an ad-hoc signature by default, which needs no Apple
-account or certificate. Set `OSMO_SIGNING_IDENTITY` to opt into certificate
-signing. Also set `OSMO_NOTARY_PROFILE` to opt into notarization using a configured
-`notarytool` keychain profile; that option requires a Developer ID Application
-identity. If explicitly requested signing/notarization fails, packaging fails
-instead of silently downgrading. `release.json.signing` records `ad-hoc`,
-`signed`, or `developer-id-notarized`. Standalone Mach-O binaries cannot have
-notarization tickets stapled. Do not commit credentials.
-## Notices
-`third-party/inventory.json` enumerates the actual Studio bundle inputs, installed
-CLI dependencies and target-specific Cargo dependency graphs. Full upstream
-notices, Inter OFL, and matching Mediabunny MPL source are included. The CLI
-renderer excludes desktop UI dependencies and their unused fonts. Cargo entries conservatively include build-time dependencies.
-Missing third-party license text fails packaging. For crates omitting notices from their
-published archive, `licenses/rust-sources.json` pins upstream notice files by
-version, source commit and SHA-256. Dependency updates require reviewing these
-records. The upstream declaration and standard MIT text are retained for crates
-that declare MIT but omit its full text; see `licenses/README.md`.
-`release.json` records the source commit, dirty-tree state, lockfile hashes,
-platform, cloud default, signing state, renderer/Studio hashes, and payload sizes
-by directory with the largest files. These are
-local build records, not npm or SLSA provenance attestations. Review the archive
-contents before publishing. No Passenger fonts should be present.
-## Before opening access
-- Validate the archive on a second Apple Silicon Mac, including launch behavior,
-  install, login to studio.osmo.inc, font rendering, MP4 export and both deploy workflows.
-- Confirm the intended production account access policy, storage limits, upload rate
-  limits and operational budget. Those backend policies are not added by this
-  packaging change. Existing per-file limits are not per-account quotas.
-- Use your company npm publishing credentials for `@osmo.inc/cli`. Publish stable versions under npm's
-  `latest` tag.
-- Publish separately when ready:
-```sh
-npm publish ./dist/osmo.inc-cli-0.1.15-darwin-arm64.tgz --access public --tag latest
-```
-The private GitHub repository is not made public by this workflow. No automated
-public publishing workflow is enabled here. Project initialization now uses `osmo studio init`; the scene API is unchanged.
-## Local validation of 0.1.15-beta.1
-Validated on macOS 27.0 / Apple Silicon, Node 22.23.1. The native binary declares
-macOS 11.0 as its deployment target; this does not certify older macOS versions.
-All scene, editor, Studio and CLI typechecks passed after the TypeScript port.
-Scene tests: 233 passed; editor: 129; Studio: 68; CLI: 76, with the native deploy
-case run separately. Packaging regressions: 3 passed, including stale-font
-removal, missing/tampered notice rejection, and execution of the trimmed compiler
-and ZIP dependency. The actual 19.5 MiB archive installed
-offline outside the checkout, rejected unavailable Git without creating a partial
-project, initialized and typechecked the starter, and rendered visible Inter text
-to MP4. The archive contains `dist/osmo.js`, not raw CLI TypeScript, and its
-bundled auth flow independently verifies the studio.osmo.inc default. All 5 deploy tests passed against local cloud fixtures using the installed
-CLI and native release binary, including both deploy modes and comments. Two
-additional installed-package tests passed: generated SVG/WGSL/GLB fixtures and
-audible AAC export, plus Studio static assets and a native worker frame. The
-normal desktop build still passes Cargo check with its default features.
-The public npm archive also builds without a first-party LICENSE file or Apple
-credentials and passes all nine installed-package checks. A separate standalone
-video deployment to preview succeeded with Studio disabled. No npm publication,
-Developer ID signing, or notarization was performed.
-## Package size audit
-Measured from the macOS arm64 internal npm tarball, with MiB = 1,048,576 bytes:
-| Payload | Before | After |
-| --- | ---: | ---: |
-| Compressed download | 24.89 MiB | 19.48 MiB |
-| Unpacked files | 77.52 MiB | 56.32 MiB |
-| Native renderer | 22.25 MiB | 16.13 MiB |
-| TypeScript dependency | 22.53 MiB | 9.45 MiB |
-The archive excludes the standalone desktop window, file picker, playback audio
-output library and desktop UI fonts. Audio mixing/export and Studio preview remain
-supported. Checkout desktop builds retain their default features.
-The staged compiler retains the compiler API and standard library declarations;
-CLI executables, language server, translated diagnostics and development files are
-excluded. Its JavaScript receives whitespace-only minification, with notices and
-a modification notice retained. Unused fflate builds, duplicate raw Studio fonts,
-vendor documentation, sample scripts and install metadata are also excluded.
-`init` now creates a small text animation with no external assets or shaders.
-Built-in WGSL implements rendering and effects; it stays embedded in the native
-and WASM renderers. Project media, resource catalog downloads, repository examples,
-shader demos and test fixtures are not bundled, except the existing 0.36 MiB
-`resources examples` templates. Removing that public command requires separate
-API approval. Resource listing/download/import continues to fetch content on demand.
-The remaining major components are native rendering (16.13 MiB), browser WASM
-(10.43 MiB), esbuild (9.90 MiB), the Node compiler and its standard libraries
-(9.45 MiB), and Studio JavaScript (4.46 MiB). Studio includes its own browser
-compiler for local source editing. Required notices and matching MPL source are
-retained. A much smaller base install would require optional/on-demand Studio and
-renderer downloads; that architectural change is not part of this cleanup.
-Package verification rejects desktop dependencies, redundant assets and removed
-compiler tools, and limits the macOS arm64 unpacked payload to 60 MiB. Review
-size changes deliberately before raising that budget. `release.json.contents`
-measures staged payload files before adding the release manifest itself.