diff --git a/graph/procedures/gitea-issue-management-comment-before-closing-close-on-merge-29c1f2.md b/graph/procedures/gitea-issue-management-comment-before-closing-close-on-merge-29c1f2.md
new file mode 100644
index 00000000000..af169e1af8e
--- /dev/null
+++ b/graph/procedures/gitea-issue-management-comment-before-closing-close-on-merge-29c1f2.md
@@ -0,0 +1,36 @@
+---
+id: 29c1f2c9-d5f5-41f2-91cd-4a76fcb42d17
+type: procedure
+title: "Gitea issue management: comment before closing, close on merge to main"
+tags: [major-domo, gitea, workflow, git, issues]
+importance: 0.6
+confidence: 0.8
+created: "2026-02-20T16:50:31.798849+00:00"
+updated: "2026-02-20T16:50:31.798849+00:00"
+---
+
+# Gitea Issue Management Workflow
+
+## When to use
+When fixing issues on a feature or release branch that has NOT yet merged to `main`.
+
+## Steps
+
+1. **Add a comment to each issue** referencing the commit hash and branch:
+   > "Addressed in commit `f4be20a` on `next-release` branch. Will be closed when merged to main."
+
+2. **Keep issues OPEN** until the branch merges to main.
+   - Closing early creates confusion if the release is delayed or reverted.
+
+3. **Auto-close on merge** by using `closes #N` syntax in the PR description, or batch-close manually after merge.
+
+## API for commenting
+```bash
+curl -X POST https://git.manticorum.com/api/v1/repos/cal/major-domo-bot/issues/{number}/comments \
+  -H "Authorization: token $(cat /home/cal/.claude/secrets/gitea_token)" \
+  -H "Content-Type: application/json" \
+  -d '{"body": "Addressed in commit `abc1234` on `next-release`. Will close on merge to main."}'
+```
+
+## Gitea CLI alternative (tea)
+`tea` does not have a direct "add comment" command; use the API directly or the Gitea web UI.