[josephfusco]

Presence Scenes changes are outside Presence API's release path, so a scenes-only change like #918 ships in the next zip only once something else in Presence API cuts a release; until then the newest release has no presence-scenes.zip, which is what Riff's wp-env needs to install it by URL.

I couldn't run the job itself: I built the zip locally with the same rsync and zip commands and checked it holds one presence-scenes/ folder without tests/, but actionlint and zizmor only ran in CI.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): claude-opus-5-5
Used for: Wrote the workflow step, the .distignore and the CONTRIBUTING line; to be reviewed by me before merge.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props huzaifaalmesbah, joefusco.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[github-actions]

🛝 WordPress Playgrounds

Built from 2dace45

	Post locks	RTC	Synced patterns	Settings
Single site
Multisite

[huzaifaalmesbah]

LGTM! The release step and .distignore packaging are clean, and verified the zip structure matches WordPress plugin install requirements.