Skip to content

v2.0.1 — Release integrity remediation

Choose a tag to compare

View all tags
@wzwailr wzwailr released this 31 Aug 06:04
· 7 commits to main since this release
v2.0.1
c3dba22

v2.0.1 — Release-integrity remediation

v2.0.1 makes the public package, documented runtime contract, real renderer, and release evidence agree. It preserves v2.0.0 as historical evidence and supersedes it for new installations.

Install

The dependency-free Python lifecycle CLI works without Node.js:

pipx install creating-explainer-videos-skill==2.0.1
explainer-video-skill --version

Project creation, template preview, rendering, and media commands use the bundled JavaScript runtime and require Node.js 22+, Chrome or Edge, FFmpeg, and ffprobe.

The guaranteed npm-form artifact is the GitHub Release tarball:

npm install --global https://github.com/wzwailr/creating-explainer-videos-skill/releases/download/v2.0.1/creating-explainer-videos-skill-2.0.1.tgz

The npm Registry is an independent publication channel. Check its live state before using it:

npm view creating-explainer-videos-skill version

What changed

  • Node.js 22+ now matches the pinned HyperFrames 0.8.15 runtime.
  • doctor detects installed or pinned on-demand HyperFrames without downloading during diagnosis.
  • Generated renderers satisfy the HyperFrames composition, timeline, font, caption, and safe-geometry contract.
  • Cover capture waits for a real non-empty output.
  • Short-video contact sheets must exist and be non-empty before the audit can pass.
  • Python wheel and source-distribution metadata is pinned to Core Metadata 2.4 for current Twine/registry compatibility.
  • CI performs an actual browser frame render, WAV generation, audio/video mux, ffprobe inspection, and automated media audit.

Scope and release boundary

The built-in scene is a generic runnable mechanism scaffold. It does not automatically create subject-specific high-fidelity diagrams, illustrations, or visual direction. The Agent must author those assets and motions from the knowledge structure, then a named human must review the exact candidate hash. Automation can produce only release_candidate_pending_human_listen, never passed.

Release assets include the PyPI wheel/source distribution, npm tarball, portable Skill ZIP, and SHA256SUMS attached to the GitHub Release.

Assets 7
Loading