@machinal/scenes 0.0.0-stage → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog
+
+## 0.1.1
+
+- Show readable setup/doctor status and a concise render result by default; use `--json` for complete tool and scene metadata. The Node API and saved scene manifests are unchanged.
+- Report the native renderer's real version instead of its help banner.
+- Reuse cached tools without announcing another Chrome or FFmpeg installation; FFmpeg integrity and license checks still run.
+- Fix negative preview frames when an animation timestamp precedes the Play click, including pause/resume and end-of-scene replay.
+- Default the starter scene to 1280×720 and show the complete local export path; clarify that the standalone tool has no S3 upload or project connection.
+- Styled, responsive quickstart workspace with preview transport and an in-browser local export panel.
+- Explicit rendering-tool download, prerequisite checks, build/render status, actionable errors and completed MP4 downloads.
+- Browser exports save unique videos and manifests in `renders/` without replacing earlier exports; CLI export remains available.
+
+## 0.1.0
+
+- Initial public `@machinal/scenes` distribution, combining the runtime and Svelte integration in one package.
+- Root, `/runtime`, `/svelte` and `/node` entrypoints with TypeScript declarations.
+- Frame-based seeking, resource readiness, CSS animation seeking and reproducible seeded randomness.
+- Svelte 5 canvas, video and Three.js scene integration with choreography, geometry and object helpers.
+- Standalone Vite quickstart, with no account or native-rendering setup required for preview.
+- `machinal-scenes init <directory>` scaffolds the quickstart without overwriting existing directories or installing tools automatically.
+- Precompiled Go renderers and their source/notices are included for Windows x64, Linux x64, macOS x64 and macOS arm64.
+- Explicit `setup`, `doctor` and `render` commands plus Node `renderVideo()` export real H.264 MP4 and VP9/alpha WebM, without Go or a private service on the user's machine.
+- Pinned native-tool provisioning retains FFmpeg license/build information and verifies its published release hashes.
+- The starter builds a dedicated capture page, separate from preview UI, and includes `npm run render`.
+
+The private Machinal service is not included in the npm distribution. External Chrome and FFmpeg programs retain their own licenses and are provisioned separately by `setup`.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/LICENSING.md

@@ -0,0 +1,13 @@
+# License scope
+
+The Apache License, Version 2.0 applies to the original `@machinal/scenes` library and renderer code in this repository: `runtime/`, `svelte/`, `node/`, `bin/`, `renderer/`, `examples/quickstart/`, `scripts/`, `tests/`, configuration and documentation. Copyright belongs to the respective contributors.
+
+The same license covers the generated distribution in `dist/` and original-code portions of the compiled native renderers.
+
+The native executables also contain Go standard-library and third-party code under their respective licenses, reproduced in `native/THIRD_PARTY_NOTICES.txt`. Those notices are not replaced by the Apache license for the project's original code.
+
+Chrome/Chromium and FFmpeg are separate external programs, downloaded only by explicit `setup` or supplied by the user. They are not included in the npm tarball and are not relicensed under Apache-2.0. FFmpeg builds may be GPL/LGPL licensed; their license and build/source information are downloaded, checksum-verified and retained in the tool cache. Anyone redistributing those programs must comply with their own applicable terms.
+
+The separate Machinal application, private services, application integration adapters and project media are not included in this repository or npm package. This license does not grant rights to those separate products or content.
+
+Other npm dependencies retain their respective licenses. No permission to use Machinal trademarks is granted beyond the Apache License's provisions.

package/NOTICE

@@ -0,0 +1,8 @@
+@machinal/scenes
+Copyright 2026 Catalin Flintasu.
+
+This product includes the frame-driven scene runtime, Svelte integration and renderer
+developed for Machinal. It is distributed under the Apache License, Version 2.0.
+
+Third-party dependencies retain their own copyright and license notices.
+Native executable dependency notices are provided in native/THIRD_PARTY_NOTICES.txt.

package/README.md

