Harden release workflows and engine lifecycle

[Alex-Wengg]

Summary

• make ACE-Step cache use, cancellation, output cleanup, and disposal safe across tabs and lifecycle races
• protect active songs with per-output ownership locks before reclaiming stale OPFS data
• await DiCoSe GPU teardown before starting replacement generation work
• bound ACE worker disposal and force local teardown when a worker becomes unresponsive
• make playground, DiCoSe, and Kokoro resource teardown deterministic
• separate the publishable SDK registry from site-only engines and validate the packed SDK in clean browser and SSR consumers
• deploy GitHub Pages only after every CI job succeeds
• clarify and shorten the setup, music-download, playback, stem, and release documentation
• update development dependencies and GitHub Actions runtimes to remove security and deprecation warnings

Validation

• npm audit: 0 vulnerabilities
• npm run test:unit: 4 passed
• npm run test:integration: 39 passed
• npm run acestep:test: 2025 passed, 27 skipped artifact-dependent tests
• npm run dicose:test: 34 passed, 1 skipped artifact-dependent test
• npm run build
• npm run sdk:test
• npm run wasm:verify
• npm run ci:smoke with real Parakeet, EOU, and Kokoro model assets
• npm run typecheck
• npm run format:check

Manual coverage note

No browser session was attached to this environment, so I could not repeat the full 5.75 GB WebGPU song-generation and audio-playback flow manually. The relevant worker, lock, cancellation, storage, disposal, and timeout paths are covered by the integration tests. The optional backend parity script also needs local model artifacts under /tmp/pk-raw; its artifact-free WASM parity counterpart passed.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	fluidaudio-web	2e1be1f	Sep 15 2026, 05:35 PM