shiroikuma-ongaku

Check whether Felicity Music Player upstream (Hamza417/Felicity) has a newer release tag and, if so, sync the shiroikuma.ongaku fork to it — present 白い熊 a proceed-gated table of what the new upstream version introduces, then (on go-ahead) fast-forward `master`, rebase the `custom` commit stack onto the new tag, and build the new signed APK per the ongaku-build skill. Use this skill whenever 白い熊 runs /upstream-new-version, or asks to "check for a new Felicity version", "sync to the latest Felicity release", "update to the new upstream", "rebase onto the new tag", or otherwise wants the ongaku fork brought up to a newer upstream release. This is the orchestration layer on top of ongaku-build; read that skill for all the build/rebase/version detail this one references.

Publish 白い熊's shiroikuma-ongaku fork (customized Felicity Music Player, app id shiroikuma.ongaku, label "白い熊 音楽") as a GitHub release — tag the newest already-built APK, refresh the fork README + CHANGELOG, switch the GitHub default branch to `custom`, and create the release with the APK attached. Use whenever 白い熊 says /publish-version, "publish a version", "publish to github", "make/cut a release", or "release the latest build" in the ongaku fork. Never rebuilds — it publishes the newest APK already in ~/tmp/; if there is none, tell 白い熊 to build first (ongaku-build).