Skip to content

feat(music-data): take the deck model's WASM release packages as engines - #28

Merged
nichinichisou0609 merged 2 commits into
mainfrom
feat/deck-release-engines
Oct 6, 2026
Merged

nichinichisou0609 merged 2 commits into
mainfrom
feat/deck-release-engines

Conversation

@nichinichisou0609

Copy link
Copy Markdown
Collaborator

Summary

  • music-data --replay-engine and --recommend-engine take the ournotes-deck WASM release packages of the pinned model: ournotes-replay-wasm-vVERSION.tar.gz and ournotes-recommend-wasm-vVERSION.tar.gz, or their extracted directories. The package's build-info.json must describe that module's WASM package (kind, module), name the pinned commit and list the SHA-256 of the web binding's JS and WASM files. The web binding and build-info.json are copied byte for byte into the replay bundle (engine/ournotes_replay_wasm.js, engine/ournotes_replay_wasm_bg.wasm, engine/build-info.json, and the same under recommend/), so a published engine is the released one and its hashes match the release.
  • .github/workflows/deck.yml follows ournotes-deck's releases instead of its main: it moves the pin to the latest release once that release's replay and recommendation WASM packages are published, and names the tag in the pull request.
  • Moves the deck model to ournotes-deck v0.0.2.

Tests

tests/test_replaydata.py builds synthetic release packages and covers directory and .tar.gz input, a stale commit, a package of the other module, a changed WASM file, a missing file and a file that is not a package.

🤖 Generated with Claude Code

nichinichisou0609 and others added 2 commits October 6, 2026 09:06
--replay-engine and --recommend-engine now take the ournotes-deck WASM
release packages of the pinned model, as the downloaded
ournotes-<module>-wasm-vVERSION.tar.gz or its directory. The package's
build-info.json must describe that module's WASM package, name the
pinned commit and list the SHA-256 of the web binding's JS and WASM
files; the binding and build-info.json are copied byte for byte, so the
published engine is the released one.

The deck pin workflow follows ournotes-deck's releases: it moves the
pin to the latest release once its replay and recommendation WASM
packages are published.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moves the deck model to ournotes-deck v0.0.2 (76e96b617842bdcc031cce98e3dfeead27ddbb85),
https://github.com/empty-sekai/ournotes-deck/releases/tag/v0.0.2

Music data files made after this change name the new commit in `provenance.deck.commit`; their deck
statistics may differ.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nichinichisou0609
nichinichisou0609 merged commit 8a088f4 into main Oct 6, 2026
7 checks passed
@nichinichisou0609
nichinichisou0609 deleted the feat/deck-release-engines branch October 6, 2026 01:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant