0.1.21: synthesized music and creative playbook

新片现在默认使用代码合成的原创配乐，并冻结 WAV 与同源音乐时间轴。全片配乐和 Scene 动作共用绝对帧原点；有口播时继续以实测封存音频决定字幕与语义边界，无口播时可由音乐安排画面。画幅由用户选择，允许连续长场景和安静转场。

随 Workspace 分发的创作手册、剪纸案例、参考图和可运行教学小片补充了构图、材质、动作阶段、转场与混音方法。本版还整合 Edge TTS 宿主代理支持、受检输出失败恢复、兼容正文 BGM 隔离，以及五首获授权的循环音乐 seed。

源码完整检查：1440 项测试，1438 通过、零失败、2 项 Darwin 专属跳过。Actions 对精确候选执行包检查、208 项回归、源码/构建、全新 Workspace、doctor 和最小真实渲染/完整解码，再以 OIDC provenance 发布两个包。

维护者批准本版复用此前验收。独立 Codex CLI 首用因 HTTP 401 未通过，本版没有新的原生首用认证；旧收据保留原版本和验证范围。参见批准记录和发布 Actions。

• @axmorf/studio@0.1.21
• create-axmorf-studio@0.1.21

创建新 Workspace：npm create axmorf-studio@latest my-video -- --yes。已安装 Workspace 和既有作品不会因本次发布自动升级或迁移。

AXMORF Studio 0.1.20

Changes

• Fix bound Scene preview for continuous owners spanning several visual beats. Preview now uses the production grouping, checks every frozen beat and timing boundary, and forwards the full owner captions and covered beats.
• Support authored-frame preview without attempting to read absent narration manifests. Keep legacy explicit-null narration checks.
• Authenticate current Codex code-mode diagnostic batches, serialized authoring, stdout accumulation and temporal image bytes against the complete original app-server records. Missing production mutations and mismatched native evidence still fail closed.

Verification

• Actual post-merge full-film acceptance: a 60-second 1080×1920 continuous scene and fresh 40-second 1280×720 six-scene productions, with H.264/AAC stereo, complete decoding and both official covers.
• Fresh candidate native first use: one ordinary business prompt, 420.923 seconds of four-way bound task overlap, eight fresh production children, four refill admissions and one fixed continuation. Exact package contents and all generated guides were unchanged.
• Final delivery checks pass. Visual samples and muted technical playback were reviewed; subjective listening and stable aesthetic quality are not certified.

Publication uses the existing trusted OIDC workflow and the exact reviewed candidates. Full source, regression, package, fresh-install and registry checks are recorded in the repository evidence.

The unpublished v0.1.19 tag is retained with its failed regression-inventory CI record. This release corrects that inventory and uses a new 0.1.20 candidate installation and native acceptance.

v0.1.18 — continuous film authoring

This release merges the published 0.1.17 branch with the continuous-film authoring upgrade. The default branch and v0.1.18 now share the merged release commit.

• Whole-film direction, multi-Beat Scene ownership and continuous camera/event motion.
• Explicit authored frame timing with zero TTS, alongside the existing narrated and visual-scene contracts.
• Frozen whole-film preview, presence-aware revision snapshots and single-encode AAC alignment.
• Preserved shared SVG handoffs, bound Scene previews and whole-composition BGM from 0.1.17.
• Updated Workspace-local video Skill and generated guidance, authored chapter review fix and patched transitive dependencies.

Release verification retains exact package fingerprints, affected regressions, type/lint/build, dependency audit, fresh external installation and doctor, a minimal real render with EOF decoding, and npm trusted-publisher provenance. The maintainer explicitly approved reuse of earlier video/native acceptance; fresh merged-package native first use is not claimed.

See the release plan and review scope.

v0.1.10 — production supervision and task recovery

Video production now keeps the Root Agent responsible through verified delivery using long blocking waits or native completion events. Root can guide the owning worker and organize at most one recovery for a proven authored-output fault after the previous continuation and workers exit. System, provider, permission, identity and integrity failures remain diagnosis-and-report only.

