chore(governance): onboard playtester

[zoeyrose]

Summary

• onboard atrinik/playtester as active Classic tooling
• require the proven Playtester validation and Conventional PR title checks
• protect release tags and record the repository's source-only semantic-release policy
• publish the tooling / classic / active / semantic-release custom-property values

The destination repository now carries the MIT-licensed source, documents the GPL boundary for native binary distributions, and runs its source-only release workflow with actions/setup-node. These contracts landed on atrinik/playtester@f2a2f41accb52b6fb5de6da28653028beaac6736; both required check names have completed successfully there.

Related work: atrinik/playtester#11 and atrinik/tools#19.

Validation

• bin/validate
• every tests/*.sh test
• bash -n bin/* tests/*.sh
• shellcheck bin/* tests/*.sh
• actionlint .github/workflows/*.yml
• bin/publish in plan mode
• bin/publish-repository-properties in plan mode
• git diff --check

The organization-policy plan contained the expected playtester pull-request, required-CI, and release-tag convergence. It showed no archival, security-policy, or immutable-release drift. The repository-property plan contained one playtester update with the four values listed above.

Deployment and rollback

This pull request does not apply live organization settings. After merge, rerun and review both publisher plans, then obtain separate authorization before using either publisher's --apply mode.

To roll back after application, revert this change, review the resulting plans, and separately authorize applying them. That removes playtester from the pull-request, required-CI, and release-tag inventories and restores its custom properties to the reviewed replacement values.

[github-actions]

🎉 This PR is included in version 1.7.13 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