Release beta 1.0.4 update settlement

docs/runbooks/production-deployment.md

@@ -73,7 +73,12 @@ The deployer prints an eight-stage progress bar and:
 - leaves legacy OCR disabled;
 - verifies Edge health and adaptive restart stability;
 - writes and verifies backup SHA-256 checksums;
-- rolls back files, state, and unit topology on failure.
+- rolls back files, state, and unit topology on cutover failure;
+- after rollback is disarmed, grants each existing account 200 Mora, records a
+  version-labelled movement, and sends the guarded group update announcement.
+
+The first bullet in the current `CHANGELOG.md` release section is the canonical
+one-sentence announcement summary. Keep it concise and user-facing.
 
 ## Post-Cutover
 
@@ -104,6 +109,28 @@ PY
 Player-visible acceptance must use deliberate synthetic messages in the
 configured group and confirm exactly one ACK and one final response.
 
+The deployer also runs the installed release settlement tool. Its successful
+JSON result must report the expected account count and announcement delivery.
+The operation is idempotent by the full release string, so rerunning the same
+command never grants Mora twice:
+
+```sh
+/opt/jwebot/venv/bin/python \
+  ~/.local/lib/wechat-health-watch/jwebot_release_update.py
+```
+
+If it reports `AnnouncementUncertainError`, inspect the configured group first.
+Only when the announcement is confirmed absent may the operator retry:
+
+```sh
+/opt/jwebot/venv/bin/python \
+  ~/.local/lib/wechat-health-watch/jwebot_release_update.py \
+  --retry-uncertain-announcement
+```
+
+Do not repeat the full deployment to repair an uncertain announcement. The
+runtime cutover and version-keyed compensation may already be complete.
+
 ## Rollback
 
 If any gate fails: