docs: keep the version and What’s New card in every release PR

AGENTS.md

@@ -56,6 +56,11 @@ requires the exact Expo SDK 57 documentation before writing mobile code.
   better. Describe actual benefits, not error lists, technical diagnostics, or
   internal maintenance. Use the existing dismissal mechanism so it appears once
   per version on each device after dismissal.
+- Treat the release version bump and matching What's New entry as one required
+  release deliverable. Before opening or marking a release PR ready, verify that
+  its final `develop` → `main` diff contains both. A preparation PR does not
+  replace including both changes in the release PR. State the version, card
+  highlights and verification in the release PR description every time.
 - PR descriptions explain the resulting behavior, list meaningful changes and
   validation, and disclose remaining limitations. Keep the PR scope aligned
   with the assigned chunk while retaining its commit history.

RELEASING.md

@@ -23,6 +23,11 @@ Production release flow. Keep it boring and repeatable.
    lists, technical diagnostics, or internal maintenance. Reuse the existing
    version-based dismissal so the card stays hidden after the user dismisses it.
    This owner instruction supersedes the earlier features-only policy in issue #97.
+   **Permanent owner requirement:** every release PR must contain both the app
+   version bump and the matching nonempty What's New entry in its final diff
+   against `main`, even when prepared through a separate PR into `develop`.
+   Before opening or marking it ready, verify both and explicitly list the
+   release version, user-facing highlights and card verification in its description.
 3. **Apply pending DB migrations to production** (see below) **before opening the
    release PR.**
 4. Open the release PR **develop → main**. It must pass the required

docs/WORK_LOG.md

@@ -7,6 +7,19 @@ claims as completed work.
 
 ## Current status
 
+### Permanent release/card requirement and 1.9.1 handoff
+
+- Owner reiterated that every release PR must contain both the version bump and
+  its matching one-time What's New card, and explicitly document both in that PR.
+  Strengthened AGENTS.md and RELEASING.md with final-diff verification; this applies
+  automatically to future releases without another reminder.
+- Release [#205](https://github.com/Coding-Moves/one-concept/pull/205) includes
+  version 1.9.1, its four highlights, and this durable rule. The existing dismissal
+  remains once per version; preview/card checks are recorded below. Main is not
+  merged and no production OTA is published by this work.
+- Documentation validation: referenced paths exist and whitespace checks passed.
+
+
 ### Requested 1.9.1 release and visible What's New verification
 
 - Owner requested another version/release PR after 1.9.0 merged but was not