hypit

Highlights

• Hypit now has a domain-neutral language host and an adaptive video authoring layer. SVML, SVS and SVRun remain the author-facing source family, while video semantics, audiovisual tracks, components and execution are owned by composable packages instead of being hard-coded into Core.
• Time is explicit and reusable. Timeline construction resolves an absolute end and anchors; semantic projections are explicit author relations; component surfaces consume named Windows and Instants. Visual, audio, typography and caption tracks share a clearer item model without making semantic time a mandatory skeleton.
• Captions preserve authored structure. Caption documents distinguish display words, semantic units and authored cues, with complete timing bindings and Studio presentation based on the same model.
• Media composition is more orthogonal. A-roll and B-roll use the same visual and audio clip model after contributing any timing evidence. Playback, spatial mapping and drawing order are expressed independently, and local media/image execution has a single owner.
• The local toolchain is composable without a second package system. The root CLI discovers installed command contributors through project configuration; npm packages and the package-manager lockfile remain the installation and version authority.
• The Distribution has an explicit ownership graph. Essential implementation packages are embedded, while default models, providers and kits are ordinary versioned dependencies. Release candidates are assembled from that graph and verified through cold installation and real rendering on Linux and Windows.

Upgrade

Install @hypit/[email protected] with your package manager and commit the resulting lockfile. This is an architectural release: migrate 0.2 Sources, Recipes, Runs and project components to the 0.3 author model rather than relying on removed legacy forms. The repository examples, public documentation and Hypit Skill describe the current syntax and ownership boundaries.

If you installed the Hypit Skill separately, refresh that installation from hypit-ai/hypit; npm and Skill installations update independently.

Validation

Publication is gated on type checks, tests, cold installation of one immutable candidate on Linux and Windows, component compilation, browser preparation, a 240-frame render, export and media decoding. The Distribution is published only after all independent package versions and candidate integrity have been verified.

Highlights

• Frame animations of later Presents render at the right time again. Since 0.2.15, a lifecycle motion (for example enter: fade) on an Item that starts after frame 0 was evaluated at absolute composition time, so the Item skipped its fade or stayed invisible for most of its window. Animations now follow their own Present's time, as in 0.2.13. (#373, fixes #372)
• Still-image clips keep their colors. Pictures turned into video are now converted with the BT.709 matrix and tagged, so players no longer shift the colors of HD still clips. (#363)
• Alpha sources normalize about 9x faster. The lossless VP9 encode for video with transparency now runs at libvpx's fastest speed. Decoded frames are identical. (#383, fixes #382)
• hypit media fetch works with TikTok. The locked yt-dlp environment now includes curl_cffi, so yt-dlp can impersonate a browser. (#384, fixes #381)
• Frame-boundary errors surface before Build. A Timeline end or Take at that does not land on a whole frame (for example end="8s" at 30000/1001 fps) is now reported by hypit check when the Clock is static (#355, fixes #354). hypit plan also reports any Producer failure in a step that carries no request, and exits 1 instead of calling the plan valid (#348).

Upgrade

Install @hypit/[email protected]. Existing video projects and materials need no migration.

If you have already run hypit media prepare-fetch, run it once more so the prepared environment picks up curl_cffi.

hypit.cli-plan@1 output gains producerFailureCount, present on every plan, and producerFailures, present when it is non-zero.

Validation

CI passed on Linux and Windows for the release candidate on main.

Highlights

• A network failure now says which network failure it was. Node's fetch reports every connection-level failure as fetch failed and keeps the reason on error.cause, which the shared transport() helper dropped. A failed HypiHub catalogue check therefore read ... generation not submitted: fetch failed, which cannot tell DNS, TLS, a reset, a timeout or a proxy problem apart, and was misread as an upstream provider outage.

  The cause's code and message are now appended:

  Failure	Before	After
  DNS	fetch failed	fetch failed: getaddrinfo ENOTFOUND <host>
  Certificate	fetch failed	fetch failed: CERT_HAS_EXPIRED certificate has expired
  Connect timeout	fetch failed	fetch failed: UND_ERR_CONNECT_TIMEOUT Connect Timeout Error (attempted address: <ip>:<port>, timeout: 10000ms)

  Every provider's network failures pass through this helper, so HypiHub catalogue reads, OAuth refresh, uploads and downloads all gain the reason. The text comes from Node's network layer (host, address and port, error code, certificate reason) and contains no URL path, query string or header. (#376)

Upgrade

Install @hypit/[email protected]. Existing video projects and materials need no migration. Error messages keep their original text as the prefix.

Validation

PR checks passed on Linux and Windows, including the packaged-Distribution check. The new messages above were produced by sending real failing requests through transport().

Highlights

• hypit packages status <name>@<version> now answers the question a Build asks. It read the machine package home and nothing else, while the loader finds an external package in two places — the node_modules chain above whoever requires it, and the machine home addressed by the version that requirer declares. A package installed where the first half looks was reported not ready, and hypit doctor then loaded the provider from it on the next line.

  Status locates the Distribution package that declares the specifier and makes one locateNodePackage call from there, so one call covers both places instead of this command reimplementing one of them beside the loader. The version is still exact and checked twice: a requirer is found only at the version asked for, and the resolved manifest's version is compared to it afterwards. A specifier nothing declares now names that as the reason instead of a bare not-ready.

  This is what an agent container hits: npm i -g @hypit/hypit @hyperframes/engine puts both in the same global node_modules, Builds resolve the engine and work, and packages status called it missing.

Upgrade

Install @hypit/[email protected]. Existing video projects and materials need no migration. packages status output gains declaredBy, installedVersion and detail as optional fields; the machine-readable format stays hypit.cli-package@1. packages install is unchanged.

Validation

The packaged Distribution was installed outside the checkout, used to compile the bundled project component, prepare its font and managed browser, render and export an MP4, and decode the complete output successfully.

The status change itself was measured in a container-shaped layout — the Distribution and its dependencies installed globally, machine package home empty — where @hyperframes/[email protected] and @hyperframes/[email protected] now report ready with the declaring package and the resolved installation path, against not-ready and exit 1 before. An unknown version and an unknown package still exit 1, naming that no Distribution package declares them.