History

Strycher 5fc41e9808 docs(#359 ): reframe Discord donation as community-requested, not solicited Owner's call: 'a few of you asked how to chip in, so I put up a page' reads as responsive/humble and implies traction, vs. asking for money. Community-request framing fits Discord (talking to the folks who asked); release-notes donation line stays broader-audience. Part of #160. Agent: SapphireCompass (session 8d755b5e)		10 hours ago
..
1.1.2-rc.3.md	feat(#342 ): author rc.3 release notes (GitHub / Play / Discord)	16 hours ago
1.2.0.md	docs(#359 ): reframe Discord donation as community-requested, not solicited	10 hours ago
README.md	feat(#342 ): full-platform release automation + four-file notes gate	16 hours ago

README.md

Discord announcement

One file per release: discord/<version>.md, e.g. discord/1.1.2-rc.4.md.

Style

Casual, paste-ready community announcement. What landed, in plain excited-but-honest terms, with the download link. Emoji fine. This is the message the owner posts to Discord.

The owner pastes this into Discord manually. CI validates the file exists and is non-empty; it never posts. Posting to a community is an external, human-triggered action.

The release gate (scripts/release-gate.sh) fails the build if this file is missing or empty for the version being tagged.