diff --git a/docs/DEVELOPMENT.md b/docs/DEVELOPMENT.md
index e6ac54d..11c01bc 100644
--- a/docs/DEVELOPMENT.md
+++ b/docs/DEVELOPMENT.md
@@ -275,9 +275,21 @@ and `CHANGELOG.md`, matching the local `package-*` scripts.
 
 ### Cutting a release
 
-Bump `src/app/version.go`, then create and publish a release with a matching `v`
-tag on the forge (GitHub Releases / Codeberg releases). You can do that from the
-web UI or the CLI, e.g.:
+Before tagging:
+
+1. Bump `src/app/version.go`. The tag must match it exactly.
+2. Add the version's [CHANGELOG.md](CHANGELOG.md) section.
+3. Retake the README screenshots (`images/screenshot_jobs.PNG`,
+   `images/screenshot_settings.PNG`) if the GUI changed its appearance. This is
+   easy to forget because nothing fails without it: `README.md` is packaged
+   inside every release archive and is what the forge shows on the project page,
+   so a stale shot advertises an application that no longer exists. Take them
+   from a real build, not from a development run with test data.
+4. Run `scripts/test.bat` (or `go vet ./... && go test -race ./...`) and push
+   `main`, so the tag lands on a commit the forge actually has.
+
+Then create and publish a release with a matching `v` tag on the forge (GitHub
+Releases / Codeberg releases). You can do that from the web UI or the CLI, e.g.:
 
 ```bash
 git tag v0.11.5