From b1170ea8ca60390cd2449dd9bd2916b8a3b42632 Mon Sep 17 00:00:00 2001
From: RainbowBird <git@luoling.moe>
Date: Mon, 7 Sep 2026 00:18:00 +0800
Subject: [PATCH] docs(server): clarify adr delivery workflow

---
 server/AGENTS.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/server/AGENTS.md b/server/AGENTS.md
index 3f3cd1984..bce5e6e1d 100644
--- a/server/AGENTS.md
+++ b/server/AGENTS.md
@@ -13,6 +13,8 @@
 ## Architecture decisions
 
 - Put server ADRs in `../airi-docs/adr/`.
+- For an ADR task, write or update the ADR only. Do not stage, commit, push, or open a PR for ADR files.
+- The user owns ADR commits and pushes.
 - Create or update the ADR before you change a server boundary.
 - A server boundary includes an HTTP contract, provider contract, persistence model, or cross-module lifecycle.
 - Add a module dependency graph, an affected-file tree, and a sequence diagram to every implementation ADR.