A release before M5Stack merges the first store PR would open a second PR that adds the same files, so the two would conflict and both would wait for a person. store-publish.py now publishes nothing while any open PR of ours is for the package, and in CI it shows a warning. The release itself goes out as usual. After the merge, a rerun of that release's store job publishes its version; the release skill says how. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>