From e030486ce6d663a3170e6667526c2c5be7d4142b Mon Sep 17 00:00:00 2001
From: Frank <frank@dankware>
Date: Sun, 18 Oct 2026 16:41:21 -0700
Subject: [PATCH] docs: pin cwd meaning in attribution footer

Mirror of command-center clarification: first dogfooding round stamped the
build worktree instead of the session's own working directory. Rule text
now says which one, and to note the build worktree in the body.
---
 AGENTS.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/AGENTS.md b/AGENTS.md
index fe00228..a72b1bd 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -78,7 +78,7 @@ the same regime.
 cwd: <working directory> · session: <omp session id>
 ```
 
-Session id from `/status`. Machine-made artifacts stay attributable to the box and session that spawned them.
+Session id from `/status`; `cwd` is that session's own working directory — not the build checkout, when they differ (note the build worktree in the body instead). Machine-made artifacts stay attributable to the box and session that spawned them.
 
 ## Deployment