diff --git a/backend/src/main/resources/content/processes/gitea-issues/overview.md b/backend/src/main/resources/content/processes/gitea-issues/overview.md
index 0e83d71..3659962 100644
--- a/backend/src/main/resources/content/processes/gitea-issues/overview.md
+++ b/backend/src/main/resources/content/processes/gitea-issues/overview.md
@@ -27,10 +27,16 @@ already exist (avoid duplicates).
   - **Frontend** fixes → **tristan** (QA). **Backend** fixes → **johannes** (tristan can't test backend).
   - `erin` has no Gitea account yet — assign only `tristan` until she does.
 
-## Closing — always manual
+## Closing — always manual (and it now notifies the reporter)
 **Never close an issue via the API.** Claude applies labels and comments only. The team closes
 issues in the Gitea UI after verification. Never PATCH `state: closed`.
 
+> **Closing an issue auto-notifies the reporter.** A Gitea webhook (`gitea-notify`, built by
+> dlx-claude 2026-07-01) sends the reporter a DIRECT message in their HiveIQ inbox when an issue is
+> closed — using the **Resolution** field from the issue template. **Fill in the Resolution before
+> closing** so the customer gets a meaningful message. (Reporter email is read from the issue body;
+> if they're not a HiveIQ user, the notification is silently skipped.)
+
 ## A fix isn't done until its issue is reconciled
 After deploying a fix: **comment the fix on the matching issue + apply `Verify Fix` + assign the
 verifier.** Never leave a deployed fix with a stale/untouched issue.