Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.
TypeScript agentic-aiaiai-agentsai-videocompilerdslffmpeggenerative-aillmmarkup-languagemonorepoplugin-systemprogramming-languagetext-to-videotypescriptvideovideo-automationvideo-clonevideo-editingvideo-generation
docs: align public guidance with the 0.3 architecture
kashorina54f7ee8cc68
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex 6034251e..27284ff0 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -31,7 +31,7 @@ For a Profile selecting local rendering, run `hypit programs up --runtime <profi<render-instance>` before the first render (or `hypit runtime up --runtime <profile>` to preparethe Profile and start its Worker). This explicitly prepares Chrome even when pnpm skips dependencybuild scripts. `hypit doctor --runtime <profile>` diagnoses missing setup without installing it.-See the [local renderer README](packages/provider-hyperframes-local/README.md) for browser overrides.+See the [local renderer README](packages/provider-html-local/README.md) for browser overrides.## Make the changediff --git a/CONTRIBUTING.zh-CN.md b/CONTRIBUTING.zh-CN.mdindex c965c29a..2a9edf6e 100644--- a/CONTRIBUTING.zh-CN.md+++ b/CONTRIBUTING.zh-CN.md@@ -26,7 +26,7 @@ pnpm install --frozen-lockfile`hypit runtime up --runtime <profile>`,准备整个 Profile 并启动 Worker。这一步显式准备 Chrome,不依赖 pnpm 放行依赖安装脚本。`hypit doctor --runtime <profile>` 只诊断,不安装。-浏览器路径配置见[本地渲染器 README](packages/provider-hyperframes-local/README.md)。+浏览器路径配置见[本地渲染器 README](packages/provider-html-local/README.md)。## 进行改动diff --git a/docs/guide/author-packages.md b/docs/guide/author-packages.mdindex 70f667e9..f869ca88 100644--- a/docs/guide/author-packages.md+++ b/docs/guide/author-packages.md@@ -48,8 +48,8 @@ chosen names and the accepted values in the component's own vocabulary and READM## Implement and inspect the scene-Use `@hypit/hypit/author-kit` for the author package API and public domain subpaths for the values you-consume. [Component Anatomy](./component-anatomy.md) explains how the Manifest, Surface, Fragment and+Use the narrow `author`, `producer`, `admission` and `markup` public subpaths for their respective+responsibilities, and public domain subpaths for the values you consume. [Component Anatomy](./component-anatomy.md) explains how the Manifest, Surface, Fragment andProducer cooperate. Keep project copy and media as inputs; draw the component's own panels, framesand decoration in its implementation.@@ -58,7 +58,7 @@ explain the behavior: entry, meaningful changes, held layout and exit. Check theactual composition too, where its content, space and timing have a purpose.For richer interactive editing, add a Studio Companion. The-[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md)+[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md)shows how to expose timeline entities, properties and source bindings. The rendering code andCompanion are separate contributions in the same package.diff --git a/docs/guide/component-anatomy.md b/docs/guide/component-anatomy.mdindex 22fa9db3..bb68c85e 100644--- a/docs/guide/component-anatomy.md+++ b/docs/guide/component-anatomy.md@@ -26,8 +26,8 @@ These roles can be organized into files that suit the component's size:| Activation | Publish the contributions the selected package offers || Studio Companion | Describe timeline entities and editable properties for Studio |-The [Author SDK](https://github.com/hypit-ai/hypit/blob/main/packages/author-kit/README.md)-and included example own the exact object shapes. A small component can keep related roles together;+The [Author Package guide](./author-packages.md) and included example route each exact object shape to+its owning API. A small component can keep related roles together;a larger component benefits from separating reusable scheduling, styling and drawing logic.## Design around relationshipsdiff --git a/docs/guide/conventions.md b/docs/guide/conventions.mdindex 4abe76a8..70c4da96 100644--- a/docs/guide/conventions.md+++ b/docs/guide/conventions.md@@ -9,8 +9,8 @@ These conventions describe work inside the Hypit repository. Project extensions| Thing | Convention | Example ||---|---|---|-| Package directory | kebab-case | `packages/speech-alignment/` |-| Package name | `@hypit/` scope | `@hypit/speech-alignment` |+| Package directory | kebab-case | `packages/narrative-speech-alignment/` |+| Package name | `@hypit/` scope | `@hypit/narrative-speech-alignment` || Provider package | `provider-` prefix | `@studio/provider-images` || TypeScript file | kebab-case | `align.ts` || Exported type | PascalCase | `SpeechAlignment` |diff --git a/docs/guide/develop.md b/docs/guide/develop.mdindex 0eae8295..be71d1fa 100644--- a/docs/guide/develop.md+++ b/docs/guide/develop.md@@ -12,7 +12,7 @@ description: Getting started with Hypit development.| Python | 3.10–3.13 | local WhisperX and OpenCV Managed Programs || uv | latest | Python environment management || ffmpeg / ffprobe | recent stable | media processing |-| Chrome / Chromium | downloaded by `hypit runtime up` | local HyperFrames rendering |+| Chrome / Chromium | downloaded by `hypit runtime up` | local HTML rasterization |Node.js and pnpm are the only hard requirements. The rest are needed only for live Builds.diff --git a/docs/guide/packages.md b/docs/guide/packages.mdindex 802cf626..612e2465 100644--- a/docs/guide/packages.md+++ b/docs/guide/packages.md@@ -42,9 +42,9 @@ The consumer installs a chosen version and keeps its lockfile with the project.The Skill, executable Distribution and video project are installed and updated separately. The`@hypit/hypit` Distribution includes the official author packages and public extension APIs. Its selected-Runtime adapters can prepare additional service dependencies through `hypit runtime up`; optional-author assets can be installed with the precise `hypit packages install` command reported by the CLI.-A project's own component dependencies are managed in that project.+Runtime adapters can prepare their declared services and other runtime materials through+`hypit runtime up`. npm dependencies are installed with the package that owns them: Distribution+dependencies with the Distribution, and project component dependencies with the project.Source uses a logical Module address such as `@your-studio/scoreboard@1`. npm's installed packageversion selects the implementation; the logical `@1` identifies its author interface. Building a@@ -53,8 +53,10 @@ install them.## Write and share an extension-An external package develops against public subpaths such as `@hypit/hypit/author-kit`,-`@hypit/hypit/composition`, `@hypit/hypit/model-kit` or `@hypit/hypit/endpoint-kit`. Use the selected `@hypit/hypit` release as a+An external package develops against the narrow public owners it uses, such as+`@hypit/hypit/author`, `@hypit/hypit/producer`, `@hypit/hypit/admission`,+`@hypit/hypit/markup`, `@hypit/hypit/composition`, `@hypit/hypit/generation/model` or+`@hypit/hypit/endpoint`. Use the selected `@hypit/hypit` release as adevelopment dependency, compile the extension to JavaScript, and ship its own code and assets. Its`package.json` names an activation entry describing what it provides. The active Distributionsupplies the public Hypit APIs when it loads the selected extension.diff --git a/docs/guide/providers.md b/docs/guide/providers.mdindex 80a48770..90a26726 100644--- a/docs/guide/providers.md+++ b/docs/guide/providers.md@@ -59,12 +59,13 @@ deployment and executing a video Build have separate lifetimes.## Add a Model-Develop a project package against `@hypit/hypit/model-kit`, `@hypit/hypit/generation` and `@hypit/hypit/author-kit`.+Develop a project package against `@hypit/hypit/generation/model`, `@hypit/hypit/generation`,+`@hypit/hypit/author`, `@hypit/hypit/producer`, `@hypit/hypit/admission` and `@hypit/hypit/markup`.Declare the exact request ports, parameter values, result type and capability. Its author Surfaceconnects prompt Text and reference media to the request, then publishes the resulting media as anormal graph Output.-The [Model SDK](https://github.com/hypit-ai/hypit/blob/main/packages/model-kit/README.md) includes a+The [Generation Model authoring API](https://github.com/hypit-ai/hypit/blob/main/packages/generation/README.md#exact-model-authoring) includes arequest definition and explains activation. The package owns the model interface; credentials andHTTP mapping belong to the Provider.@@ -73,8 +74,8 @@ HTTP mapping belong to the Provider.Use the selected `@hypit/hypit` release as a development dependency and import the public SDK:```ts-import { defineEndpointPackage } from "@hypit/hypit/endpoint-kit";-import type { AsyncEndpoint, CredentialRef, EndpointRequest } from "@hypit/hypit/endpoint-kit";+import { defineEndpointPackage } from "@hypit/hypit/endpoint";+import type { AsyncEndpoint, CredentialRef, EndpointRequest } from "@hypit/hypit/endpoint";```Implement the exact capabilities and result types the service supports. Map request ports to the@@ -85,7 +86,7 @@ Concurrency and action limits belong to the Endpoint's resource declarations.A genuine failure ends that execution attempt. Build Results preserve completed Outputs and publictask receipts. Further work uses a new Run and Build with suitable existing Outputs selected for reuse.-The [Endpoint SDK](https://github.com/hypit-ai/hypit/blob/main/packages/endpoint-kit/README.md)+The [Endpoint SDK](https://github.com/hypit-ai/hypit/blob/main/packages/endpoint/README.md)owns the handler interfaces, activation, resource declarations and pricing API. Compile the packageto JavaScript and install it in the project through its package manager. Configure its Endpointunder `endpoints` and select it in `bindings` in the [Runtime Profile](./runtime.md).diff --git a/docs/guide/runtime.md b/docs/guide/runtime.mdindex 295307f0..a3f7a607 100644--- a/docs/guide/runtime.md+++ b/docs/guide/runtime.md@@ -19,9 +19,9 @@ Core plans and advances dependencies without knowing that they make a video. A n## Select the project and Profile-Run commands from the video project, or select it explicitly with `--workspace`. Otherwise the-nearest `package.json` above the current directory establishes the project; when none exists, the-current directory is the project. Source filenames and Runtime configuration do not choose this boundary.+Run commands from a project whose `package.json` declares `"hypit": { "project": true }`, or select+it explicitly with `--project`. Otherwise the CLI searches upward for that marker. An Author Package,+arbitrary directory, Source filename or Runtime configuration does not choose this boundary.```bashhypit paths@@ -48,7 +48,7 @@ A small local-processing Profile looks like this:"dataRoot": ".hypit/runtimes/local","credentials": {},"endpoints": {- "media.local": { "use": "@hypit/provider-media-local" }+ "media.local": { "use": "@hypit/media-local" }},"bindings": {}}@@ -145,21 +145,10 @@ of files a component reads later.## Keep products with the project-Without extra configuration, Results live in `.hypit/results`. A project can select another location-or repository through `hypit.results.json`, independently of its Runtime Profile:--```json-{- "format": "hypit.build-results@1",- "use": "@hypit/build-result-fs",- "config": { "path": ".hypit/results" }-}-```--The S3 adapter can instead store Results in a bucket and project prefix. The selected adapter owns-access and credentials; changing Result storage does not move the active Runtime or upload external-file references automatically. A submitted Build retains its chosen destination, and changing that-selection does not migrate history.+Results live with the project in `.hypit/results` on the machine running Hypit. A local workstation,+an SSH Linux host and the official WebUI backend use the same rule: the whole Runtime moves to that+host instead of splitting its queue, working files and Result storage across services. Archive or+migrate completed Results explicitly after a Build when needed.Results publish completed public Outputs as they become available and retain the terminal outcome.A new Output can reference an existing file, including within a composite; it does not necessarily@@ -168,5 +157,5 @@ future reuse. `get` creates a separate export when a person or another tool need`builds`, `history`, `inspect` and `get` read project Results without requiring the original Runtime.For exact storage and execution interfaces, see the-[Result package](https://github.com/hypit-ai/hypit/blob/main/packages/build-result/README.md) and+[Result package](https://github.com/hypit-ai/hypit/blob/main/packages/result/README.md) and[local Runtime package](https://github.com/hypit-ai/hypit/blob/main/packages/runtime-local/README.md).diff --git a/docs/guide/service-partners.md b/docs/guide/service-partners.mdindex ff980ab9..754b64a6 100644--- a/docs/guide/service-partners.md+++ b/docs/guide/service-partners.md@@ -12,11 +12,16 @@ Providers, and users can connect their own services through project Providers.The services introduced below are independent partners. They have their own accounts, terms,prices, model availability and APIs. A partnership is an introduction, not a shared HypiHub account.-The Distribution bundles an API-key Provider for each service named below; each Provider maps the-installed models that service offers and reports that service's input limits, and its README lists-both. A model the service offers beyond that set connects through the ordinary+Each service Provider below is an independently versioned npm package. Install the one the project+selects with the ordinary package manager, then name it in the Runtime Profile; merely installing it+does not activate the service. Each Provider maps the installed models that service offers and reports+that service's input limits, and its README lists both. A model the service offers beyond that set connects through the ordinary[Model and Provider](./providers.md) extension path.+```bash+npm install @hypit/provider-tokendance+```+## Model and tool API partners### TokenDance@@ -73,4 +78,4 @@ account owns compute and deployment costs; HypiHub credits do not pay for that d[Using your own deployment](./providers.md#use-your-own-model-deployment) explains what changes whenyou own the serving environment. A deployment can be used without a partnership or an officially-bundled Provider.+maintained Provider.diff --git a/docs/guide/studio-companion-architecture.md b/docs/guide/studio-companion-architecture.mdindex cf36bc19..7c0d3a89 100644--- a/docs/guide/studio-companion-architecture.md+++ b/docs/guide/studio-companion-architecture.md@@ -14,8 +14,8 @@ facet in the same physical package. The official Distribution supplies its Compaindependent packages. In both cases, Studio loads the Companions for the packages selected by thecurrent Source and Distribution.-The [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md)-provides the activation and interface examples. External packages import `@hypit/hypit/studio-adapter`,+The [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md)+provides the activation and interface examples. External packages import `@hypit/hypit/studio-companion`,compile the Companion to JavaScript, and ship it with the component. Restart Studio after changingthe installed code so the new contribution is loaded.diff --git a/docs/guide/testing.md b/docs/guide/testing.mdindex 40e634a0..e6bd7fcc 100644--- a/docs/guide/testing.md+++ b/docs/guide/testing.md@@ -52,8 +52,8 @@ exports, Records or plan steps. Never calls an external service.```typescripttest("compiles the expected exports", async () => {const compiler = createCompiler({ root, packageContributions });- const workspace = await compiler.openFile("fixture.svml");- const result = await compiler.compileSource(workspace.entry, workspace);+ const workspace = await compiler.openEntry("fixture.svml");+ const result = await compiler.compileResolvedSource(workspace.entry, workspace);assert.equal(result.exports.length, 3);});```@@ -80,12 +80,12 @@ explicitly opt-in, use no committed secret and incur no cost when not enabled.| Command | What it tests | Prerequisites ||---|---|---|| `pnpm test:whisperx-service` | Python WhisperX service | Python 3.13, uv, frozen sync |-| `pnpm test:image-opencv` | the shared OpenCV Raster interpreter across both request variants | the service's own interpreter at `services/image-opencv/.venv`; set `HYPIT_OPENCV_PYTHON` to use another |+| `pnpm test:image-opencv` | the OpenCV Provider across Transform and Compose | the Provider's interpreter at `packages/provider-image-opencv-local/runtime/.venv`; set `HYPIT_OPENCV_PYTHON` to use another |-For the local HyperFrames browser render tests, set `HYPIT_BROWSER_TESTS=1` in your shell environment, then run the command below from the repository root. Chrome, ffmpeg and ffprobe must be available.+For the local HTML rasterization tests, set `HYPIT_BROWSER_TESTS=1` in your shell environment, then run the command below from the repository root. Chrome, ffmpeg and ffprobe must be available.```sh-node --import tsx --test packages/provider-hyperframes-local/test/provider.test.ts+node --import tsx --test packages/provider-html-local/test/provider.test.ts```## Test fixturesdiff --git a/docs/quickstart/composition.md b/docs/quickstart/composition.mdindex 54c2293d..807e0819 100644--- a/docs/quickstart/composition.md+++ b/docs/quickstart/composition.md@@ -10,7 +10,7 @@ Composition into a video.```svml<import as="space" from="@hypit/spatial@1"/><import as="film" from="@hypit/film@1"/>-<import as="render" from="@hypit/render-hyperframes@1"/>+<import as="html" from="@hypit/html-video@1"/>```## Assemble the Film@@ -68,22 +68,22 @@ caption.base { stack-order: 70; }```Presents from different Tracks can interleave. A Present may also own an internal element tree or a-browser program when several pictures, graphics and text share layout or motion. Put content together+HTML visual when several pictures, graphics and text share layout or motion. Put content togetherwhen its behavior belongs together; keep independently useful contributions as peers.## Render the complete video```svml-<render:Video id="final"+<html:Video id="final"composition={main.composition} timeline={speech.timeline}/>```The renderer compiles the visual contributions, captures requested frames, renders AudioTracks and-muxes them into the delivered file. `{final.video}` is an ordinary Resource-backed `BlobArtifact` and+muxes them into the delivered file. `{final.video}` is an ordinary Resource-backed `Blob` andthe usual Run Target.```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/><target output="final.video"/>@@ -93,7 +93,7 @@ the usual Run Target.## Render a frame interval```svml-<render:Video id="detail" composition={main.composition} timeline={speech.timeline}+<html:Video id="detail" composition={main.composition} timeline={speech.timeline}start-frame="240" end-frame-exclusive="360"/>```@@ -122,7 +122,7 @@ Timeline does not require speech or media:appearance={recipes.film.main}><film:Track source={conversation.visual}/></film:Film>-<render:Video id="final" composition={main.composition} timeline={animation.timeline}/>+<html:Video id="final" composition={main.composition} timeline={animation.timeline}/>```The component owns its reading rhythm through ordinary absolute time. With no selected AudioTrack,diff --git a/docs/quickstart/generation.md b/docs/quickstart/generation.mdindex 0ec04292..4474186f 100644--- a/docs/quickstart/generation.md+++ b/docs/quickstart/generation.md@@ -10,7 +10,7 @@ Every component shown here must be imported by its package specifier before use:```svml<import as="media" from="@hypit/media@1"/>-<import as="mediaop" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="text" from="@hypit/text@1"/><import as="seedance" from="@hypit/seedance@1"/><import as="speaker-kit" source="@hypit/seedance-kits/speaker"/>@@ -50,10 +50,10 @@ Typically used as a voice-timbre reference for `seedance:ReferenceVideo`.## Durations are literalsA generated take's length is the author's decision, written as a literal on the element that needs-it. Measure the line first, then write the number:+it. Estimate the line first, then write the number:```bash-hypit measure main.svml --segment hook --language en --pace normal --rounding round+hypit estimate main.svml --segment hook --language en --pace normal --rounding round# 7s```@@ -63,8 +63,8 @@ hypit measure main.svml --segment hook --language en --pace normal --rounding ro</seedance:ReferenceVideo>```-`hypit measure` counts pronunciation units of the Segment's speech at a delivery policy — `language`,-`pace` (`slow = 4.2`, `normal = 4.6`, `fast = 5.0` syllables per second for English) or a numeric+`hypit estimate` counts pronunciation units of the Segment's speech at a delivery policy — `language`,+`pace` (`slow = 4.2`, `normal = 4.6`, `fast = 5.6` syllables per second for English) or a numeric`rate` and `rounding` — with no external call. Nothing in the graph computes a duration,so the requested durations are available before a Build starts. Use the estimate to shape thewording and choose a supported request duration; the produced performance supplies actual word timing.@@ -163,8 +163,8 @@ service's input-duration limits; the requested output duration is a separate choThe component does not know that this is a talking head. That meaning lives in the supplied Text.Common attributes are `id`, `model`, `prompt`, `duration`, `resolution`, `aspect-ratio` and-`generate-audio`. `duration` is a literal in whole seconds inside the model's range, measured-beforehand with `hypit measure`.+`generate-audio`. `duration` is a literal in whole seconds inside the model's range, estimated+beforehand with `hypit estimate`.The audio generated in an earlier take can be reused as a later reference through an ordinary graphedge. Extraction does not turn it into speech evidence or attach speaker meaning:@@ -321,7 +321,7 @@ reference media or generation endpoint.## Combination example-A two-take setup with measured durations written as literals, explicit Text assembly and Seedance+A two-take setup with estimated durations written as literals, explicit Text assembly and Seedancegeneration:```svmldiff --git a/docs/quickstart/images.md b/docs/quickstart/images.mdindex 41d8a0a3..da9a1854 100644--- a/docs/quickstart/images.md+++ b/docs/quickstart/images.md@@ -1,27 +1,26 @@---title: Image Operations-description: Compose, correct and cut out images before they reach a generator or a Track.+description: Compose and correct images before they reach a generator or a Track.----Three packages work on a picture and hand back a picture. None of them produces a Track: each output+One Image Operations package works on pictures and hands back a picture. It does not produce a Track: each outputis an image you reference downstream — as a Seedance reference frame, as a Visual Clip, or as thesource of another operation.-They all need an endpoint. `image-compose` and `image-transform` ask for the raster capability, which-`@hypit/provider-image-opencv-local` answers by running OpenCV in a bounded Python process on-your own machine; `background-removal` asks for its own capability, which a selected project Provider implements. Select the supporting Endpoint in your [Runtime Profile](../guide/runtime.md)-when using these operations.+Transform and Compose ask for separate image capabilities. The default+`@hypit/provider-image-opencv-local` Endpoint implements both by running OpenCV in bounded Python+processes on your own machine.## Composing layers-`compose:Image` paints layers onto one canvas, in the order they are written, and hands back a PNG.+`image:Compose` paints layers onto one canvas, in the order they are written, and hands back a PNG.```svml-<import as="compose" from="@hypit/image-compose@1"/>+<import as="image" from="@hypit/image-operations@1"/>```The element takes `id` and `canvas`, and optionally `background` — which must carry alpha, as-`#RRGGBBAA`, and defaults to fully transparent. Its children are `compose:Layer`, at least one and at+`#RRGGBBAA`, and defaults to fully transparent. Its children are `image:Layer`, at least one and atmost sixty-four, each empty:| Attribute | Takes |@@ -33,10 +32,10 @@ most sixty-four, each empty:| `opacity` | optional — 0 to 1, default 1 |```svml-<compose:Image id="card" canvas={portrait.canvas} background="#00000000">- <compose:Layer source={background.image} frame={full} fit="cover"/>- <compose:Layer source={product.image} frame={product-frame} fit="contain"/>-</compose:Image>+<image:Compose id="card" canvas={portrait.canvas} background="#00000000">+ <image:Layer source={background.image} frame={full} fit="cover"/>+ <image:Layer source={product.image} frame={product-frame} fit="contain"/>+</image:Compose>```**Output:** `{card.image}` — an image, not a Track.@@ -47,7 +46,7 @@ An `image:Program` is a named list of operations; an `image:Transform` runs onesplit is deliberate: a program written once is applied to every shot that needs the same treatment.```svml-<import as="image" from="@hypit/image-transform@1"/>+<import as="image" from="@hypit/image-operations@1"/>````image:Program` takes only `id`, and holds its operations as children, applied in the order written:@@ -82,23 +81,7 @@ and `Crop` runs on defaults alone, so `<image:Denoise/>` is a complete instructi**Output:** `{clean-shot.image}`. The program on its own produces no image — it is a recipe, andnaming it in a `Transform` is what runs it.-## Removing a background--```svml-<import as="remove" from="@hypit/background-removal@1"/>-```--`remove:Background` is empty and takes `id` and `source`. It picks no model, threshold or storage —-that is the endpoint's business, not the Source's.--```svml-<remove:Background id="cutout" source={portrait.image}/>-```--**Output:** `{cutout.image}` — typically fed to a Visual Clip so a presenter sits over the picture-rather than in a box.--## Removing a moving person's background+## Matting a moving personFor a presenter over another picture, process the generated or supplied video with[`@hypit/volcengine-matting`](https://github.com/hypit-ai/hypit/blob/main/packages/volcengine-matting/README.md),diff --git a/docs/quickstart/preview.md b/docs/quickstart/preview.mdindex 03356490..a0dbba01 100644--- a/docs/quickstart/preview.md+++ b/docs/quickstart/preview.md@@ -27,7 +27,7 @@ It changes the interface, while your Script, video captions and comments keep th| --- | --- || `--run <file.svrun>` | Select the Run to open. || `--runtime <profile.json>` | Select a Runtime Profile; otherwise use the project's saved Runtime selection. |-| `--workspace <directory>` | Set the project boundary for Source access and edits. |+| `--project <directory>` | Set the project boundary for Source access and edits. || `--port <number>` | Request a browser-server port; the default is `5179`. |The selected target must lead to one Film and its Timeline. Placed Takes add their semantic anchors;@@ -60,7 +60,7 @@ Candidate selection. This keeps the material choice in the editable project.## Picture, timeline and Inspector-The central Preview draws the composition with HyperFrames. It uses the same component layout,+The central Preview evaluates the composition's compiled `HtmlProgram`. It uses the same component layout,media sampling and motion as an encoded render. Check the actual picture when adjusting captionplacement, graphic emphasis or coverage.@@ -94,7 +94,7 @@ ready for delivery, run its export Build to create the encoded video. Studio andavailable to explore the editable work and discuss further changes.For component authors, [Timing edits in Studio](../guide/studio-temporal-windows.md) explains semantic-editing, and the [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md)+editing, and the [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md)explains how to expose component entities and controls.To add another interface language, load a local JSON translation with `--locale-pack ./language.json`.diff --git a/docs/quickstart/run.md b/docs/quickstart/run.mdindex 6878778b..b887679f 100644--- a/docs/quickstart/run.md+++ b/docs/quickstart/run.md@@ -48,7 +48,6 @@ my-video/packages/ project-local Author packages when the work introduces themoutput/ explicit exports for people and other toolshypit.runtime.json execution environment- hypit.results.json optional Result repository selection.hypit/ generated local Runtime and Result data```@@ -68,13 +67,13 @@ the Author Source or in packages that it explicitly imports.Every `.svrun` file begins with its processing instruction:```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?>```### Minimal Run Source```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/>@@ -118,7 +117,7 @@ As soon as a generated image or take is accepted, reuse it explicitly in the nex`build-record` and `satisfy`, then inspect the plan before starting paid downstream work.```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/>@@ -215,7 +214,7 @@ A local file is the simplest zero-input Candidate. The Run Source names the byteto one current Logical Output:```svml-<file id="approved-opening" type="@hypit/artifact@1#BlobArtifact" from="./approved-opening.mp4" media-type="video/mp4"/>+<file id="approved-opening" type="@hypit/blob@1#Blob" from="./approved-opening.mp4" media-type="video/mp4"/><satisfy output="opening-shot.video" candidate="approved-opening"/>```@@ -240,9 +239,9 @@ hypit pathsto overwrite an existing file, installs nothing, contacts no service and starts no Worker. For anexisting intentional Profile, use `hypit runtime use <profile>`; that command writes only`.hypit/runtime`. See [Runtime](../guide/runtime.md) for the Profile schema and boundaries.-The CLI resolves the project first: `--workspace` is an explicit boundary; otherwise the nearest-`package.json` above the current directory is the boundary, falling back to the current directory-for a plain creative folder. It then reads only that project's `.hypit/runtime`. It never discovers+The CLI resolves the project first: `--project` is an explicit boundary; otherwise it searches upward+for a `package.json` whose `hypit.project` field is `true`. A component package or arbitrary current+directory never silently becomes a project. It then reads only that project's `.hypit/runtime`. It never discoversa Profile from a conventional filename or inherits another project's selection from a parent directory.## Configure selected credentials@@ -311,15 +310,16 @@ and Providers remain ordinary project dependencies, installed with that project'[`uv`](https://docs.astral.sh/uv/) is only needed first when the Profile selects local Pythonprograms such as WhisperX or OpenCV.-When an author package such as Fontsource is missing, `check`/`plan` report the precise command, for-example:+The official Distribution supplies the Fontsource adapter. Exact font families are project-owned+dependencies; add them with that project's package manager, for example:```bash-hypit packages install @fontsource-variable/[email protected]+npm install --save-exact @fontsource-variable/[email protected]```-`hypit runtime up` manages dependencies, the background Worker and external programs; `build` does-not perform deployment preparation.+`hypit runtime up` prepares the selected Runtime's background Worker, external Programs and runtime+materials; `build` does not perform deployment preparation. npm dependencies are installed beforehand+by the Distribution or project's package manager.#### Keeping a real video project outside the Hypit checkout@@ -333,7 +333,7 @@ hypit runtime use hypit.runtime.jsonhypit plan build.svrun```-The Workspace is resolved before the Runtime Profile. Override it explicitly with `--workspace`; the+The Project is resolved before the Runtime Profile. Override it explicitly with `--project`; theentry Source path and Runtime selection never choose it. `--package-root` locates installed packagesand never widens Source access; `--asset-root` only grants read access to additional asset bytes.@@ -348,11 +348,10 @@ The authoritative result of every Build lives in `.hypit/results/<UTC-date>/<bui`result.json` records the name, status, Target and public Outputs, media in `files/`, structuredvalues in `values/`.-That is the zero-configuration Result repository. The `output/` directory shown earlier is only a-convenient destination for explicit exports and is not part of Result storage. A project-owned-`hypit.results.json` may instead select `@hypit/build-result-s3`; commands and historical-`build-record` references then use that same repository. Temporary Resources for an active Build-remain local and private to the Runtime.+This project-local directory is the Result repository. The `output/` directory shown earlier is only+a convenient destination for explicit exports and is not part of Result storage. Archive or migrate+completed Results after the Build when needed. Temporary Resources for an active Build remain local+and private to the Runtime.Read-only archive commands such as `status` and `builds` do not initialize the Runtime database whenstate does not exist yet.@@ -449,7 +448,7 @@ A plain `status <build-id>` prints one snapshot. `status --watch` exits when the|---|---|| `--runtime` | One-command Runtime Profile override; normally select it once with `runtime use` || `--package-root` | Host directory containing the installed packages |-| `--workspace` | Explicit Source Workspace override |+| `--project` | Explicit Project boundary; also the default Source Workspace root || `--title` | Optional human-facing Result title || `--follow` | Wait for a Result outcome as an observer; durable execution remains with the Worker |diff --git a/docs/quickstart/styles.md b/docs/quickstart/styles.mdindex 948ba469..789c2b23 100644--- a/docs/quickstart/styles.md+++ b/docs/quickstart/styles.md@@ -10,7 +10,7 @@ immutable typed Records that consuming components validate and interpret.## Basic syntax```svs-<?svml using="@hypit/svs@1"?>+<?svml using="@hypit/recipe@1"?><sheet version="1" id="studio">film.vertical {@@ -25,7 +25,7 @@ immutable typed Records that consuming components validate and interpret.</sheet>```-- The processing instruction `<?svml using="@hypit/svs@1"?>` selects the SVS parser.+- The processing instruction `<?svml using="@hypit/recipe@1"?>` selects the SVS parser.- The `<sheet>` element wraps all declarations. The `id` attribute becomes the top-level namespace.- Each block is `namespace.name { ... }` with `;`-terminated key-value properties.- Comments use `/* ... */`.@@ -100,7 +100,7 @@ For reproducible rendering, select an exact installed face in the `.svml` sourceRecord to the Fine Style. Family, weight and style have one source of truth on this exact font edge:```svml-<fonts:Stack id="caption-font" family="inter" weight="600" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="600" style="normal"/><caption-fine:Style id="primary-caption" recipe={recipes.caption.dialogue}font={caption-font}/>```@@ -136,7 +136,7 @@ caption.bob {Then select them with timed Uses in the Track:```svml-<fonts:Stack id="caption-font" family="inter" weight="600" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="600" style="normal"/><caption-fine:Style id="default-caption" recipe={recipes.caption.dialogue} font={caption-font}/><caption-fine:Style id="alice-caption" recipe={recipes.caption.alice} font={caption-font}/><caption-fine:Style id="bob-caption" recipe={recipes.caption.bob} font={caption-font}/>@@ -227,7 +227,7 @@ text.title {Compiled with exact font bytes into a `text:Style`, then referenced by a concrete placement form:```svml-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><text:Style id="title-style" recipe={recipes.text.title} font={title-font}/><text:Flow id="meaning" timeline={speech.timeline} within={title-frame}style={title-style} z="90" align="center" during="timeline">@@ -308,28 +308,30 @@ model Surface and graph edges.## Exact font declarations-SVS describes typography policy, but it does not choose or open font bytes. For common open fonts,-import the private pre-release catalog and select only the faces the Author Graph uses:+SVS describes typography policy, but it does not choose or open font bytes. The official Hypit+Distribution supplies the Fontsource adapter; install the selected upstream font packages in the+video project's `package.json`. The ordinary lockfile fixes their actual versions:```svml-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/>+<import as="media" from="@hypit/media@1"/>-<fonts:Stack id="caption-fonts" family="inter" weight="600" style="normal" emoji="color">- <fonts:Fallback family="noto-sans-sc" weight="600" style="normal"/>-</fonts:Stack>+<fonts:Face id="caption-latin" package="@fontsource-variable/inter" weight="600" style="normal"/>+<fonts:Face id="caption-han" package="@fontsource-variable/noto-sans-sc" weight="600" style="normal"/>+<media:FontStack id="caption-fonts" primary={caption-latin}>+ <media:Fallback font={caption-han}/>+</media:FontStack>```| Property | Description ||---|---|-| `family` | A family from the package's finite catalog |+| `package` | One installed `@fontsource` or `@fontsource-variable` package || `weight` | Exact selected face weight |-| `style` | Selected style: `normal` or a family-supported `italic` |-| `emoji` | Optional `color` (COLRv1) or `mono` fallback on `Stack` |+| `style` | Selected style: `normal` or a package-supported `italic` |-The catalog contains 109 open families across handwriting, script, display, sans, serif,-monospace, CJK, world-script and Emoji categories. Fontsource dependencies are pinned to `5.3.0`;-the Chromium-compatible COLRv1 Emoji package is pinned separately. The compiler hashes installed-bytes into Resource-backed font values. It performs no download during a build, and the Runtime+Hypit carries no finite font catalog and does not install a family during compilation. The adapter+reads the selected package's metadata, CSS and font files as data, and the compiler turns those+installed bytes into Resource-backed font values. A build performs no download and the Runtimenever guesses a font:```svml@@ -337,14 +339,14 @@ never guesses a font:font={caption-fonts}/>```-`fonts:Stack` emits one generic `FontStackRef`; its primary and fallbacks preserve their own honest+`media:FontStack` emits one generic `FontStackRef`; its primary and fallbacks preserve their own honestmetadata. The Caption Recipe does not repeat family, weight or style. CJK and Emoji can be split into severalUnicode-range files while remaining one logical graph edge. Terminal Text and Fine Caption rejectan omitted stack; machine-font fallback is not part of Visual IR.For a symbol with both text and Emoji presentation, write the authored Unicode Emoji sequence(for example `☎️`, including VS16); no package rewrites display text to force color.-Brand and custom fonts remain explicit author assets rather than additions to the shared catalog:+Brand and custom fonts remain explicit author assets rather than additions to a central catalog:```svml<import as="media" from="@hypit/media@1"/>@@ -357,7 +359,7 @@ Brand and custom fonts remain explicit author assets rather than additions to thA complete `recipes.svs` file for a four-take talking-head project:```svs-<?svml using="@hypit/svs@1"?>+<?svml using="@hypit/recipe@1"?><sheet version="1" id="studio">diff --git a/docs/quickstart/timing.md b/docs/quickstart/timing.mdindex deb21661..cb4d8ea6 100644--- a/docs/quickstart/timing.md+++ b/docs/quickstart/timing.md@@ -18,7 +18,7 @@ word evidence; reframing picture does not change audio; a pure animation needs Tor Script.```svml-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="whisperx" from="@hypit/whisperx@1"/><import as="semantic" from="@hypit/narrative-temporal@1"/><import as="time" from="@hypit/timeline-author@1"/>@@ -33,9 +33,9 @@ The Clock fixes the frame rate shared by the final Timeline and every local doma```svml<time:Clock id="clock" frame-rate="30"/>-<pipeline:Normalize id="opening-media" source={opening-video.video}+<mediaop:Normalize id="opening-media" source={opening-video.video}video="primary-moving" audio="default" span-authority="video" clock={clock}/>-<pipeline:Normalize id="answer-media" source={answer-video.video}+<mediaop:Normalize id="answer-media" source={answer-video.video}video="primary-moving" audio="default" span-authority="video" clock={clock}/>```diff --git a/docs/quickstart/tracks.md b/docs/quickstart/tracks.mdindex 8710ae00..2d188385 100644--- a/docs/quickstart/tracks.md+++ b/docs/quickstart/tracks.md@@ -21,7 +21,7 @@ Binding + NarrativeProjection → CaptionTiming → Use presentation<import as="caption" from="@hypit/caption@1"/><import as="caption-fine" from="@hypit/caption-fine@1"/><import as="media" from="@hypit/media@1"/>-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/>````@hypit/caption` owns the common CaptionDocument contract, complete-unit Selection/Role projection,@@ -68,9 +68,11 @@ caption.primary {``````svml-<fonts:Stack id="caption-fonts" family="inter" weight="700" style="normal" emoji="color">- <fonts:Fallback family="noto-sans-sc" weight="700" style="normal"/>-</fonts:Stack>+<fonts:Face id="caption-latin" package="@fontsource-variable/inter" weight="700" style="normal"/>+<fonts:Face id="caption-han" package="@fontsource-variable/noto-sans-sc" weight="700" style="normal"/>+<media:FontStack id="caption-fonts" primary={caption-latin}>+ <media:Fallback font={caption-han}/>+</media:FontStack><caption-fine:Style id="primary-caption" recipe={recipes.caption.primary}font={caption-fonts}/>```@@ -171,7 +173,7 @@ to the occurrence; reusable pixel treatment and typed Motion remain optional val<space:Frame id="product-frame" within={vertical.bounds}left="8%" top="20%" right="92%" bottom="68%"/>-<pipeline:Normalize id="product-media" source={product-motion.video}+<mediaop:Normalize id="product-media" source={product-motion.video}video="primary-moving" audio="none" span-authority="video" clock={clock}/><visual:Motion id="product-motion-in">@@ -211,7 +213,7 @@ Every direct Clip or sample Layer declares exactly one visual input form:| `media={...}` | `SynchronizedMedia` | Connect an explicitly prepared timed source directly || `surface={...}` | `CompositableSurfaceRef` | Connect an alpha-aware still or timed surface directly |-A generated or imported video Blob reaches a Track through `<pipeline:Normalize>`, which inspects it,+A generated or imported video Blob reaches a Track through `<mediaop:Normalize>`, which inspects it,selects its streams and puts them on one frame domain; its `.media` output is what `media=` connectsto. `audio="none"` carries the picture alone, and `audio="default"` carries the source's own sound,which `audio-gain` then scales. These forms are explicit so a generic Blob is never guessed to be an@@ -228,13 +230,13 @@ then choose its exact program Window and source-time relation:```svml<import as="media" from="@hypit/media@1"/>-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="audio" from="@hypit/audio-track@1"/><import as="time" from="@hypit/timeline-author@1"/><time:Clock id="clock" frame-rate="30"/><media:Audio id="music" src="./assets/music.wav"/>-<pipeline:Normalize id="music-media" source={music}+<mediaop:Normalize id="music-media" source={music}video="none" audio="default" span-authority="audio" clock={clock}/><audio:Track id="music-bed" timeline={speech.timeline}>@@ -277,7 +279,7 @@ piece of editorial copy is one occurrence and one ordinary VisualTrack contribut<space:Canvas id="vertical" width="1080" height="1920"/><space:Frame id="title-frame" within={vertical.bounds}left="6%" top="6%" right="94%" bottom="16%"/>-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><text:Style id="title-style" recipe={recipes.text.title} font={title-font}/><text:Flow id="title" timeline={speech.timeline} within={title-frame}style={title-style} z="90" align="center" during="timeline">@@ -345,7 +347,9 @@ inputs; coordination between them belongs in a project component, not an acciden## Ranking boardsA ranking board animates an ordered list against the Script. The concrete container, item and Style-vocabulary is package-owned; inspect the installed package before authoring it.+vocabulary is package-owned. Ranking, Depth Stack and Comment Sticker are optional packages, not+part of the default Hypit installation. Add the selected published version to the video's ordinary+`package.json` and lockfile before importing it; inspect that installed package before authoring.| Container | Item | Style ||---|---|---|@@ -450,45 +454,6 @@ give both and it is refused. `size`, `color`, `align`, `block` and `padding` are**Output:** `{deck.visual}` — a VisualTrack, an ordinary peer of every other Track in the Film.-## Screen overlays--Effects that cover the picture rather than sit in a Frame: a flash on a cut, a vignette that holds-for a Selection, grain over the whole programme. One Track carries them all, and each child is one-effect bound to its own window.--```svml-<import as="screen" from="@hypit/screen-overlay@1"/>-```--`screen:Track` takes `id`, `canvas` and `timeline`. Its children are the effects, at least one, each-empty, each with a required `z` for stacking order and a window that is one of:--| Window | Written |-|---|---|-| The whole programme | `during="timeline"` |-| An already resolved Window | `during={story-time.overlay}` |-| An absolute start and length | `from="2s" for="12f"` |-| An explicit span | `from={story-time.start} until={story-time.end}` |--Lengths are `12f`, `250ms` or `1.5s`. A Selection-names one contiguous interval and a Moment names one point; author another item when an effect should-appear again.--Eleven effects are available — `Flash`, `ColorWash`, `Vignette`, `ScanLines`, `DirectionalMatte`,-`WhipVeil`, `GlitchVeil`, `Grain`, `LightLeak`, `Bokeh` and `TVStatic` — and each carries its own-required attributes, such as `color` / `intensity` / `attack` / `hold` / `decay` on a `Flash`, or-`center-x` / `center-y` / `radius-x` / `radius-y` / `softness` / `color` / `opacity` on a `Vignette`.-None have defaults: an effect states its whole shape or is refused.--```svml-<screen:Track id="effects" timeline={speech.timeline} within={vertical.bounds}>- <screen:Flash during={story-time.overlay} z="80"- color="#ffffff" intensity="0.6" attack="2" hold="2" decay="6"/>-</screen:Track>-```--**Output:** `{effects.visual}` — a VisualTrack.-## Comment stickersSocial-style comment cards placed in a Frame: an avatar, an author, the comment itself, and an@@ -504,8 +469,8 @@ enter/hold/exit motion — and every key has a default, so a recipe may set only`comment:Track` takes `id`, `canvas` and `timeline` for the complete work.-`comment:Sticker` requires `id`, `frame` and `style`, and takes the same windows as a screen overlay-above. Its copy is either the `comment=` attribute or the element's own text — both is refused. The+`comment:Sticker` requires `id`, `frame` and `style`. Its Window can use `during`, `from` + `for`, or+`from` + `until`. Its copy is either the `comment=` attribute or the element's own text — both is refused. Theoptional `author`, `header` and `meta` each take a string or a Text reference, `avatar` takes animage, and there is no `z`: stacking order comes from the recipe's `stack-order`.@@ -528,9 +493,9 @@ All four track families together in one source file:```svml<import as="caption" from="@hypit/caption@1"/><import as="caption-fine" from="@hypit/caption-fine@1"/>-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/><import as="media" from="@hypit/media@1"/>-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="visual" from="@hypit/visual-track@1"/><import as="text" from="@hypit/text-fine@1"/><import as="audio" from="@hypit/audio-track@1"/>@@ -540,8 +505,8 @@ All four track families together in one source file:<time:Clock id="clock" frame-rate="30"/><!-- Captions: primary style for all text -->-<fonts:Stack id="caption-font" family="inter" weight="700" style="normal"/>-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="700" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><caption-fine:Style id="base-caption" recipe={recipes.caption.base} font={caption-font}/><caption:Hidden id="hidden"/>@@ -560,7 +525,7 @@ All four track families together in one source file:left="10%" top="20%" right="90%" bottom="70%"/><!-- Media: one ordinary Clip used editorially as B-roll -->-<pipeline:Normalize id="card-media" source={motion.video}+<mediaop:Normalize id="card-media" source={motion.video}video="primary-moving" audio="none" span-authority="video" clock={clock}/><visual:Track id="cards" timeline={speech.timeline}><visual:Clip media={card-media.media} frame={card-frame}@@ -576,7 +541,7 @@ All four track families together in one source file:<!-- Audio: normalize one declared source, then place it for the complete program --><media:Audio id="music" src="./assets/music.wav"/>-<pipeline:Normalize id="music-media" source={music}+<mediaop:Normalize id="music-media" source={music}video="none" audio="default" span-authority="audio" clock={clock}/><audio:Track id="music-bed" timeline={speech.timeline}><audio:Clip source={music-media.media} during="timeline"diff --git a/docs/zh/guide/author-packages.md b/docs/zh/guide/author-packages.mdindex 50dc99f6..b0662d6a 100644--- a/docs/zh/guide/author-packages.md+++ b/docs/zh/guide/author-packages.md@@ -28,11 +28,11 @@ Style 一类 Surface 在裸作者 id 下公开其值,例如 `style={board-styl## 实现并查看场景-作者包 API 使用 `@hypit/hypit/author-kit`,消费的领域值使用对应公开子路径。[组件结构](./component-anatomy.md) 介绍 Manifest、Surface、Fragment 和 Producer 如何配合。项目文案与素材作为输入,组件自己的面板、边框与装饰由实现绘制。+作者包按职责使用 `@hypit/hypit/author`、`producer`、`admission` 与 `markup` 等窄公共子路径,消费的领域值使用对应所有者的公开子路径。[组件结构](./component-anatomy.md) 介绍 Manifest、Surface、Fragment 和 Producer 如何配合。项目文案与素材作为输入,组件自己的面板、边框与装饰由实现绘制。preview Source 为作者提供可打开或渲染的小例子。查看能说明行为的状态:进入、关键变化、停留布局和退出。也要在实际编排中查看,这时内容、空间和时机才有具体用途。-需要更丰富的交互编辑时,可以添加 Studio Companion。[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md) 介绍如何公开时间线实体、属性和 Source 绑定。绘制代码和 Companion 是同一个包中分别提供的贡献。+需要更丰富的交互编辑时,可以添加 Studio Companion。[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md) 介绍如何公开时间线实体、属性和 Source 绑定。绘制代码和 Companion 是同一个包中分别提供的贡献。## 使用与分享diff --git a/docs/zh/guide/component-anatomy.md b/docs/zh/guide/component-anatomy.mdindex 2fdf8ad3..d6f35abb 100644--- a/docs/zh/guide/component-anatomy.md+++ b/docs/zh/guide/component-anatomy.md@@ -22,7 +22,7 @@ description: 将场景的创作接口变成可复用的图贡献。| Activation | 公开所选包提供的贡献 || Studio Companion | 描述时间线实体与可编辑属性 |-精确对象形状由 [Author SDK](https://github.com/hypit-ai/hypit/blob/main/packages/author-kit/README.md) 和随包示例维护。小组件可以把相关职责放在一起;大组件则可以分离可复用的调度、样式和绘制逻辑。+精确对象形状由 [Author Package 指南](./author-packages.md) 和随包示例指向各自所有者。小组件可以把相关职责放在一起;大组件则可以分离可复用的调度、样式和绘制逻辑。## 围绕关系设计diff --git a/docs/zh/guide/conventions.md b/docs/zh/guide/conventions.mdindex 7f9959b1..2a31a20c 100644--- a/docs/zh/guide/conventions.md+++ b/docs/zh/guide/conventions.md@@ -9,8 +9,8 @@ description: 命名、模块边界、TypeScript 配置与 wire 数据。| 项目 | 约定 | 示例 ||---|---|---|-| 包目录 | kebab-case | `packages/speech-alignment/` |-| 包名 | `@hypit/` scope | `@hypit/speech-alignment` |+| 包目录 | kebab-case | `packages/narrative-speech-alignment/` |+| 包名 | `@hypit/` scope | `@hypit/narrative-speech-alignment` || Provider 包 | `provider-` 前缀 | `@studio/provider-images` || TypeScript 文件 | kebab-case | `align.ts` || 导出类型 | PascalCase | `SpeechAlignment` |diff --git a/docs/zh/guide/develop.md b/docs/zh/guide/develop.mdindex 57825c72..6fbc699e 100644--- a/docs/zh/guide/develop.md+++ b/docs/zh/guide/develop.md@@ -12,7 +12,7 @@ description: 开始 Hypit 开发工作。| Python | 3.10–3.13 | 本地 WhisperX 与 OpenCV Managed Program || uv | latest | Python 环境管理 || ffmpeg / ffprobe | 较新的稳定版 | 媒体处理 |-| Chrome / Chromium | 由 `hypit runtime up` 下载 | 本地 HyperFrames 渲染 |+| Chrome / Chromium | 由 `hypit runtime up` 下载 | 本地 HTML 光栅化 |只有 Node.js 与 pnpm 是硬性要求。其余都只在跑真实 Builds 时才需要。diff --git a/docs/zh/guide/packages.md b/docs/zh/guide/packages.mdindex 55d8810a..f82165cc 100644--- a/docs/zh/guide/packages.md+++ b/docs/zh/guide/packages.md@@ -28,13 +28,13 @@ Hypit 把视频需要什么,与哪些代码和服务完成它,分别表达## 安装与 Source 导入-Skill、可执行 Distribution 和视频项目分别安装与更新。`@hypit/hypit` Distribution 包含官方作者包和公开扩展 API。所选 Runtime Adapter 可以通过 `hypit runtime up` 准备额外服务依赖;可选作者素材可以按 CLI 给出的准确 `hypit packages install` 命令安装。项目组件自己的依赖由项目管理。+Skill、可执行 Distribution 和视频项目分别安装与更新。`@hypit/hypit` Distribution 包含官方作者包和公开扩展 API。所选 Runtime Adapter 可以通过 `hypit runtime up` 准备其声明的服务与运行材料。npm 依赖随其所有者安装:Distribution 的依赖随 Distribution 安装,项目组件的依赖由项目管理。Source 使用 `@your-studio/scoreboard@1` 这样的逻辑 Module 地址。npm 安装的包版本决定实际实现,逻辑 `@1` 标识作者接口。视频 Build 使用这些已安装的版本;缺包时会报告安装所需的信息。## 编写与分享扩展-外部包使用 `@hypit/hypit/author-kit`、`@hypit/hypit/composition`、`@hypit/hypit/model-kit` 或 `@hypit/hypit/endpoint-kit` 等公开子路径。将选定的 `@hypit/hypit` 版本作为开发依赖,把扩展编译为 JavaScript,分发它自己的代码与素材。`package.json` 中的 activation 入口描述它提供的能力;加载选中的扩展时,当前 Distribution 提供公开 Hypit API。+外部包只使用自己实际需要的窄公共所有者,例如 `@hypit/hypit/author`、`producer`、`admission`、`markup`、`composition`、`model-kit` 或 `endpoint`。将选定的 `@hypit/hypit` 版本作为开发依赖,把扩展编译为 JavaScript,分发它自己的代码与素材。`package.json` 中的 activation 入口描述它提供的能力;加载选中的扩展时,当前 Distribution 提供公开 Hypit API。- [添加作者包](./author-packages.md):从随发行包提供的可构建组件开始。- [组件结构](./component-anatomy.md):组件内部各部分的职责。diff --git a/docs/zh/guide/providers.md b/docs/zh/guide/providers.mdindex 18a7c165..c51d3f62 100644--- a/docs/zh/guide/providers.md+++ b/docs/zh/guide/providers.md@@ -38,24 +38,24 @@ Model 定义生成请求,Provider 实现推理服务的 API,Endpoint 选择## 添加 Model-项目包使用 `@hypit/hypit/model-kit`、`@hypit/hypit/generation` 和 `@hypit/hypit/author-kit`。声明准确的请求端口、参数取值、输出类型和能力。作者 Surface 把 Prompt Text 与参考素材连接到请求,再将生成素材作为普通图输出公开。+项目包使用 `@hypit/hypit/generation/model`、`generation`、`author`、`producer`、`admission` 与 `markup` 等窄公共子路径。声明准确的请求端口、参数取值、输出类型和能力。作者 Surface 把 Prompt Text 与参考素材连接到请求,再将生成素材作为普通图输出公开。-[Model SDK](https://github.com/hypit-ai/hypit/blob/main/packages/model-kit/README.md) 提供请求定义与 activation 示例。包拥有模型接口;凭据与 HTTP 映射由 Provider 负责。+[Generation Model 作者 API](https://github.com/hypit-ai/hypit/blob/main/packages/generation/README.md#exact-model-authoring) 提供请求定义与 activation 示例。包拥有模型接口;凭据与 HTTP 映射由 Provider 负责。## 添加 Provider将选定的 `@hypit/hypit` 版本作为开发依赖,使用公开 SDK:```ts-import { defineEndpointPackage } from "@hypit/hypit/endpoint-kit";-import type { AsyncEndpoint, CredentialRef, EndpointRequest } from "@hypit/hypit/endpoint-kit";+import { defineEndpointPackage } from "@hypit/hypit/endpoint";+import type { AsyncEndpoint, CredentialRef, EndpointRequest } from "@hypit/hypit/endpoint";```实现服务支持的准确能力与输出类型,将请求端口映射到服务 API,解析声明的凭据并返回结果。即时操作可以直接返回;远程任务可以先提交得到 ID,再轮询完成情况、收集输出文件。并发和动作限制由 Endpoint 的资源声明负责。真正的失败会结束本次执行尝试。Build Result 保留已完成的 Output 与公开任务回执。后续工作通过新的 Run 与 Build,选择仍适用的已有 Output 复用。-[Endpoint SDK](https://github.com/hypit-ai/hypit/blob/main/packages/endpoint-kit/README.md) 维护处理接口、activation、资源声明和价格 API。将包编译为 JavaScript,由项目包管理器安装。在 [Runtime Profile](./runtime.md) 的 `endpoints` 中配置实例,并通过 `bindings` 选择它。+[Endpoint SDK](https://github.com/hypit-ai/hypit/blob/main/packages/endpoint/README.md) 维护处理接口、activation、资源声明和价格 API。将包编译为 JavaScript,由项目包管理器安装。在 [Runtime Profile](./runtime.md) 的 `endpoints` 中配置实例,并通过 `bindings` 选择它。[完整项目 Provider 示例](https://github.com/hypit-ai/hypit/tree/main/examples/provider-package) 使用示意 API 展示参考上传、任务回执、结果收集与价格读取。示例随执行包分发,Agent 无需仓库 checkout 就能读取和改写。它包含两个包:`provider-images` 对应生成图像,`provider-videos` 对应生成视频——后者的服务接收更宽的参考词汇(图像、视频、音频以及首尾帧),并通过独立的结果收集步骤返回产物。diff --git a/docs/zh/guide/runtime.md b/docs/zh/guide/runtime.mdindex f42bd245..8a65307e 100644--- a/docs/zh/guide/runtime.md+++ b/docs/zh/guide/runtime.md@@ -19,8 +19,9 @@ Core 只规划和推进依赖,不需要知道作品是一条视频。新组件## 先确定项目,再选择 Profile-从视频项目运行命令,或用 `--workspace` 明确指定项目。否则使用当前目录向上最近的-`package.json`;没有时,以当前目录为项目。Source 文件名和 Runtime 配置都不决定这个边界。+从 `package.json` 明确声明 `"hypit": { "project": true }` 的视频项目运行命令,或用+`--project` 明确指定项目。否则 CLI 向上寻找该标记。组件包、任意当前目录、Source 文件名和+Runtime 配置都不决定这个边界。```bashhypit paths@@ -45,7 +46,7 @@ hypit runtime init"dataRoot": ".hypit/runtimes/local","credentials": {},"endpoints": {- "media.local": { "use": "@hypit/provider-media-local" }+ "media.local": { "use": "@hypit/media-local" }},"bindings": {}}@@ -132,20 +133,9 @@ Provider 可以分别声明任务容量和 submit、poll、collect 的短调用## 产物留在项目里-默认 Result 位于 `.hypit/results`。项目通过独立的 `hypit.results.json` 选择位置或仓库,-不放进 Runtime Profile:--```json-{- "format": "hypit.build-results@1",- "use": "@hypit/build-result-fs",- "config": { "path": ".hypit/results" }-}-```--S3 适配器可以把 Result 放进桶及项目专属前缀。适配器负责访问和凭据;更换 Result 存储不会-搬走活跃 Runtime,也不会自动上传外部文件引用。已提交 Build 保留提交时的目标位置,-修改选择不迁移历史。+Result 位于运行 Hypit 的机器上、项目自己的 `.hypit/results`。本地电脑、SSH Linux 主机和+官方 WebUI 后端遵循同一规则:整套 Runtime 部署到那个宿主,不把队列、工作文件和 Result+存储拆到不同服务。需要长期归档或迁移时,在 Build 完成后显式处理这些文件。Result 在公开 Output 完成时发布它们,最后保留终态。新 Output 可以引用已有文件,复合值内部也一样,不意味着多一份素材。显式本地文件引用保持实时性;继续复用时需要保留它们的依赖。@@ -153,5 +143,5 @@ Result 在公开 Output 完成时发布它们,最后保留终态。新 Output`builds`、`history`、`inspect`、`get` 读取项目 Result,不依赖原 Runtime。精确存储和执行接口见-[Result 包](https://github.com/hypit-ai/hypit/blob/main/packages/build-result/README.md) 与+[Result 包](https://github.com/hypit-ai/hypit/blob/main/packages/result/README.md) 与[本地 Runtime 包](https://github.com/hypit-ai/hypit/blob/main/packages/runtime-local/README.md)。diff --git a/docs/zh/guide/service-partners.md b/docs/zh/guide/service-partners.mdindex 0dc67119..f16b5a5a 100644--- a/docs/zh/guide/service-partners.md+++ b/docs/zh/guide/service-partners.md@@ -10,10 +10,15 @@ HypiHub 是 Hypit 推荐的集成托管服务,提供已支持的生成与 Whis下面介绍的合作方是独立服务,各有自己的账户、条款、价格、模型可用性和 API。合作关系提供一个了解服务的入口,不共用 HypiHub 账户。-发行包为下面每个服务内置了一个使用 API Key 的 Provider,覆盖该服务提供的已安装模型,+下面每个服务 Provider 都是独立版本的 npm 包。项目用普通包管理器安装自己选择的包,再在+Runtime Profile 中引用它;安装本身不会启用服务。Provider 覆盖该服务提供的已安装模型,并按该服务的输入限制报告不支持的请求;具体清单见各 Provider 的 README。服务提供、但不在这个范围内的模型,通过普通的 [Model 与 Provider](./providers.md) 扩展方式连接。+```bash+npm install @hypit/provider-tokendance+```+## 模型与工具 API 合作方### TokenDance@@ -61,4 +66,4 @@ Agent 可以在项目包中实现这次所需的请求与结果映射。HypiHub 额度不支付这份部署。[使用自有模型部署](./providers.md#使用自有模型部署)说明自己管理服务环境时需要处理什么。-没有合作关系、没有官方内置 Provider,也可以使用一份合适的部署。+没有合作关系、没有官方维护的 Provider,也可以使用一份合适的部署。diff --git a/docs/zh/guide/studio-companion-architecture.md b/docs/zh/guide/studio-companion-architecture.mdindex 70151141..ee24e8e0 100644--- a/docs/zh/guide/studio-companion-architecture.md+++ b/docs/zh/guide/studio-companion-architecture.md@@ -9,7 +9,7 @@ description: 为组件提供有意义的时间线实体和 Studio 编辑控件Companion 是应用贡献。项目组件可以在同一个物理包中,以独立文件和 facet 携带它;官方 Distribution 通过独立包提供官方 Companion。两种情况下,Studio 都加载当前 Source 和 Distribution 所选包的 Companion。-[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md) 提供 activation 与接口示例。外部包使用 `@hypit/hypit/studio-adapter`,将 Companion 编译为 JavaScript 并与组件一起分发。修改安装代码后,重启 Studio 加载新贡献。+[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md) 提供 activation 与接口示例。外部包使用 `@hypit/hypit/studio-companion`,将 Companion 编译为 JavaScript 并与组件一起分发。修改安装代码后,重启 Studio 加载新贡献。## 描述作者面对的对象diff --git a/docs/zh/guide/testing.md b/docs/zh/guide/testing.mdindex 7e851c39..6f15c4e2 100644--- a/docs/zh/guide/testing.md+++ b/docs/zh/guide/testing.md@@ -44,8 +44,8 @@ describe("someFunction", () => {```typescripttest("compiles the expected exports", async () => {const compiler = createCompiler({ root, packageContributions });- const workspace = await compiler.openFile("fixture.svml");- const result = await compiler.compileSource(workspace.entry, workspace);+ const workspace = await compiler.openEntry("fixture.svml");+ const result = await compiler.compileResolvedSource(workspace.entry, workspace);assert.equal(result.exports.length, 3);});```@@ -69,12 +69,12 @@ test("compiles the expected exports", async () => {| 命令 | 测试内容 | 前置条件 ||---|---|---|| `pnpm test:whisperx-service` | Python WhisperX 服务 | Python 3.13、uv、frozen sync |-| `pnpm test:image-opencv` | OpenCV 图像变换 | 服务自带的解释器,位于 `services/image-opencv/.venv`;要用别的解释器就设 `HYPIT_OPENCV_PYTHON` |+| `pnpm test:image-opencv` | OpenCV Transform 与 Compose | Provider 自带的解释器,位于 `packages/provider-image-opencv-local/runtime/.venv`;要用别的解释器就设 `HYPIT_OPENCV_PYTHON` |-要运行本地 HyperFrames 浏览器渲染测试,先在当前 shell 环境中设置 `HYPIT_BROWSER_TESTS=1`,再从仓库根目录执行以下命令。需要可用的 Chrome、ffmpeg 和 ffprobe。+要运行本地 HTML 光栅化测试,先在当前 shell 环境中设置 `HYPIT_BROWSER_TESTS=1`,再从仓库根目录执行以下命令。需要可用的 Chrome、ffmpeg 和 ffprobe。```sh-node --import tsx --test packages/provider-hyperframes-local/test/provider.test.ts+node --import tsx --test packages/provider-html-local/test/provider.test.ts```## 测试 fixturesdiff --git a/docs/zh/quickstart/composition.md b/docs/zh/quickstart/composition.mdindex b7b08ed2..7c17174f 100644--- a/docs/zh/quickstart/composition.md+++ b/docs/zh/quickstart/composition.md@@ -9,7 +9,7 @@ Film 是普通作者组件。它把显式选择的 VisualTrack、AudioTrack 与```svml<import as="space" from="@hypit/spatial@1"/><import as="film" from="@hypit/film@1"/>-<import as="render" from="@hypit/render-hyperframes@1"/>+<import as="html" from="@hypit/html-video@1"/>```## 装配 Film@@ -71,15 +71,15 @@ caption.base { stack-order: 70; }## 渲染完整视频```svml-<render:Video id="final"+<html:Video id="final"composition={main.composition} timeline={speech.timeline}/>```渲染器编译视觉贡献、捕获所需帧、渲染 AudioTrack,并复用封装为交付文件。-`{final.video}` 是普通 Resource-backed `BlobArtifact`,通常也是 Run Target。+`{final.video}` 是普通 Resource-backed `Blob`,通常也是 Run Target。```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/><target output="final.video"/>@@ -89,7 +89,7 @@ caption.base { stack-order: 70; }## 渲染帧区间```svml-<render:Video id="detail" composition={main.composition} timeline={speech.timeline}+<html:Video id="detail" composition={main.composition} timeline={speech.timeline}start-frame="240" end-frame-exclusive="360"/>```@@ -117,7 +117,7 @@ Timeline 不要求语音或媒体:appearance={recipes.film.main}><film:Track source={conversation.visual}/></film:Film>-<render:Video id="final" composition={main.composition} timeline={animation.timeline}/>+<html:Video id="final" composition={main.composition} timeline={animation.timeline}/>```组件用普通绝对时间拥有自己的阅读节奏。没有选择 AudioTrack 时,结果是静音的。在语音作品diff --git a/docs/zh/quickstart/generation.md b/docs/zh/quickstart/generation.mdindex ab32e608..ef752ef7 100644--- a/docs/zh/quickstart/generation.md+++ b/docs/zh/quickstart/generation.md@@ -9,7 +9,7 @@ description: 声明媒体资源并使用 Seedance 生成视频。```svml<import as="media" from="@hypit/media@1"/>-<import as="mediaop" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="text" from="@hypit/text@1"/><import as="seedance" from="@hypit/seedance@1"/><import as="speaker-kit" source="@hypit/seedance-kits/speaker"/>@@ -47,10 +47,10 @@ description: 声明媒体资源并使用 Seedance 生成视频。## 时长是字面量-生成片段的长度由作者决定,直接写在需要它的元素上。先量稿子,再写数字:+生成片段的长度由作者决定,直接写在需要它的元素上。先估算稿子,再写数字:```bash-hypit measure main.svml --segment hook --language en --pace normal --rounding round+hypit estimate main.svml --segment hook --language en --pace normal --rounding round# 7s```@@ -60,7 +60,7 @@ hypit measure main.svml --segment hook --language en --pace normal --rounding ro</seedance:ReferenceVideo>```-`hypit measure` 按口播策略——`language`、`pace`(英语 `slow = 4.2`、`normal = 4.6`、`fast = 5.0` 音节/秒)或数值 `rate`、`rounding`——统计 Segment 台词的读音单位,不调用任何外部服务。请求时长在 Build 开始前已经明确。用估时结果调整稿子并选择模型支持的时长;实际词时间由生成表演后的语义处理提供。+`hypit estimate` 按口播策略——`language`、`pace`(英语 `slow = 4.2`、`normal = 4.6`、`fast = 5.6` 音节/秒)或数值 `rate`、`rounding`——统计 Segment 台词的读音单位,不调用任何外部服务。请求时长在 Build 开始前已经明确。用估时结果调整稿子并选择模型支持的时长;实际词时间由生成表演后的语义处理提供。## text:Value@@ -143,7 +143,7 @@ Seedance 2.5 复用同样的 Surface,而不是由 Runtime 把别的模型偷这个低层组件并不知道它被用来做口播;用途只存在于传入的 Text 中。公共属性包括`id`、`model`、`prompt`、`duration`、`resolution`、-`aspect-ratio`、`generate-audio`;`duration` 是模型范围内的整秒字面量,事先用 `hypit measure` 量好。+`aspect-ratio`、`generate-audio`;`duration` 是模型范围内的整秒字面量,事先用 `hypit estimate` 估算。可以直接抽取前一段生成视频里的音频,并通过普通图边给后续片段当作参考。这个操作不会把音频提升成语音证据,也不会凭空附加说话人语义:diff --git a/docs/zh/quickstart/images.md b/docs/zh/quickstart/images.mdindex d069800a..04804af2 100644--- a/docs/zh/quickstart/images.md+++ b/docs/zh/quickstart/images.md@@ -1,21 +1,21 @@---title: 图片操作-description: 在图片流向生成器或 Track 之前,对它做合成、校正与抠图。+description: 在图片流向生成器或 Track 之前,对它做合成与校正。----有三个包接收一张图片、交还一张图片。它们都不产出 Track:每个输出都是一张可供下游引用的图片——作为 Seedance 的参考帧、作为 Visual Clip,或作为下一次操作的来源。+一个 Image Operations 包接收已有图片、交还一张图片。它不产出 Track:每个输出都是一张可供下游引用的图片——作为 Seedance 的参考帧、作为 Visual Clip,或作为下一次操作的来源。-它们都需要 Endpoint。`image-compose` 与 `image-transform` 索取 raster 能力,由 `@hypit/provider-image-opencv-local` 在本机运行 OpenCV 来满足;`background-removal` 索取的是它自己声明的能力,由所选项目 Provider 实现。使用这些操作时,在 [Runtime Profile](../guide/runtime.md) 中选择支持它们的 Endpoint。+Transform 与 Compose 索取两项不同的图像能力;默认的 `@hypit/provider-image-opencv-local` Endpoint 在本机通过有界 Python 进程同时实现二者。## 合成图层-`compose:Image` 按书写顺序把各图层画到同一张画布上,交还一张 PNG。+`image:Compose` 按书写顺序把各图层画到同一张画布上,交还一张 PNG。```svml-<import as="compose" from="@hypit/image-compose@1"/>+<import as="image" from="@hypit/image-operations@1"/>```-元素接受 `id` 与 `canvas`,以及可选的 `background`——它必须带 alpha,写作 `#RRGGBBAA`,默认为完全透明。子元素是 `compose:Layer`,至少一个、至多六十四个,各自为空:+元素接受 `id` 与 `canvas`,以及可选的 `background`——它必须带 alpha,写作 `#RRGGBBAA`,默认为完全透明。子元素是 `image:Layer`,至少一个、至多六十四个,各自为空:| 属性 | 取值 ||---|---|@@ -26,10 +26,10 @@ description: 在图片流向生成器或 Track 之前,对它做合成、校正| `opacity` | 可选——0 到 1,默认 1 |```svml-<compose:Image id="card" canvas={portrait.canvas} background="#00000000">- <compose:Layer source={background.image} frame={full} fit="cover"/>- <compose:Layer source={product.image} frame={product-frame} fit="contain"/>-</compose:Image>+<image:Compose id="card" canvas={portrait.canvas} background="#00000000">+ <image:Layer source={background.image} frame={full} fit="cover"/>+ <image:Layer source={product.image} frame={product-frame} fit="contain"/>+</image:Compose>```**输出:** `{card.image}`——一张图片,不是 Track。@@ -39,7 +39,7 @@ description: 在图片流向生成器或 Track 之前,对它做合成、校正`image:Program` 是一份具名的操作清单,`image:Transform` 把它作用在某个来源上。这样拆开是有意的:一份写好的 program 可以套用到每一个需要同样处理的镜头上。```svml-<import as="image" from="@hypit/image-transform@1"/>+<import as="image" from="@hypit/image-operations@1"/>````image:Program` 只接受 `id`,操作以子元素形式书写,按书写顺序依次施加:@@ -72,20 +72,6 @@ description: 在图片流向生成器或 Track 之前,对它做合成、校正**输出:** `{clean-shot.image}`。program 本身不产出任何图片——它是一份配方,在 `Transform` 中指名它才会真正运行。-## 去除背景--```svml-<import as="remove" from="@hypit/background-removal@1"/>-```--`remove:Background` 必须为空,接受 `id` 与 `source`。它不挑选模型、阈值或存储——那是 endpoint 的事,不是 Source 的事。--```svml-<remove:Background id="cutout" source={portrait.image}/>-```--**输出:** `{cutout.image}`——通常喂给一个 Visual Clip,好让出镜者叠在画面上,而不是待在一个方框里。-## 移动人物抠像人物需要出现在其他画面之上时,可以将生成或已有视频交给 [`@hypit/volcengine-matting`](https://github.com/hypit-ai/hypit/blob/main/packages/volcengine-matting/README.md),由支持该能力的 HypiHub Endpoint 执行:diff --git a/docs/zh/quickstart/preview.md b/docs/zh/quickstart/preview.mdindex a55bbb4b..4c432bc2 100644--- a/docs/zh/quickstart/preview.md+++ b/docs/zh/quickstart/preview.md@@ -20,7 +20,7 @@ hypit studio --run build.svrun| --- | --- || `--run <file.svrun>` | 选择要打开的 Run。 || `--runtime <profile.json>` | 选择 Runtime Profile;省略时使用项目保存的 Runtime 选择。 |-| `--workspace <directory>` | 设置 Source 访问与修改的项目边界。 |+| `--project <directory>` | 设置 Source 访问与修改的项目边界。 || `--port <number>` | 指定浏览器服务端口,默认请求 `5179`。 |所选目标需要指向一个 Film 及其 Timeline。放入的 Take 带来对应的语义锚点;纯动画也使用 Timeline,声明结束时间、不放入 Take 即可。两者都支持视觉组件与属性编辑。显示编排所需的素材应已通过 Run 提供。Studio 可以完成所选 Runtime 支持的媒体准备;生成和编码渲染通过 `hypit build` 提交。@@ -43,7 +43,7 @@ hypit studio --run build.svrun## 画面、时间线与 Inspector-中央 Preview 使用 HyperFrames 绘制编排,组件布局、素材采样和动作与编码渲染来自同一份编排。调整字幕位置、图形重点或覆盖画面时,可以对照真实素材查看。+中央 Preview 求值编排生成的 `HtmlProgram`;组件布局、素材采样和动作与编码成片来自同一份编排。调整字幕位置、图形重点或覆盖画面时,可以对照真实素材查看。Timeline 把组件的出现放在同一时钟上。语义编排还会显示 Segment、Word、Selection 和 Moment。选择实体即可定位;播放、逐帧、缩放和滚动便于查看具体转场或版面。@@ -59,6 +59,6 @@ Source 编辑修改所选 `.svml`、`.svs` 或 `.svrun` 文件。支持的 Inspe预览播放包含 Film 选中的 AudioTrack,例如口播、音乐与音效。导出视频的音频由渲染的媒体管线装配。作品准备好交付后,运行导出 Build 得到编码后的成片;Studio 与 Comments 仍可用于查看可编辑作品、沟通后续修改。-组件作者可以阅读 [Studio 中的时间编辑](../guide/studio-temporal-windows.md) 了解语义编辑,以及 [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-adapter/README.md) 了解如何公开组件实体和控件。+组件作者可以阅读 [Studio 中的时间编辑](../guide/studio-temporal-windows.md) 了解语义编辑,以及 [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md) 了解如何公开组件实体和控件。需要其他界面语言时,可以通过 `--locale-pack ./language.json` 加载本地 JSON 译文。[本地化指南](https://github.com/hypit-ai/hypit/blob/main/packages/studio/LOCALIZATION.md) 介绍译文格式、缺项检查和语言包分享方法。diff --git a/docs/zh/quickstart/run.md b/docs/zh/quickstart/run.mdindex a3765d41..8dfff11b 100644--- a/docs/zh/quickstart/run.md+++ b/docs/zh/quickstart/run.md@@ -44,7 +44,6 @@ my-video/packages/ 作品需要时创建的项目本地 Author 包output/ 显式导出给人或其他工具的副本hypit.runtime.json 执行环境- hypit.results.json 可选的 Result 仓库选择.hypit/ 自动产生的本地 Runtime 与 Result 数据```@@ -62,13 +61,13 @@ Run Source 与 Runtime Profile 不会悄悄改写视频。创作性的模型选每个 `.svrun` 文件都以其处理指令开头:```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?>```### 最简 Run Source```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/>@@ -104,7 +103,7 @@ Hypit 没有隐式缓存。复用结果是显式的运行图编写:把某个生成图片或 Take 一完成,就能在下一份 `.svrun` 中用 `build-record` 与 `satisfy` 显式复用,并在启动付费下游工作前检查 plan。```svml-<?svml using="@hypit/run-markup@1"?>+<?svml using="@hypit/markup/run@1"?><svrun version="1"><author source="./main.svml"/>@@ -180,7 +179,7 @@ Core 不再给 Candidate 标注 `exact` 或 `substitute`。选择 Candidate 本本地文件就是最简单的零输入 Candidate:```svml-<file id="approved-opening" type="@hypit/artifact@1#BlobArtifact" from="./approved-opening.mp4" media-type="video/mp4"/>+<file id="approved-opening" type="@hypit/blob@1#Blob" from="./approved-opening.mp4" media-type="video/mp4"/><satisfy output="opening-shot.video" candidate="approved-opening"/>```@@ -203,8 +202,9 @@ hypit paths`runtime use` 只写入 `.hypit/runtime`,不会启动 Worker、创建 Runtime 数据或修改已安装包。Profile 结构和完整边界见 [Runtime](../guide/runtime.md)。-CLI 必须先确定项目:显式 `--workspace` 直接给出边界;否则使用当前目录向上的最近-`package.json`,普通创作目录没有该文件时就以当前目录为边界。随后只读取这个项目自己的+CLI 必须先确定项目:显式 `--project` 直接给出边界;否则向上寻找+`package.json` 中明确声明 `"hypit": { "project": true }` 的目录。组件包与任意当前目录不会+静默成为项目。随后只读取这个项目自己的`.hypit/runtime`。它不会按约定文件名猜 Profile,也不会从父目录继承另一个项目的选择。## 配置所选凭据@@ -256,10 +256,11 @@ Runtime Profile,把其 Adapter 声明的上游 npm 包安装到机器共享目自己的组件和 Provider 仍是普通项目依赖,由项目的包管理器安装。只有 Profile 选择 WhisperX、OpenCV 等本地 Python 程序时,才需要先安装 [`uv`](https://docs.astral.sh/uv/)。-作者侧缺少 Fontsource 等上游包时,`check`/`plan` 会给出精确命令,例如:+官方 Distribution 提供 Fontsource 适配器;具体字体族是项目自己的普通依赖,应通过该项目的包+管理器加入,例如:```bash-hypit packages install @fontsource-variable/[email protected]+npm install --save-exact @fontsource-variable/[email protected]````hypit runtime up` 管理依赖、后台 Worker 和外部程序;`build` 不做部署准备。@@ -276,7 +277,7 @@ hypit runtime use hypit.runtime.jsonhypit plan build.svrun```-Workspace 在 Runtime Profile 之前确定;显式 `--workspace` 可以覆盖它,入口 Source 路径和+项目在 Runtime Profile 之前确定;显式 `--project` 可以覆盖它,入口 Source 路径和Runtime 选择都无权改变这条源码边界。`--package-root` 只定位已经安装的`node_modules`;`--asset-root` 只额外授权读取素材字节。@@ -290,9 +291,9 @@ output/每次 Build 的权威结果位于 `.hypit/results/<UTC-date>/<build-id>/`:`result.json` 记录名字、状态、Target和公开 Output,媒体在 `files/`,结构化值在 `values/`。-这是无需配置的默认 Result 仓库。项目根的 `hypit.results.json` 也可以选择 `@hypit/build-result-s3`;历史命令-与 `.svrun` 中的 `build-record` 会使用同一个仓库。活跃 Build 的临时 Resource 仍由 Runtime 在本地-私有管理。+这个项目本地目录就是 Result 仓库;需要长期归档或迁移时,在 Build 完成后显式处理这些文件。+历史命令与 `.svrun` 中的 `build-record` 使用同一目录。活跃 Build 的临时 Resource 仍由 Runtime+在本机私有管理。`status`、`builds` 等只读归档命令不会在状态尚不存在时初始化 Runtime 数据库。@@ -375,7 +376,7 @@ hypit status <build-id> --watch|---|---|| `--runtime` | 单次命令的 Runtime Profile 覆盖;通常用 `runtime use` 选择一次即可 || `--package-root` | 存放已安装包的 Host 目录 |-| `--workspace` | 显式 Source Workspace 覆盖项 |+| `--project` | 显式项目边界,也是默认的 Source Workspace 根目录 || `--title` | 给这次 Result 一个供人阅读的标题 || `--follow` | 将 Build 进度流式输出到终端 |diff --git a/docs/zh/quickstart/styles.md b/docs/zh/quickstart/styles.mdindex e7fa3584..8691db94 100644--- a/docs/zh/quickstart/styles.md+++ b/docs/zh/quickstart/styles.md@@ -8,7 +8,7 @@ SVS(`.svs`)文件使用类 CSS 语法定义可复用的类型化配置值。## 基本语法```svs-<?svml using="@hypit/svs@1"?>+<?svml using="@hypit/recipe@1"?><sheet version="1" id="studio">film.vertical {@@ -23,7 +23,7 @@ SVS(`.svs`)文件使用类 CSS 语法定义可复用的类型化配置值。</sheet>```-- 处理指令 `<?svml using="@hypit/svs@1"?>` 用于选择 SVS 解析器。+- 处理指令 `<?svml using="@hypit/recipe@1"?>` 用于选择 SVS 解析器。- `<sheet>` 元素包裹所有声明。`id` 属性成为顶层命名空间。- 每个块的格式为 `namespace.name { ... }`,属性以 `;` 结尾的键值对形式书写。- 注释使用 `/* ... */`。@@ -96,7 +96,7 @@ caption.dialogue {Style。字体家族、字重和字形只在这条精确字体边上声明一次:```svml-<fonts:Stack id="caption-font" family="inter" weight="600" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="600" style="normal"/><caption-fine:Style id="primary-caption" recipe={recipes.caption.dialogue}font={caption-font}/>```@@ -132,7 +132,7 @@ caption.bob {然后在 Track 中通过 Use 选择呈现样式:```svml-<fonts:Stack id="caption-font" family="inter" weight="600" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="600" style="normal"/><caption-fine:Style id="default-caption" recipe={recipes.caption.dialogue} font={caption-font}/><caption-fine:Style id="alice-caption" recipe={recipes.caption.alice} font={caption-font}/><caption-fine:Style id="bob-caption" recipe={recipes.caption.bob} font={caption-font}/>@@ -220,7 +220,7 @@ text.title {先与精确字体字节一起编译为 `text:Style`,再由具体放置形式引用:```svml-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><text:Style id="title-style" recipe={recipes.text.title} font={title-font}/><text:Flow id="meaning" timeline={speech.timeline} within={title-frame}style={title-style} z="90" align="center" during="timeline">@@ -293,35 +293,38 @@ interview.street {## 精确字体声明-SVS 描述字体策略,但不选择或打开字体字节。常用开源字体由私有的预发布字体目录显式导入;只有作者图真正引用的字体会进入本次 Build:+SVS 描述字体策略,但不选择或打开字体字节。官方 Hypit Distribution 已提供 Fontsource 适配器;+在视频项目自己的 `package.json` 中安装实际选中的上游字体包,普通 lockfile 固定真实版本:```svml-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/>+<import as="media" from="@hypit/media@1"/>-<fonts:Stack id="caption-fonts" family="inter" weight="600" style="normal" emoji="color">- <fonts:Fallback family="noto-sans-sc" weight="600" style="normal"/>-</fonts:Stack>+<fonts:Face id="caption-latin" package="@fontsource-variable/inter" weight="600" style="normal"/>+<fonts:Face id="caption-han" package="@fontsource-variable/noto-sans-sc" weight="600" style="normal"/>+<media:FontStack id="caption-fonts" primary={caption-latin}>+ <media:Fallback font={caption-han}/>+</media:FontStack>```| 属性 | 描述 ||---|---|-| `family` | 字体包有限目录中的字体族 |+| `package` | 一个已经安装的 `@fontsource` 或 `@fontsource-variable` 包 || `weight` | 精确选择的字体粗细 |-| `style` | `normal` 或该字体族支持的 `italic` |-| `emoji` | `Stack` 可选的 `color`(COLRv1)或 `mono` 兜底 |+| `style` | `normal` 或该字体包支持的 `italic` |-目录现有 109 个开源字体族,覆盖手写、书法、展示、无衬线、衬线、等宽、CJK、其他文字系统与 Emoji。Fontsource 依赖固定为 `5.3.0`,Chromium 兼容的 COLRv1 Emoji 包另行锁定版本;编译器把已安装字节哈希成内容寻址的字体值,Build 过程不会下载字体,Runtime-也不猜字体:+Hypit 不维护有限字体目录,也不会在编译时安装字体族。适配器只把所选包的 metadata、CSS+和字体文件作为数据读取;编译器把已安装字节变成 Resource-backed 字体值。Build 过程不会下载字体,Runtime 也不猜字体:```svml<caption-fine:Style id="dialogue" recipe={recipes.caption.dialogue}font={caption-fonts}/>```-`fonts:Stack` 产出通用 `FontStackRef`,主字体与 Fallback 都保留自己的真实元数据;+`media:FontStack` 产出通用 `FontStackRef`,主字体与 Fallback 都保留自己的真实元数据;Caption Recipe 不再重复家族、字重或字形。CJK 与 Emoji 即使由多个 Unicode-range 文件组成,在作者图中仍是一条逻辑边。终端 Text 与 Fine Caption 都拒绝省略字体栈;Visual IR 不接受机器字体兜底。对于同时具有文本与 Emoji 两种呈现的符号,作者应写真实的 Unicode Emoji 序列(例如包含 VS16 的 `☎️`);任何包都不会为了强制彩色而改写显示稿。-品牌字体与自定义字体仍是显式作者资产,不会被塞进共享目录:+品牌字体与自定义字体仍是显式作者资产,不会被塞进中央目录:```svml<import as="media" from="@hypit/media@1"/>@@ -334,7 +337,7 @@ Caption Recipe 不再重复家族、字重或字形。CJK 与 Emoji 即使由多一个完整的 `recipes.svs` 文件,用于四段式说话人头像项目:```svs-<?svml using="@hypit/svs@1"?>+<?svml using="@hypit/recipe@1"?><sheet version="1" id="studio">diff --git a/docs/zh/quickstart/timing.md b/docs/zh/quickstart/timing.mdindex 63460ce2..4b665ed0 100644--- a/docs/zh/quickstart/timing.md+++ b/docs/zh/quickstart/timing.md@@ -17,7 +17,7 @@ Hypit 只有一条节目时间轴:`Timeline`。它只是 `{ id, frameRate, fra只需要 Timeline,不需要媒体或 Script。```svml-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="whisperx" from="@hypit/whisperx@1"/><import as="semantic" from="@hypit/narrative-temporal@1"/><import as="time" from="@hypit/timeline-author@1"/>@@ -32,9 +32,9 @@ Clock 固定最终 Timeline 与所有局部时间域共享的帧率:```svml<time:Clock id="clock" frame-rate="30"/>-<pipeline:Normalize id="opening-media" source={opening-video.video}+<mediaop:Normalize id="opening-media" source={opening-video.video}video="primary-moving" audio="default" span-authority="video" clock={clock}/>-<pipeline:Normalize id="answer-media" source={answer-video.video}+<mediaop:Normalize id="answer-media" source={answer-video.video}video="primary-moving" audio="default" span-authority="video" clock={clock}/>```diff --git a/docs/zh/quickstart/tracks.md b/docs/zh/quickstart/tracks.mdindex a46ea865..43aae7cf 100644--- a/docs/zh/quickstart/tracks.md+++ b/docs/zh/quickstart/tracks.md@@ -21,7 +21,7 @@ Script → CaptionDocument + NarrativeCaptionBinding<import as="caption" from="@hypit/caption@1"/><import as="caption-fine" from="@hypit/caption-fine@1"/><import as="media" from="@hypit/media@1"/>-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/>```公共 Caption 负责 CaptionDocument、完整 Alignment Unit 的 Selection/Role 投影、样式分配与@@ -52,9 +52,11 @@ caption.primary {``````svml-<fonts:Stack id="caption-fonts" family="inter" weight="700" style="normal" emoji="color">- <fonts:Fallback family="noto-sans-sc" weight="700" style="normal"/>-</fonts:Stack>+<fonts:Face id="caption-latin" package="@fontsource-variable/inter" weight="700" style="normal"/>+<fonts:Face id="caption-han" package="@fontsource-variable/noto-sans-sc" weight="700" style="normal"/>+<media:FontStack id="caption-fonts" primary={caption-latin}>+ <media:Fallback font={caption-han}/>+</media:FontStack><caption-fine:Style id="primary-caption" recipe={recipes.caption.primary}font={caption-fonts}/>```@@ -125,7 +127,7 @@ Recipe 与类型化 Motion 都只是可选的复用值:<space:Frame id="product-frame" within={vertical.bounds}left="8%" top="20%" right="92%" bottom="68%"/>-<pipeline:Normalize id="product-media" source={product-motion.video}+<mediaop:Normalize id="product-media" source={product-motion.video}video="primary-moving" audio="none" span-authority="video" clock={clock}/><visual:Motion id="product-motion-in">@@ -160,7 +162,7 @@ Clip 模型也能表达全屏切换、分屏和角落小窗。公开 Clip 只有| `media={...}` | `SynchronizedMedia` | 直接连接显式准备好的含时素材 || `surface={...}` | `CompositableSurfaceRef` | 直接连接带透明度语义的静态或含时 Surface |-生成或导入的视频 Blob 经 `<pipeline:Normalize>` 进入 Track:它检查该 Blob、选出其中的流并放到同一个帧域上,输出的 `.media` 即 `media=` 所连接的值。`audio="none"` 只取画面,`audio="default"` 取源自带的声音,再由 `audio-gain` 调节。输入名必须显式,是为了绝不靠猜测把一个通用 Blob 当成图片或视频。+生成或导入的视频 Blob 经 `<mediaop:Normalize>` 进入 Track:它检查该 Blob、选出其中的流并放到同一个帧域上,输出的 `.media` 即 `media=` 所连接的值。`audio="none"` 只取画面,`audio="default"` 取源自带的声音,再由 `audio-gain` 调节。输入名必须显式,是为了绝不靠猜测把一个通用 Blob 当成图片或视频。**输出:**`{product-broll.program}` 与 `{product-broll.visual}`。音频始终在 Audio Track中单独声明;这里连接 SynchronizedMedia 不会顺带选择它的音频成员。@@ -172,13 +174,13 @@ Clip 模型也能表达全屏切换、分屏和角落小窗。公开 Clip 只有```svml<import as="media" from="@hypit/media@1"/>-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="audio" from="@hypit/audio-track@1"/><import as="time" from="@hypit/timeline-author@1"/><time:Clock id="clock" frame-rate="30"/><media:Audio id="music" src="./assets/music.wav"/>-<pipeline:Normalize id="music-media" source={music}+<mediaop:Normalize id="music-media" source={music}video="none" audio="default" span-authority="audio" clock={clock}/><audio:Track id="music-bed" timeline={speech.timeline}>@@ -220,7 +222,7 @@ Track 都会作为独立输入进入 Film。输出 `{music-bed.audio}` 是普通<space:Canvas id="vertical" width="1080" height="1920"/><space:Frame id="title-frame" within={vertical.bounds}left="6%" top="6%" right="94%" bottom="16%"/>-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><text:Style id="title-style" recipe={recipes.text.title} font={title-font}/><text:Flow id="title" timeline={speech.timeline} within={title-frame}style={title-style} z="90" align="center" during="timeline">@@ -286,7 +288,9 @@ Run 时,继续使用内联 `P`/`Span`/`Break`。## 榜单板-榜单板让一份有序列表跟着 Script 动起来。具体的容器、条目和 Style 词汇由包声明;写作前先检查已安装包的词汇。+榜单板让一份有序列表跟着 Script 动起来。Ranking、Depth Stack 与 Comment Sticker 是可选包,不随默认+Hypit 安装。使用前先把所选发布版本写入视频项目的普通 `package.json` 与 lockfile,再检查已安装包的词汇。+具体容器、条目和 Style 仍由各包自己声明。| 容器 | 条目 | 样式 ||---|---|---|@@ -377,37 +381,6 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出**输出:** `{deck.visual}`——一条 VisualTrack,与 Film 中其它每一条 Track 平级。-## 屏幕叠加层--覆盖在整个画面之上、而非落在某个 Frame 里的效果:切点上的一次闪白、持续整个 Selection 的暗角、铺满全片的颗粒。一条 Track 承载全部,每个子元素是一个效果加它自己的时间窗。--```svml-<import as="screen" from="@hypit/screen-overlay@1"/>-```--`screen:Track` 接受 `id`、`canvas`,以及 统一的 `timeline` 时间来源。它的子元素就是各个效果,至少一个,各自为空,都必须带 `z` 决定层叠顺序,并且各有一个时间窗,形式是以下之一:--| 时间窗 | 写法 |-|---|---|-| 整个节目 | `during="timeline"` |-| 已解析的 Window | `during={story-time.overlay}` |-| 绝对起点与时长 | `from="2s" for="12f"` |-| 显式区间 | `from={story-time.start} until={story-time.end}` |--时长写作 `12f`、`250ms` 或 `1.5s`。一个 Selection-只表示一个连续区间,一个 Moment 只表示一个点;同一效果需要再次出现时,应再写一个 item。--可用的效果有十一种——`Flash`、`ColorWash`、`Vignette`、`ScanLines`、`DirectionalMatte`、`WhipVeil`、`GlitchVeil`、`Grain`、`LightLeak`、`Bokeh` 与 `TVStatic`——每种各有自己的必填属性,例如 `Flash` 的 `color` / `intensity` / `attack` / `hold` / `decay`,或 `Vignette` 的 `center-x` / `center-y` / `radius-x` / `radius-y` / `softness` / `color` / `opacity`。它们都没有默认值:一个效果要么把自己的形状说全,要么被拒绝。--```svml-<screen:Track id="effects" timeline={speech.timeline} within={vertical.bounds}>- <screen:Flash during={story-time.overlay} z="80"- color="#ffffff" intensity="0.6" attack="2" hold="2" decay="6"/>-</screen:Track>-```--**输出:** `{effects.visual}`——一条 VisualTrack。-## 评论贴纸放置在 Frame 中的社交风格评论卡:头像、作者、评论正文,以及可选的一行附注。@@ -420,7 +393,7 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出`comment:Track` 接受 `id` 与 `timeline`,两者皆为必填。-`comment:Sticker` 必填 `id`、`frame` 与 `style`,时间窗与上面的屏幕叠加层相同。它的文案来自 `comment=` 属性或元素自身的文字,两个都给会被拒绝。可选的 `author`、`header` 与 `meta` 各接受字符串或 Text 引用,`avatar` 接受一张图片;这里没有 `z`,层叠顺序来自 recipe 的 `stack-order`。+`comment:Sticker` 必填 `id`、`frame` 与 `style`。它的 Window 可以使用 `during`、`from` + `for` 或 `from` + `until`。文案来自 `comment=` 属性或元素自身的文字,两个都给会被拒绝。可选的 `author`、`header` 与 `meta` 各接受字符串或 Text 引用,`avatar` 接受一张图片;这里没有 `z`,层叠顺序来自 recipe 的 `stack-order`。```svml<comment:Style id="social" recipe={recipes.comment} font={ui-font}/>@@ -441,9 +414,9 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出```svml<import as="caption" from="@hypit/caption@1"/><import as="caption-fine" from="@hypit/caption-fine@1"/>-<import as="fonts" from="@hypit/fonts-open@1"/>+<import as="fonts" from="@hypit/fontsource@1"/><import as="media" from="@hypit/media@1"/>-<import as="pipeline" from="@hypit/media-pipeline@1"/>+<import as="mediaop" from="@hypit/media-operations@1"/><import as="visual" from="@hypit/visual-track@1"/><import as="text" from="@hypit/text-fine@1"/><import as="audio" from="@hypit/audio-track@1"/>@@ -453,8 +426,8 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出<time:Clock id="clock" frame-rate="30"/><!-- Captions: primary style for all text -->-<fonts:Stack id="caption-font" family="inter" weight="700" style="normal"/>-<fonts:Stack id="title-font" family="inter" weight="900" style="normal"/>+<fonts:Face id="caption-font" package="@fontsource-variable/inter" weight="700" style="normal"/>+<fonts:Face id="title-font" package="@fontsource-variable/inter" weight="900" style="normal"/><caption-fine:Style id="base-caption" recipe={recipes.caption.base} font={caption-font}/><caption-fine:Caption id="captions" document={story.caption} timing={story-captions}@@ -472,7 +445,7 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出left="10%" top="20%" right="90%" bottom="70%"/><!-- Media:Selection 期间显示一个普通 Clip -->-<pipeline:Normalize id="card-media" source={motion.video}+<mediaop:Normalize id="card-media" source={motion.video}video="primary-moving" audio="none" span-authority="video" clock={clock}/><visual:Track id="cards" timeline={speech.timeline}><visual:Clip media={card-media.media} frame={card-frame}@@ -488,7 +461,7 @@ DepthStack 的直接子元素,自闭合,至少一张,按书写顺序发出<!-- Audio:先规范化一份已声明素材,再把它放满整个节目 --><media:Audio id="music" src="./assets/music.wav"/>-<pipeline:Normalize id="music-media" source={music}+<mediaop:Normalize id="music-media" source={music}video="none" audio="default" span-authority="audio" clock={clock}/><audio:Track id="music-bed" timeline={speech.timeline}><audio:Clip source={music-media.media} during="timeline"