History

Strycher b7606de536 chore(#359 ): cut 1.2.0+61 (version bump + release notes) Marketing version 1.2.0 (Ben's call: minor bump for a storage-engine migration + nav overhaul, not a patch). versionCode 61 (next after 60, current on Play). - pubspec 1.1.2-rc.3+60 -> 1.2.0+61 - CHANGELOG [1.2.0] section - release-notes/1.2.0.md (GitHub release body) - play/1.2.0.txt (498/500 chars) - discord/1.2.0.md Release-gate passes (all four texts present, play within limit). No em-dashes in the new copy. Headlines: drift/SQLite storage migration (auto-migrates existing data), new nav shell, cross-client GIF links. First release cut end-to-end through the #312 pipeline. Part of Play epic #160. Agent: SapphireCompass (session 8d755b5e)		10 hours ago
..
1.1.2-rc.3.txt	feat(#342 ): author rc.3 release notes (GitHub / Play / Discord)	16 hours ago
1.2.0.txt	chore(#359 ): cut 1.2.0+61 (version bump + release notes)	10 hours ago
README.md	feat(#342 ): full-platform release automation + four-file notes gate	16 hours ago

README.md

Play Console "What's new"

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

Hard limit: 500 Unicode characters. The release gate (scripts/release-gate.sh) fails the build if this file is missing, empty, or over 500 chars — so the limit is caught here, not as a Console rejection at upload time.

Style

Plain language for end users. No issue numbers, no internal terms. Not promotional (Google's Metadata policy forbids "free", "#1", "best", etc. and ALL-CAPS except a brand name).

The owner pastes this into Play Console manually. CI validates the file; it never uploads. Play distribution is an external, human-triggered action.