dank/serverAppConfigs
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: pin cwd meaning in attribution footer

Browse Source 
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.
This commit is contained in:
Frank
2026-10-18 16:41:21 -07:00
parent d89ae23195
commit e030486ce6
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+1 -1
View File
@@ -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