The updated instructions ship through create-axmorf-studio; use the published creator to create a new Workspace. Existing Workspace guides are not automatically migrated. Runtime validators, task ownership and immutable failed attempts retain their existing gates.

Validation includes 811 repository tests, package type checking/builds, macOS ARM64 and exact-tag Linux gates, and fresh native Codex/Hermes runs with five creative children, peak concurrency four, one refill, and verified four-file deliveries. This is an Agent-guidance release; a real fault-recovery video run and a quantitative token-savings benchmark are not claimed.

Published-package first-use verification also passed: fresh Codex and Hermes runs produced 26.67-second and 27.37-second videos with verified four-file deliveries. Both public latest versions and registry integrities were checked against the exact CI tarballs.

v0.1.9

Native video workers now enter their bound task workflow directly, with Root-only environment checks and a fresh child session for each TaskRevision. New npm Workspaces default to subagents with maximum concurrency 4. macOS cleanup failures retain sanitized process-inspection diagnostics without weakening cleanup checks.

Both @axmorf/studio@0.1.9 and create-axmorf-studio@0.1.9 are published with npm provenance. Official-registry fresh Workspace tests passed using real Codex and Hermes sessions: each used 5 production children, peak concurrency 4 and one queued admission. They delivered 27.93 s and 27.90 s videos; original continuations, seven final checks, exact-four checksums and EOF decoding passed. Each host received one ordinary video prompt, without controller follow-ups or package repairs.

Validation: 811 local macOS tests passed; macOS ARM64 CI passed; Linux passed 810 with one explicitly Darwin-only test skipped. Published package files match the accepted candidates byte-for-byte and registry integrity matches CI archives.

Test profiles and Workspaces were fresh, with normal host permissions rather than OS filesystem isolation. External provider failures remain possible.

Full release evidence · Publish workflow

AXMORF Studio 0.1.8

Improves first-time video creation from an npm workspace:

• Complete requirement examples and structured authoring error guidance.
• Total-duration budgets and measured duration/deviation feedback.
• Installation stages, elapsed time and retained npm logs.
• Mandatory Codex/Hermes first-use candidate evidence before npm publication.

Both packages use version 0.1.8. Strict validators, PCM timing authority and immutable production attempts are preserved.

Candidate acceptance used fresh profiles and only ordinary video requests: Codex produced 29.3 seconds and Hermes 27.7 seconds. Both completed the original continuation, with no follow-up engineering prompts or package edits; Agent-owned output corrections were allowed. Exact delivery checks, checksums and EOF decoding passed.

macOS ARM64 CI: https://github.com/AXMORF/axmorf-studio/actions/runs/34052681328

Official npm acceptance after publication used two new workspaces created by npm create axmorf-studio@latest, new caches and new native profiles. Codex produced 26.9 seconds; Hermes produced 26.87 seconds. Both original continuations succeeded, independent public final checks passed 7/7 each, and exact files, checksums, media properties and full EOF decoding passed. Both installations' 252 runtime files and 10 guide files match the accepted candidate.

Hermes corrected an initial requirement scope/targetMeaningIds mismatch using the new structured error and example, plus its own JSON parsing and Scene readability issues. No user follow-up or maintainer intervention was supplied. This is completion evidence, not a zero-error or exact-duration guarantee. The runs cover one Mac and model with two native hosts and unattended authorization.

Both macOS and Ubuntu CI passed the complete 794-test suite.

npm publication CI: https://github.com/AXMORF/axmorf-studio/actions/runs/34053013522

AXMORF Studio v0.1.7

Fix macOS cleanup false failures discovered during real Hermes and Codex video acceptance.

• Accept the legitimate macOS ?E state for unrelated processes; unknown or active members in the owned group still fail closed.
• Allow a single bounded close-time group snapshot after a successful signal-zero observation as well as EPERM.
• Preserve strict process ownership, deadlines, output diagnostics and production failure boundaries.
• Includes prior Workspace Skill/docs, creator browser preparation, default template, and current four-file final verification improvements.