@@ -1,3 +1,184 @@
-# Temporary Holding Version
+# @machinal/scenes
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Author, preview and render frame-driven **Svelte 5**, HTML/CSS and Three.js scenes to **MP4 and WebM** with Go.
+
+One npm package contains the runtime, Svelte integration, Node rendering API, CLI and precompiled native renderer. No private service or Go installation is required to author or export a video.
+
+## Install
+
+In a Svelte 5 project with a Svelte-aware bundler, such as Vite:
+
+```sh
+npm install @machinal/scenes
+```
+
+Requires Node.js 22.12+ and Svelte 5.15+. Three.js and its public TypeScript types are installed as dependencies. There are no install scripts: Chromium and FFmpeg are downloaded only when you explicitly run `setup` or click **Download rendering tools** in the starter. The native renderer is already in the package. Run `npm install` inside a project directory, not a drive root such as `D:\`.
+
+The library is ESM. The root and `/svelte` entrypoints contain Svelte components and runes, so they must be processed by a Svelte-aware bundler. Use `/runtime` for framework-independent code, plain Node.js imports and manifest validation.
+
+## From a new project to an MP4
+
+```sh
+npx @machinal/scenes init my-scene
+cd my-scene
+npm install
+npm run setup
+npm run render
+```
+
+This creates **`scene.mp4`** and **`scene.mp4.scene.json`**, a manifest containing the output's dimensions, duration, frame count and SHA-256. `setup` is a one-time download of pinned Chrome Headless Shell and FFmpeg into a user cache; it checks that the tools execute. `npm run render` builds the scene with Vite and exports the video locally using the included renderer.
+
+The CLI shows readable tool status and a short export summary, not the internal metadata report. For scripts that need the complete JSON result, use `npm run setup -- --json`, `npm run doctor -- --json` or `npm run render -- --json`. Progress stays on stderr; call `machinal-scenes render --json` directly for JSON-only stdout (the npm script also prints Vite build output). The Node API and saved manifests always retain the full metadata.
+
+For the browser workflow, run `npm run dev` and open the local URL shown in the terminal:
+
+1. **Preview**: play, pause, reset or scrub the default **1280 × 720** scene, scaled to fit the available preview space. No rendering tools are required.
+2. **Download rendering tools**: the export panel checks the included renderer, Chrome and FFmpeg. If tools are missing, this explicit action downloads them once to your user cache. Already installed tools are marked **Ready**.
+3. **Render MP4**: builds the current scene source and exports it locally, with visible status and renderer progress.
+4. **Download MP4**: saves the completed video through your browser. A copy and its manifest also remain in a **local** `renders/` directory, created inside the starter next to its `package.json` when you render. For example, a starter at `D:\my-scene` saves browser exports under `D:\my-scene\renders\`. The completed export shows the full local path. Each export uses a unique filename; previous exports are preserved. Nothing is uploaded to S3 or Machinal, and the tool does not connect to your application or any Machinal project.
+
+The browser export actions run only through the loopback Vite development server (`npm run dev`), not on a statically hosted build or `npm run preview`. They require same-origin requests; there is no cloud render service or automatic download on page load. The terminal workflow above remains available.
+
+Edit `src/Title.svelte` to change the artwork and `scene.config.json` to change dimensions, FPS, duration, props or audio. `npm run doctor` checks rendering prerequisites without downloading anything.
+
+The initializer refuses to overwrite an existing directory. Rendering also refuses to replace an existing video or manifest. Choose another output filename for another export:
+
+```sh
+npm run render -- --output second.mp4
+```
+
+The starter uses separate preview and capture pages. `scene.html` contains only the scene, so exported video does not include the preview's buttons, slider or heading.
+
+## Your first scene
+
+Create `Title.svelte`:
+
+```svelte
+<script lang="ts">
+  import { SceneCanvas, useScene, interpolate } from '@machinal/scenes';
+
+  let { title = 'Hello, scenes!' }: { title?: string } = $props();
+  const scene = useScene();
+  const x = $derived(interpolate(scene.frame.frame, [0, 60], [0, 200]));
+</script>
+
+<SceneCanvas background="#f5f2eb">
+  <h1 style:transform="translateX({x}px)">{title}</h1>
+</SceneCanvas>
+```
+
+Mount it from your browser entrypoint:
+
+```ts
+import { mountSvelteScene, exposeScene, type SceneRequest } from '@machinal/scenes';
+import Title from './Title.svelte';
+
+const request: SceneRequest = {
+  version: 1,
+  sceneId: 'title',
+  props: { title: 'Hello, scenes!' },
+  config: { width: 1280, height: 720, fps: 30, durationInFrames: 180 },
+};
+
+const controller = mountSvelteScene(
+  Title,
+  document.getElementById('scene')!,
+  request,
+  {},
+);
+const disconnect = exposeScene(controller);
+await controller.ready();
+await controller.seek(30); // One second into the scene; indexes start at zero.
+
+window.addEventListener('pagehide', () => {
+  disconnect();
+  void controller.dispose();
+}, { once: true });
+```
+
+Add `<div id="scene"></div>` to the page. `useScene()` and `SceneCanvas` must run inside a scene mounted with `mountSvelteScene()`; rendering them directly in an unrelated Svelte component does not establish scene context. In SvelteKit, mount from `onMount` and dispose on unmount rather than running this code during SSR.
+
+`seek()` updates the Svelte component, seeks supported CSS animations and video, and waits for tracked resources, DOM images and fonts. Playback is driven by the host requesting frames; mounting does not automatically start a wall-clock animation.
+
+## API map
+
+| Import | Includes |
+| --- | --- |
+| `@machinal/scenes` | Runtime helpers and all Svelte components |
+| `@machinal/scenes/runtime` | Frame/controller protocol, resources, seeded randomness, interpolation, choreography, geometry, object parameters, layout and asset-manifest validation; no Svelte or Three.js imports |
+| `@machinal/scenes/svelte` | `mountSvelteScene`, `useScene`, `SceneCanvas`, `SceneVideo`, `SceneThree`, Three.js camera/light helpers and controlled model/texture loading |
+| `@machinal/scenes/node` | Local `setup()`, `doctor()` and `renderVideo()`; no Svelte compilation or private service required to run a built scene |
+
+All entrypoints belong to **one installed package**, not separate npm dependencies. Keep `/node` imports in Node/server code, not browser bundles. Internal source paths are not public entrypoints. Version `0.1.x` is an initial API; consult the changelog when upgrading.
+
+### Three.js and media
+
+`SceneThree` owns a Three.js renderer. Its `setup(context)` returns `update(frame)` and optional `dispose()`, synchronously or through a tracked promise. Derive transforms from absolute `frame.time`; do not accumulate deltas across seeks.
+
+`SceneVideo` follows scene time, including backward seeks, reverse playback and freeze frames. Its media is silent: page audio is not captured by this library. Mix narration/music separately in the renderer.
+
+For non-DOM resources, use `scene.resources.track(promise)` and honor `scene.resources.signal`. Arbitrary timers, network responses and third-party animation timelines are not made deterministic automatically. Pixel identity across browsers, operating systems and GPUs is not guaranteed.
+
+## Local rendering
+
+The included precompiled renderer supports **Windows x64, Linux x64, macOS x64 and macOS arm64**. The browser runtime can be used elsewhere, but native export on other targets is not supported in this release. No compilation is performed on the user's machine.
+
+For an existing built scene project:
+
+```sh
+npx machinal-scenes setup
+npx machinal-scenes render --request scene.config.json --serve dist --output output.mp4
+```
+
+The built page must mount and expose the scene controller as shown above. The request includes `url: "/scene.html"` in addition to the scene request fields. `--serve` starts an ephemeral loopback-only file server; it does not start or require the private Machinal service.
+
+From Node:
+
+```ts
+import { setup, renderVideo } from '@machinal/scenes/node';
+
+await setup(); // Explicit one-time downloads; omit after provisioning.
+const asset = await renderVideo({
+  request: 'scene.config.json',
+  serveDirectory: 'dist',
+  output: 'output.mp4',
+  onProgress: message => process.stderr.write(message),
+});
+console.log(asset.file, asset.sha256);
+```
+
+`request` accepts a JSON/YAML filename or a `RenderRequest` object. Audio filenames in request files resolve relative to that file; object audio paths resolve relative to the working directory. Audio is mixed by FFmpeg, not captured from the browser.
+
+For real alpha, set `config.transparent: true` and choose a `.webm` output. The renderer uses VP9 alpha; MP4 output is opaque H.264. `--lossless`, `--workers` and `--gpu` are available; run `npx machinal-scenes render --help` for options.
+
+`setup` pins Chrome Headless Shell `151.0.7922.34` from Chrome for Testing and FFmpeg release `b6.1.1` from `eugeneware/ffmpeg-static`. FFmpeg archives, licenses and build information are checked against pinned SHA-256 values; native renderer binaries are checked against the packaged manifest. Browser downloads use the official HTTPS distribution and a fixed version; no independent browser checksum is asserted. FFmpeg's license and build/source information are retained beside the cached executable.
+
+Use `--cache-dir` or `MACHINAL_SCENES_CACHE` to select another cache. Existing tools can be supplied with absolute `--browser`/`--ffmpeg` paths, the `SCENE_BROWSER`/`SCENE_FFMPEG` environment variables, or the Node API's `browserExecutable`/`ffmpegExecutable` options. Custom browser/tool versions are your compatibility responsibility.
+
+Linux requires glibc, `unzip`, and Chromium's system libraries (NSS, ATK, X11, GBM, ALSA and related dependencies); minimal containers must provision them first. Windows uses its built-in `tar.exe` for browser extraction; macOS needs `unzip`. `setup` never runs privileged package-manager commands. Run as a non-root user to retain normal Chromium sandbox behavior. `--no-sandbox` is for externally isolated containers; the underlying chromedp allocator also disables the sandbox when launched as root.
+
+Scenes are executable code, not a security sandbox. Use trusted scenes or provide your own execution isolation, authorization and resource limits.
+
+## VS Code reports missing children or rejects onclick
+
+These two diagnostics can appear together when the Svelte extension is running in **Restricted Mode**:
+
+```text
+Property 'children' is missing in type '{ background: string; }'
+'"onclick"' does not exist in type 'HTMLProps<"button", HTMLAttributes<any>>'
+```
+
+In an untrusted workspace, the extension avoids loading the project's local compiler and can fall back to its bundled Svelte 4 compiler/types. The starter uses Svelte 5: nested component content supplies the `children` snippet, and `onclick` is a supported button attribute.
+
+Open the generated starter directory itself in VS Code and run `npm install` there. If you have reviewed and trust its code, use **Workspaces: Manage Workspace Trust** to trust only that folder, then **Svelte: Restart Language Server**. Do not disable Workspace Trust globally. You can also validate the project independently of the editor:
+
+```sh
+npm run check
+npm ls svelte
+```
+
+With the local Svelte 5 compiler, these starter components should pass the check. If the terminal also reports errors, investigate those diagnostics and the installed dependency versions rather than treating them as an editor-only issue. Do not make `SceneCanvas.children` optional or replace Svelte 5 event handlers just to suppress a mismatched editor diagnostic.
+
+## License
+
+Apache-2.0 for the library and renderer sources. See [LICENSE](LICENSE), [NOTICE](NOTICE), [LICENSING.md](LICENSING.md) and the included native third-party notices. Downloaded Chrome/FFmpeg and dependencies retain their own licenses; in particular, the downloaded FFmpeg builds have separate GPL/LGPL terms. This package license does not relicense those tools, the surrounding Machinal application or its private services.

package/bin/machinal-scenes.mjs

@@ -0,0 +1,89 @@
+#!/usr/bin/env node
+import { cp, mkdir, readFile, rename } from 'node:fs/promises';
+import { join, resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { parseArgs } from 'node:util';
+import { doctor, renderVideo, setup } from '../node/index.mjs';
+import { formatRenderResult, formatToolchainStatus } from '../node/cli-output.mjs';
+
+const help = `@machinal/scenes
+
+Usage:
+  machinal-scenes init <directory>  Create a standalone Svelte/Vite scene project
+  machinal-scenes setup             Install pinned Chromium and FFmpeg once
+  machinal-scenes doctor            Check the packaged renderer and local tools
+  machinal-scenes render            Render scene.config.json + dist/ to scene.mp4
+  machinal-scenes --version        Print the installed version
+  machinal-scenes --help           Show this help
+
+Render options:
+  --request <file>   JSON/YAML request (default: scene.config.json)
+  --serve <dir>      Built scene directory (default: dist)
+  --output <file>    New MP4/WebM filename (default: scene.mp4)
+  --workers <1-16>   Frame-capture workers (default: 2)
+  --lossless        Lossless intermediate encoding
+  --gpu             Enable hardware GPU rendering
+  --no-sandbox      Explicitly disable Chromium sandbox (isolated containers only)
+
+Setup/doctor/render options:
+  --json            Print complete metadata instead of a readable summary
+  --browser <file>   Use an existing Chrome/Chromium executable
+  --ffmpeg <file>    Use an existing FFmpeg executable
+  --cache-dir <dir>  Override the native-tool cache
+
+Only setup downloads tools. Rendering is local and requires no Go installation,
+Machinal account, API key or private service. Existing output files are never replaced.
+`;
+
+async function run(args) {
+  if (args.length === 0 || args.length === 1 && ['--help', '-h'].includes(args[0])) {
+    console.log(help);
+    return;
+  }
+  if (args.length === 1 && ['--version', '-v'].includes(args[0])) {
+    const manifest = JSON.parse(await readFile(new URL('../package.json', import.meta.url), 'utf8'));
+    console.log(manifest.version);
+    return;
+  }
+  if (['setup', 'doctor', 'render'].includes(args[0])) {
+    await runTools(args[0], args.slice(1));
+    return;
+  }
+  if (args.length !== 2 || args[0] !== 'init' || !args[1].trim() || args[1].startsWith('-')) throw new Error(`Expected a supported command.\n\n${help}`);
+
+  const destination = resolve(args[1]);
+  try {
+    await mkdir(destination);
+  } catch (error) {
+    if (error.code === 'EEXIST') throw new Error(`Destination already exists: ${destination}. No files were changed.`);
+    throw error;
+  }
+  await cp(fileURLToPath(new URL('../examples/quickstart/', import.meta.url)), destination, {
+    recursive: true, errorOnExist: true, force: false,
+  });
+  await rename(join(destination, 'gitignore'), join(destination, '.gitignore'));
+  console.log(`Created ${destination}\n\nOpen this directory, then run:\n  npm install\n  npm run dev\n\nIn the browser, use Download rendering tools (once), Render MP4, then Download MP4.\n\nTerminal alternative:\n  npm run setup\n  npm run render`);
+}
+
+async function runTools(command, args) {
+  const common = { help: { type: 'boolean' }, json: { type: 'boolean' }, browser: { type: 'string' }, ffmpeg: { type: 'string' }, 'cache-dir': { type: 'string' } };
+  const rendering = { request: { type: 'string' }, serve: { type: 'string' }, output: { type: 'string' }, workers: { type: 'string' }, lossless: { type: 'boolean' }, gpu: { type: 'boolean' }, 'no-sandbox': { type: 'boolean' } };
+  const { values } = parseArgs({ args, options: { ...common, ...(command === 'render' ? rendering : {}) }, strict: true, allowPositionals: false });
+  if (values.help) { console.log(help); return; }
+  const options = { browserExecutable: values.browser, ffmpegExecutable: values.ffmpeg, cacheDirectory: values['cache-dir'] };
+  if (command === 'render') {
+    const result = await renderVideo({ ...options, request: values.request ?? 'scene.config.json', serveDirectory: values.serve ?? 'dist', output: values.output ?? 'scene.mp4', workers: values.workers === undefined ? undefined : Number(values.workers), lossless: values.lossless, gpu: values.gpu, noSandbox: values['no-sandbox'], onProgress: message => process.stderr.write(message) });
+    console.log(values.json ? JSON.stringify(result, null, 2) : formatRenderResult(result));
+    return;
+  }
+  const result = command === 'setup' ? await setup({ ...options, onProgress: message => console.error(message) }) : await doctor(options);
+  console.log(values.json ? JSON.stringify(result, null, 2) : formatToolchainStatus(result));
+  if (!result.ready) process.exitCode = 1;
+}
+
+try {
+  await run(process.argv.slice(2));
+} catch (error) {
+  console.error(error instanceof Error ? error.message : String(error));
+  process.exitCode = 1;
+}

package/dist/index.d.ts

@@ -0,0 +1,3 @@
+/// <reference types="@webgpu/types" />
+export * from './runtime/index.js';
+export * from './svelte/index.js';

package/dist/index.js

@@ -0,0 +1,2 @@
+export * from './runtime/index.js';
+export * from './svelte/index.js';

package/dist/runtime/artifact.d.ts

@@ -0,0 +1,18 @@
+import type { SceneManifest } from './types.js';
+export interface RenderedSceneAsset {
+    version: 1;
+    file: string;
+    sha256: string;
+    size: number;
+    duration: number;
+    width: number;
+    height: number;
+    fps: number;
+    frames: number;
+    hasAudio: boolean;
+    transparent: boolean;
+    codec: 'h264' | 'vp9';
+    scene: SceneManifest;
+    elapsedNanoseconds: number;
+}
+export declare function parseRenderedSceneAsset(value: unknown): RenderedSceneAsset;

package/dist/runtime/artifact.js

@@ -0,0 +1,26 @@
+import { validateRequest } from './validation.js';
+export function parseRenderedSceneAsset(value) {
+    if (!value || typeof value !== 'object')
+        throw new Error('Scene asset manifest must be an object');
+    const asset = value;
+    if (asset.version !== 1 || typeof asset.file !== 'string' || !asset.file.trim())
+        throw new Error('Invalid scene asset identity');
+    if (typeof asset.sha256 !== 'string' || !/^[a-f0-9]{64}$/.test(asset.sha256))
+        throw new Error('Invalid scene asset SHA-256');
+    if (!Number.isSafeInteger(asset.size) || asset.size <= 0)
+        throw new Error('Invalid scene asset size');
+    if (asset.codec !== 'h264' && asset.codec !== 'vp9')
+        throw new Error('Unsupported scene asset codec');
+    if (typeof asset.hasAudio !== 'boolean' || typeof asset.transparent !== 'boolean')
+        throw new Error('Invalid scene asset media flags');
+    validateRequest(asset.scene);
+    const config = asset.scene.config;
+    if (asset.width !== config.width || asset.height !== config.height || asset.fps !== config.fps || asset.frames !== config.durationInFrames || asset.transparent !== Boolean(config.transparent)) {
+        throw new Error('Scene asset dimensions or timing do not match its scene');
+    }
+    if (!Number.isFinite(asset.duration) || Math.abs(asset.duration - asset.frames / asset.fps) > 0.000001)
+        throw new Error('Invalid scene asset duration');
+    if (asset.transparent && asset.codec !== 'vp9')
+        throw new Error('Transparent scenes require VP9');
+    return structuredClone(asset);
+}

package/dist/runtime/bridge.d.ts

@@ -0,0 +1,8 @@
+import type { SceneController, SceneManifest } from './types.js';
+export declare function exposeScene(controller: SceneController, view?: Window): () => void;
+export interface SceneConnection {
+    ready: () => Promise<SceneManifest>;
+    seek: (frame: number) => Promise<SceneManifest>;
+    dispose: () => void;
+}
+export declare function connectScene(iframe: HTMLIFrameElement, timeoutMs?: number): SceneConnection;