The new regressions failed before the fix. All 778 repository tests passed with no skips, along with package, macOS ARM64 and npm publication gates. The corrected source passed ten concurrent real-delivery final checks before release.

A fresh Workspace created from official npm latest on macOS completed two real Agent videos:

• Codex 0.153.4: “从十分钟专注开始”, 31.67 seconds, five committed Agent artifacts.
• Hermes 0.21.0: “每天进步一点点”, 31.3 seconds, six committed Agent artifacts.

Both reached project-production-complete. Both public final commands then passed all seven checks concurrently. Independent verification confirmed exact four-file delivery, checksums, 1080×1920/30fps H.264, stereo AAC, PNG covers and complete EOF decode. All 251 installed runtime files and eight generated instruction files remained byte-identical to release tarballs. No installed-package patch or validator weakening was used.

Detailed release and acceptance evidence

v0.1.6 — reliable cleanup and current delivery checks

Improve Workspace process diagnostics and replace stale final-validation evidence requirements with current production verification.

• Preserve owned child status/output and bound cleanup, registration and deadlines.
• Handle the macOS zombie-group exit race without accepting real or unknown permission failures.
• Verify current Revision, artifact set, expected DeliveryBuildId, exact four-file media and a stable read-only snapshot.

776 repository tests, the macOS ARM64 gate and npm publication passed. A fresh official npm Workspace completed real Codex 0.153.4 and Hermes 0.21.0 videos (32.23 s and 32 s); independent checksums, codec/specification and EOF checks passed. Published package bytes remained unchanged.

A subsequent concurrent final check exposed an additional macOS edge: an unrelated process state ?E caused the strict snapshot parser to reject the target group's absence. The videos are valid, but v0.1.6 does not close this cleanup issue. v0.1.7 corrects this parser edge and is now published.

v0.1.5 — production-valid default templates

Fix the default intro/outro validation failure found by a real Hermes run against the published npm Workspace.

The shipped templates now use explicit readable text sizes and numeric geometry for logo zoom and text movement. Production validators remain unchanged. New regressions load the creator's real default configuration, create a Project, copy the full template source/audio graph, produce fixed artifacts and revalidate them.

This release includes the Workspace setup, creation guidance, process lifetime and interruption-recovery improvements from v0.1.4. Existing Project-local immutable template instances are preserved; the acceptance run uses a newly created Workspace and Projects.

Validation: complete repository checks with 757 passing tests, package checks/typechecks/build, and actual rendered intro, credits and follow frames on macOS x86_64.

Release gates: macOS ARM64, npm publication and registry integrity. Both passed. Hermes completed a real 31.13-second video on macOS x86_64. Codex reached doctor but exposed intermittent process-group cleanup EPERM; it stopped before Project creation. A follow-up source patch is being prepared. Dual-Agent acceptance is not yet complete.

v0.1.4 — npm Workspace reliability

Follow-up acceptance: a fresh Hermes video run exposed a fixed-validation failure in the shipped default intro template (readability-transform). The production lifecycle stopped correctly, but default video delivery is not accepted for this version. The template correction and real default-template regression are published in v0.1.5; validators remain unchanged.

Workspace creation now prepares the pinned browser and verifies a real PNG render before reporting readiness. Browser downloads honor supported native Node proxy settings, and read-only diagnostics cannot start competing downloads.

• Add public creation context, validated examples and JSON Schema; preserve configured execution and boundary-scene defaults.
• Improve readability errors with source locations and correct SVG CSS precedence.
• Bound media processes, clean up process groups and preserve diagnostic logs; add explicit interruption inspection and safe fresh-attempt recovery.
• Resolve delivery media tools from the selected Workspace, including revision candidates.
• Derive the creator's default runtime version from its own release manifest.

Both @axmorf/studio@0.1.4 and create-axmorf-studio@0.1.4 were published with provenance and exact registry-integrity verification.

Validation: 755 tests on the release commit, complete macOS ARM64 package/scaffold gate, Linux publication gate, and a cold macOS x86_64 package installation with a real browser render.

macOS gate · npm publication